Solved

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

Posted on 2007-11-13
3
11,950 Views
Last Modified: 2010-06-23
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
.......
===============================
0
Comment
Question by:azizparacha
3 Comments
 
LVL 32

Accepted Solution

by:
Kamran Arshad earned 500 total points
ID: 20287383
0

Featured Post

Backup Your Microsoft Windows Server®

Backup all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

The use of stolen credentials is a hot commodity this year allowing threat actors to move laterally within the network in order to avoid breach detection.
How to set-up an On Demand, IPSec, Site to SIte, VPN from a Draytek Vigor Router to a Cyberoam UTM Appliance. A concise guide to the settings required on both devices
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

867 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now