Connection for Downstream PU Fails to Reactivate After Outage

Last reviewed: April 14, 1997
Article ID: Q165656
The information in this article applies to:
  • Microsoft SNA Server, version 3.0

SYMPTOMS

A downstream connection fails to activate after an outage even though both stations are ready.

CAUSE

If SNA Server received a reactivation XID while it was processing the outage, it would set the link in a state from which it could not reactivate. The connection would have to be manually reset for it to reactivate.

NOTE: This article is related to the following Knowledge Base article, which documents a similar (but not identical) issue for SNA Server version 2.11:

   ARTICLE-ID: Q150472
   TITLE     : Downstream PU Fails to Reactivate After an Outage

RESOLUTION

The components have been instructed to not pass reactivation XIDs to the server component until it has finished processing the outage.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0. This problem was corrected in the latest Microsoft SNA Server 3.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K


Additional query words: dspu down stream
Keywords : kbbug3.00 kbfix3.00.sp1 kbnetwork prodsna snadlc
Version : 3.0
Platform : WINDOWS
Issue type : kbbug
Resolution 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: April 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.