PRB: NT Client Does Not Support Dynamic Definition of Invokable TPs (182576)

The information in this article applies to:

Microsoft SNA Server 3.0
Microsoft SNA Server 3.0 SP1
Microsoft SNA Server 3.0 SP2
Microsoft SNA Server 3.0 SP3
Microsoft SNA Server 4.0

This article was previously published under Q182576

SYMPTOMS

You cannot dynamically define invokable Advanced Program-to-Program Communication or Common Programming Interface for Communications (APPC/CPIC) transaction programs (TPs) on an SNA Server Windows NT client. When a new invokable TP is defined in the registry, you must stop and restart the SnaBase process to recognize the presence of the new TP.

NOTE: The SNA Server Windows 95 client has supported this feature since SNA Server version 3.0.

CAUSE

The SNA Server Windows NT client was not originally designed to support the dynamic definition of new invokable TPs.

RESOLUTION

This problem was corrected in the latest SNA Server version 4.0 U.S. Service Pack.

For additional information and to download this service pack, click the article number below to view the article in the Microsoft Knowledge Base:

215838 How to Obtain the Latest SNA Server 4.0 Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

After you apply this update, any Windows NT program may notify the SnaBase service that a new TP has been installed on the computer by signaling the SNABASE_NEWTP_EVENT event. When this event is signaled, SnaBase re-reads the local registry to find the newly installed, invokable TPs.

Modification Type:	Minor	Last Reviewed:	5/13/2005
Keywords:	kbfix kbprb KB182576