Q205017: A problem occurred while resolving the security digests into the database.

Symptoms

---Problem---

(s0m0): A problem occurred while resolving the security digests into the database.


Please report this issue immediately to support.

Note that you may not be able to receive additional security bulletins until this issue is resolved.

---System exception---

Could not find stored procedure 'PackageVersionGetCurrent'.

---Source---

.Net SqlClient Data Provider

---Stack trace---

System.Data.SqlClient.SqlException: Could not find stored procedure 'PackageVersionGetCurrent'.
 at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
 at System.Data.SqlClient.SqlInternalConnection.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.SqlDataReader.ConsumeMetaData()
 at System.Data.SqlClient.SqlDataReader.get_MetaData()
 at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
 at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
 at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
 at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
 at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
 at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
 at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()
 at ManageSoft.Database.DatabaseCommand.ExecuteReader(IDatabaseLayer m_DataLayer)
 at ManageSoft.Database.Impl.DatabaseLayerBaseSql.GetResult(IDatabaseObjectFactory p_ObjectFactory, CommandType p_CommandType, String p_CommandText, DatabaseParameter[] p_Parameters)
 at ManageSoft.Database.Impl.DatabaseLayerBase.GetResult(String p_StoredProcedure, DatabaseParameter[] p_Parameters)
 at ManageSoft.SecurityPatch.Database.API.DataLayer.PackageVersionGetCurrent(String p_PackageFullName)
 at ManageSoft.Packaging.SecurityPatch.Import.Errata.WindowsErrata.Package()
 at ManageSoft.Packaging.SecurityPatch.Import.SPM.UpdateErrata(String[] errataNames)
 at ManageSoft.PatchManager.ScopePane.SyncAllProgressDialog.DoOperation(IProgressCallback p_Progress)

 

Cause

This usually appears because the database scripts for SPM haven't been executed or didn't complete, this is common if the database is on a separate server.

 

To resolve this:
  1. Search the knowledge base for the article with the upgrade scripts for your current Security Manager version.
    Please contact your support representative if the migration scripts for your version should not be available from the knowledge base.
  2. Download the attachment: "public_sm<current SM version>_dbmig.zip"
  3. Extract the files to the server
  4. Open a command prompt
  5. Change the directory to the folder you extracted the files to e.g. if you extracted them to C:\SPM then the command will be cd C:\SPM
  6. Type: mgsDatabaseUpdate -i SecurityManagerMigration.xml -nsu
  7. Once it's compete check you SPM installation (it may need repairing in Programs and Features).

 

Additional Information

The missing stored procedure could also be "SecurityBulletinGetAlerts"

Support Admin -

Comments

Powered by Zendesk