Incoming SDLC Connections Log Event 182 and Fail to Activate (305160)
The information in this article applies to:
- Microsoft SNA Server 3.0
- Microsoft SNA Server 3.0 SP1
- Microsoft SNA Server 3.0 SP2
- Microsoft SNA Server 3.0 SP3
- Microsoft SNA Server 3.0 SP4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 SP1
- Microsoft SNA Server 4.0 SP2
- Microsoft SNA Server 4.0 SP3
- Microsoft SNA Server 4.0 SP4
- Microsoft Host Integration Server 2000
This article was previously published under Q305160 SYMPTOMS
A Synchronous Data Link Control (SDLC) connection that is configured with Allowed Directions set to Incoming may log the following event message and fail to connect to the host system:
Event ID: 182
Source: SNA SDLC Link Service
Description: Connection failure, code = 11
Cause Data = 3601 3401 3302 f035
Link Role = 02
Remote Node Type = 03
The connection failure code in the Event 182 message indicates a Data Set Ready (DSR) failure.
The other symptom associated with this problem is that the SDLC Link Service sends a NULL Exchange Identifier (XID) to the host system when the SDLC connection is activated. This should not occur when the SDLC connection is configured as an incoming connection.
The following Microsoft Knowledge Base article describes a similar problem that existed for X.25 connections:
180706 Incoming X.25 Host Connection Indicates Primary Link Role
CAUSE
The link role (that is, primary, secondary, or negotiable) is incorrectly set to negotiable in the internal link data record for an incoming SDLC connection. The internal link data record is written when the SNA configuration file (Com.cfg) is saved after the connection is created or modified.
A link role of negotiable causes the SDLC link service to send an initial NULL XID to the remote system when the connection is activated. The correct link role for an incoming SDLC connection is secondary.
RESOLUTIONSNA Server 4.0A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SNA Server version 4.0 that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
|
Aug-06-2001 | 14:31 | Snacfg.dll | NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.
Host Integration Server 2000To resolve this problem, obtain the latest service pack for Host Integration Server 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
328152 How to Obtain the Latest Host Integration Server 2000 Service Pack
The English version of this fix should have the following file attributes or later:
|
Sep-11-2001 | 15:35 | Snacfg.dll | NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Host Integration Server 2000 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 10/6/2005 |
---|
Keywords: | kbBug kbfix kbHostIntegServ2000preSP1fix kbHostIntegServ2000SP1fix KB305160 |
---|
|