SNA Server Connection Stays Inactive

 Last reviewed: April 17, 1997
Article ID: Q125882

The information in this article applies to:
  • Microsoft SNA Server for Windows NT versions 2.0, 2.1, 2.11, 2.11 SP1, and 3.0

SUMMARY

An SNA Server connection may remain inactive. You cannot reactivate the connection using SNA Administrator. Here are some possible causes and resolutions:

The SNA Server Service Owning the Connection Is Inactive

Start the SNA Server service using SNA Server Admin (SNA Server 2.x) or SNA Server Manager (SNA Server 3.0). In order for the SNA Server service to start, all SNA Server link services installed by SNA Setup must also start successfully.

SNA Server Shows [Out of Date]

If a new connection is defined in SNA Server Admin or SNA Server Manager when SNA Server is running, the server status appears as "Active [Out of Date]." This indicates that the SNA Server service must be restarted to enable the configuration changes. When a new connection is created, the SNA Server service must be stopped and restarted to enable the change.

The SNA Server Backup Server Had an Old Configuration File

The SNABase service running on the SNA Server primary and backup configuration servers automatically handles the replication of the SNA Server configuration file. However, if security is enabled on the COMCFG share point, or NTFS file permissions restrict access to the configuration file, <SNAROOT>\SYSTEM\CONFIG\COM.CFG, the configuration file on the backup configuration server may be out of date. To test this, copy the configuration file from the primary to the backup server: 

   copy \\<primary>\comcfg\com.cfg \\<backup>\comcfg\com.cfg
where <primary> is the SNA Server primary configuration server and <backup> is the SNA Server backup server. After you copy the configuration file, you'll need to restart the SNA Server service on any backup servers.

By default, the SNABase service runs under the Windows NT Local System context. If the Everyone group does not have Read access to the COMCFG share point on the primary server, or Full Control access on the backup server, the replication to the backup server will fail.

See Chapter 12, "Setting Up Security with SNA Server," in the SNA Server Administrator's Guide for a full discussion on limiting user access to the SNA Server configuration file. In addition, Article Q140556 (Securing SNA Server to Not Require Everyone: Read Access) explains how to tighten the secuity on the SNA Server configuration file.

Additional query words: prodsna inactive connection
Keywords : kbnetwork snaadmin snamanager
Version : 2.0 2.1 2.11 3.0
Platform : WINDOWS

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 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.