The Windows Event Log Provider is still unable to open the UCS Management Service event log on computer 'PROD-SCOM01.OLH.LOCAL'. The Provider has been unable to open the UCS Management Service event log for 720 seconds.

Most recent error details: Access is denied.

 

One or more workflows were affected by this. 

Workflow name: Cisco.Ucsm.4f3a6bb8525c472bb6fd850f5d6ecb02.Close.MiscellaneousFaults.Rule

Instance name: PROD-SCOM03.OLH.LOCAL

Instance ID: {0C0F66E5-1083-BED0-C927-F9907483C856}

Management group: OnLife Management Group

I'm getting this error in my operations manager log. I moved the UCS management service from SCOM01 to SCOM03. Along with a few other monitors and the RMS role. This allowed my SCOM01 and SCOM02 servers to just handle the servers agents. I uninstalled the UCS service and deleted the management packs completely however even on SCOM03 there is something pointing to SCOM01 and I dont know how to stop it from trying to point to something that isnt there anymore.

Anyone seen this before?

Matt

 

• Edited by Matt Novitsch Tuesday, July 07, 2015 7:23 PM added more detail

I figured it out a long with my other issue. I had <Category Name="Cmdb"> and <Category Name="ConfigStore"> configured to an old SQL server setting in ConfigService.config. I plugged in the current one and its playing catch up right now.

Location: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\ConfigService.config

I'll post back this afternoon to provide an update.

I figured it out a long with my other issue. I had <Category Name="Cmdb"> and <Category Name="ConfigStore"> configured to an old SQL server setting in ConfigService.config. I plugged in the current one and its playing catch up right now.

Location: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\ConfigService.config

I'll post back this afternoon to provide an update.

• Marked as answer by Matt Novitsch 18 hours 52 minutes ago

I figured it out a long with my other issue. I had <Category Name="Cmdb"> and <Category Name="ConfigStore"> configured to an old SQL server setting in ConfigService.config. I plugged in the current one and its playing catch up right now.

Location: C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\ConfigService.config

I'll post back this afternoon to provide an update.

• Marked as answer by Matt Novitsch Monday, July 13, 2015 12:18 PM

Fixing the configuration fixed the issue.

Hi Matt,

Thanks for your sharing.

Best Regards,

Elton Ji