Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/172291

From BetaArchive Wiki
Knowledge Base

Snacfg.exe Does Not Support Omission of LOCALBLOCKNO

Article ID: 172291

Article Last Modified on 7/15/2004


  • 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

This article was previously published under Q172291


When you configure an SDLC connection using Snacfg.exe, if the LOCALBLOCKNO (the first three digits of the Local Node ID, also known as the IDBLK) value is omitted, you receive the following error message:

The first three digits of the Local Node ID are invalid. These digits, also called the Block Number, can be any three hexadecimal digits except 000 or FFF, which are reserved.


Snacfg.exe does not set the SDLC connection "fSdlcLeased" flag based on the specified link service. If this flag is not set, the validate routine in Snacfg.exe does not recognize the connection as being associated with a Leased SDLC link service and considers the omission of the IDBLK as invalid.


Snacfg.exe has been corrected so that it now verifies the specified link service is SDLC and Leased. If the link service meets both these criteria, the IDBLK value can be omitted.


Microsoft has confirmed this to be a problem in SNA Server 3.0 and 3.0 Service Pack 1 (SP1). This problem was corrected in the latest SNA Server version 3.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):


Additional query words: snacfg snaconfig

Keywords: kbbug kbenv kbnetwork KB172291