Hi,
We have a new SCOM 2012 install with 2 servers, plus a dedicated DB server.
There are 5 nodes now reporting to it and all are healthy, but there are repeating script errors from the 2 SCOM servers and similar on the DB server. The errors logged are 6028 and 21405.
21405:
The process started at 8:24:03 AM failed to create System.Discovery.Data, no errors detected in the output. The process exited with 1 Command executed: "C:\Windows\system32\cscript.exe" /nologo "DiscoverHealthServiceCommunicationRelationships.js" 0 {3237253B-2A1C-38E7-8E52-588635224D35} {719C5DC4-6418-D15F-E009-2CF12E293AAF} SCOM-02.dev.local "DEVSCOM" Working Directory: C:\Program Files\System Center 2012\Operations Manager\Server\Health Service State\Monitoring Host Temporary Files 579\2314\ One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DiscoveryHealthServiceCommunication Instance name: SCOM-02.dev.local Instance ID: {719C5DC4-6418-D15F-E009-2CF12E293AAF} Management group: DEVSCOM
6028:
DiscoverHealthServiceCommunicationRelationships.js : HealthServiceCommuncation relationship discovery for HealthServices configured via AD Integration Could not find "HKLM\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Agent Management Groups\DEVSCOM\AD Cache\Primary SCP Info\Service DNS Name" The HealthService needs at least a primary management server to communicate. This may indicate that the following: * HealthService has not queried and cached the AD SCPs yet * HealthService doesn't have access to any SCPs, yet is configured for AD Integration Match results: undefined
I have checked the registry and the key named does not exist. AD Integration is otherwise working though and a new agent can successfully configure via ADI and add to monitoring.
I have checked SCPs, re-ran AD tools (MOMADAdmin, OOMADs), checked user permissions, computer account AD security...but cant find anything that makes a difference.
Is there anything I can do to reset ADI on the SCOM servers, or is that not relevant to 21405?
Thanks.