"Stop 0x1E" or "Stop 0x50" with Terminal Services Client Print Session (279343)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional
This article was previously published under Q279343 SYMPTOMS
A Windows 2000-based Terminal Services server may generate a "Stop 0x1E" or "Stop 0x50" error message during a Terminal Services client print session. This may be caused by selecting a particular font in the document that is being printed. Such fonts include:
- Type 1 multiple master fonts (legacy fonts)
- Far East fonts containing both English and a localized name
This problem can occur if such fonts are installed on the computer or are accessed as printer fonts.
CAUSE
The error is caused by a comparison operation within the font data.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
--------------------------------------------------------
11/11/2000 12:01a 5.0.2195.2291 222,480 Gdi32.dll
11/11/2000 12:01a 5.0.2195.2303 379,152 User32.dll
11/10/2000 11:45p 5.0.2195.2715 1,639,760 Win32k.sys
11/11/2000 12:01a 5.0.2195.2228 243,472 Winsrv.dll
WORKAROUND
You may be able to work around this problem by changing the printer driver to a substitute driver.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbWin2000PreSP2Fix KB279343 |
---|
|