Re: Can not connect to WMI

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



"Manbinder Pal Singh [MSFT]" <manbins@xxxxxxxxxxxxx> wrote in message
news:eD%23i73SNHHA.1252@xxxxxxxxxxxxxxxxxxxxxxx
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.


"Rick Sears" <rsears@xxxxxxxxx> wrote in message
news:u7H4KMQNHHA.3588@xxxxxxxxxxxxxxxxxxxxxxx
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

"Rick Sears" <rsears@xxxxxxxxx> wrote in message
news:Oz1il%23PNHHA.724@xxxxxxxxxxxxxxxxxxxxxxx
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








.

Relevant Pages

  • Re: Can not connect to WMI
    ... Well ours was a group policy issue. ... Apply each group policy object until you break WMI. ... see if there are events in the event viewer or logs? ... The reason I say this is as domain admin I connect to theWMI on my ...
    (microsoft.public.windowsxp.wmi)
  • Re: Can not connect to WMI
    ... Can you please run WMIDIAG tool and send the logs. ... You can reboot your workstation now and on restart see logs and wevent ... selectively apply GPO to a newly installed PC and figure out what policy ... is causing WMI to FUBAR ...
    (microsoft.public.windowsxp.wmi)
  • Re: How do I get the PCs Processor speed?
    ... We use a script here at work that runs whenever someone logs into ... their machine that logs various bits of information to a database. ... following registry key for the CPU info: ... I've also used Tim Golden's WMI module like so: ...
    (comp.lang.python)
  • Re: unable to create the WMI namespace
    ... maybe try repairing the WMI repository on the system itself. ... rmdir /s /q repository ... rmdir /s /q Logs ... net start winmgmt ...
    (microsoft.public.sms.admin)
  • Re: Can not connect to WMI
    ... You can reboot your workstation now and on restart see logs and wevent ... apply GPO to a newly installed PC and figure out what policy is causing ... WMI to FUBAR ...
    (microsoft.public.windowsxp.wmi)