Operator Started CPIC/APPC Application May Cause Events 60 and 703

ID: Q240840

The information in this article applies to:

Microsoft SNA Server, version 4.0 SP2

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe.

SYMPTOMS

Events 60 and 703 may be logged and a negative response to an FMH-5 Attach Message may be sent with a sense code of 084C0000 (transaction program not available, no retry).

CAUSE

An operator-started transaction program (TP) may have registry entries defining it as an auto-started invokable TP running as a service and/or as an application. This causes two or more entries in the SNA Server service table with the same TP name. When an FMH-5 Attach message is sent to start a conversation with the TP, the DMOD process should search the SNA Server service table using the following priority order:

1. Operator-started TPs currently running locally
2. Operator-started TPs currently running on another computer
3. Auto-started (invokable) TPs running locally
4. Auto-started (invokable) TPs on another computer

SNA Server 4.0 Service Pack 2 may route an incoming Attach message to an auto-started TP even though an operator-started TP exists and is located by the DMOD. If the auto-started TP is configured to run the same application as the operator-started TP, the TP should execute successfully. If the auto-started TP is not correctly configured or is configured to run a different program than the operator-started TP, the incoming Attach message may fail with the symptoms described earlier or may result in some other error.

WORKAROUND

Operator-started transaction programs do not require registry entries defining them as auto-started invokable transaction programs to an SNA Server computer.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

To stop the errors from occurring, delete the registry entries for the operator-started invokable transaction program.

STATUS

Microsoft has confirmed this to be a problem in SNA Server 4.0.

Additional query words:

Keywords : sna4sp2
Version : WINDOWS:4.0 SP2
Platform : WINDOWS
Issue type : kbbug