Troubleshooting

  • Article

Applies To: Operations Manager 2007

You can use the following tips for troubleshooting issues with System Center Service Manager 2010 Management Pack.

Unable to Detect Failures of the Health Service

If both Service Manager 2010 and an Operations Manager 2007 R2 agent are running on the same server, they are sharing the Health service. Therefore, if the Health service is experiencing issues, these issues might affect both applications.

This might cause problems with the Service Manager Health service to be detected as issues with the Operations Manager Health service. When investigating issues with the Operations Manager agent on servers where Service Manager is also present, keep in mind that the issue might be caused by Service Manager.

Discovery Fails to Run

If the Diagram view is not displaying any discovered objects, but the Windows Computers view displays a Service Manager instance, then it is probably because Agent proxy is not enabled. In addition, there is an alert indicating that Agent proxy is not enabled. In this case, enable Agent proxy.

If discovery does not run, check the event log on the Service Manager management server. It might contain an error message where Source is Health Service Modules, EventID is 11852, and the Details string is:

‘OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied’

This typically indicates that the Run As account for the Service Manager management pack is misconfigured or has insufficient privileges to access the database. Ensure that the Run As account has read access to the database. For information about adding a Run As account to the Service Manager Database Account profile, see Security Considerations.

Otherwise, if discovery does not seem to be running on its scheduled time, you can use the following steps:

  1. Clear the Health service management pack cache on the Service Manager management server.

  2. After you have cleared the cache, remove the Service Manager Management Pack from Operations Manager, and then re-import it.

  3. Override the discovery time.