Article ID: 898552
Article Last Modified on 12/4/2007
APPLIES TO
- Microsoft Host Integration Server 2004 Standard Edition
- Microsoft Host Integration Server 2000 Standard Edition
SYMPTOMS
When Microsoft Host Integration Server uses Logical Unit Application (LUA) applications to access applications that are running on IBM mainframe computers, the computer that is running Host Integration Server may log multiple Event ID 8 warning messages. The LUA applications function correctly even though the Event ID 8 warning messages are logged.
When this problem occurs, the Event ID 8 warning messages that are logged are similar to the following:
Event ID: 8
Source: SNA Server
Description:
(1144) Internal Protocol Violation
EXPLANATION
A protocol violation has occurred at the interface between the SNA Service and another SNA component (for example, the emulator or link service).
SUBCODE INFORMATION
X'1105' Insufficient space to copy data into node buffer.
X'1112' Received unknown message type at the node interface.
X'1144' Received illegal message at the node interface.
X'1151' Received unrecognized message from the link service component.
X'1174' Received invalid session limits message from Host Integration Server SNA Manager.
X'1175' Received invalid CNOS command. X'1188' Received invalid CNMS message.
CAUSE
The SNA Server service (Snaservr.exe) incorrectly logs an Event ID 8 warning message during a bracket race condition when the SNA Server service processes LUA data.
RESOLUTION
Host Integration Server 2004
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:
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:
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 tool in Control Panel.
Date Time Version Size File name ----------------------------------------------------- 26-Apr-2005 18:26 6.0.1949.0 407,552 Snaservr.exe 26-Apr-2005 18:26 6.0.1949.0 847,360 Trcservr.exe
Note Because of file dependencies, the most recent hotfix that contains these files may contain additional files.
Host Integration Server 2000
Hotfix information
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 2000 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:
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.
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 tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------- 11-May-2005 23:22 5.0.0.2068 471,312 Snaservr.exe 11-May-2005 23:22 5.0.0.2068 1,057,040 Trcservr.exe
Note Because of file dependencies, the most recent hotfix that contains these files may 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
To determine whether you are experiencing this problem, you can use the SNA Trace Utility (Snatrace.exe). The following is an example of the data flow that causes this problem. This trace data is excerpted from a Data Link Control message trace on the SNA Server service.
The mainframe application sends a Request Unit (RU) that has the End Bracket (EB) flag set:
DLC 05160000->01020101 DLC DATA DLC DAF:02 OAF:01 ODAI:off Normal DLC RQE FMD BC EC DR1 EB DLC DLC ---- Header at address 01385388, 1 elements ---- DLC 00000100 00002C00 02010A84 0100500D <......,....d..P.> DLC DLC ---- Element at address 01D74B50, start 10, end 12 ---- DLC 039040 <..@ >
The mainframe application sends the RU to the client LUA application:
FMI 01022D02->0C1D0001 FMI DATA FMI NO ACK reqd Key:27 Seq:2692 BCI ECI EBI CEI FMI BBIUI EBIUI FMI FMI ---- Header at address 01385388, 1 elements ---- FMI 0000001B 640E2C00 02010A84 0100500D <....d.,....d..P.> FMI FMI ---- Element at address 01D74B50, start 4, end 12 ---- FMI 2C000201 0A840390 40 <,....d..@ >
Then, the host application sends another RU to start a new chain. This RU has the Begin Bracket (BB) flag and the EB flag set. The host application sends the data to the client LUA application:
DLC 05160000->01020101 DLC DATA DLC DAF:02 OAF:01 ODAI:off Normal DLC RQE FMD FI BC DR2 BB EB DLC DLC ---- Header at address 01385388, 1 elements ---- DLC 04090004 00032C00 02010A85 0100500D <......,....e..P.> DLC DLC ---- Element at address 01D74B50, start 10, end 35 ---- DLC 0A30C017 42428001 F0F10940 40404040 <.0..BB..01.@@@@@> DLC 40404007 C6E3D5C2 C1D3 <@@@.FTNBAL > FMI -------------------------------------------------------------------------------- FMI 01022D02->0C1D0001 FMI DATA FMI NO ACK reqd Key:28 Seq:2693 FMHI BCI COMMIT FMI BBI EBI BBIUI EBIUI FMI FMI ---- Header at address 01385388, 1 elements ---- FMI 0009001C DC062C00 02010A85 0100500D <......,....e..P.> FMI FMI ---- Element at address 01D74B50, start 4, end 35 ---- FMI 2C000201 0A850A30 C0174242 8001F0F1 <,....e.0..BB..01> FMI 09404040 40404040 4007C6E3 D5C2C1D3 <.@@@@@@@@.FTNBAL>
The client LUA application then sends the following data to the SNA Server service:
FMI 0C1D0001->01022D02 FMI DATA FMI NO ACK reqd Key:1 Seq:2693 FMHI BCI COMMIT FMI BBI EBI BBIUI EBIUI FMI FMI ---- Header at address 01385388, 1 elements ---- FMI 00090001 DC062C00 02010A85 01002807 <......,....e..(.> FMI FMI ---- Element at address 01D74B50, start 4, end 47 ---- FMI 2C000000 00000B30 A0104202 80010000 <,......0..B.....> FMI 09C6E3C9 C1C2C1D3 00E7F0F8 F2F7F2F4 <.FTIABAL.X082724> FMI E7F0F0F2 F6F0F1F3 F9F1F6D4 <X0026013916M >
The SNA Server service queues this data.
The host application then sends multiple RUs to complete the chain that the host application previously started. The following is the first Middle Chain (MC) RU:
DLC 05160000->01020101 DLC DATA DLC DAF:02 OAF:01 ODAI:off Normal DLC RQE FMD MC DR2 DLC DLC ---- Header at address 01385320, 1 elements ---- DLC 04090004 00032C00 02010A86 0100500D <......,....f..P.> DLC DLC ---- Element at address 01D70EDC, start 10, end 268 ---- DLC 003000F0 F8F2F7F2 F4E7F0C6 E3D5C2C1 <.0.082724X0FTNBA> DLC D3F0F140 F0F7F9F2 F54040F1 D7C1C7C5 <L01@07925@@1PAGE> DLC 404040F1 5C4040F0 F461F0F1 61F0F540 <@@@1\@@04a01a05@> DLC F0F87AF2 F77AF2F5 4040C1C2 D4E240C2 <08z27z25@@ABMS@B> DLC C1D3C1D5 C3C54040 40404040 404040C2 <ALANCE@@@@@@@@@B>
Note The other RUs are omitted for brevity.
The SNA Server service logs an Event ID 8 warning message for each RU in the chain because the client data is still queued in the Normal Flow Requests Pending Queue.
The SNA Server service correctly sends the data that the SNA Server service has received from the mainframe application to the client LUA application.
Additionally, the SNA Server service sends the queued client data to the host application after the SNA Server service receives the End Chain (EC) RU from the host application.
The Event ID 8 warning messages are the only indicators that a problem has occurred because the SNA Server service correctly processes all the data that the LUA application sends and receives.
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
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB898552
