Microsoft KB Archive/326900

= FIX: Stop XID Exchange When It Does Not Complete =

Article ID: 326900

Article Last Modified on 10/21/2005

-

APPLIES TO


 * Microsoft Host Integration Server 2000 Standard Edition

-



This article was previously published under Q326900



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SUMMARY
Under certain error conditions, when the SNA Server service tries to open a connection, the Exchange Identifiers (XIDs) that are exchanged between two link stations to establish a connection cannot be negotiated. This behavior causes a perpetual XID negotiation deadlock situation.

In the Host Integration Server 2000 Management Console snap-in, the affected connection shows a pending status. If a client application is started at this time, the application is queued up. However, the application stops responding because it is not notified that the connection cannot be established.

By using the fix that is described in the &quot;More Information&quot; section, you can add a counter, so that you can stop this XID negotiation after a set number of tries. 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



MORE INFORMATION
A supported feature that modifies the product's default behavior is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if the system is not severely affected by the lack of this feature, we recommend that you wait for the next Product Name service pack that contains this feature.

To obtain this feature immediately, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

The English version of this fix has the file attributes (or later) 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 --  16-May-2002    21:49   5.0.0.860    98,576   Snadlc.dll WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

After you apply this fix, you can manually add a registry entry to turn on this functionality. To do this, follow these steps:  Start Registry Editor (Regedt32.exe).  Locate and then click the following key in the registry:

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SnaDlcx\Parameters \ExtraParameter

where x stands for the appropriate instance of the Link Service, (for example, SnaDlc1).   On the Edit menu, click Add Value, and then add the following registry value:   Value name: XIDAbortCounter Data type: REG_DWORD DWORD: 1 - 20 (Decimal)

</li> Quit Registry Editor. When you set this DWORD, XID negotiation stops after the specified number of completed XID negotiation attempts if the link connection cannot be established. When negotiation stops, an Event 23 that has Outage code 0x29 is logged in the Application Event log.</li></ol>

NOTE: Because of file dependencies, the most recent fix that contains the preceding files may also contain additional files.

Additional query words: XID NULL hang abo rt

Keywords: kbinfo kbbug kbhostintegserv2000sp1fix kbhostintegserv2000presp1fix kbhis2000bug KB326900

-

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

© Microsoft Corporation. All rights reserved.