NT Client Doesn't Support Dynamic Definition of Invokable TPs

• Microsoft SNA Server, versions 3.0, 3.0 SP1, 3.0 SP2, 4.0

SYMPTOMS

You cannot dynamically define invokable APPC/CPIC transaction programs (TPs) on an SNA Server Windows NT client. When a new invokable TP is defined in the registry, the SnaBase process must be stopped and restarted to recognize the presence of the new TP.

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

CAUSE

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

STATUS

Microsoft has confirmed this to be a problem in SNA Server Windows NT client, versions 3.0, 3.0 SP1, and 3.0 SP2. Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. Microsoft has confirmed this to be a problem in SNA Server Windows NT client, version 4.0. This problem was corrected in the latest SNA Server version 4.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

MORE INFORMATION

With this update applied, any Windows 95 program may notify the SnaBase service that a new TP has been installed on the computer by signaling the following named event: "SNABASE_NEWTP_EVENT". When this event is signaled, SnaBase re-reads the local registry to find newly installed invokable TPs.

Additional query words:

Keywords : kbfix4.00.sp1 prodsna snaappc snacpic snaprog snatp snawinnt
Version : WINDOWS:3.0,3.0 SP1,3.0 SP2,4.0
Platform : WINDOWS
Issue type : kbbug