The Terminal Server Licensing tool may unexpectedly quit after you install Windows Server 2003 Service Pack 1 on a Terminal Server

Consider the following scenario:

• You start the Terminal Server Licensing tool (Licmgr.exe), and then connect to a Terminal Server license server.
• You click the Windows Server 2003 - Terminal Server Per User CAL Token node in the left pane.
• You press F5 or click Refresh on the View menu to update the display.

In this scenario, the Terminal Server Licensing tool may unexpectedly quit (crash). You may experience this problem after you install Microsoft Windows Server 2003 Service Pack 1 (SP1) on the Terminal Server.

This problem occurs because of a problem in the Licmgr.exe program that is included with Windows Server 2003 SP1. An access violation error may occur in the Licmgr.exe program.

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:

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 apply this hotfix.

Note x64-based versions of Windows Server 2003 include SP1.

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 tool in Control Panel.

Windows Server 2003 with SP1, 32-bit versions

Windows Server 2003, x64-based versions

Windows Server 2003 with SP1, Itanium-based versions

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.

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