Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. You cannot receive event notifications after you back up and then clear event logs in Windows Server 2008 or in Windows Vista

You cannot receive event notifications after you back up and then clear event logs in Windows Server 2008 or in Windows Vista

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2008 or Windows Vista.
  • You subscribe to receive notifications when some specific events are added to event logs. For example, you subscribe to receive a notification when a specific event is added to the security event log.
  • You back up and then clear the event logs.
In this scenario, you cannot receive event notifications when new specified events are added to the event logs.

Notes
  • This issue affects any program that uses the EvtSubscribe function.
  • The issue does not occur in Windows Server 2008 R2 or in Windows 7.


Here is a sample scenario:
  • You install Microsoft System Center Operations Manager 2007 on a server in a domain environment.
  • You install the System Center Operations Manager 2007 agent on a client computer that is running Windows Server 2008 in the domain.
  • You create a rule on the client computer to generate a message when a specified event is added to the security event log.
  • You can receive a message when the specified event is added to the security event log.
  • You back up and then clear the security event log.
In this scenario, you cannot receive messages for any specified events that are added to the security event log.

↑ Back to the top

Cause

The issue occurs because the Windows Event Log service does not restore the next logical record number when it creates a new event log file after you back up and then clear the event log.

The Windows Event Log service maintains a state for each subscription. The state includes the value of last event record number. Before the Windows Event Log service passes an event to subscriber, it checks whether this event is a past event. If this event is a past event, the service does not pass the event to the subscriber.

If the Windows Event Log service does not pass the next logical record number when it creates a new event log file, the logical record number is reset to 1. This behavior causes the Windows Event Log service to incorrectly handle new events as past events after an event log is cleared. Therefore, you cannot receive event notifications.

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 Service Pack 2 (SP2) or Windows Vista SP2.

For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack

For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    2.
    22xxx    		Windows Vista and Windows Server 2008SP2LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Wevtsvc.dll6.0.6002.225211,020,41609-Nov-201019:49x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Wevtsvc.dll6.0.6002.225211,495,04009-Nov-201020:18x64
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Wevtsvc.dll6.0.6002.225212,706,94409-Nov-201019:03IA-64

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

More Information


For more information about the EvtSubscribe function, visit the following Microsoft Developer Network (MSDN) website:
General information about the EvtSubscribe function

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameX86_0db67e37c7564e4878854ff89853e0f6_31bf3856ad364e35_6.0.6002.22521_none_f4b67af113d62fa1.manifest
File versionNot applicable
File size696
Date (UTC)10-Nov-2010
Time (UTC)01:17
PlatformNot applicable
File nameX86_microsoft-windows-eventlog_31bf3856ad364e35_6.0.6002.22521_none_df1fd889292c61bc.manifest
File versionNot applicable
File size47,715
Date (UTC)09-Nov-2010
Time (UTC)20:08
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_c27af8e322be6a27b355898be2b620f2_31bf3856ad364e35_6.0.6002.22521_none_443163834ff04f98.manifest
File versionNot applicable
File size700
Date (UTC)10-Nov-2010
Time (UTC)01:17
PlatformNot applicable
File nameAmd64_microsoft-windows-eventlog_31bf3856ad364e35_6.0.6002.22521_none_3b3e740ce189d2f2.manifest
File versionNot applicable
File size47,983
Date (UTC)09-Nov-2010
Time (UTC)20:36
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_326ec5a83d6a9815925eb0531c54cd36_31bf3856ad364e35_6.0.6002.22521_none_c4b6302e2cb2016f.manifest
File versionNot applicable
File size698
Date (UTC)10-Nov-2010
Time (UTC)01:17
PlatformNot applicable
File nameIa64_microsoft-windows-eventlog_31bf3856ad364e35_6.0.6002.22521_none_df217c7f292a6ab8.manifest
File versionNot applicable
File size47,973
Date (UTC)09-Nov-2010
Time (UTC)19:14
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2458331
Revision : 1
Created on : 1/7/2017
Published on : 2/1/2011
Exists online : False
Views : 405