Change Made to Enable 3270 SSO Does Not Set Out-Of-Date Flag

Last reviewed: March 19, 1998
Article ID: Q172373

The information in this article applies to:

  • Microsoft SNA Server, versions 3.0 and 3.0 Service Pack 1 (SP1)

SYMPTOMS

If the SNA Server Service is active and you make a change by selecting or clearing the "Enable 3270 Single Sign-On" check box via Host Security Domains (new with SNA Server 3.0 SP1), the SNA Server Service will not show "Out of Date" after the configuration is saved.

Although it appears that this change happens dynamically by the node, the change does not take place until the SNA Server Service is stopped and then restarted.

CAUSE

The "Out of Date" flag is not being set on the SNA Server when a change is made to the "Enable 3270 Single Sign-On" check box.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0 and 3.0 Service Pack 1 (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

MORE INFORMATION

With the fix applied, the SNA Server is updated and flagged "Out of Date" when this option is changed.

Keywords          : snahostsec kbfix3.00.sp2 kbnetwork
Version           : 3.0
Platform          : winnt
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: March 19, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.