Cannot Open Configuration File if CPI-C Symbolic Name Has an Invalid LU Name

ID: Q235423

The information in this article applies to:

Microsoft SNA Server, versions 3.0, 3.0SP1, 3.0SP2, 3.0SP3, 3.0SP4, 4.0, 4.0SP1, 4.0SP2

SYMPTOMS

Opening an SNA Server configuration file (for example Com.cfg) results in the following error message:

SnaOle

The Partner LU specified for the CPI-C Symbolic Destination Name does not exist.

If you click the OK button in the error dialog box, a blank screen is displayed in the SNA Server Manager.

Attempting to dump the contents of the same SNA Server configuration file using SNA Server's offline configuration tool (Snacfg.exe.EXE) results in the following error:

Config file is: <path>\<configuration file name>
The Partner LU specified for the CPI-C Symbolic Destination Name does not exist.

CAUSE

An SNA Server Manage component incorrectly handles a non-fatal error, which results in the failure to open a configuration file that contains a CPI-C Symbolic Destination Name that refers to a Partner LU that no longer exists in the configuration file.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, 3.0 SP3, 3.0 SP4, 4.0, 4.0 SP1, 4.0 SP2.

MORE INFORMATION

This problem can occur if an SNA Server configuration file contains a CPI-C Symbolic Destination Name that is configured with a Partner LU Name that no longer exists in the configuration. When you delete Remote APPC LUs from an SNA Server configuration, existing CPI-C Symbolic Destination Names should be checked to make sure that they do not refer to these deleted APPC LUs.

CPI-C Symbolic Destination Names are global to the SNA Server subdomain, so this problem may also occur when you remove an SNA Server computer from the configuration, as removing the SNA Server computer will also remove all APPC LUs defined for that SNA Server computer.

Additional query words:


Keywords          : sna3 sna3sp1 sna3sp2 sna3sp3 sna3sp4 sna4 sna4sp1 sna4sp2 
Version           : WINDOWS:3.0,3.0SP1,3.0SP2,3.0SP3,3.0SP4,4.0,4.0SP1,4.0SP2
Platform          : WINDOWS 
Issue type        : kbbug

Last Reviewed: June 18, 1999