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/171622

From BetaArchive Wiki
Knowledge Base

CMINIT Returns Error 24 if Symbolic Name Not Space-Padded

Article ID: 171622

Article Last Modified on 6/28/2004


  • Microsoft SNA Server 2.0
  • Microsoft SNA Server 2.1
  • Microsoft SNA Server 3.0
  • Microsoft SNA Server 2.11 Service Pack 1
  • Microsoft SNA Server 2.11 Service Pack 2
  • Microsoft SNA Server 4.0

This article was previously published under Q171622


Calling CPIC Initialize_Conversation() (or CMINIT) may fail with error 24, or CM_PROGRAM_PARAMETER_CHECK.


The CPIC application must supply a sym_dest_name parameter to CMINIT. If the sym_dest_name is less than eight characters long, the CPIC interface requires the application to pad the name with spaces, or CPIC fails to match the name against the CPIC symbolic names configured in the SNA Server configuration file, causing CPIC to return CM_PROGRAM_PARAMETER_CHECK.

The CPIC Programmer's Guide does not document the requirement of providing a space-padded sym_dest_name.


To work around this problem:

  • Space-pad the sym_dest_name passed to CMINIT, if the name is less than eight characters long.

An updated CPIC DLL is also available which automatically space-pads the name to eight characters, if the application did not supply the sym_dest_name in this format.


Microsoft has confirmed this to be a problem in SNA Server versions 2.0, 2.1, 2.11, 2.11 Service Pack 1 (SP1), 2.11 SP2, and 3.0 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):


A supported fix is now available for systems running SNA Server 2.11 SP2, 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.

Keywords: kbbug kbfix kbnetwork KB171622