Event ID: 56 with Distributed Link Services to AS/400 (141592)



The information in this article applies to:

  • Microsoft SNA Server 4.0 SP4
  • Microsoft Host Integration Server 2000
  • Microsoft Host Integration Server 2000 SP1
  • Microsoft Host Integration Server 2004

This article was previously published under Q141592

SYMPTOMS

Event ID: 56 appears in the SNA Server Application log when you have Distributed Link Services (DLS) connected to an AS/400. Detail information from of the event is:
Event 56: Connection <connection> failed: XID rejected by remote computer
The connection becomes Pending, but never becomes active. The AS/400 shows an error such as (use DSPMSG QSYSOPR to view AS/400 system operator messages):
CPA575D: Controller CNIRV02 on line ETHLINE not contacted. Probable configuration problem.
For more information about Event 56 and other AS/400 connection problems, click the following article number to view the article in the Microsoft Knowledge Base:

126393 SNA Server configurations that produce XID rejections

CAUSE

The AS/400 does not create a second controller for the same MAC address and the same RSAP (Remote Source Access Point). This is defined in SNA Server as the link service SAP in SNA Server Setup, not the connection's Remote SAP Address. If there is a controller already created for a particular line that shares a MAC address and RSAP with a pending connection, the AS/400 attempts to use the existing controller. This does not present a problem if the SNA Server Control Point Name and the MAC address on the Host Integration Server or SNA Server match the Control Point Name and the LAN Remote Adapter Address respectively on the AS/400 controller description. Otherwise, the AS/400 generates an error message that states that there was a problem activating the offending controller.

RESOLUTION

To resolve this problem, use one of the following methods:
  • Reconfigure the controller on the AS/400 to match the desired parameters.
  • Delete the controller on the AS/400 and allow it to auto- create.
  • Match the Control Point Name of the SNA Server using the SNA Manager only if the Control Point Name is not in use by any other device.

Modification Type:MajorLast Reviewed:5/6/2005
Keywords:kb3rdparty kbprb KB141592