Unable to Start Print Sessions Until Print Service Restarted

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

SYMPTOMS

Print sessions defined in the SNA Server Print Service may go to an Inactive or Pending state requiring the print server be restarted to reactivate the sessions. This may occur with both LU1 and LU3 printing. The SNA Server Print Server may send a badly formatted Open PLU Response to the SNA Server service that the SNA Server will reject.

CAUSE

An uninitialized field in the SNA Server Print Service could cause the sending of a badly formatted OPEN PLU RSP to the SNA Server service, which logs an error and rejects it. This causes the print session to fail to activate.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0, 3.0 Service Pack 1 (SP1), 3.0 SP2, and 4.0. 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 Product Support Services for more information.

Keywords          : kbbug3.00 kbbug3.00.sp1 prodsna snaprintservice kbbug3.00.sp2 kbbug4.00 kbbuglist
Version           : WINDOWS:3.0,3.0SP1,3.0SP2,4.0
Platform          : WINDOWS
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.