Can not connect to WMI

  • Thread starter Thread starter Rick Sears
  • Start date Start date
R

Rick Sears

We are having problems with applications that use WMI. Digging in to this I
am sure it is an issue with a domain policy which is preventing people from
accessing WMI.
The reason I say this is as domain admin I connect to theWMI on my Domain
Controllers and Member Servers without issue. However when I try to connect
to member worstations I get a Win32 access is denied message. We also get
an Event 1090 constantly on all of our member worsations. The essage reads:
Windows couldn't log the RSoP (Resultant Set of Policies) session status. An
attempt to connect to WMI failed. No more RSoP logging will be done for this
application of policy.

In addition when I try to connect to the WMI in the control panel I get
Event 43 and event 60 in my event logs

WMI ADAP failed to connect to namespace \\.\root\cimv2 with the following
error: 0x80070005

WMI ADAP was unable to process the performance libraries: 0x80041001

All of our workstations are XP SP2. I can not connect to any of the XP boxes
either as a local admin or remotely as admin. I have tried shutting of the
windows firewall and creating a GPO which sets DCOM permmisions.

Thanks for the help
 
Update we are not sure that this is a permissions issue it may be that we
have and older Group Policy object that is corrupt and is causing this
issue. We are going to creat new OU in the root so that we can selectively
apply GPO to a newly installed PC and figure out what policy is causing WMI
to FUBAR

Rick
 
I would say
1. clear all logs under %windir%\system32\wbem\logs , and event viewer
events.
2. and then restart the wmi service "net stop winmgmt & net start winmgmt"
3. see if there are events in the event viewer or logs?
4. You can reboot your workstation now and on restart see logs and wevent
viewer again to see ifsomething failed?
5. Try using wbemtest localy on your workstation machines and connect to
root\cimv2 and try to enumurate win32_process or some class if it connects
successfully.
6. If local connection succeeds then you need to configure your workstation
for remote configuration.. So follow this
http://msdn2.microsoft.com/en-us/library/aa389290.aspx

Please give the log or error event log details for each of this in more
detail.
Hopefully that should help and fix.

Thanks,
Manbinder Pal Singh

This posting is provided "AS IS" with no warranties, and confers no rights.
 
I have also problem with this, I noticed it when I try to configure the
local sqlserver 2005 .
Error message in SQL server 2005 Surface area configuration:

Computer localhost does not exist on the network. or the computer cannot be
configured remotely. Verify that the remote computer has the required
Windows Management Instumentation components and then try again. (SQLSAC)

Addaitional information:

An exception occured in smo while trying to manage a service. -> Access is

denied. (Exception from HRESULT: 0x080070005(E_ACCESSDENIED)) (mscorlib)





Then I check using wmimgmt.msc and when I right click WMI Control and

select properties, it gives the following message in General

tab:

Failed to connect to <local computer> because "Win32: Access is denied."


So I think that the problem must be in Windows-WMI.

Help

Christers
 
Can you please run WMIDIAG tool and send the logs. You can find this in
download microsoft section.

Thanks,
Manbinder Pal Singh

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Well ours was a group policy issue. A prior admin had made changes to the
domain level policy which prevented users from running DCOM and in turn WMI.
There was another article that suggested the following:
Create a new OU at the root
Format a new PC and move it to the test ou.
Apply each group policy object until you break WMI. Since this is a computer
based policy issue it could take lots of reboots before you find the
offending policy.

Rick
..
 
Back
Top