Microsoft KB Archive/893399

= FIX: A Host Integration Server 2004-based server may log Event 60 and Event 730 when a mainframe application tries to invoke an APPC or CPI-C application that is running on a Host Integration Server 2004 client =

Article ID: 893399

Article Last Modified on 12/4/2007

-

APPLIES TO


 * Microsoft Host Integration Server 2004 Standard Edition

-





SYMPTOMS
A Microsoft Host Integration Server 2004-based server may log the following event messages when a mainframe application tries to invoke an APPC application or a Common Programming Interface for Communications (CPI-C) application that is running on a Host Integration Server 2004 client:

Event ID: 60

Source: SNA Server

Description: Failed to invoke APPC TP TP Name, local LU = APPC LU Name, sense data = 84c0000

EXPLANATION

An attempt to invoke the APPC TP shown has failed. The error will be reported to the invoking TP on the remote system with the following primary return code:

AP_ALLOCATION_ERROR. The sense data shown is the secondary return code, which will be one of the following hexadecimal values:

X'084B6031' AP_TRANS_PGM_NOT_AVAIL_RETRY

X'084C0000' AP_TRANS_PGM_NOT_AVAIL_NO_RETRY

X'10086021' AP_TP_NAME_NOT_RECOGNIZED

X'10086031' AP_PIP_NOT_ALLOWED

X'10086032' AP_PIP_NOT_SPECIFIED_CORRECTLY

X'10086034' AP_CONVERSATION_TYPE_MISMATCH

X'10086041' AP_SYNC_LEVEL_NOT_SUPPORTED

X'080F6051' AP_SECURITY_NOT_VALID

Event ID: 730

Source: SNA Base Service

Description: The Host Integration Server computer was unable to locate an invokable TP, APPC LU Alias  , Workstation name:.

EXPLANATION

An attempt to invoke the APPC TP shown has failed because Host Integration Server did not find the TP name registered on any client in the subdomain. If this is an auto-started TP, make sure the TP is defined on the client machine using the Host Integration Server TPSETUP program.



CAUSE
This problem occurs because the Host Integration Server 2004 client does not correctly initialize an internal flag when the SnaBase service (Snabase.exe) starts. If the internal flag is not correctly initialized, the SnaBase service does not register invokable APPC or CPI-C transaction programs (TPs) with the sponsor server of the Host Integration Server 2004 client. Mainframe applications cannot communicate with invokable APPC or CPI-C applications if they are not registered with the Host Integration Server 2004-based servers in the Host Integration Server subdomain.



RESOLUTION
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

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 09-May-2005 22:34  6.0.1951.0  214,016  Snabase.exe Note Because of file dependencies, the most recent fix that contains these files may also contain additional files.



WORKAROUND
To work around this problem, run the SNA Trace Utility (Snatrace.exe) on the Host Integration Server 2004 client. Then, enable one or more of the trace settings that are available for the SnaBase service. If the invokable TP is started after you enable SnaBase traces on the Host Integration Server 2004 client, the TP will be registered on the Host Integration Server 2004-based servers.

Note We do not recommend that you keep Host Integration Server 2004 traces running continuously. However, you can use this method as a short-term workaround until you can apply this hotfix. You can also use this workaround to verify that the Event 60 and Event 730 messages are caused by this problem. An Event 60 message may also be logged for other reasons.



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
The exact symptoms of this problem can vary.

In some instances, the invokable APPC or CPI-C application is not registered with a Host Integration Server 2004-based server when the application is started on a Host Integration Server 2004 client. In this case, the invokable TP is never registered. Therefore, the mainframe application can never communicate with the invokable TP on the Host Integration Server 2004 client.

In other instances, the invokable APPC or CPI-C application is first registered with a Host Integration Server 2004-based server when the application starts. At this point, the mainframe application can communicate with the invokable TP on the Host Integration Server 2004 client. If the Host Integration Server 2004 server that the Host Integration Server 2004 client registered the invokable TP with is restarted, the Host Integration Server 2004 client does not reregister the invokable TP with the Host Integration Server 2004-based server. At this point, the mainframe application cannot communicate with the invokable TP on the Host Integration Server 2004 client.

Depending on the particular scenario that you experience, the problem may occur intermittently or the problem may occur consistently.

A Host Integration Server 2004-based server logs an Event 60 message any time that a SNA Server service (Snaservr.exe) cannot locate an invokable TP with which a mainframe application tries to start a conversation. Therefore, the Event 60 message can be logged for reasons that are different from the problem that is described in this article.

Additional query words: HIS HIS2004

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver KB893399

-

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

© Microsoft Corporation. All rights reserved.