Microsoft KB Archive/169370
Article ID: 169370
Article Last Modified on 6/29/2004
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
This article was previously published under Q169370
When 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:
When 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.
There are two font handle leaks:
- When fonts are created and then rejected as the wrong width, they are not subsequently deleted. The Sprtintx.trc shows the rejection as:
- The fonts created and stored in an array to use in a document are not properly freed when the document is finished printing.
Microsoft 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: kbbug kbfix kbnetwork KB169370