Microsoft KB Archive/884112

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

Article ID: 884112

Article Last Modified on 5/19/2005

-

APPLIES TO


 * Microsoft Host Integration Server 2000 Standard Edition
 * Microsoft Host Integration Server 2000 Service Pack 1

-



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), error code = 1036. The request to invoke the TP was sent by Host Integration Server 2000.

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 , local LU =   , 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  folder. Tpstart.exe is copied to the  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 &quot;Applies to&quot; 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 &quot;Global&quot; prefix for Win32 named objects. The version of Tpstart.exe that is installed with Host Integration Server 2000 correctly adds the &quot;Global&quot; prefix to Win32 named objects.

The following excerpt from the Microsoft Platform SDK describes how the &quot;Global&quot; 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 &quot;Global\&quot; or &quot;Local\&quot; 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 &quot;Global\&quot; and &quot;Local\&quot; prefixes are ignored. The names of events, semaphores, mutexes, waitable timers, file-mapping objects, and job objects share the same namespace.

Additional query words: APPC CPIC CPI-C openmutex access denied HIS

Keywords: kbprb KB884112

-

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

© Microsoft Corporation. All rights reserved.