Article ID: 305160
Article Last Modified on 2/20/2007
APPLIES TO
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 3.0 Service Pack 2
- Microsoft SNA Server 3.0 Service Pack 3
- Microsoft SNA Server 3.0 Service Pack 4
- Microsoft SNA Server 4.0
- Microsoft SNA Server 4.0 Service Pack 1
- Microsoft SNA Server 4.0 Service Pack 2
- Microsoft SNA Server 4.0 Service Pack 3
- Microsoft SNA Server 4.0 Service Pack 4
- Microsoft Host Integration Server 2000 Standard Edition
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:
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.
RESOLUTION
SNA Server 4.0
A 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:
| Date | Time | File name |
|---|---|---|
| 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 2000
To 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:
| Date | Time | File name |
|---|---|---|
| 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.
STATUS
Microsoft 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.
MORE INFORMATION
Once the updated Snacfg.dll file has been applied, the SNA Server Manager program must be run and the configuration file must be resaved after you make a configuration file change. In this case, the easiest change to make is to change the SDLC connection's "Allowed Directions" value from "Incoming" to "Outgoing" and back to "Incoming".
Host connections can be configured with one of the following Allowed Directions settings in SNA Manager:
- Outgoing
- Incoming
- Both Directions
If Outgoing is selected, SNA Server or Host Integration Server (HIS) 2000 initiate the link-level (that is, SDLC or DLC) connection to the remote system. If the remote system attempts to initiate the connection, SNA Server or HIS 2000 does not accept the connection attempt.
If Incoming is selected, SNA Server or HIS 2000 do not attempt to initiate the link-level connection. In this case, the connection is not activated until the remote system initiates the link-level connection. In this case, an initial XID is not sent by SNA Server or HIS 2000.
If Both Directions is selected, SNA Server or HIS 2000 can initiate the link-level connection and accept incoming connection activation requests from the remote system.
Additional query words: HIS 2000
Keywords: kbbug kbfix kbhostintegserv2000sp1fix kbhostintegserv2000presp1fix KB305160
