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.
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.
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.
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:
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.
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
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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.
6.0.600 2. 22xxx
Windows Vista and Windows Server 2008
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
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
For all supported IA-64-based versions of Windows Server 2008
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the EvtSubscribe function, visit the following Microsoft Developer Network (MSDN) website: