KNOWN ISSUE: Unable to process event message due to System.Data.SqlClient.SqlException: There is already an object named '#PackageInfo' in the database

Article:TECH202799  |  Created: 2013-02-14  |  Updated: 2015-02-19  |  Article URL
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Package Server status events are failing to process on the SMP server.  Errors appear in the a.log as indicated below referencing #CodebaseInfo or #PackageInfo objects already existing in the database.



Process: AeXSvc (1400)
Thread ID: 913
Module: AeXSVC.exe
Source: Altiris.NS.StandardItems.PackageServer.PkgSvrEventPolicy.OnClientMessage
Description: Unable to process the event message from resource 3333c474-3333-3333-8419-22c4f4fc3333.
**CEDUrlStart** :**CEDUrlEnd**

( Exception Details: System.Data.SqlClient.SqlException: There is already an object named '#PackageInfo' in the database.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Altiris.NS.ResourceManagement.Database.BatchSqlClientConnection.ExecuteSQLNoResults(String query, Int32& rowsAffected)
   at Altiris.NS.ResourceManagement.Database.BatchSqlClientConnection.ExecuteSQLNoResults(String query)
   at Altiris.NS.StandardItems.PackageServer.PkgSvrEventPolicy.ProcessSummaryNSE(Guid packageServerGuid, XmlElement pkgSvrStatusEventElement, Boolean complete, DateTime messageCreatedDate)
   at Altiris.NS.StandardItems.PackageServer.PkgSvrEventPolicy.OnClientMessage(ClientMessage message) )
( Exception logged from:
   at Altiris.Diagnostics.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception)
   at Altiris.NS.Logging.EventLog.ReportException(Int32 severity, String strMessage, String category, Exception exception)
   at Altiris.NS.StandardItems.PackageServer.PkgSvrEventPolicy.OnClientMessage(ClientMessage message)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.Dispatch(String message, Boolean useFilename)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.PerformDispatch(DispatchSlot slot)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.DispatchSingleNSE(DispatchSlot slot)
   at Altiris.NS.ClientMessaging.EventQueueDispatcher.WorkerLoop(Object deliverySlot)
   at System.Threading.ThreadHelper.ThreadStart(Object obj)
( Extra Details:  Type=System.Data.SqlClient.SqlException Src=.Net SqlClient Data Provider )


Errors in the log also could mention "System.Data.SqlClient.SqlException: There is already an object named '#CodebaseInfo' in the database."




Symantec Management Platform 7.1 SP2



The issue is related to processing multiple package status events simultaneously from package servers.  These are the events sent back to the SMP by package servers to indicate which packages are available to download from their local repositories.  During the processing of package status events on the SMP, temporary tables #CodebaseInfo and #PackageInfo are utilized and dropped once the event has been processed.



A permanent fix has been provided in 7.1 SP2 MP1 V5. (See HOWTO81832) (HOWTO81832).

Any efforts taken to minimize the likelihood of package status events getting processed at the same time will reduce the possibility of seeing these errors.  For example, if client configuration updates for site servers are set aggressively for 15 minute update intervals and new batch of packages are created on the SMP (such as staging a new set of Patch Management bulletins) it is very likely that all package servers will be downloading these packages at the same time and therefore reporting package status events at the same time.  By increasing the configuration update interval for site servers, you can minimize the likelihood of package status events arriving at the SMP server at the same time for processing.


Supplemental Materials


Article URL

Terms of use for this information are found in Legal Notices