Print Sessions Stop with Host Print Service

Last reviewed: February 11, 1998
Article ID: Q180864
The information in this article applies to:
  • Microsoft SNA Server, versions 3.0, 3.0 SP1, 3.0 SP2

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

An SNA Server computer using the Host Print service configured with a large number of print sessions may experience problems starting print sessions. When this occurs, print sessions may appear to stop responding or get stuck in a Spooling status when attempting to start the session or sessions. This problem may cause other symptoms as well.

NOTE: Due to the factors involved, there are no specifics on exactly how many print sessions can be defined before this problem may occur.

CAUSE

  
There is a limit on the number of DCs (Device Contexts) that can exist on a Windows NT Server computer at one time. The number of DCs that can be created depends on a number of factors; therefore, a specific number cannot be given. After the limit of DCs has been reached, the problem that occurs when starting print sessions may become apparent.
  
  

STATUS

  
Microsoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, and 3.0 SP2. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

The updated modules are Winvprt.dll and Ppd5250.dll.

MORE INFORMATION

  
An update has been made to Host Print service so that it can be configured to reject print jobs if there are already 30 (or a number configured in the registry) DCs open and also to log an Event 21 to the Windows NT Application event log. In this case, the SNA Print Server will return IBM Sense Code 0x0814 (Bracket BID Reject - RTR Forthcoming) to the host when a print job is rejected for this reason. The host should interpret this error as meaning that the print job can be re-sent at a later time.
  
NOTE: The SNA Print service may reject print jobs for reasons other than this, which would result in the same IBM sense code being returned to the host.

If there is a need to control how many DCs the print server is allowed to create, follow these steps:

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.

  1. Apply the hotfix.
2. Start the Windows NT Registry Editor (Regedt32.exe) and find the
   following key:
       
       HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SnaPrint
       \Parameters\
       
   Add the following entry to this key:
   
       Value Name: MaxGDISessions
       Data Type: REG_SZ
       String: <value>
  
  where value is 1 - 30.
  
In addition, the limit of 30 DCs is not applicable if the host print sessions are configured to use a PDF file. Print sessions configured to use a PDF file do not create DCs, and they do not make any other Graphical Device Interface (GDI) calls.

Keywords          : prodsna snaprintservice kbbuglist kbfixlist
Version           : WINDOWS:3.0,3.0SP1,3.0SP2
Platform          : WINDOWS
Hardware          : x86
Issue type        : kbbug
Solution Type     : kbfix


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 11, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.