Microsoft KB Archive/274185

From BetaArchive Wiki
Knowledge Base


LocalLU for Invoking TPs is Documented Incorrectly in CPI-C SDK Online Help

Article ID: 274185

Article Last Modified on 2/22/2007



APPLIES TO

  • Microsoft Host Integration Server 2000 Standard Edition
  • Microsoft SNA Server 4.0
  • Microsoft SNA Server 4.0 Service Pack 1
  • Microsoft SNA Server 4.0 Service Pack 2
  • Microsoft SNA Server 4.0 Service Pack 3



This article was previously published under Q274185

SYMPTOMS

The SNA Server 4.0 CPI-C Programmer's Guide online Help incorrectly documents the "LocalLU" registry parameter for both the SNA Server Microsoft Windows NT client and SNA Server Microsoft Windows 95 and Microsoft Windows 98 client. The Windows NT client and Windows 9x client are documented as follows:

Location in Windows NT registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNABase \Parameters TPname:REG_SZ:localLUalias


Location in Windows 9x registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SNABase \Parameters TPname:REG_SZ:localLUalias


However, the correct syntax for the SNA Server Microsoft Windows NT client is as follows:

Location in Windows NT registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SNABase\Parameters \Client <exename>:REG_SZ:localLUalias


Note that EXENAME is the CPI-C program name (Win32 executable name). For example, to force the APING sample program to use a Local LU alias of "LOCAL", the registry setting should be specified as follows:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SnaBase\Parameters \Client APING:REG_SZ:LOCAL


Location in Windows 9x registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SnaBase\Parameters \Client <exename>:REG_SZ:localLUalias


RESOLUTION

To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

215838 How to Obtain the Latest SNA Server Version 4.0 Service Pack


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in SNA Server 4.0 Service Pack 4.


Additional query words: HIS 2000

Keywords: kbbug kbdocerr kbfix kbqfe kbsna400presp4fix kbsna400sp4fix KB274185