As per the advice of my friend Daniel I proceeded to build a laboratory where SCOM MP patch and try first to bring into production.

As the buggy version of QFE KB957123 has, in fact, destroyed my RMS virtual machine I restored the backup I had created and on the DB (and OperationManager OperationManagerDW).

To its restart I found the following error:

The SQL Server Service Broker for the database is current OpsMgr

not enabled

The problem is easily resolved because the SQL Server Service Broker is a feature of SQL Server that enables the exchange of messages in a transactional (such as transactional MSMQ queues) with simple extensions of SQL Server is DML.

I perfected the procedure found here for environments with multiple management servers like mine.

1. RMS put it to sleep services HEALTHSERVICE OpsMgr, Config, SDK
2. The other MS put in stop service HEALTHSERVICE
3. With SQL Server Management Studio, open a query window and run the database OperationManager sequence queries:

  SINGLE_USER WITH ROLLBACK IMMEDIATE ALTER DATABASE WITH ROLLBACK IMMEDIATE OperationsManager September SINGLE_USER 

  ENABLE_BROKER ALTER DATABASE OperationsManager September ENABLE_BROKER 

  MULTI_USER ALTER DATABASE OperationsManager September MULTI_USER 

Throughout the execution of these queries does not require a few seconds. If it lasts longer is certainly someone who is using the database and does not allow the alteration of its parameters.

Reactivated the services listed above and you will stop after a while, a nice green dot will appear next to your RMS.

Tweet This Post Delicious Facebook