The Discovery Wizard may stop responding during the discovery process in Microsoft System Center Operations Manager

Symptoms

When you run the Discovery Wizard in Microsoft System Center Operations Manager , the wizard may stop responding (hang). This behavior typically occurs in the "Discovery Progress" section of the wizard. Additionally, the following event may be logged in the Operations Manager log:


Cause

This issue may occur if Microsoft SQL Server Service Broker is not running on the management server.

Resolution

To resolve this issue, enable SQL Server Service Broker. To do this, follow these steps at a time when the Management Server services can be stopped:
  1. On the Management Server(s), open the Services.msc Microsoft Management Console (MMC) snap-in, for System Center Operations Manager 2007 stop the OpsMgr Health service, the OpsMgr SDK service, and the OpsMgr Config service. For System Center Operations Manager 2007 R2 and 2012 stop the System Center Management Configuration Service, the System Center Management Service, and the System Center Data Access Service
  2. Start Microsoft SQL Server Management Studio on the Operations Manager database server or on a computer that has the SQL Server tools installed and that can connect to the Operations Manager database server.
  3. Click New Query.
  4. In the navigation pane, expand Databases, and then click OperationsManager.
  5. In the details pane, type the following command, and then click Execute:
    SELECT is_broker_enabled FROM sys.databases WHERE name = 'OperationsManager'
  6. In the results that are displayed, verify the value that is displayed in the is_broker_enabled field. SQL Server Service Broker is disabled if this value is 0 (zero).
  7. In the details pane, type the following command, and then click Execute:
    ALTER DATABASE OperationsManager SET ENABLE_BROKER
    Check for successful completion of the TSQL command. SQL Server Service Broker is now enabled.
  8. On the Management Server(s), for System Center Operations Manager 2007 start the OpsMgr SDK service, the OpsMgr Health service, and the OpsMgr Config service. For System Center Operations Manager 2007 R2 and 2012 start the System Center Data Access Service, the System Center Management Service, and the System Center Management Configuration Service.
  9. Close all open windows and dialog boxes.
  10. Test the Discovery Wizard in System Center Operations Manager 2007.

More Information

System Center Operations Manager depends on SQL Server Service Broker to implement all task operations. If SQL Server Service Broker is disabled, all task operations will be affected. The resulting behavior may vary according to the task that has been initiated. Therefore, it is important to check the state of SQL Server Service Broker whenever unexpected behavior is observed around a task in System Center Operations Manager.
Propriedades

ID do Artigo: 941409 - Última Revisão: 25/04/2012 - Revisão: 1

Comentários