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.

Windows Event Collector stops responding when it tries to process System event log data on a computer that is running Windows Server 2003 R2


View products that this article applies to.

Symptoms

When Microsoft Windows Event Collector tries to process System event log data, Event Collector stops responding and data is not written to the expected log files. This behavior occurs on a computer that is running an English version of Microsoft Windows Server 2003 R2.

↑ Back to the top


Cause

This problem occurs when Russian or German is selected as the Language for non-Unicode programs regional setting.

↑ Back to the top


Workaround

To work around this problem, change the Language for non-Unicode programs regional setting from the selected language back to English (United States). To change this setting, follow these steps:
  1. Click Start, click Run, type intl.cpl, and then click OK.
  2. In the Regional and Language Options dialog box, click the Advanced tab.
  3. In the Language for non-Unicode programs area, select English (United States), and then click OK.

↑ Back to the top


Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

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 this specific problem. 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 Web site: 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

You must be running Windows Server 2003 R2 to install this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003 R2, 64-bit x64-based versions
File nameFile versionFile sizeDateTimePlatform
Wsmselpl.dll5.2.3790.2703181,24816-May-200603:30x64
Windows Server 2003, 64-bit Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Wsmselpl.dll5.2.3790.2703270,33616-May-200603:29IA-64
Windows Server 2003, 32-bit x86-based versions
File nameFile versionFile sizeDateTimePlatform
Wsmselpl.dll5.2.3790.2703104,96016-May-200603:10x86

↑ 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. This problem was first corrected in Windows Server 2003 Service Pack 2.

↑ Back to the top


Keywords: kbautohotfix, kbwinserv2003sp2fix, kbserver, kbqfe, kbhotfixserver, kbfix, KB919256

↑ Back to the top

Article Info
Article ID : 919256
Revision : 10
Created on : 3/27/2007
Published on : 3/27/2007
Exists online : False
Views : 135