UPDATE: This problem seems to be fixes in the latest update!
The MSMQ Management Pack seems to have a few problems with it’s discovery script that can lead to the following error showing up in the logs:
The process started at 13:34:40 failed to create System.Discovery.Data. Errors found in output:
C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 49\9788\DiscoverQueues.vbs(107, 4) Microsoft VBScript runtime error: Subscript out of range: '[number: 0]'
Command executed: "C:\WINDOWS\system32\cscript.exe" /nologo "DiscoverQueues.vbs" {615D37C9-477D-62E2-0833-6ECBF0E89A87} {A176AC83-CC31-01C3-5DE9-E2DFF64E7CC7} "MASKED.server.fqdn" "MSMQ" "true" "true" "False" "false"
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 49\9788\
One or more workflows were affected by this.
Workflow name: Microsoft.MSMQ.2003.DiscoverQueues
Instance name: MASKED.server.fqdn
Instance ID: {A176AC83-CC31-01C3-5DE9-E2DFF64E7CC7}
Management group: MASKED
This seems to be related to the discovery of public queues on some servers that has none. One quick fix, or rather work-around, is to override the discovery on these servers to set DiscoverPublic to False.
