Microsoft KB Archive/817985

= A Terminal Services Server May Stop Working Because of a Client License That Is Not Valid =

Article ID: 817985

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 6

-



SYMPTOMS
Termsrv.exe may stop working when a Terminal Services client with a corrupted license connects to the Terminal Services server. When this problem occurs, the Drwatson log file contains these entries:

Application exception occurred:

App: exe\termsrv.dbg (pid=277)

When:  @

Exception number: c0000005 (access violation)



RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) 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.   Date         Time   Version         Size    File name --  03-Jun-2003  12:26  4.0.1381.33548  70,928  Icaapi.dll Note Because of file dependencies, this hotfix requires Microsoft Windows NT 4.0 Service Pack 6a.



STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0.

This problem does not occur in Microsoft Windows 2000 or later versions of Microsoft Windows.

Keywords: kbhotfixserver kbqfe kbfix kbbug KB817985

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.