Advertisement

11.13.2007 at 11:19PM PST, ID: 22959324
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
8.0

WMI Error returned while querying remote server through asp.net web application (IIS6)

Asked by azizparacha in Microsoft IIS Web Server, Microsoft Visual Basic.Net, Network Management

Tags:

This exception message was returned from the System.Management.ManagementScope.Connect()
The call succeeds from my local machine and further WMI operations too , using the same web app but when it was published to IIS on a dedicated server , it throws this error.
I am quite sure but still wondering if the problem is with the user account that is used by web app(If the user used by the app while connecting from my system is different from the server).
Consider the scraps of following logs for more detail ,
which were located in
system32\WBEM\Logs\
===========================
FrameWork.log
===========================
Unable to locate Shell Process, Impersonation failed.      11/13/2007 03:00:49.802      thread:1588      [d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.1027]
Shell Name Explorer.exe in Registry not found in process list.      11/13/2007 03:00:49.982      thread:3592      [d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.1019]
Unable to locate Shell Process, Impersonation failed.      11/13/2007 03:00:50.012      thread:3592      [d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.1027]
Shell Name Explorer.exe in Registry not found in process list.      11/13/2007 03:00:50.172      thread:1588      [d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.1019]
Unable to locate Shell Process, Impersonation failed.      11/13/2007 03:00:50.202      thread:1588      [d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.1027]
Shell Name Explorer.exe in Registry not found in process list.      11/13/2007 03:00:50.343      thread:3592      [d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.1019]
Unable to locate Shell Process, Impersonation failed.      11/13/2007 03:00:50.413      thread:3592      [d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.1027]
Shell Name Explorer.exe in Registry not found in process list.      11/13/2007 03:00:50.633      thread:3592      [d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.1019]
Unable to locate Shell Process, Impersonation failed.      11/13/2007 03:00:50.693      thread:3592      [d:\nt\admin\wmi\wbem\providers\win32provider\common\implogonuser.cpp.1027]
......
=============================
mofcomp.log
=============================
(Tue May 29 09:33:05 2007.952639) : Parsing MOF file: C:\WINDOWS\system32\WBEM\cimwin32.mof
(Tue May 29 09:33:12 2007.959439) : Finished compiling file:C:\WINDOWS\system32\WBEM\cimwin32.mof
(Tue May 29 09:33:13 2007.960521) : Parsing MOF file: C:\WINDOWS\system32\WBEM\cimwin32.mfl
(Tue May 29 09:33:17 2007.964717) : Finished compiling file:C:\WINDOWS\system32\WBEM\cimwin32.mfl
(Tue May 29 09:33:17 2007.965167) : Parsing MOF file: C:\WINDOWS\system32\WBEM\system.mof
(Tue May 29 09:33:18 2007.965638) : Finished compiling file:C:\WINDOWS\system32\WBEM\system.mof
(Tue May 29 09:33:18 2007.965678) : Parsing MOF file: C:\WINDOWS\system32\WBEM\wmipcima.mof
(Tue May 29 09:33:18 2007.965868) : Finished compiling file:C:\WINDOWS\system32\WBEM\wmipcima.mof
(Tue May 29 09:33:18 2007.965868) : Parsing MOF file: C:\WINDOWS\system32\WBEM\wmipcima.mfl
(Tue May 29 09:33:18 2007.965968) : Finished compiling file:C:\WINDOWS\system32\WBEM\wmipcima.mfl
......
==============================
wbemcore.log
==============================
(Wed Nov 14 06:00:15 2007.10459009) : GetUserDefaultLCID failed, restorting to system verion(Wed Nov 14 06:03:04 2007.10627781) : GetUserDefaultLCID failed, restorting to system verion(Wed Nov 14 06:03:19 2007.10643164) : GetUserDefaultLCID failed, restorting to system verion(Wed Nov 14 06:03:26 2007.10650053) : GetUserDefaultLCID failed, restorting to system verion(Wed Nov 14 06:04:38 2007.10722197) : GetUserDefaultLCID failed, restorting to system verion(Wed Nov 14 06:05:21 2007.10764859) : GetUserDefaultLCID failed, restorting to system verion(Wed Nov 14 06:05:45 2007.10789364) : GetUserDefaultLCID failed, restorting to system verion(Wed Nov 14 06:07:18 2007.10882197) : GetUserDefaultLCID failed, restorting to system verion(Wed Nov 14 06:07:18 2007.10882277) : GetUserDefaultLCID failed, restorting to system
....
=================================
wbemess.log
================================
(Tue Nov 13 03:18:44 2007.43916067) : Dropping event destined for event consumer NTEventLogEventConsumer="SCM Event Log Consumer" in namespace //./root/subscription
(Tue Nov 13 03:18:44 2007.43916067) : Failed to deliver an event to event consumer NTEventLogEventConsumer="SCM Event Log Consumer" with error code 0x80041003. Dropping event.
(Tue Nov 13 03:18:47 2007.43918251) : Dropping event destined for event consumer NTEventLogEventConsumer="SCM Event Log Consumer" in namespace //./root/subscription
(Tue Nov 13 03:18:47 2007.43918251) : Failed to deliver an event to event consumer NTEventLogEventConsumer="SCM Event Log Consumer" with error code 0x80041003. Dropping event.
(Tue Nov 13 03:18:48 2007.43919162) : Dropping event destined for event consumer NTEventLogEventConsumer="SCM Event Log Consumer" in namespace //./root/subscription
(Tue Nov 13 03:18:48 2007.43919162) : Failed to deliver an event to event consumer
..........
==============================
wbemprox.log
==============================
(Tue May 29 09:43:07 2007.1554575) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 03:06:40 2007.140081) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 02:52:09 2007.2754951) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 02:52:09 2007.2755121) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 02:52:16 2007.2761771) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 02:52:21 2007.2766768) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 02:56:29 2007.3015265) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 03:24:52 2007.4718154) : ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x8007045b
(Tue May 29 03:24:52 2007.4718164) : ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x8007045b
(Tue May 29 03:24:53 2007.4719486) : ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x8007045b
(Tue May 29 05:26:11 2007.53196) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 05:26:11 2007.53506) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 05:26:18 2007.60266) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 05:26:19 2007.61448) : NTLMLogin resulted in hr = 0x8004100e
(Tue May 29 04:17:10 2007.3111143) : ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x8007045b
(Tue May 29 04:17:10 2007.3111153) : ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x8007045b
(Tue May 29 04:17:12 2007.3114077) : ConnectViaDCOM, CoCreateInstanceEx resulted in hr = 0x8007045b
.......
===============================
Start Free Trial
[+][-]11.14.2007 at 11:09PM PST, ID: 20287383

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: Microsoft IIS Web Server, Microsoft Visual Basic.Net, Network Management
Tags: getuserdefaultlcid
Sign Up Now!
Solution Provided By: uetian1707
Participating Experts: 1
Solution Grade: A
 
 
[+][-]09.12.2008 at 08:53AM PDT, ID: 22461031

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 7-day free trial to view this Administrative Comment or ask the Experts your question.

 
[+][-]09.17.2008 at 07:07PM PDT, ID: 22506308

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 7-day free trial to view this Administrative Comment or ask the Experts your question.

 
 
Loading Advertisement...
20081112-EE-VQP-42 / EE_QW_2_20070628