Event 730 Can Return Garbled Characters for Local LU Name

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

SYMPTOMS

An Event 730 in the Windows NT Application Event Log may return garbled ASCII characters rather than the correct Local LU Name.

CAUSE

The LU Name logs as a string, when in fact it is a non-NULL terminated CHAR8, causing the log to incorrectly interpret the Local LU Alias.

STATUS

Microsoft has confirmed this to be a problem in SNA Server 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 version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

MORE INFORMATION

One example of this problem was generated with the following parameters:

"UN301" is the invokable TP name, "AK6" is the remote LU alias, and "LOCAL" is the local LU alias.

The message text of the Event 730 in the Application Event log stated:

"The SNA Server was unable to locate an invokable TP UN301   , APPC LU
Alias <AK6     LOCAL #&%&^%*@>, Workstation name: (null)."

Keywords          : prodsna snaappc snacpic snaserverservice
Version           : WINDOWS:3.0,3.0SP1,3.0SP2,4.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix