You receive an Event 703 message when you invoke an auto-started transaction program in Host Integration Server 2000 (884112)


The information in this article applies to:

  • Microsoft Host Integration Server 2000
  • Microsoft Host Integration Server 2000 SP1

SYMPTOMS

When you try to invoke an auto-started transaction program (TP) on a Microsoft Host Integration Server 2000 client or server, the following message may be logged in the event log:
Event ID: 703
Source: SNA Base Service
Description: Failed to invoke APPC Transaction Program (TP) TP Name, error code = 1036. The request to invoke the TP was sent by Host Integration Server 2000 ServerName. Additionally, the following event will be logged on the Host Integration Server 2000 server when this problem occurs:
Event ID: 60
Source: SNA Server
Description: Failed to invoke APPC TP TP Name in EBCDIC (TP Name), local LU = LU Alias , sense data = 84c0000

CAUSE

This problem occurs when you use the Tpstart.exe program that is included in the Host Integration Server 2000 SDK as the transaction program loader.

RESOLUTION

This problem does not occur when you use the Tpstart.exe program that is located in the %SNAROOT% folder. Tpstart.exe is copied to the %SNAROOT% folder when you install Host Integration Server 2000.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

You must have a transaction program loader to successfully invoke an auto-started transaction program that runs as an application in Microsoft Windows 2000, Microsoft Windows XP Professional, and Microsoft Windows Server 2003. The Tpstart.exe program is the transaction program loader that is included with Host Integration Server 2000.

The version of the Tpstart.exe program that is included with the Host Integration Server 2000 SDK does not add a "Global" prefix for Win32 named objects. The version of Tpstart.exe that is installed with Host Integration Server 2000 correctly adds the "Global" prefix to Win32 named objects.

The following excerpt from the Microsoft Platform SDK describes how the "Global" prefix is used with Windows 2000:

Terminal Services: A Terminal Services environment has a global namespace for events, semaphores, mutexes, waitable timers, file-mapping objects, and job objects. In addition, each Terminal Services client session has its own separate namespace for these objects. Terminal Services client processes can use object names with a "Global\" or "Local\" prefix to explicitly create an object in the global or session name space. For more information, see Kernel Object Name Spaces.

Windows 2000: On Windows 2000 systems without Terminal Services running, the "Global\" and "Local\" prefixes are ignored. The names of events, semaphores, mutexes, waitable timers, file-mapping objects, and job objects share the same namespace.

Modification Type:MinorLast Reviewed:5/19/2005
Keywords:kbprb KB884112 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.