100 Percent CPU Utilization and Event ID 8 Warnings After MC_ALLOCATE Request (320010)
The information in this article applies to:
- Microsoft Host Integration Server 2000
This article was previously published under Q320010 SYMPTOMS
An APPC transaction program may cause Host Integration Server 2000 to
log multiple Event ID 8 messages and cause CPU utilization to reach 100
percent.
Details of the Event ID 8Event Type: Warning
Event Source: SNA Server
Event Category: None
Event ID: 8
Description:
(1174) 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.
ACTION
Provide network support personnel with the event log file(s) related
to
SNA, SNA trace file(s), and the number and description of the
displayed
subcode. For information about SNA log and trace files, see the
"Microsoft Host Integration Server Online Books."
When this problem occurs, you must stop and restart the SNA Server
service.
CAUSE
This problem occurs if the following conditions exist:
- An APPC mode has been configured with an automatic activation
limit, and an explicit partnership has been defined.
- An invoking APPC transaction program issues an MC_ALLOCATE
request by using the FQPLU_NAME (fully-qualified partner LU name) field
instead of the PLU_ALIAS (partner LU alias) field. However the string
that the transaction program specifies in the FQPLU_NAME field actually
represents the partner LU alias instead of the fully-qualified partner
LU name.
When the APPC transaction program issues an MC_ALLOCATE request under
these conditions, the SNA Server service enters an internal loop. This
looping causes the service to generate the symptoms that are listed in
the "Symptoms" section of this article.
RESOLUTIONTo 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
To resolve this problem, correct the APPC transaction program by using
one of the following methods:
- Change the invoking APPC transaction program so that it uses
the PLU_ALIAS field of the MC_ALLOCATE instead of the FQPLU_NAME
field.
- Change the invoking APPC transaction program so that it
specifies a fully-qualified partner LU name in the FQPLU_NAME field
instead of specifying a partner LU alias.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Host Integration Server 2000 Service Pack 1.
Modification Type: | Minor | Last Reviewed: | 4/18/2005 |
---|
Keywords: | kbbug kbenv kbfix kbHostIntegServ2000preSP1fix kbHostIntegServ2000SP1fix KB320010 |
---|
|