When I run the "Discover the Windows Server 2008 R2 Cluster Components" task on two nodes of a specific cluster, it fails with the following output:
"Data was found in the output, but has been dropped because the Event Policy for the process started at 3:54:44 PM has detected errors.The 'ExitCode' policy expression:
[^0]+
matched the following output:
-1
Command executed: "C:\Windows\system32\cscript.exe" /nologo "DiscoverClustering.vbs" {2befc419-be49-00dd-d277-b8c0f1cd0dd5} {6e300fbc-ddfb-da7b-4dae-337c34fba109} ALN507.contoso.org ALN507 false {da9bf4d4-17da-0343-2906-d711a7689d8e} {bcea54d6-aab8-2556-1fc1-f1d2469cd64f} {a0d8689d-5653-09f6-3305-45373fa9fb45} {064ec4fd-25a1-38d2-c18d-a53fd57393df} true false 300 true
Working Directory: C:\Program Files\System Center Operations Manager\Agent\Health Service State\Monitoring Host Temporary Files 5663\3\
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.2008.R2.Cluster.RunDiscovery
Instance name: Cluster Service
Instance ID: {6E300FBC-DDFB-DA7B-4DAE-337C34FBA109}
Management group: TUR12
Error Code: -2130771918 (Unknown error (0x80ff0032))."
When I run the script manually with the parameters passed above, it's immediately obvious that there are too many parameters being passed to the script. If I run it with the following parameters, it runs fine:
c:\temp>cscript /nologo Microsoft.Windows.Server.2008.Discovery.Probe.vbs {2befc419-be49-00dd-d277-b8c0f1cd0dd5} {6e300fbc-ddfb-da7b-4dae-337c34fba109} ALN507.contoso.org ALN507 6.1
Why is the discovery task passing the wrong parameters, and how can I correct it? I haven't had any trouble using that task to discover other cluster resources, so I'm not sure why it's failing for this cluster.