Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/170071

From BetaArchive Wiki
Knowledge Base


Invokable TP Timeout May Occur With Non-queued Operation

Article ID: 170071

Article Last Modified on 11/19/2003



APPLIES TO

  • Microsoft SNA Server 3.0, when used with:
    • Microsoft Windows NT 4.0
  • Microsoft SNA Server 3.0 Service Pack 4, when used with:
    • Microsoft Windows NT 4.0



This article was previously published under Q170071


SYMPTOMS

When you attempt to invoke a non-queued Win32 autostarted APPC or CPIC application configured to run on the SNA Server Windows NT and Windows 95 client computer, the following error may occur:

Event ID: 60
Failed to invoke APPC TP <tpname>, sense data = 084C0000

SNA client-side traces reveal that the application is invoked and correctly posts a RECEIVE_ALLOCATE (or CMACCP) before the dynamic load request for the TP arrives, though the RECEIVE_ALLOCATE (or CMACCP) never completes and the above dynamic load timeout error is logged.

CAUSE

Due to changes implemented within SNA Server 2.11 (and later versions) to support IBM CICS for Windows NT, invokable APPC TPs which require non- queued operation may occasionally experience dynamic load timeout problems along with Event 60.

RESOLUTION

An update to the SNA Server 3.0 Windows NT and Windows 95 client is available to correct this problem (post-SP1). With this update applied, a new registry setting can be configured to disable this special support for the IBM CICS product

   CicsSupport: REG_DWORD: 0
                

where:

   0 = disable support for IBM CICS for Windows NT
   1 = enable support (the default)
                

If the initial invokable TP is written as a Windows NT service, then the registry key value to add exists in:

   HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/<tpname>
   /Parameters/ 
                

If the initial invokable TP is written as a Windows NT application, then the registry key value to add exists in:

   HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/SnaBase/Tps
   /<tpname>/Parameters/ 
                

If the initial invokable TP is configured to run on a Windows 95 client, then the registry key value to add exists in

   HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/SnaBase/Parameters/TPs
   /<tpname>/Parameters/ 
                

where <tpname> is the APPC or CPIC transaction program name.

STATUS

Microsoft has confirmed this to be a problem in SNA Server version 3.0 and 3.0 Service Pack 1. This problem was corrected in the latest SNA Server version 3.0 U.S. Service Pack. For information on obtaining this Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

S E R V P A C K



Additional query words: SAS

Keywords: kbbug kbfix kbinterop kbnetwork kbprogramming KB170071