Microsoft KB Archive/125882

= SNA Server connection stays inactive =

Article ID: 125882

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft Host Integration Server 2004 Standard Edition
 * Microsoft Host Integration Server 2000 Standard Edition
 * Microsoft SNA Server 2.0
 * Microsoft SNA Server 2.1
 * Microsoft SNA Server 3.0
 * Microsoft SNA Server 2.11 Service Pack 1
 * Microsoft SNA Server 2.11 Service Pack 2
 * Microsoft SNA Server 3.0 Service Pack 4
 * Microsoft SNA Server 4.0
 * Microsoft SNA Server 3.0 Service Pack 2
 * Microsoft SNA Server 4.0
 * Microsoft SNA Server 4.0 Service Pack 1

-



This article was previously published under Q125882



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), SNA Server Manager (SNA Server 3.0), or SNA Manager (Host Integration Server). 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, \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 \\ \comcfg\com.cfg \\ \comcfg\com.cfg

where is the SNA Server primary configuration server and 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 in SNA Server versions prior to 3.0. SNA Server services including SNABase normally run under a user account specified during SNA Server Setup for SNA Server versions 3.0 and later. 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 140556 (Securing SNA Server to Not Require Everyone: Read Access) explains how to tighten the secuity on the SNA Server configuration file.

Additional query words: HIS2004 HIS 2000prodsna inactive connection snafaq

Keywords: kbinfo kbnetwork KB125882

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.