Hi all,
I hope someone here can help me, because I'm pretty much stuck...
My domain has 9 computers in it. Out of these, two are DCs (one holds all the roles), two are database computers in a cluster, two are web front-ends in an NLB, and one is the backup/SCOM server (yes, it runs SCOM:) ). A couple of months back we had some problems with one of the servers and its AD connectivity. Since I couldn't figure out what was wrong I reinstallerd it, patched it to the lates patch level, then reinstalled the other one making it an exact duplicate. Now, a couple of weeks later the SAME computer is having problems while the other seems fine. What are the odds of that happing?
I, personally, thinks it's probably our sharepoint application doing it, but our developer swears they're identical in every way. The server, an HP box, doesn't show any errors in diagnostics and I even tried dissolving the network teamed adapters and then binding them back to see if that helped - guess how that went ;)
Now, the errors I'm getting from the SCOM monitoring are:
* Script or executable failed to run:
The process started at 10:16:27 failed to create System.Discovery.Data, no errors detected in the output. The process exited with 128
Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "GetServerName.vbs" {EBD515FB-2C1B-46EA-DBC9-0C23AC91A654} {FC956DBF-9B7D-B5E9-52C2-09218C08A600} osldpfront01.xxx.local
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 13\1113\
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.SharePoint.Services.3.0.WSS.Server.Discovery
Instance name: osldpfront01.xxx.local
Instance ID: {FC956DBF-9B7D-B5E9-52C2-09218C08A600}
Management group: xxx
oh, well - there are 12 different ones with Script or Executable failed to run, so I won't include them all unless someone's interested.
* The PDC Emulator cannot be contacted
Client PDC Response : While running 'Client PDC Response' 3 consecutive errors were encountered.
A message will be generated when the script succeeds. Look for a 'success' event from 'Client PDC Response' with ID = 1004.
The events that triggered this alert were:
Failed to bind to PDC Op Master 'osldpad01' (10.47.2.10).
Failed to bind to PDC Op Master 'osldpad01' (10.47.2.10).
Failed to bind to PDC Op Master 'osldpad01' (10.47.2.10).
(This one has repeated 7 times in 17 hours)
* AD Client side - Script Based Test Failed to Complete
AD Client GC Availability : The script 'AD Client GC Availability' encountered an error while executing the query '<LDAP://OSLDPAD01.xxx.local/CN=Sites,CN=Configuration,DC=xxx,DC=local>;(&(objectCategory=nTDSDSA)(options:1.2.840.113556.1.4.803:=1));adspath,cn;subtree'.
The error returned was: 'Table does not exist.' (0x80040E37)
(112 in 18 hours)
* AD Client side - Script Based Test Failed to Complete
AD Client Connectivity : The script 'AD Client Connectivity' failed while getting 'LDAP://OSLDPAD01.necohosting.local/RootDSE.The error returned was: 'LDAP://OSLDPAD01.necohosting.local/RootDSE' (0x8007203A)
(244 in 18 hours)
Any of you gurus able to give me any hints on how to kill this gremlin? I tried keeping away from water after midnight and all... :p
Cheers!