Microsoft KB Archive/922405

= FIX: An APPC BIND request may fail in Host Integration Server 2004 =

Article ID: 922405

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft Host Integration Server 2004 Enterprise Edition
 * Microsoft Host Integration Server 2004 Standard Edition

-



SYMPTOMS
An Advanced Program-to-Program Communications (APPC) BIND request may fail in Microsoft Host Integration Server 2004. This problem occurs if the following conditions are true:
 * You automatically activate an APPC session that uses an IP-DLC connection.
 * The IP-DLC connection is configured to use a primary network node server (NNS) and a backup NNS.

When this problem occurs, events that resemble the following are logged in the Application log:

Event message 1

Event Source: SNA IP-DLC Link Service

Event Type: Error

Event ID: 533

Description:

Locate search failed: LU not found

Sense code = 0x08400007

Origin CP name =.

Origin LU name =.

Destination LU name =.

Event message 2

Event Source: SNA IP-DLC Link Service

Event Type: Error

Event ID: 543

Description:

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

Sense code = 0x08400007

FQPCID =

Primary LU name =.

Secondary LU name =.

BIND RU :

Event message 3

Event Source: SNA Server

Event Type: Information

Event ID: 18

Description:

APPC session activation failure: BIND negative response or UNBIND request received

Sense data = 08400007 (NOTE: 0032xxxx indicates UNBIND received)

Connection =

LU alias =

PLU alias =

Mode name = SNASVCMG



CAUSE
This problem occurs when the IP-DLC link service receives an APPC BIND request when the IP-DLC link service is switching control point to control point (CP-CP) sessions from the backup NNS to the primary NNS. The Microsoft SNA Server service (Snaservr.exe) receives sense code 08400007 from the IP-DLC link service. The SNA Server service processes this sense code as an unrecoverable error. Therefore, the SNA Server service does not try to activate the APPC session again.



Hotfix information
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

File information
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 item in Control Panel.

Note Because of file dependencies, the most recent hotfix 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
After you apply this hotfix, the SNA Server service processes sense code 08400007 as a recoverable error. Therefore, the SNA Server service tries to activate the automatically activated APPC session based on the BINDRETRY setting. By default, the BINDRETRY setting configures the SNA Server service to retry APPC BIND requests for automatically activated APPC sessions every 10 seconds.

The following events describe this problem and how this hotfix resolves this problem:
 * 1) The IP-DLC connection is configured to use a primary NNS and a backup NNS.
 * 2) When the SNA Server service starts, the Advanced Peer-To-Peer Networking (APPN) component in the IP-DLC link service tries to start High Performance Routing/Internet Protocol (HPR/IP) links to the primary NNS and to the backup NNS.
 * 3) The backup NNS responds to the IP-DLC link service before the primary NNS responds.
 * 4) The IP-DLC link service establishes CP-CP sessions to the backup NNS.
 * 5) The SNA Server service establishes the internal peer connection to the IP-DLC link service.
 * 6) The IP-DLC link service establishes a link to the primary NNS. Therefore, the SNAP-APPN component of the IP-DLC link service determines that the CP-CP sessions to the backup NNS should be ended.
 * 7) The SNA Server service establishes the internal peer connection to the IP-DLC link service and issues an independent APPC BIND request to one of the automatically activated APPC sessions.
 * 8) The APPN component of the IP-DLC link service rejects the APPC BIND request. The APPN component does this because the IP-DLC link service does not have CP-CP sessions established to the primary NNS. The IP-DLC link service cannot locate the destination without the CP-CP sessions. Therefore, the APPN component rejects the APPC BIND request that has sense code 08400007.
 * 9) The IP-DLC link service ends the CP-CP sessions to the backup NNS.
 * 10) The IP-DLC link service establishes the CP-CP sessions to the primary NNS.
 * 11) The updated SNA Server service retries the APPC BIND request, and the APPC sessions are activated successfully. If this hotfix is not applied, the SNA Server service does not retry the APPC BIND request.

For more information about a similar problem that may occur when you use automatically activated APPC sessions together with IP-DLC connections, click the following article number to view the article in the Microsoft Knowledge Base:

888246 FIX: Event ID 533 and event ID 543 are logged in the application event log, and LU 6.2 sessions do not successfully start in Host Integration Server 2004

Note Hotfix 888246 changes the timing of when the SNA Server service tries to establish APPC sessions over connections that use the IP-DLC link service. Therefore, this problem may be more likely to occur if you apply hotfix 888246.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: IPDLC 08400007 NNS

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB922405

-

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

© Microsoft Corporation. All rights reserved.