WMI Probe Module Failed Execution

[SCOM General]

Hi,

Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"

Module was unable to connect to namespace '\\machine-name\root\cimv2'
This has happened 11 times since this instance was loaded. HRESULT:
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test

Can anyone help?

Thank you.

Regards,
Steven

[Rem-8]

This was mentioned several times :) Is the machine a cluster? If so,
are physical nodes have agent proxy enabled? Can you easily connect to
\root\cimv2 to this machine from SCOM server?

Post by SCOM General
Hi,
Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"
Module was unable to connect to namespace '\\machine-name\root\cimv2'
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test
Can anyone help?
Thank you.
Regards,
Steven

[François Dufour [Exakis]]

Post by Rem-8
This was mentioned several times :) Is the machine a cluster? If so,
are physical nodes have agent proxy enabled? Can you easily connect to
\root\cimv2 to this machine from SCOM server?

Post by SCOM General
Hi,
Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"
Module was unable to connect to namespace '\\machine-name\root\cimv2'
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test
Can anyone help?
Thank you.
Regards,
Steven- Masquer le texte des messages précédents -

- Afficher le texte des messages précédents -

Same problem here with RMS cluster both nodes and RMS virtual server
are returning those WMI alerts.
About proxy enabled setting on nodes the problem is nodes on a RMS
cluster are agentless managed so no proxy enabled setting.

[Megan Kielman]

All -

I just got off the phone with MS about this issue. It is a bug in the
base OS MP that will be fixed in the RTM version of SP1. The workaround
is to disable the monitor for the Windows 2000 and Windows 2003 computer
group.

Thanks!

Megan

Post by François Dufour [Exakis]

Post by Rem-8
This was mentioned several times :) Is the machine a cluster? If so,
are physical nodes have agent proxy enabled? Can you easily connect to
\root\cimv2 to this machine from SCOM server?

Post by SCOM General
Hi,
Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"
Module was unable to connect to namespace '\\machine-name\root\cimv2'
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test
Can anyone help?
Thank you.
Regards,
Steven- Masquer le texte des messages précédents -

- Afficher le texte des messages précédents -

Same problem here with RMS cluster both nodes and RMS virtual server
are returning those WMI alerts.
About proxy enabled setting on nodes the problem is nodes on a RMS
cluster are agentless managed so no proxy enabled setting.

[Jan Matejka]

Really? Nobody uses Agent-less monitoring till SP1 release??? I cant believe
i...:-))))

I just added Agent-less server, defined proxy agent server (not RMS) and
thats all. Than my agent-less server is always in "not monitored" state
(Windows state) and log on agent proxy server is full of alerts mentioned
above. Dont tell me nobody solved it?!?!?!?!:-))

It means you cannot use agent-less monitoring.

Jan

All -
I just got off the phone with MS about this issue. It is a bug in the base
OS MP that will be fixed in the RTM version of SP1. The workaround is to
disable the monitor for the Windows 2000 and Windows 2003 computer group.
Thanks!
Megan

Post by François Dufour [Exakis]

Post by Rem-8
This was mentioned several times :) Is the machine a cluster? If so,
are physical nodes have agent proxy enabled? Can you easily connect to
\root\cimv2 to this machine from SCOM server?

Post by SCOM General
Hi,
Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"
Module was unable to connect to namespace '\\machine-name\root\cimv2'
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test
Can anyone help?
Thank you.
Regards,
Steven- Masquer le texte des messages précédents -

- Afficher le texte des messages précédents -

Same problem here with RMS cluster both nodes and RMS virtual server
are returning those WMI alerts.
About proxy enabled setting on nodes the problem is nodes on a RMS
cluster are agentless managed so no proxy enabled setting.

[AKSisson]

I just installed the SP1 RTM...it is not fixed.

Andrew Sisson

Post by Megan Kielman
All -
I just got off the phone with MS about this issue. It is a bug in the
base OS MP that will be fixed in the RTM version of SP1. The workaround
is to disable the monitor for the Windows 2000 and Windows 2003 computer
group.
Thanks!
Megan

Post by François Dufour [Exakis]

Post by Rem-8
This was mentioned several times :) Is the machine a cluster? If so,
are physical nodes have agent proxy enabled? Can you easily connect to
\root\cimv2 to this machine from SCOM server?

Post by SCOM General
Hi,
Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"
Module was unable to connect to namespace '\\machine-name\root\cimv2'
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test
Can anyone help?
Thank you.
Regards,
Steven- Masquer le texte des messages précédents -

- Afficher le texte des messages précédents -

Same problem here with RMS cluster both nodes and RMS virtual server
are returning those WMI alerts.
About proxy enabled setting on nodes the problem is nodes on a RMS
cluster are agentless managed so no proxy enabled setting.

[Walter Eikenboom]

Hello AKSisson,

There is a new KB for WMI errors and DELL hardware agents.
http://support.microsoft.com/kb/948730

Mayby it applies for your environment.

Regards,
Walter Eikenboom
http://weblogwally.spaces.live.com

Post by AKSisson
I just installed the SP1 RTM...it is not fixed.
Andrew Sisson

Post by Megan Kielman
All -
I just got off the phone with MS about this issue. It is a bug in the
base OS MP that will be fixed in the RTM version of SP1. The workaround
is to disable the monitor for the Windows 2000 and Windows 2003 computer
group.
Thanks!
Megan

Post by François Dufour [Exakis]

Post by Rem-8
This was mentioned several times :) Is the machine a cluster? If so,
are physical nodes have agent proxy enabled? Can you easily connect to
\root\cimv2 to this machine from SCOM server?

Post by SCOM General
Hi,
Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"
Module was unable to connect to namespace '\\machine-name\root\cimv2'
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test
Can anyone help?
Thank you.
Regards,
Steven- Masquer le texte des messages précédents -

- Afficher le texte des messages précédents -

Same problem here with RMS cluster both nodes and RMS virtual server
are returning those WMI alerts.
About proxy enabled setting on nodes the problem is nodes on a RMS
cluster are agentless managed so no proxy enabled setting.

[Mick McKean]

Hi,
My customer is experiencing exactly the same event as the original post on
the proxy for the agentless managed server. It is also for logical disk
discovery, and the agentless server is X64 as per original post. In our case,
we are agentless monitoring the RMS of another SCOM management group, for
cross-monitoring purposes.
We are also getting 3 of this event (all for ComputerbrowserServiceHealth)
on the agentless proxy server at the same time:
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 11773
Date: 2/04/2008
Time: 10:59:53 AM
User: N/A
Computer: SIFO
Description:
Error getting state of service
Error: 0x80070005
Details: Access is denied.
One or more workflows were affected by this.
Workflow name:
Microsoft.Windows.Server.2003.OperatingSystem.ComputerbrowserServiceHealth
Instance name: Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition
Instance ID: {BB5C668D-8A0D-496B-93CA-A014392FC83E}
Management group: SCLOM
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Using the AD account we use as the management server action account I am
able to connect to the agentless server, and successfully run an SC.exe query
against the computer browser service, a WMI query against root\CIMV2, and
using perfmon view logical disk free space on all disks. This makes me
believe the default action account for the management server that is the
agentless proxy is fine. I also changed the agentless proxy to the secondary
management server with the same failure events being logged on the new
agentless proxy.
The entire OpsMgr 2007 system is now up to RTM release of SP1, after being
installed as RTM, then upgraded to SP1 RC then SP1 RTM.
I would be interested in any more information or troubleshooting I could get
on this problem.

[GestiefelterKater40]

We have the same errors here
No solution somewehre ?
We also have those WMI errors, although SP1 of SCOM.
I guess MS will tell us now SP2 will solve this :-(
--
GestiefelterKater40
--- Denke bringt nix ---

Post by Mick McKean
Hi,
My customer is experiencing exactly the same event as the original post on
the proxy for the agentless managed server. It is also for logical disk
discovery, and the agentless server is X64 as per original post. In our case,
we are agentless monitoring the RMS of another SCOM management group, for
cross-monitoring purposes.
We are also getting 3 of this event (all for ComputerbrowserServiceHealth)
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 11773
Date: 2/04/2008
Time: 10:59:53 AM
User: N/A
Computer: SIFO
Error getting state of service
Error: 0x80070005
Details: Access is denied.
One or more workflows were affected by this.
Microsoft.Windows.Server.2003.OperatingSystem.ComputerbrowserServiceHealth
Instance name: Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition
Instance ID: {BB5C668D-8A0D-496B-93CA-A014392FC83E}
Management group: SCLOM
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Using the AD account we use as the management server action account I am
able to connect to the agentless server, and successfully run an SC.exe query
against the computer browser service, a WMI query against root\CIMV2, and
using perfmon view logical disk free space on all disks. This makes me
believe the default action account for the management server that is the
agentless proxy is fine. I also changed the agentless proxy to the secondary
management server with the same failure events being logged on the new
agentless proxy.
The entire OpsMgr 2007 system is now up to RTM release of SP1, after being
installed as RTM, then upgraded to SP1 RC then SP1 RTM.
I would be interested in any more information or troubleshooting I could get
on this problem.
--
Regards,
Mick McKean
Brisbane Australia

[Jan Matejka]

Try to add your Agent-proxy server in Local Admins in agent-less server.
It should work!
I suppose your Agent-proxy (monitoring agent) runs like "local system" so
this server doesnt have permission to use WMI service on agent-less server.

Jan

Post by GestiefelterKater40
We have the same errors here
No solution somewehre ?
We also have those WMI errors, although SP1 of SCOM.
I guess MS will tell us now SP2 will solve this :-(
--
GestiefelterKater40
--- Denke bringt nix ---

Post by Mick McKean
Hi,
My customer is experiencing exactly the same event as the original post on
the proxy for the agentless managed server. It is also for logical disk
discovery, and the agentless server is X64 as per original post. In our case,
we are agentless monitoring the RMS of another SCOM management group, for
cross-monitoring purposes.
We are also getting 3 of this event (all for
ComputerbrowserServiceHealth)
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 11773
Date: 2/04/2008
Time: 10:59:53 AM
User: N/A
Computer: SIFO
Error getting state of service
Error: 0x80070005
Details: Access is denied.
One or more workflows were affected by this.
Microsoft.Windows.Server.2003.OperatingSystem.ComputerbrowserServiceHealth
Instance name: Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition
Instance ID: {BB5C668D-8A0D-496B-93CA-A014392FC83E}
Management group: SCLOM
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Using the AD account we use as the management server action account I am
able to connect to the agentless server, and successfully run an SC.exe query
against the computer browser service, a WMI query against root\CIMV2, and
using perfmon view logical disk free space on all disks. This makes me
believe the default action account for the management server that is the
agentless proxy is fine. I also changed the agentless proxy to the secondary
management server with the same failure events being logged on the new
agentless proxy.
The entire OpsMgr 2007 system is now up to RTM release of SP1, after being
installed as RTM, then upgraded to SP1 RC then SP1 RTM.
I would be interested in any more information or troubleshooting I could get
on this problem.
--
Regards,
Mick McKean
Brisbane Australia

[CK]

Try this one: http://support.microsoft.com/Default.aspx?kbid=933061

ck

Post by GestiefelterKater40
We have the same errors here
No solution somewehre ?
We also have those WMI errors, although SP1 of SCOM.
I guess MS will tell us now SP2 will solve this :-(
--
GestiefelterKater40
--- Denke bringt nix ---

Post by Mick McKean
Hi,
My customer is experiencing exactly the same event as the original post on
the proxy for the agentless managed server. It is also for logical disk
discovery, and the agentless server is X64 as per original post. In our case,
we are agentless monitoring the RMS of another SCOM management group, for
cross-monitoring purposes.
We are also getting 3 of this event (all for
ComputerbrowserServiceHealth)
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 11773
Date: 2/04/2008
Time: 10:59:53 AM
User: N/A
Computer: SIFO
Error getting state of service
Error: 0x80070005
Details: Access is denied.
One or more workflows were affected by this.
Microsoft.Windows.Server.2003.OperatingSystem.ComputerbrowserServiceHealth
Instance name: Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition
Instance ID: {BB5C668D-8A0D-496B-93CA-A014392FC83E}
Management group: SCLOM
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Using the AD account we use as the management server action account I am
able to connect to the agentless server, and successfully run an SC.exe query
against the computer browser service, a WMI query against root\CIMV2, and
using perfmon view logical disk free space on all disks. This makes me
believe the default action account for the management server that is the
agentless proxy is fine. I also changed the agentless proxy to the secondary
management server with the same failure events being logged on the new
agentless proxy.
The entire OpsMgr 2007 system is now up to RTM release of SP1, after being
installed as RTM, then upgraded to SP1 RC then SP1 RTM.
I would be interested in any more information or troubleshooting I could get
on this problem.
--
Regards,
Mick McKean
Brisbane Australia

[Sven Wells]

This link points towards W2K3 and XP. We are seeing this issue primarily on
W2K systems.

Anyone?

Thanks,
Sven

Post by CK
Try this one: http://support.microsoft.com/Default.aspx?kbid=933061
ck

Post by GestiefelterKater40
We have the same errors here
No solution somewehre ?
We also have those WMI errors, although SP1 of SCOM.
I guess MS will tell us now SP2 will solve this :-(
--
GestiefelterKater40
--- Denke bringt nix ---

Post by Mick McKean
Hi,
My customer is experiencing exactly the same event as the original post on
the proxy for the agentless managed server. It is also for logical disk
discovery, and the agentless server is X64 as per original post. In our case,
we are agentless monitoring the RMS of another SCOM management group, for
cross-monitoring purposes.
We are also getting 3 of this event (all for
ComputerbrowserServiceHealth)
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 11773
Date: 2/04/2008
Time: 10:59:53 AM
User: N/A
Computer: SIFO
Error getting state of service
Error: 0x80070005
Details: Access is denied.
One or more workflows were affected by this.
Microsoft.Windows.Server.2003.OperatingSystem.ComputerbrowserServiceHealth
Instance name: Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition
Instance ID: {BB5C668D-8A0D-496B-93CA-A014392FC83E}
Management group: SCLOM
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Using the AD account we use as the management server action account I am
able to connect to the agentless server, and successfully run an SC.exe query
against the computer browser service, a WMI query against root\CIMV2, and
using perfmon view logical disk free space on all disks. This makes me
believe the default action account for the management server that is the
agentless proxy is fine. I also changed the agentless proxy to the secondary
management server with the same failure events being logged on the new
agentless proxy.
The entire OpsMgr 2007 system is now up to RTM release of SP1, after being
installed as RTM, then upgraded to SP1 RC then SP1 RTM.
I would be interested in any more information or troubleshooting I could get
on this problem.
--
Regards,
Mick McKean
Brisbane Australia

[GestiefelterKater40]

We have installed this MS KB fix.
Still all over WMI errors.
So..there seems to be no correct solution for this untl SCOm 2010 ?
--
GestiefelterKater40
--- Denke bringt nix ---

Post by Sven Wells
This link points towards W2K3 and XP. We are seeing this issue primarily on
W2K systems.
Anyone?
Thanks,
Sven

Post by CK
Try this one: http://support.microsoft.com/Default.aspx?kbid=933061
ck

Post by GestiefelterKater40
We have the same errors here
No solution somewehre ?
We also have those WMI errors, although SP1 of SCOM.
I guess MS will tell us now SP2 will solve this :-(
--
GestiefelterKater40
--- Denke bringt nix ---

Post by Mick McKean
Hi,
My customer is experiencing exactly the same event as the original post on
the proxy for the agentless managed server. It is also for logical disk
discovery, and the agentless server is X64 as per original post. In our case,
we are agentless monitoring the RMS of another SCOM management group, for
cross-monitoring purposes.
We are also getting 3 of this event (all for
ComputerbrowserServiceHealth)
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 11773
Date: 2/04/2008
Time: 10:59:53 AM
User: N/A
Computer: SIFO
Error getting state of service
Error: 0x80070005
Details: Access is denied.
One or more workflows were affected by this.
Microsoft.Windows.Server.2003.OperatingSystem.ComputerbrowserServiceHealth
Instance name: Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition
Instance ID: {BB5C668D-8A0D-496B-93CA-A014392FC83E}
Management group: SCLOM
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Using the AD account we use as the management server action account I am
able to connect to the agentless server, and successfully run an SC.exe query
against the computer browser service, a WMI query against root\CIMV2, and
using perfmon view logical disk free space on all disks. This makes me
believe the default action account for the management server that is the
agentless proxy is fine. I also changed the agentless proxy to the secondary
management server with the same failure events being logged on the new
agentless proxy.
The entire OpsMgr 2007 system is now up to RTM release of SP1, after being
installed as RTM, then upgraded to SP1 RC then SP1 RTM.
I would be interested in any more information or troubleshooting I could get
on this problem.
--
Regards,
Mick McKean
Brisbane Australia

[Roger]

Forgive my ignorance. What do you mean by connect to \root\cimv2 ? Is there a
WMI command to use for that test ? What I find ineteresting in the event text
in my environment is that the path is \\.\root\cimv2. The dot is interesting.
Is that shorthand for localhost ? Could it be something not defined correctly
on the OS ? I have hundreds of these WMI errors. some complain about the
namespace and others about not being able to execute a select call.
Like most in the thread I have SP1 RTM as well as the KB951979 hotfix.
Thanks

Post by Rem-8
This was mentioned several times :) Is the machine a cluster? If so,
are physical nodes have agent proxy enabled? Can you easily connect to
\root\cimv2 to this machine from SCOM server?

Post by SCOM General
Hi,
Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"
Module was unable to connect to namespace '\\machine-name\root\cimv2'
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test
Can anyone help?
Thank you.
Regards,
Steven

[Ben Derr]

We have found (At least on the RMS), that by assigning an account to the
Priviliged Monitoring Run As Profile, helped clear this issue. We used the
Action Account, and a large amount of these disappeared.

Post by Roger
Forgive my ignorance. What do you mean by connect to \root\cimv2 ? Is there a
WMI command to use for that test ? What I find ineteresting in the event text
in my environment is that the path is \\.\root\cimv2. The dot is interesting.
Is that shorthand for localhost ? Could it be something not defined correctly
on the OS ? I have hundreds of these WMI errors. some complain about the
namespace and others about not being able to execute a select call.
Like most in the thread I have SP1 RTM as well as the KB951979 hotfix.
Thanks

Post by Rem-8
This was mentioned several times :) Is the machine a cluster? If so,
are physical nodes have agent proxy enabled? Can you easily connect to
\root\cimv2 to this machine from SCOM server?

Post by SCOM General
Hi,
Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"
Module was unable to connect to namespace '\\machine-name\root\cimv2'
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test
Can anyone help?
Thank you.
Regards,
Steven

[Sam Patton [MSFT]]

Is the 'machine-name' that is in the event below an agentless machine? If
so, then you may need to run as a more privileged user to access WMI
remotely on the machine.

Sam

Post by Ben Derr
We have found (At least on the RMS), that by assigning an account to the
Priviliged Monitoring Run As Profile, helped clear this issue. We used the
Action Account, and a large amount of these disappeared.

Post by Roger
Forgive my ignorance. What do you mean by connect to \root\cimv2 ? Is there a
WMI command to use for that test ? What I find ineteresting in the event text
in my environment is that the path is \\.\root\cimv2. The dot is interesting.
Is that shorthand for localhost ? Could it be something not defined correctly
on the OS ? I have hundreds of these WMI errors. some complain about the
namespace and others about not being able to execute a select call.
Like most in the thread I have SP1 RTM as well as the KB951979 hotfix.
Thanks

Post by Rem-8
This was mentioned several times :) Is the machine a cluster? If so,
are physical nodes have agent proxy enabled? Can you easily connect to
\root\cimv2 to this machine from SCOM server?

Post by SCOM General
Hi,
Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"
Module was unable to connect to namespace '\\machine-name\root\cimv2'
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test
Can anyone help?
Thank you.
Regards,
Steven

[MigrateMe]

Did anyone find by adding the account to the "Privileged Monitoring Account"
this resolved your issues?

I just tried using the "Agent Action Account" for a specific server and I am
now receiving IIS Probe errors.

Post by Ben Derr
We have found (At least on the RMS), that by assigning an account to the
Priviliged Monitoring Run As Profile, helped clear this issue. We used the
Action Account, and a large amount of these disappeared.

Post by Roger
Forgive my ignorance. What do you mean by connect to \root\cimv2 ? Is there a
WMI command to use for that test ? What I find ineteresting in the event text
in my environment is that the path is \\.\root\cimv2. The dot is interesting.
Is that shorthand for localhost ? Could it be something not defined correctly
on the OS ? I have hundreds of these WMI errors. some complain about the
namespace and others about not being able to execute a select call.
Like most in the thread I have SP1 RTM as well as the KB951979 hotfix.
Thanks

Post by Rem-8
This was mentioned several times :) Is the machine a cluster? If so,
are physical nodes have agent proxy enabled? Can you easily connect to
\root\cimv2 to this machine from SCOM server?

Post by SCOM General
Hi,
Recently, I've found the RMS has generated an error "WMI Probe Module
Failed Execution"
Module was unable to connect to namespace '\\machine-name\root\cimv2'
0x80070005 Details: Access is denied. One or more workflows were
affected by this. Workflow name: Microsoft.Windows.Server.
2003.LogicalDisk.Discovery Instance name: Microsoft(R) Windows(R)
Server 2003 Enterprise x64 Edition Instance ID: {5F7C4305-A0AB-EFC0-
FC2C-50AC178005AA} Management group: SCOM_Beta_Test
Can anyone help?
Thank you.
Regards,
Steven