Link to home
Start Free TrialLog in
Avatar of fpifferini
fpifferiniFlag for Switzerland

asked on

WMI Error 0X80070005 (Access is denied) from WBEMTEST

I would like to discover machine details using a tools (PlateSpin PowerP2V) that is based on WMI, but always i receive an error that the "Access is denied".
The machine that I would like discover as Win XP SP1 and Win XP SP2 the other, Firewall disabled,
WMI service is running, DCOM is enabled, RPC service is running, Remote Registry is running, File and Print Sharing for Microsoft Networks is enabled. Both are Virtual Machines in a VMware GSX server.

If I test the WMI with the command WBEMTEST from my main server (Win2003 Srv), I put the name of the machine
in the Namespace (i.e. \\TIMEAS\root\cimv2 ), and the appropriate credentials hostname\LocalAdmin and password
(the machine aren't in a domain).
When I click Connect I got the error message:
Number: 0x80070005
Facility:  Win32
Description: Access is denied

Any idea how the resolve this?
Avatar of chalapa
chalapa

check the following link
http://support.microsoft.com/default.aspx?scid=kb;en-us;884573
let me know the details


chalapathi
Avatar of fpifferini

ASKER

I've tried the workaround suggested in the KB884573, but the problem persist.
(I don't have made a reboot of the machine...it's necessary?)

Do you know how to find the Fix proposed in this KB and how is named?
Download windows xp post sp2 and update chek the following link

http://www.softpedia.com/get/System/OS-Enhancements/RyanVM-Windows-XP-Post-SP2-Update-Pack.shtml
chalapathi
Avatar of sramesh2k
fpifferini,

Configuring the DCOMCNFG.EXE may be needed. See:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/connecting_through_windows_firewall.asp

<quote>

The 0x80070005 error occurs when this privilege is not set.

</quote>
Try this.

Click Start -- Run
Type wmimgmt.msc and press Enter

A window should open up.  In the left pane it should say WMI Control (Local).  Right click that and select properties.  Select the Security Tab.  Select the Root Folder and Press the Security Button.  Give appropriate Permissions.
Tried the suggested task from  2hype   and    sramesh2k  but seams that they don't resolve the problem...
The permissions was OK.
I would like the try to apply the Post SP2 patches suggested by  chalapa  ,but I don't know how...
I've the  .cab file...what should I do?
Try this.

Go to Start -- Control Panel -- Administrative tools -- Services

Scroll Down to Windows Managment Instrumentation and Stop the Service

Migratet to C:\Windows\System32\WBEM and delete the Repository Folder.

Go Back to Services and Start the Windows Managmet Instrumentation.  Wait about 10 min and the Respository Folder should be recreated.  Rebooting the Machine usually speeds the process up.

After the folder is recreated, try to see if it works now.

I had a program that collected Inventory From My computers through WMI and sometimes I would get an error trying to query the computer.  The above worked for me.
ASKER CERTIFIED SOLUTION
Avatar of sramesh2k
sramesh2k
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
:-(
no way....repair WMI don't resolve my problem...
other suggestion?
Find the solution:  MS KB307874
http://support.microsoft.com/default.aspx?scid=kb;en-us;307874

The Advanced Shared mode was not enabled.
fpifferini,

Glad you found the answer. And thanks for posting back. You may request for a refund for this question, and convert this to PAQ.
fpifferini,

Can you tell me where you found the "Advanced Shared" mode. It does not seem to be referenced in the article.
Yes, I could not find the term "Advanced Shared" in the document. It refers to Simple File Sharing and how to tun it off. Is this what you mean by "Advanced Shared"?
If you disbale "Simple File Sharing" you have Advanced Sharing....
DialaFix http://www.softpedia.com/progDownload/Dial-a-fix-Download-27328.html
This is a handy little tool..  If your in MIS and not using this, you should be.