KNOWN ISSUE: Unable to add large packages to the Software Library in Software Management 7.0

Products

• Software Management Solution

Issue/Introduction

Unable to add large packages to the Software Library in Software Management 7.0. When selecting the Software Library when creating a package, and adding the source files, after it calculates the file hashes and hangs for a time, it displays the message:

"Failed to create the package. Check the server logs for more information."

The following sequence of errors are found in the logs:

Process: w3wp (3108)
Thread ID: 1
Module: w3wp.exe
Source: Altiris.NS.ResourceManagement.Database.ResourceDatabaseContext.Dispose
Description: Failed to remove Resource Change Transaction Marker.
( Exception Details: System.InvalidOperationException: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.

Process: w3wp (3108)
Thread ID: 1
Module: w3wp.exe
Source: Altiris.NS.ContextManagement.AdminDatabaseContext.LogWarning
Description: Transaction being rolled back automatically during dispose. To disable this warning rollback your transaction explicitly! Dispose location:    at Altiris.Database.DatabaseContext`1.Dispose(Boolean disposing)

Process: w3wp (3108)
Thread ID: 1
Module: w3wp.exe
Source: Altiris.NS.ContextManagement.AdminDatabaseContext.LogError
Description: Automatic rollback during expose threw unexpected exception. Exception: System.InvalidOperationException: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.

Process: w3wp (3108)
Thread ID: 1
Module: w3wp.exe
Source: Altiris.NS.ResourceManagement.Resource.SavePartitionedResource
Description: An unexpected exception has occured (Item: e14e148b-d998-4de3-b539-9cdae08f325f)
( Exception Details: System.InvalidOperationException: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.

Process: w3wp (3108)
Thread ID: 1
Module: w3wp.exe
Source: Altiris.SoftwareManagement.PackageRepository.PackageRepositoryManager.ProcessManifest
Description: Failed to process package manifest: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.

Process: w3wp (3108)
Thread ID: 1
Module: w3wp.exe
Source: Altiris.SoftwareManagement.Web.PackageRepository.AddPackageManifest
Description: The thread was aborted while adding the package manifest.

Process: w3wp (3108)
Thread ID: 1
Module: w3wp.exe
Source: global.asax
Description: Unhandled exception.  Type=System.InvalidOperationException Msg=ExecuteReader requires an open and available Connection. The connection's current state is closed.

Cause

It appears that the number of files within the package, or the total size of the package, can cause this issue.

Resolution

This issue will be fixed in the SP4 release of the Symantec Management Platform. Below is some work-around information that can work around the issue.

The timeout is usually caused by the timeout value set in the Software Library Configuration.

In the Symantec Management Console, browse under Settings > All Settings > Software > Software Catalog and Software Library Settings. There is a Timeout value specified here. Try doubling it, or adding time until you find the right combination. The change made in the Web.Config needs to be the same or longer than the value set here so http timeouts also don't affect it. See below for an example of how to edit the http timeout:

Increase Runtime timeout - On your server, at the installation path for Notification Server, go to \Program Files\Altiris\SoftwareManagement\Web\. Open up the file Web.config in a true text editor (such as www.crimsoneditor.com). Search for the value httpRuntime. The line should read:

<httpRuntime maxRequestLength="2000000" />

Edit the line to read:

<httpRuntime executionTimeout="1200" maxRequestLength="2000000" />

Save the file when complete, and restart the Altiris Service and IIS.

If you use another package method besides the Software Library, such as UNC or Local directory on the NS, the timeout does not occur.

Applies To
Notification Server 7.0
Software Management 7.0