Microsoft Knowledge Base Email Alertz

Applications unable to log and track errors in the event log

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 2252217 - Last Review: June 29, 2010 - Revision: 2.0

Applications unable to log and track errors in the event log

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you.Visit the Windows Vista Solution Center

SYMPTOMS


You may receive errors similar to the following in the Event Log of a machine:


Event ID: 10
Source : WinMgmt
Type: Error
Description:
Event filter with query "Select * from _InstanceCreationEvent where
TargetInstance ISA "Win32_NTLogEvent” AND
Targetinstance.LogFile.”System” AND
Tagetlnstance.SourceName="IMAService" AND
Tagetlnstance.EventCode=4035” could not be (re)activated in
namespace “//./root/CIMv2” because of error 0x80041010. Events may not be delvered through this filter until the problem is corrected.

From the wbemess.log

(Tue Apr 27 09:43:31 2010.211419593) : Could not activate filter select * from __InstanceCreationEvent where TargetInstance ISA "Win32_NTLogEvent" AND TargetInstance.LogFile="Application" AND TargetInstance.SourceName="CitrixHealthMon" AND TargetInstance.EventCode=1001 in namespace //./root/CIMv2. HR=0x80041010

(Tue Apr 27 09:43:31 2010.211419609) : Could not get class Win32_NTLogEvent for which intrinsic events are requested. Error code: 80041002

(Tue Apr 27 09:43:31 2010.211419609) : Failed to determine instance classes required by query 'select * from __InstanceCreationEvent where TargetInstance ISA "Win32_NTLogEvent" AND TargetInstance.LogFile="Application" AND TargetInstance.SourceName="Citrix Configuration Logging" AND TargetInstance.EventCode=1':0x80041010

(Tue Apr 27 09:43:31 2010.211419609) : Could not activate filter select * from __InstanceCreationEvent where TargetInstance ISA "Win32_NTLogEvent" AND TargetInstance.LogFile="Application" AND TargetInstance.SourceName="Citrix Configuration Logging" AND TargetInstance.EventCode=1 in namespace //./root/CIMv2. HR=0x80041010

(Tue Apr 27 09:43:31 2010.211419625) : Could not get class Win32_NTLogEvent for which intrinsic events are requested. Error code: 80041002

(Tue Apr 27 09:43:31 2010.211419625) : Failed to determine instance classes required by query 'select * from __InstanceCreationEvent where TargetInstance ISA "Win32_NTLogEvent" AND TargetInstance.LogFile="System" AND TargetInstance.SourceName="TermService" AND (TargetInstance.EventCode=1003 OR TargetInstance.EventCode=1004 OR TargetInstance.EventCode=1011 OR TargetInstance.EventCode=1028)':0x80041010

CAUSE

Per wbemcli.h, 0x80041010 translates to either WBEM_E_INVALID_CLASS or wbemErrInvalidClass. Based on the error, the Win32_NTLogEvent WMI class used to translate instances from the Windows NT event log is missing. It appears applications are using WMI to track errors in the application log and System log. They log the event 10 errors since they are unable to query the WMI class Win32_NTLogEvent.

According to MSDN, the MOF file that supports this class (Win32_NTLogEvent) is Ntevt.mof in the namespace \root\cimv2 using the DLL Ntevt.dll.

To confirm this issue :

1. Connect to the root\cimv2 namespace using WBEMTEST
2. Enumerate all classes recursively
3. Look for Win32_NTLogEvent () and the class would be missing.

RESOLUTION

To resolve the issue, recompile ntevt.mof and reregister ntevt.dll using the below commands:

mofcomp Ntevt.mof
regsvr32 Ntevt.dll
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

APPLIES TO
  • Microsoft Windows Server 2003 Service Pack 2
Keywords: 
KB2252217
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate