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.

Many instances of Error events 59 and 32 are logged in the System log on a Windows Server 2003-based terminal server


View products that this article applies to.

Symptoms

After you connect to a Microsoft Windows Server 2003-based computer that has Terminal Server enabled, many instances of the following Error events are logged in the System log.

Error event 1
Event Type: Error
Event Source: SideBySide
Event ID: 59
Description:
Generate Activation Context failed for c:\windows\system32\winlogon.exe. Reference error message: The referenced assembly is not installed on your system.
Error event 2
Event Type: Error
Event Source: SideBySide
Event Category: None
Event ID: 32
Description:
Dependent Assembly Microsoft.Windows.SystemCompatible could not be found and Last Error was The referenced assembly is not installed on your system.

Additionally, an error event that resembles the following may be logged in the System event log:
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: Date
Time: Time
User: N/A
Computer: Computer_Name
Description:
Application Popup: winlogon.exe - Unable To Locate Component : This application has failed to start because WINHTTP.dll was not found. Re-installing the application may fix this problem.


Additionally, when you try to restart the computer, you may receive the following error message:
winlogon.exe - Unable To Locate Component
This application has failed to start because WINHTTP.dll was not found. Re-installing the application may fix this problem.
The restart is delayed until this dialog box is closed.

↑ Back to the top


Cause

This problem occurs when you have version 5.2.3790.2426 or a more recent version of the Winlogon.exe program installed. For example, this problem occurs if you have applied the hotfix that is described in either of the following Microsoft Knowledge Base articles:
897040 A program that uses a remote access PPP connection to a Windows Server 2003-based computer is disconnected when the user logs off
908011 You cannot use a Group Policy setting to set the same mandatory profile for all the Terminal Services users in Windows Server 2003

↑ Back to the top


Resolution

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 Service Pack 1 (SP1) to install this hotfix.

Note x64-based versions of Windows Server 2003 do not require this service pack.

Restart requirement

You must restart your 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, x86-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Licdll.dll5.2.3790.2632450,04803-Feb-200603:47x86SP1SP1QFE
Winlogon.exe5.2.3790.2632509,44003-Feb-200603:32x86SP1SP1QFE
Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Licdll.dll5.2.3790.2632736,25603-Feb-200604:04x64SP1SP1QFE
Winlogon.exe5.2.3790.2632924,16003-Feb-200604:04x64SP1SP1QFE
Windows Server 2003, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Winlogon.exe5.2.3790.2632681,47203-Feb-200604:04IA-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. This problem was first corrected in Windows Server 2003 Service Pack 2.

↑ Back to the top


More information

For more information, 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

Technical support for Windows x64 editions

Your hardware manufacturer provides technical support and assistance for Microsoft Windows x64 editions. Your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about Microsoft Windows Server 2003 x64 editions, visit the following Microsoft Web site:

Note This hotfix may also resolve a problem that occurs when the computer stops responding during system shutdown when you try to install updates by using Automatic Updates.

↑ Back to the top


Keywords: kbautohotfix, kbwinserv2003presp2fix, kbqfe, kbexpertiseinter, kberrmsg, kbhotfixserver, KB914061

↑ Back to the top

Article Info
Article ID : 914061
Revision : 11
Created on : 10/11/2007
Published on : 10/11/2007
Exists online : False
Views : 328