SNA Server Print Stuck in InSession StatusLast reviewed: March 19, 1998Article ID: Q169370 |
The information in this article applies to:
SYMPTOMSWhen you print through the SNA Server Print Service, a print session may get stuck in InSession status and never print. This usually happens after many print jobs have printed to this logical SNA Server Printer. The following trace excerpt from the Sprtintx.trc file shows where this problem occurs. The Windows NT api call, CreateFontIndirect(), returns a null pointer, thus giving the following error message:
winvprtj.c(762) FONTM ERROR CreateFontIndirect failed, rc=0x20000017When this error occurs, the SNA Server Print service attempts to cycle through initializing the Windows NT print again, but continues to fail with the same error. The administrator must stop the SNA Server Print service and restart to temporarily correct this problem. NOTE: If the print session is configured for a PDT file, the result is that the printer prints some errors at the top of the page.
CAUSEThere are two font handle leaks:
STATUSMicrosoft has confirmed this to be a problem in SNA Server 3.0 and 3.0 sp1. This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K Keywords : prodsna snaprintservice kbfix3.00.sp2 kbnetwork Platform : WINDOWS |
================================================================================
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |