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 (888246)


The information in this article applies to:

  • Microsoft Host Integration Server 2004

SYMPTOMS

You configure Microsoft Host Integration Server 2004 to autoactivate logical unit (LU) 6.2 sessions over a host connection by using the IP data link connection (IP-DLC) link service. When you do this, the following event messages are repeatedly logged in the application event log:
Event ID 533
Description: Locate search failed: LU not found
Sense code = 0x08400007
Origin CP name = CP Name
Origin LU name = LU Name
Destination LU name = LU Name

Cause: A network search for which this node was the originator or the network node server failed to locate the target LU. This may be caused by the target LU name being incorrect, the target system being inoperative, or by link errors in the backbone of the network. Note that this message could be logged during normal node shutdown.

Effect: Session activation will fail with the specified sense code.

Action: If the target LU name is correct, check that the system the LU is defined on is active. If the system is active, check the topology of the network (using the QUERY_NN_TOPOLOGY_* verbs) to ensure that the target system (or its network node server) is reachable from this node.

For more information, see Help and Support Center at http://support.microsoft.com.
Event ID 543
Description: Unable to identify or activate the next hop of an ISR session
Sense code = 0x08400007
FQPCID = Fully qualified PCID
Primary LU name = LU Name
Secondary LU name = LU Name
BIND RU : BIND DATA

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. Additionally, the LU 6.2 sessions do not successfully start when this problem occurs.

CAUSE

When you configure Host Integration Server 2004 to autoactivate LU 6.2 sessions, the Microsoft SNA Server service tries to establish these LU 6.2 sessions at startup. The SNA Server service tries to do this even if the underlying High Performance Routing (HPR) control point to control point (CP-CP) session is not established. The LU 6.2 sessions do not successfully start, and you receive the sense code 0840 0007 error message.

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Host Integration Server 2004 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. 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

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 usual 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 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
   -------------------------------------------------------
   02-Nov-2004  19:47  6.0.1911.0    959,488  Snaipdlc.dll     
   02-Nov-2004  19:47  6.0.1911.0    407,552  Snaservr.exe     
   02-Nov-2004  19:47  6.0.1911.0  2,944,512  Trcipdlc.dll     
   02-Nov-2004  19:47  6.0.1911.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 "Applies to" section.

MORE INFORMATION

When a peer IP-DLC connection is in process to be established at server startup, the SNA Server service receives a DLCST STCD message. This indicates that the station is contacted. Therefore, the SNA Server service tries to send a SNASVCMG mode BIND request for all autoactivated sessions to start the sessions. A Data Link Control message trace file that is captured with the Trace Initiator program may look similar to the following trace file:
DLC   --------------------------------------------------------------------------------
DLC   04160000->01020201 DLCST STCD 
DLC   
DLC   ---- Header at address 011942E0, 0 elements ----
DLC   17000000 00000D00 00000C00 0100B401     <................>
DLC   --------------------------------------------------------------------------------
DLC   01020201->04160000 DLC DATA     
DLC                      DAF:01 OAF:01 ODAI:on  Exp.   
DLC                      BIND   RQD SC  FI BC EC DR1 
DLC   
DLC   ---- Header at address 01194244, 1 elements ----
DLC   00000000 00002F00 01010000 0100C804     <....../.......H.>
DLC   
DLC   ---- Element at address 01B80DB8, start 10, end 128 ----
DLC   6B800031 001307B0 B050B107 07858587     <k..1.....P...eeg>
DLC   07060200 00000000 00001623 000011C1     <...........#...A>
DLC   E3D9C1C9 D5F0F14B E3F1F6F1 F3F0F0F0     <TRAIN01KT1613000>
DLC   33000902 E2D5C1E2 E5C3D4C7 0903F000     <3...SNASVCMG..0.>
DLC   00000000 00011204 C1E3D9C1 C9D5F0F1     <........ATRAIN01>
DLC   4BE3F1F6 F1F3F0F0 F00A1300 2C330126     <KT1613000...,3.&>
DLC   A42ACC3E 0011C1E3 D9C1C9D5 F0F14BC1     <u*.>..ATRAIN01KA>
DLC   F1F6C3C9 C3E3F3                         <16CICT3         >
DLC   --------------------------------------------------------------------------------
DLC   04160000->01020201 DLC DATA     
DLC                      DAF:01 OAF:01 ODAI:on  Exp.   
DLC                      BIND   -RSP SC  FI SD BC EC DR1 
DLC   
DLC   ---- Header at address 01194244, 1 elements ----
DLC   04000007 00002F00 01010000 0100B401     <....../.........>
DLC   
DLC   ---- Element at address 01B80DB8, start 10, end 17 ----
DLC   EF900008 40000731                       <....@..1        >
Although the internal connection between the SNA Server service and the IP-DLC Advanced Peer-To-Peer Networking (APPN) service has been established, IP-DLC has not finished starting the HPR CP-CP session. Therefore, a LOCATE SEARCH command fails, and you receive the following sense code error message:

0840
Procedure Invalid for Resource: The received RU is not supported in the receiver for this type of resource (for example, (1) SETCV specifies boundary function support for a type 1 node but the capability is not supported by the receiving node, or (2) the PU receiving an EXECTEST or TESTMODE is not the primary PU for the target link.)

0007
Resource Not Found: A Delete or Find could not be satisfied because the specified entry does not exist in the receiver's directory.
Modification Type:MajorLast Reviewed:9/20/2006
Keywords:kbHotfixServer kbQFE kbfix kbbug KB888246 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.