5 Replies Latest reply on Mar 14, 2013 4:55 AM by masterpetz

    Error applying LDMS 9 SP4

    Apprentice

      During LDMS 9 SP4 upgrade process have received this error:

       

      Incorrect function.

          CommonCore.inf: (0x00000001) coredbutil.exe /upgradedatabase,90000

       

      Attached is WindowsUpdate.log (SP4 install log)

       

      Any Ideas?

        • 1. Re: Error applying LDMS 9 SP4
          masterpetz ITSMMVPGroup

          From which version did you upgrade? In the readme it says you have to install SP3 first! Did you follow this guideline?

          If so, please post the coredbutil.exe.log because this one throws the error.

           

          Regards

          Christian

          • 2. Re: Error applying LDMS 9 SP4
            Apprentice

            Yes, prior applying SP4, SP3 was in place. But after reapplying SP4 again now it completes without errors....

            • 3. Re: Error applying LDMS 9 SP4
              masterpetz ITSMMVPGroup

              To be on the safe side, I would check the coredbutil.exe.log for errors...

              • 4. Re: Error applying LDMS 9 SP4
                Apprentice

                You are right. There are some previous errors from the erste SP4 installation:

                 

                 

                02/14/2013 17:56:45 ERROR 2196:1 DataServices : System.Data.OleDb.OleDbException: Could not create constraint. See previous errors.

                Column name 'MP_AC_Devices_Idn' does not exist in the target table or view.

                   at LANDesk.DataServices.Schema.CreateTables.CreateNewTable(Table table)

                   at LANDesk.DataServices.Schema.CreateTables.EnsureTable(Table table)

                 

                03/14/2013 10:32:09 ERROR 4492:1 DataServices : Database.Create error loading translations for language esn. Error System.Data.OleDb.OleDbException: Invalid column name 'esn'.

                   at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

                   at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()

                   at LANDesk.DataServices.OleDbHelper.LocalExecuteNonQuery(OleDbCommand cmd, Int32 retry)

                   at LANDesk.DataServices.OleDbHelper.ExecuteNonQuery(OleDbTransaction transaction, CommandType commandType, String commandText, Object[] commandParameters)

                   at LANDesk.DataServices.OleDbHelper.ExecuteNonQuery(String commandText, Object[] commandParameters)

                   at LANDesk.DataServices.Schema.CreateTranslations.PushAttribute(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateTranslations.Push(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.Create(XmlNode node)

                   at LANDesk.DataServices.Schema.Schema.LoadTranslations(IOleDbHelper oleDbHelper, String file, String language, String xmlFile)

                   at LANDesk.DataServices.Schema.Schema.CreateDatabase(IOleDbHelper oleDbHelper, XmlDocument document)

                 

                 

                03/14/2013 10:33:27 INFO  4492:1 RollingLog : Upgrade.Database: unexpected exception

                System.Data.OleDb.OleDbException: The statement has been terminated.

                The DELETE statement conflicted with the REFERENCE constraint "R_PUFFile_Idn". The conflict occurred in database "LDIKEBUKURU", table "dbo.SLM_ProductUsageFile", column 'FileInfo_Idn'.

                   at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

                   at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()

                   at LANDesk.ManagementSuite.Database.Database.ExecuteNonQueryP(String sql, Int32 timeoutSeconds, Object[] parameters)

                   at LANDesk.ManagementSuite.Database.Database.ExecuteNonQueryP(String sql, Object[] parameters)

                   at LANDesk.ManagementSuite.Upgrade.Database.Upgrade902To9021.ESIDOut_FileInfo(LanDeskDatabase database)

                   at LANDesk.ManagementSuite.Upgrade.Database.Upgrade902To9021.DoESIDOut(LanDeskDatabase database)

                   at LANDesk.ManagementSuite.Upgrade.Database.Upgrade902To9021.PostUpgrade(LanDeskDatabase database)

                   at LANDesk.ManagementSuite.Upgrade.Database.UpgradeSchema.Upgrade()

                   at LANDesk.ManagementSuite.Upgrade.Database.UpgradeSchema.UpgradeDatabaseSchema(String logPath)

                03/14/2013 10:33:27 ERROR 4492:1 CoreDBUtil : UpgradeDatabase failed: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.OleDb.OleDbException: The statement has been terminated.

                The DELETE statement conflicted with the REFERENCE constraint "R_PUFFile_Idn". The conflict occurred in database "LDIKEBUKURU", table "dbo.SLM_ProductUsageFile", column 'FileInfo_Idn'.

                   at LANDesk.ManagementSuite.Upgrade.Database.UpgradeSchema.UpgradeDatabaseSchema(String logPath)

                   at LANDesk.ManagementSuite.Upgrade.Database.UpgradeSchema.UpgradeDatabase(String connectionString, Boolean rollup, String logPath)

                   at LANDesk.ManagementSuite.Upgrade.Database.UpgradeSchema.UpgradeUnicodeDatabase(String legacyConnectionString, String unicodeConnectionString, String registryLinkName, Boolean rollup, String logPath, String legacyLanguage, String coreName)

                   --- End of inner exception stack trace ---

                   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

                   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)

                   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)

                   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

                   at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)

                   at LANDesk.ManagementSuite.CoreDbUtil.CoreDbUtil.UpgradeDatabase(DbConnection dbConn, String logPath, Boolean upgradeAsset, String legacyLanguage)

                03/14/2013 10:33:27 INFO  4492:1 RollingLog : CoreDBUtil returned the following exit code: 1

                 

                 

                And many more from the previous run of Coredbutil for SP4 installation.

                 

                 

                But during the second SP4 attempt to upgrade, there are only just a few errors:

                 

                03/14/2013 11:05:58 ERROR 2952:1 DataServices : Database.Create error loading translations for language esn. Error System.Data.OleDb.OleDbException: Invalid column name 'esn'.

                   at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

                   at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()

                   at LANDesk.DataServices.OleDbHelper.LocalExecuteNonQuery(OleDbCommand cmd, Int32 retry)

                   at LANDesk.DataServices.OleDbHelper.ExecuteNonQuery(OleDbTransaction transaction, CommandType commandType, String commandText, Object[] commandParameters)

                   at LANDesk.DataServices.OleDbHelper.ExecuteNonQuery(String commandText, Object[] commandParameters)

                   at LANDesk.DataServices.Schema.CreateTranslations.PushAttribute(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateTranslations.Push(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.Create(XmlNode node)

                   at LANDesk.DataServices.Schema.Schema.LoadTranslations(IOleDbHelper oleDbHelper, String file, String language, String xmlFile)

                   at LANDesk.DataServices.Schema.Schema.CreateDatabase(IOleDbHelper oleDbHelper, XmlDocument document)

                 

                 

                03/14/2013 11:07:07 ERROR 2952:1 DataServices : Database.Create error loading translations for language esn. Error System.Data.OleDb.OleDbException: Invalid column name 'esn'.

                   at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

                   at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()

                   at LANDesk.DataServices.OleDbHelper.LocalExecuteNonQuery(OleDbCommand cmd, Int32 retry)

                   at LANDesk.DataServices.OleDbHelper.ExecuteNonQuery(OleDbTransaction transaction, CommandType commandType, String commandText, Object[] commandParameters)

                   at LANDesk.DataServices.OleDbHelper.ExecuteNonQuery(String commandText, Object[] commandParameters)

                   at LANDesk.DataServices.Schema.CreateTranslations.PushAttribute(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateTranslations.Push(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.Create(XmlNode node)

                   at LANDesk.DataServices.Schema.Schema.LoadTranslations(IOleDbHelper oleDbHelper, String file, String language, String xmlFile)

                   at LANDesk.DataServices.Schema.Schema.CreateDatabase(IOleDbHelper oleDbHelper, XmlDocument document)

                 

                 

                03/14/2013 11:08:25 ERROR 3948:1 DataServices : Database.Create error loading translations for language esn. Error System.Data.OleDb.OleDbException: Invalid column name 'esn'.

                   at System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior behavior, String method)

                   at System.Data.OleDb.OleDbCommand.ExecuteNonQuery()

                   at LANDesk.DataServices.OleDbHelper.LocalExecuteNonQuery(OleDbCommand cmd, Int32 retry)

                   at LANDesk.DataServices.OleDbHelper.ExecuteNonQuery(OleDbTransaction transaction, CommandType commandType, String commandText, Object[] commandParameters)

                   at LANDesk.DataServices.OleDbHelper.ExecuteNonQuery(String commandText, Object[] commandParameters)

                   at LANDesk.DataServices.Schema.CreateTranslations.PushAttribute(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateTranslations.Push(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.CreateEx(XmlNode node)

                   at LANDesk.DataServices.Schema.CreateBase.Create(XmlNode node)

                   at LANDesk.DataServices.Schema.Schema.LoadTranslations(IOleDbHelper oleDbHelper, String file, String language, String xmlFile)

                   at LANDesk.DataServices.Schema.Schema.CreateDatabase(IOleDbHelper oleDbHelper, XmlDocument document)

                 

                 

                The second coredbutil run exits without noting any errors...

                 

                03/14/2013 11:10:16 INFO  3976:1 RollingLog : CoreDBUtil returned the following exit code: 0

                 

                Weird....

                • 5. Re: Error applying LDMS 9 SP4
                  masterpetz ITSMMVPGroup

                  Okay, I think the "esn" thing was something from the old versions of "Managed Planets" and can be ignored. The constrain errors in you first installation try could point to a runtime problem that the tables needed for the constrain were not there at the time the constrain should be created. In the second run, the tables were there from the first run and the constrain could be build without a problem. So it seems that with the exit code 0 everything seems to be fine now.

                  1 of 1 people found this helpful