Print Server Access Violation When Starting First Session

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

SYMPTOMS

When you try to start a session using SNA Server Print service, an access violation may occur when the first print session is started. The following symptoms occur when this problem happens:

- An Event 624 will be logged, indicating that the SNA Print service has 

 ended abnormally.
- An entry may be created in the <ntroot>\drwtsn32.log file, indicating an 
 access violation (0xC0000005) in snaprint.exe.

CAUSE

In a rare timing condition, an uninitialized variable causes the SNA Print service to access an invalid memory location when the first print session is started.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0, 3.0 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          : prodsna snaprintservice kbbuglist kbfixlist
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 10, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.