"Stop 0x1E" or "Stop 0x50" with Terminal Services Client Print Session

View products that this article applies to.

This article was previously published under Q279343

Expand all | Collapse all

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.

Back to the top

CAUSE

The error is caused by a comparison operation within the font data.

Back to the top

RESOLUTION

To 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 (http://support.microsoft.com/kb/260910/EN-US/ ) 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

Back to the top