LPD Job May Cause TCPSVCS to Hang

ID: Q197253

The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Server, Enterprise Edition version 4.0
  • Microsoft Windows NT Server version 4.0, Terminal Server Edition

SYMPTOMS

After you sent a print job by using LPR to the TCP/IP Print Server, the TCP/IP Print server stops responding (hangs) and causes over 90 percent CPU usage in TCPSVCS.


CAUSE

This behavior occurs when the print job contains a value of 0x1B (ESC) in any of the following conditions:

  • At offset 0xFFF (4095).


  • As the very last character in a file.


  • As the only character in a file.


TCPSVCS has a routine to detect PCL or PostScript jobs, which goes into an infinite loop under these conditions.


RESOLUTION

Windows NT 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.asp

Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the Microsoft Knowledge Base:
Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack


STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 5 and Windows NT Server 4.0, Terminal Server Edition Service Pack 5.

Additional query words: 4.00 tcpsvcs.exe

Keywords : kbbug4.00 kbfix4.00 nt4sp5fix
Version : winnt:4.0
Platform : winnt
Issue type : kbbug


Last Reviewed: November 23, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.