... please wait while loading ...

To view the complete site without permanently having to scroll, your browser-window should be maximized to support your screen-resolution of .
Business Intelligence
Hans Schweda

facebook google

  69.476.917 Nedstat Basic - Kostenlose web site statistiken Persönliche Homepage webseite Zähler
Kostenlose Zähler
In memoriam C-BIT Information-Center Hannover (2.241/1075+2.241/1076 - no longer active)
Sicherheitshinweis: Wir weisen vorsorglich darauf hin, dass wir bei der Anmeldung saemtliche automatisch uebermittelten Parameter wie IP-Adresse und/oder Einwahlrufnummer speichern, um uns und unsere Kunden vor Missbrauch zu schuetzen. Selbstverstaendlich werden wir bei Bedarf umgehend strafrechtliche Massnahmen ergreifen, um einen vorliegenden Missbrauch zu ahnden.

Akte 20.12, Abzocke vor dem Akzeptieren-Button, Buttonspielchen, Geld zurückholen - wie ?

CMINIT Returns Error 24 if Symbolic Name Not Space-Padded

Article ID:171622
Last Review:June 28, 2004
Revision:4.0
This article was previously published under Q171622

SYMPTOMS

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

Back to the top

CAUSE

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.

Back to the top

RESOLUTION

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.

Back to the top

STATUS

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):
S E R V P A C K
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.

Back to the top


APPLIES TO
 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

Back to the top



This mirror is sponsored by:
Hansjoerg G. Henker
A-Z Consulting & Development
[890]

Information-Center [19.04.2019 22:31:10]