I have been working through the script errors reported from the machines in our environment recently.
Today's error tackled was this one:
Event Type: Error
Event Source: Microsoft Operations Manager
Event Category: None
Event ID: 9100
An error occurred on line 116 while executing script 'Microsoft Windows
Server Clusters State Monitoring'
Source: Microsoft VBScript runtime error
Description: Invalid procedure call or argument
After much Googling, I found a link on the microsoft.public.mom group provided by the ever-knowledgeable Anders Bergtsson to this discussion on the microsoft.public.mom.managementpack.sql group, providing the solution.
And the solution, in reality, is rather simple.
As per Cluster MP Design, the Scripts are configured to run only on the
Physical Nodes. But it looks like the rules are deployed even in the Cluster
Virtual Server due to a incorrect Computer Group -- Rule Group association.
Also note that this failure will have one of the physical node as the
"Computer" in the Script Error and won't indicate the Virtual Server name.I was investigating this issue with one of our customer and observed the
following.
Observations:
1. Microsoft Windows Server 2003 Server Clusters Virtual Servers Computer
Group had following rules associated with it.
-- Microsoft Windows Server Clusters [This is Invalid]
-- Performance2. Microsoft Windows 2000 Server Clusters Virtual Servers Computer Group had
following rules associated with it.
-- Microsoft Windows Server Clusters [This is Invalid]
-- Performance3. Microsoft Windows Server 2003 Server Clusters Computer Group had
following rules associated with it.
-- Microsoft Windows Server Clusters [This is Invalid]
-- Extended Availability and Health
-- State Monitoring and Service Discovery4. Microsoft Windows 2000 Server Clusters computer Group has had following
rules associated with it.
-- Microsoft Windows Server Clusters [This is Invalid]
-- Extended Availability and Health
-- State Monitoring and Service Discovery
All above associations marked as "Invalid" are incorrect. Once we removed
the rule group from the above computer groups the error disappeared.Please perform the following check.
1. Launch Admin Console.
2. Select the Cluster Virtual Server Machine and view properties
3. Go to the Rules TAB
o. If you find "Microsoft Windows Server Clusters" is listed, then that
is what causing the issue.
4. Go to the Computer Groups TAB
o. For each of the Computer Groups listed, check which one of them has
"Microsoft Windows Server Clusters" and remove them.
No comments:
Post a Comment