Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
Main Topics
Browse All TopicsI have a vb.net 2005 program using .net framework 2.0 management classes, which loops through every computer on the local LAN and pulls back some WMI information.
When I run it from one particular Windows 2003 server, it fails on every computer with this message:
The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
I can run the program from any other computer and it runs fine. Even another win 2003 server with the same standalone domainless configuration.
1. All computers have windows firewall turned off
2. All computers have RPC and DCOM enabled
3. All computers have the same administrator password and thats what the 2003 server is using.
4. I CAN connect to WMI on any computer from the server, using Computer Management, WMI Control, and I can connect to every c$ using windows explorer
5. None of the computers are on simple file sharing or have forceguest switched on
6. All of the computers will work when the program is run from another server, but when the 2003 server runs the program, it only works for itself. The program does not specify credentials.
7. All the computers are fully patched
WMI logs contain the following
wbemcore.log:
GetUserDefaultLCID failed, restorting to system verion(Fri Oct 05 16:30:31 2007.1529406) : GetUserDefaultLCID failed, restorting to system verion(Fri Oct 05 16:30:31 2007.1529437) : GetUserDefaultLCID failed, restorting to system verion(Fri Oct 05 16:30:35 2007.1533328) : GetUserDefaultLCID failed, restorting to system verion(Fri Oct 05 16:30:35 2007.1533578) : GetUserDefaultLCID failed, restorting to system verion(Fri Oct 05 16:30:38 2007.1535718) : GetUserDefaultLCID failed, restorting to system verion
wbemprox.log:
(Fri Oct 05 16:30:31 2007.1529421) : SetClientIdentity failed hr = 0x800706ba
(Fri Oct 05 16:30:31 2007.1529421) : SetClientIdentity failed hr = 0x800706ba
(Fri Oct 05 16:30:31 2007.1529421) : SetClientIdentity failed hr = 0x800706ba
(Fri Oct 05 16:30:31 2007.1529453) : SetClientIdentity failed hr = 0x800706ba
(Fri Oct 05 16:30:31 2007.1529468) : SetClientIdentity failed hr = 0x800706ba
(Fri Oct 05 16:30:31 2007.1529578) : SetClientIdentity failed hr = 0x800706ba
(Fri Oct 05 16:30:43 2007.1540734) : SetClientIdentity failed hr = 0x800706ba
(Fri Oct 05 16:30:43 2007.1540765) : ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x80070005
(Fri Oct 05 16:30:46 2007.1544406) : SetClientIdentity failed hr = 0x800706ba
Framework.log
Shell Name Explorer.exe in Registry not found in process list. 10/05/2007 16:30:38.109 thread:1888 [d:\nt\admin\wmi\wbem\prov
Unable to locate Shell Process, Impersonation failed. 10/05/2007 16:30:38.109 thread:1888 [d:\nt\admin\wmi\wbem\prov
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: plqPosted on 2007-10-05 at 11:11:36ID: 20024193
Well I answered my own question.
My deployment included the DLL ws32_2.dll, which is a system DLL but is missing on some systems.
When this DLL exists in the same folder as my EXE, the RPC error happens.
When this DLL does not exist in the same folder as my EXE, the RPC error does not happen.