J
Joe Campbell
I am encountering a problem raising WMI events from an
asp.net application. The error received (as captured in
the event log) is as follows:
System.Runtime.InteropServices.COMException (0x80041003):
Exception from HRESULT: 0x80041003.
at
Microsoft.EnterpriseInstrumentation.EventSinks.WmiEventSink
..Write(Object eventToRaise)
at
Microsoft.EnterpriseInstrumentation.EventSource.RaiseEvent
(Object eventToRaise, RequestContext requestContext)
Trawling Google has revealed that this is an access denied
exception when the asp user tries to interact with WMI to
raise events. When the event raising code is executed as a
console application (as the currently logged in user) the
event is raised correctly to WMI.
To try to fix this problem I have:
Given all permissions to "everyone" to all WMI namespaces.
Given all permissions to aspnet user on all WMI namespaces.
Some of the literature on the Internet mentions turning on
impersonation within the asp application to solve this.
This is not a possibility as it is a requirement that
users will access the site anonymously. Hence anonymous
access is enabled within IIS and windows integrated
authentication is enabled.
I am running .net framework 1.1 on a windows 2000 server
sp4 system.
Any pointers are much appreciated.
Joe
asp.net application. The error received (as captured in
the event log) is as follows:
System.Runtime.InteropServices.COMException (0x80041003):
Exception from HRESULT: 0x80041003.
at
Microsoft.EnterpriseInstrumentation.EventSinks.WmiEventSink
..Write(Object eventToRaise)
at
Microsoft.EnterpriseInstrumentation.EventSource.RaiseEvent
(Object eventToRaise, RequestContext requestContext)
Trawling Google has revealed that this is an access denied
exception when the asp user tries to interact with WMI to
raise events. When the event raising code is executed as a
console application (as the currently logged in user) the
event is raised correctly to WMI.
To try to fix this problem I have:
Given all permissions to "everyone" to all WMI namespaces.
Given all permissions to aspnet user on all WMI namespaces.
Some of the literature on the Internet mentions turning on
impersonation within the asp application to solve this.
This is not a possibility as it is a requirement that
users will access the site anonymously. Hence anonymous
access is enabled within IIS and windows integrated
authentication is enabled.
I am running .net framework 1.1 on a windows 2000 server
sp4 system.
Any pointers are much appreciated.
Joe