共用方式為

Update to moving OperationsManager Database Steps

  • 發行項

It was discovered by some of my colleagues, that when they completed the steps to move the OperationsManager database from one SQL Server computer to another, several events are written to the Application Event Log.  An example of those events is:

Event Type:  Error
Event Source:  MSSQLSERVER
Event Category:  (2)
Event ID:  18054

Description:

Error 7779800008, severity 16, state 1 was raised, but no message with that error number was found in sys.messages.  If error is larger than 50000, make sure the user-defined message is added using sp_addmessage.

This event is generated because when we documented the steps to move the OperationsManager database from one SQL Server computer to another in the Operations Manager 2007 Backup and Recovery Guide, we were not aware of the fact that some specific configuration information is stored in the Master database. 

You see during Operations Manager setup, after the OperationsManager database is created, error messages specific to Operations Manager are not tied to the database, but are stored in the sys.messages Catalog View in the Master database. 

We are in the process of updating the Operations Manager 2007 Backup and Restore Guide accordingly.  In the meantime, if you are preparing to perform this operation, you will need to execute the attached snippet of code.  This snippet of code will ensure that Error Messages specific to the OperationsManagerDB are available on the new SQL Server.  Open the attached file in SQL Server 2005 Query Designer and execute against the Master database.

This posting is provided "AS IS" with no warranties, and confers no rights.

Fix_OpsMgrDB_ErrorMsgs.SQL.sql

Comments

  • Anonymous
    January 01, 2003
    PingBack from http://systemcenterforum.org/fix-update-to-steps-moving-the-operationsmanager-database/

  • Anonymous
    January 01, 2003
    Luis, I don't believe this is required any longer and the Operations Guide has the most up-to-date and accurate information.   If you find that is not the case, please let me know. Thanks, Matt

  • Anonymous
    June 02, 2009
    Is this procedure still necessary?

  • Anonymous
    June 19, 2009
    The comment has been removed

  • Anonymous
    December 23, 2009
    Hi Matt, I'm getting an error as shown below: Error 778263, severity 16, state 1 was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. U used your sql file and altered it so error 778263 is now also added. But i still don't know what kind of error this is. Can you help me?

  • Anonymous
    September 23, 2011
    The comment has been removed

  • Anonymous
    September 23, 2011
    The comment has been removed

  • Anonymous
    October 23, 2013
    Hi Matt We moved the infrastructure of the Service Manager DB (DW, transactional and Portal) and after this movement we present this issue. I'm wandering if the script works for Service Manager 2012.

  • Anonymous
    June 27, 2015
    can we get an updated version of this for 2012? also, sql error #777970008 is not included in this script.