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



The information in this article applies to:

  • Microsoft SNA Server 3.0
  • Microsoft SNA Server 4.0

This article was previously published under Q235423

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.

RESOLUTION

To resolve this problem, obtain the latest service pack for SNA Server version 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack


STATUS

Microsoft has confirmed that this is 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. This problem was first corrected in SNA Server version 4.0 Service Pack 3.

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.

Modification Type:MinorLast Reviewed:11/19/2003
Keywords:kbbug kbfix kbsna400sp3fix KB235423