Article ID: 182691 - View products that this article applies to.
This article was previously published under Q182691
This article has been archived. It is offered "as is" and will no longer be updated.
An Event 730 in the Windows NT Application Event Log may return garbled ASCII characters rather than the correct Local LU Name.
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.
Microsoft has confirmed this to be a problem in SNA Server versions 3.0, 3.0 SP1, 3.0 SP2, and 3.0 SP3. 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. 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
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).
Article ID: 182691 - Last Review: February 24, 2014 - Revision: 2.2
Contact us for more help
Connect with Answer Desk for expert help.