KB139210 - LUA App Fails with Secondary_rc = 0x87 (COMMAND_COUNT

Article ID: 139210

Article Last Modified on 5/18/2005

Microsoft SNA Server 2.0, when used with:
- Microsoft Windows NT 4.0
Microsoft SNA Server 2.1, when used with:
- Microsoft Windows NT 4.0
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
Microsoft SNA Server 4.0, when used with:
- Microsoft Windows NT 4.0
Microsoft SNA Server 3.0 Service Pack 2, when used with:
- Microsoft Windows NT 4.0
Microsoft SNA Server 3.0 Service Pack 3, when used with:
- Microsoft Windows NT 4.0
Microsoft SNA Server 4.0, when used with:
- Microsoft Windows NT 4.0
Microsoft SNA Server 4.0 Service Pack 1, when used with:
- Microsoft Windows NT 4.0
Microsoft SNA Server 4.0 Service Pack 2, when used with:
- Microsoft Windows NT 4.0

SUMMARY

Run the SNA Server Client Setup program and check that the network interface being used to communicate to the SNA Server (or servers) is correct. Since the SNA client software can communicate to the server over various interfaces (i.e. named pipes, native ipx/spx, tcp/ip sockets and Banyan IP), each interface option requires appropriate settings in order to "find" an SNA Server in the domain.
Make sure that the user who's running the LUA application has authority to establish a network session to the SNA Server computer.
If the above settings appear to be correct, collect the following SNA Server client traces and pass them to a Microsoft Support Professional:
- On Windows NT or Windows 95, capture SnaBase full internal tracing and SNA Application full internal tracing, LUA API and 3270 message tracing
- on Windows 3.x, capture an SNA client full internal trace, RUI/SLI API traces and 3270 message traces.

123256 Enabling SNA Server Windows 3.x Client Traces

Additional query words: prodsna 2.00 2.10 2.11

Keywords: KB139210