We are longtime users of the Operations Management Suite and we have seen the transition from System Center Advisor to Operational Insights and then to OMS. We use the product in combination with System Center Operation Manager.
I wanted to give a heads up for people experiencing the problems we experienced with data collection to the cloud.
The issue we had
As mentioned, we’ve been using OMS for a long time and never experienced any big problems until apparently a new update came by. From one day to the other the data collection to the cloud failed.
The views in OMS got empty and furthermore the eventlog on OMS-managed servers filled up with errors like:
Log Name: Operations Manager
Source: HealthService
Date: 10/28/2015 7:57:02 AM
Event ID: 2127
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [servername.fqdn]
Description:
The health service HTTP module in management group “[ManagementGroupName]” failed to POST data to/from url (https://[guid].ods.opinsights.azure.com/EventDataService.svc/PostDataItems) with HTTP status code (403) and error message (). The module will retry again.
And
Log Name: Operations Manager
Source: HealthService
Date: 10/28/2015 8:25:07 AM
Event ID: 2115
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: [servername.fqdn]
Description:
A Bind Data Source in Management Group [ManagementGroupName] has posted items to the workflow, but has not received a response in 6900 seconds. This indicates a performance or functional problem with the workflow.
Workflow Id : Microsoft.SystemCenter.CollectDiagnosticsInformationToCloud
Instance : [servername.fqdn]
And
Log Name: Operations Manager
Source: HealthService
Date: 10/28/2015 10:32:42 AM
Event ID: 2137
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: [servername.fqdn]
Description:
The health service HTTP module could not parse the authentication certificate. Please re-configure Advisor via the OpsMgr console under the Advisor Connection node in the administration pane.
Error:
0x80FF0004
The Cause and the Solution
Apparently there has been an update to the OMS service causing the agents to be unable to connect to the online service. The solution was as simple as straightforward.
- Open up the SCOM console
- Click Administration
- Go to Administration > Operational Insights > Operational Insights Connection
- Then click ‘Re-configure Advisor’, enter the account to connect to OMS and complete the wizard.
There was no need to re-enter the password because as soon as I entered the accountname login occurred automatically.
After completing the wizard without making changes everything started working again.