We have recently upgraded from SCOM 2007 to SCOM 2012. We are not getting a great deal of “Operations Manager Failed to start a process”. The process varies including:
DiscoverSQL2008ASDiscovery.vbs
DiscoverSQL2008DBEngineDiscovery.vbs
DiscoverSQL2008ASDiscovery.vbs
Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs
I have researched and researched. I know that you can try to run the scripts locally on the machine but it seems the scripts never make it to the machine. I go to the path in the error, no luck. I look in the other folders as I know that SCOM moves the scripts, and I even search the entire C drive but the scripts are not getting to the server. The folder is not even making it. For example:
Command executed: "C:\Windows\system32\cscript.exe" /nologo "Microsoft.Windows.Server.NetwokAdapter.BandwidthUsed.ModuleType.vbs" SERVER true Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 11606\1759\
The script is not there and the folder \1759 is not there either.
I have removed and reinstalled the client.
Antivirus is fine, up to date and not blocking on any of the machines.
I have stopped the “System Center Management service” and renamed the “Health Service State” folder and it recreates fine but not long after I get the warning in SCOM about “Operations Manager Failed to start a process”.
I look in event viewer for Operations Manager on this particular one and I see a lot of:
Performance data from the Health Service could not be collected since required registry keys could not be read, the error was 2L (The system cannot find the file specified.). Event ID 6001.
I tried the fix of"lodctr MOMConnectorCounters.ini" and "lodctr HealthServiceCounters.ini" but I get “error encountered while updating text in registry. Status: 0”. Again I am using SCOM 2012.
Do I need to look at each failed script or is there a overall issue because the scripts are not making it to the machines. Any ideas?