Remove From My Forums

Cluster 2008 MP

Question
0

Sign in to vote

Hi there.

At a customerssite (totally W2K08 SP2 based) there are also Windows Clusters. The Cluster MP has been imported and runs. However, the clusternodes are discovered properly (Proxy has been enabled) but the Cluster Resource ends up being unmonitored.

On the active Clusternode the OpsMgr eventlog logs this event every hour: EventID:7001 Source:HealthService Script. Description: DiscoverClustering.vbs: Accessing property on invalid WMI object.

We have located the script and when we run it from an elevated cmd-prompt we get the same error message. Does any one have experienced this issue before?

Best regards, Marnix Wolf

(Thoughts on OpsMgr)

Friday, August 7, 2009 7:10 AM

Answers

0

Sign in to vote
Is this Windows Server 2008 R2 by any chance? There will be an update to the MP to support R2 coming out (the cluster MP does not support it currently).
The Exchange MP is cluster-aware so it does its own monitoring of the Exchange-specific resources in the cluster. The Cluster MP adds general resource monitoring.

The cluster virtual server itself being not monitored by itself is not necessarily bad, it just means that there are no monitors targeted to it (somewhat confusing). Note that the cluster MP focuses on the physical nodes only (as well as resources and resource groups), it does not discover or monitor the virtual server.
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
- Marked as answer by Marnix WolfMVP Tuesday, August 11, 2009 6:05 PM
Monday, August 10, 2009 4:43 PM

All replies

Hi Marnix

Which view are you looking at? In monitoring, Resource Group State? What cluster resources are listed? Are any groups monitored? Do you have any 3rd party clustered applications?

Note this from the MP guide  - the overrides listed in the following table are enabled by default.

Monitor Name	Override Name	Target	Purpose
Resource Group Monitor	Override For Cluster Groups Rollup State Monitor	Windows 2008 Available Storage Cluster Resource Group	Disables monitoring for Available Storage Resource Group (these are disks in the cluster that are not used by any clustered application).
Resource Group State Monitor	Override For Hosted Cluster Group State Monitor	Windows 2008 Available Storage Cluster Resource Group	Disables monitoring for Available Storage Resource Group (these are disks in the cluster that are not used by any clustered application).
Networking Connections Service Status	Override For NetMan Service Check Monitor	Windows Server 2008 Computers	This service does not need to be monitored on Windows Server 2008 clusters, so the monitor is disabled by default.

Or are you looking at administration, agentless managed?

If it is SQL or Exchange resources that aren't monitored then have you got the SQL and Exchange MPs installed?

Good Luck ;-)

Graham

View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Friday, August 7, 2009 9:00 AM

0

Sign in to vote

Hi Graham.

I am looking at Administration > Clusters > ClusterState. I will check later when the Exchange MP has been configured.

Thanks so much for your effort. Now I see the difference between a three star general and a two star captain. :)
Best regards, Marnix Wolf

(Thoughts on OpsMgr)

Friday, August 7, 2009 9:20 AM
0

Sign in to vote

Hi Graham.

I know about the monitors which are disabled by default. It is the discovery of the Cluster which doesn't run. It states this error:
Log Name:      Operations Manager
Source:        Health Service Script
Date:          10-8-2009 xxxxxxx
Event ID:      7001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxxx
Description:
DiscoverClustering.vbs : Accessing property on invalid WMI object.

and then right afterwards:

Log Name:      Operations Manager
Source:        Health Service Modules
Date:          10-8-2009 xxxxxxxx
Event ID:      21405
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      xxxxxxx
Description:
The process started at 12:32:46 failed to create System.Discovery.Data, no errors detected in the output. The process exited with 4294967295

Command executed: "C:\Windows\system32\cscript.exe" /nologo "DiscoverClustering.vbs" {17520AAB-F22A-EB73-4E91-59A089AA68DC} {EB8F5957-A7D5-D28B-D2D6-A311163AEBEF} xxxxxxxx false {DA9BF4D4-17DA-0343-2906-D711A7689D8E} {C04320C1-6899-8B10-FD6F-E785A0DD0625} {A0D8689D-5653-09F6-3305-45373FA9FB45} {064EC4FD-25A1-38D2-C18D-A53FD57393DF} true
Working Directory: C:\Program Files\System Center Operations Manager 2007\Health Service State\Monitoring Host Temporary Files 4\2222\

One or more workflows were affected by this.

Workflow name: Microsoft.Windows.2008.Cluster.Monitoring.Discovery
Instance name: Cluster Service
Instance ID: {EB8F5957-A7D5-D28B-D2D6-A311163AEBEF}
Management group: xxxxxxx

The Exchange 2007 MP has been loaded. And this MP discovers the service/application (CCR Cluster) contained within this Cluster neatly. But the Cluster itself stays unmonitored.

Both clusternodes generate above mentioned errors in the OpsMgr eventlog.
Best regards, Marnix Wolf

(Thoughts on OpsMgr)

Monday, August 10, 2009 10:42 AM
0

Sign in to vote

Tried to run the script from the command-prompt. Gave no output. Ran very fast (splitsecond). Disabled the virusscanner, bounced the HealthService. Same errors as stated above.
Best regards, Marnix Wolf

(Thoughts on OpsMgr)

Monday, August 10, 2009 10:49 AM
0

Sign in to vote
Is this Windows Server 2008 R2 by any chance? There will be an update to the MP to support R2 coming out (the cluster MP does not support it currently).
The Exchange MP is cluster-aware so it does its own monitoring of the Exchange-specific resources in the cluster. The Cluster MP adds general resource monitoring.

The cluster virtual server itself being not monitored by itself is not necessarily bad, it just means that there are no monitors targeted to it (somewhat confusing). Note that the cluster MP focuses on the physical nodes only (as well as resources and resource groups), it does not discover or monitor the virtual server.
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
- Marked as answer by Marnix WolfMVP Tuesday, August 11, 2009 6:05 PM
Monday, August 10, 2009 4:43 PM
0

Sign in to vote

Hi Ake (do I spell your name correctly?)

Thanks for the input. The servers aren't R2.

I have figured it out (I guess) what is happening. The Cluster as it is being seen by the Windows Cluster MP is not 100% a Windows Cluster. It came to existence with building a Exchange CCR Cluster. During that setup certain components equal to Windows Cluster are created but it misses out on Shared Storage. When I open the Cluster MMC, there is nothing to be seen as a Shared Resource, even though there are File Share Witnesses. Which is something like a Shared Resource but not in Windows Cluster MP terms.

The Exchange MP has correctly identified the Cluster ID and the underlying nodes. All is being monitored properly by the native Exchange 2007 MP. So apparently all is well.

However, at a first glance in the OpsMgr UI I saw the Cluster not being monitored and that put me on the wrong track. First I hoped/guessed all would be OK when the Exchange MP was in place and configured. But then I found the Cluster still in unmonitored state. Both MP guides (Windows Cluster & Native Exchange 2007) don't talk about this, even though it is a common scenario. So perhaps both guides could describe this so others aren't falling in to the same pitfalls as I did.

However, I have gained more understanding of CCR clusters and how these compare/relate to Windows Clusters and how the Cluster MP functions.

And on top of that, I have gained much respect for the way the native Exchange MP has been constructed. It is really 'The Next Generation' of MPs and I hope other (Microsoft) MPs will follow this shining example since this MP really works great and is easy to configure, compared to what it has to monitor. Compliments to the team which built this MP.
Best regards, Marnix Wolf

(Thoughts on OpsMgr)

Monday, August 10, 2009 4:57 PM
0

Sign in to vote

We are seeing the same thing in our environment. We have a similar setup of Exchange with CCR. The cluster was showing up as completely unmanaged. After installing http://support.microsoft.com/default.aspx/kb/958807 the cluster is showing up as monitored BUT we are still getting 4 of these errors.

WMI Event Module Failed Execution
Module was unable to connect to ROOT\MSCLUSTER
Error: 0x8004100e
Workflow name: Microsoft.Windows.Cluster.Node.StateMonitoring
Instance name: myexchangeccr.my.domain.com

WMI Event Module Failed Execution
Module was unable to connect to ROOT\MSCLUSTER
Error: 0x8004100e
Workflow name: Microsoft.Windows.2008.Cluster.Discovery.SpaceChanged.ObjectAdded
Instance name: Cluster Service

WMI Event Module Failed Execution
Module was unable to connect to ROOT\MSCLUSTER
Error: 0x8004100e
Workflow name: Microsoft.Windows.2008.Cluster.Discovery.SpaceChanged.ObjectRemoved
Instance name: Cluster Service

Tuesday, September 1, 2009 9:05 PM
0

Sign in to vote

Hi Tim

Thanks so much for this reply. The KB you are refering to isn't part of SP2 for W2K08. So it is worth the try. Strange those WMI errors keep coming back. WMI errors are hunting us OpsMgr users since W2K03. :(
Best regards, Marnix Wolf

(Thoughts on OpsMgr)

Wednesday, September 2, 2009 6:24 AM
0

Sign in to vote

Hi,

We applied the hotfix that Tim mentions on our CCR and it solved an issue where the WMI query 'SELECT Name, State FROM MSCLUSTER_Resource' would hang as soon as it came to the "Exchange Information Store Instance (InstanceName)". Running the query with WbemTest threw the same error ...

Now we're seeing another one :-(
WMI Probe Module Failed Execution
Object enumeration failed Query: 'SELECT Name, State FROM MSCLUSTER_Resource' HRESULT: 0x800700ea
The query runs fine with WbemTest.

Searching around I found this article "Failover Cluster: Setup and Validation Protocol (ClusPrep) Specification" at http://download.microsoft.com/download/9/5/E/95EF66AF-9026-4BB0-A41D-A4F81802D92C/%5BMS-CSVP%5D.pdf
where our error 0x800700EA is described as: ERROR_MORE_DATA RegisteredDsms was not large enough to hold all the data.

Unfortunately I have no clue what that means ... or what I'm supposed to do about it.

Cheers,
Serge

Wednesday, September 2, 2009 7:32 PM
0

Sign in to vote

I'm seeing the same WMI error as Serge. Has anyone come across a solution for it yet?

Monday, November 30, 2009 6:22 PM
0

Sign in to vote

The latest cluster MP does not discover or monitor resources, it monitors resource groups, so it should not do that query by default anymore unless you've overridden it. Resource group monitoring should be sufficient for the majority of cases.
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm

Wednesday, December 9, 2009 5:08 PM

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support options

More support

Not an IT pro?

Answered by:

Cluster 2008 MP

Question

Answers

All replies