First SLI_OPEN is Not Traced When LUA API Tracing Enabled

• Microsoft SNA Server, versions 4.0, 4.0 SP1

SYMPTOMS

If "SNA Application" LUA API tracing is enabled, and a Session Level Interface (SLI) application is started, the first SLI call is not traced to the trace file (Cliapi1.atf or Cliapi2.atf). Tracing only starts after the SLI DLL initiates its underlying call to RUI_INIT.

CAUSE

The Win32 SLI DLL (Winsli32.dll) is not initializing API tracing until the underlying RUI DLL (Winrui32.dll) is initialized via RUI_INIT. Therefore, the first SLI_OPEN verb is not traced.

RESOLUTION

Microsoft has confirmed this to be a problem in SNA Server version 4.0 and 4.0 Service Pack 1. 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 the Service Pack is applied, tracing is initialized when the Winsli32.dll is invoked by the application.

Additional query words:

Keywords :
Version : WINDOWS:4.0,4.0 SP1
Platform : WINDOWS
Issue type : kbbug