Microsoft KB Archive/873399

= Host Integration Server 2004 does not return a negative response when an IPDLC connection is inactivated =

Article ID: 873399

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft Host Integration Server 2004 Standard Edition

-





SYMPTOMS
When an IP data link connection (IPDLC) connection is inactivated while the host sends a bind request, Microsoft Host Integration Server 2004 does not return negative response and the host waits indefinitely.



CAUSE
When an IPDLC connection is inactivated while the host sends a bind request, it is still passed to the Host Integration Server service to open an incoming connection. The Host Integration Server service does not respond to the eXchange Identifier (XID). Therefore, the IPDLC does not respond to the bind request.



RESOLUTION
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.  Date         Time   Version            Size    File name --  20-Aug-2004  17:34  6.0.1903.0        959,488  Snaipdlc.dll 20-Aug-2004 17:34  6.0.1903.0        407,552  Snaservr.exe 20-Aug-2004 17:35  6.0.1903.0      2,944,000  Trcipdlc.dll 20-Aug-2004 17:34  6.0.1903.0        847,360  Trcservr.exe

Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For an inactive connection, the Host Integration Server 2.1 node actually sends an Open (LINK) request message to the DLC to accept incoming connections. However, the Open (LINK) request message then drops any XIDs that the Open (LINK) request message receives on that connection. The IPDLC link service always expects a response to its XIDs because no network connection is involved, but the IPDLC link service does not receive a response.

The Host Integration Server 2.1 node responds to the XID3 with an error if the originator is an IPDLC link service. Additionally, the following error is logged from the IPDLC link service in the application event log:

Event Type: Error

Event Source: SNA IP-DLC Link Service

Event Category: APPN Event

ID: 543

Date: 09/07/2004

Time: 12:04:10

User: \

Computer:

Description: Unable to identify or activate the next hop of an ISR session

Sense code = 0x80020000

FQPCID =  :cf9f9a75 b77b3576

Primary LU name =

Secondary LU name =

BIND RU :

31001307 b0b05033 3fbfb7a7 bf3f0602 00000000 00004014 2300000b c1d7d7d5 4bc2e4d9 e3d6d52b 0007027b c9d5e3c5 d9090301 9f9a75b7 7b35760c 04c1d7d7 d54bc2e4 d9e3d6d5 0a1300db 26040928 b8d31900 0bc1d7d7 d54bd6d3 e3c5e2e3 0a2c0206 7bc9d5e3 c5d96014 cf9f9a75 b77b3576 0bc1d7d7 d54bc2e4 d9e3d6d5

Cause:

Unable to identify or activate the next hop of an ISR session.

Effect:

ISR session activation will fail with the specified sense code.

Action: This log is preceded by other logs giving more specific reasons for the failure. Follow the actions given in those logs.

For more information, see Help and Support Center at http://support.microsoft.com.

Data:

0000: 53 4e 41 49 50 31 2c 20 SNAIP1,

0008: 30 0

Additional query words: HIS2004

Keywords: kbbug kbfix kbqfe kbhotfixserver KB873399

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.