CSCw32 Sys Eng1

(1)

System messages

(2)

Questions and suggestions

Do you have ...

... any questions or suggestions regarding

... any technical questions or problems?

this manual?

Please note the order number or the date

Please refer to the Wincor Nixdorf

of issue of this manual and refer it to:

Customer Care Center:

address: E-mail:

[email protected]

Wincor Nixdorf International GmbH

Handbuchredaktion BD P5

33094 Paderborn

Germany

(3)

System messages

CSC-W32 V2.0/52

(4)

Copyright © Information and trademarks

© Wincor Nixdorf International GmbH 2004

All rights, including rights of translation and

rights of reproduction by reprinting,

copying or similar methods, even of parts,

are reserved.

Any violations give rise to a claim for

damages.

All rights, including rights created by patent

grants or registration of a utility model or

design, are reserved. Delivery subject to

availability; right of technical modifications

reserved.

All names of hardware and software

products mentioned in this manual are

trade names and/or trademarks of their

respective manufacturers.

(5)

Preface ...1

Target group ...1

Summary of contents ...1

Notational conventions...2

Message handling...3

Status/error classes ...4

Allocation of error codes ...7

Error entry ...8

Global error codes ...9

CSC error codes ...9

INI error codes ...16

Return code handler (RCH)...21

Error statistics (EST) ...25

Transaction statistics (TRA) ...29

COMM mutiplexer ...31

IEEE 1394 ...43

Universal serial bus (USB) ...63

DFU / DFUX Loader (DFU) ...83

Power Suspend Mode Manager (PSM) ...87

Card reader unit (IDU)...89

(6)

Special electronics (SEL / SEV4)... 115

Softkey/PINpad (PIN) ... 127

Operator Panel (OPL) ... 133

CIT Control Panel (CIT)... 141

Encryption/Decryption Software (EDS) ... 143

Encryption/Decryption module (EDM) ... 147

Secure Cash-Out (SCO)... 163

RSA module... 167

Remote Key Loading ... 169

CBKM module... 173

Swiss Encryption Protocol (SEP)... 175

Security Module SIBS ... 181

Online Personalization Terminals (OPT) ... 185

EPP Firmware Loader (LDE) ... 193

ZKA 3.0 (ZKA) ... 205

Printer (general) ... 221

ND05 printer / PMxx / Document reader ... 227

Scanner module (SCAN) ... 237

ND71, ND74, ND98, ND9A, ND9C, ND9E, TH30 printer... 245

ND79 printer... 253

ND75, ND75S, ND94 printer... 257

(7)

ND99 printer ...275

TH21 printer ...281

HPEM printer ...287

PRTX Printer messages ...291

Print System Framework...293

LDND9G - Loader for printer ND9G...299

LMND9G Printer Monitor ...301

LMTH21 Printer Monitor ...305

LDTH5X Firmware Loader ...309

LMTH5X Printer Monitor...313

LMTP07 Printer Monitor ...319

RJ03 Printers ...323

SB500 scanner (S500) ...329

CM3000 scanner (CM3K) ...339

TOSCA scanner (TSC) ...353

Scanner software RecoStar (RECO) ...361

Cash-Out Module (CDM)...413

Position of photosensors ...481

Cash-Out Module (CNG)...487

CNG: extended error codes ...495

Firmware loader (LDR) ...581

(8)

Coin-In Module (CIN)... 593

Bundle Cash Deposit Module (BCD) ... 597

Deposit Module (DPS) ... 605

Cash-Cheque Dispenser Module (CCDM) ... 617

CCDM: extended error codes ... 639

Money Door Module (MDM)... 661

Panel Protection Door (PPD) ... 667

(9)

Preface

The CSC-W32 software products allow the operation of self-service systems with the

standard operating system Windows NT®, Windows 2000® and Windows XP®.

The following WN-specific Windows 32 bit products can be used with this standard

operating system to control the self-service peripherals:

CSC-W32/BOF Basic

self-service

functions

CSC-W32/CDM

Cash dispenser module

CSC-W32/SFP

Security facility package

CSC-W32/SDK

Software development kit

Target group

This manual is intended for programmers, technicians and system operators. It provides a

complete overview of all system messages which can be output from the CSC-W32

products. This enables a fast elimination of faults which guarantees high availability of the

self-service system.

Summary of contents

The description of the message handling and the explanation of the general system

messages are followed by further descriptions in the order of the devices.

The messages are ordered numerically at the end of the manual. This helps find the

description corresponding to the message within this manual.

(10)

Notational conventions Preface

Notational conventions

The format of the message description is as follows:

– Error code and define

Listed sequentially in numerical order.

– Cause

Detailed description of the error. The causes are ordered according to the probable

error frequency.

– Application

If the message can be interpreted and acted on by the application programmer, then

the required actions are given here. This section serves as an aid for the application

programmer and should help him react correctly to errors in the application during

run-time. For this reason, these notes should only be consulted when creating user

pro-grams.

– Measure

Errors and messages to which the system operator and system administrator can

react.

Example:

XXXX Define

Cause:

– Description of the cause which occurs most frequently.

– Description of the cause with the next highest frequency of occurrence.

– etc.

Application:

Instructions for the application programmer are given here.

Measure:

The actions to be taken by the system operator or the system administrator are

described here.

(11)

Message handling

Parameters are passed via the standard device handler interface in the CSCDHLPARA

structure. The messages are divided into status or error classes (StClass), error

specifi-cation (StCode) and warning specifispecifi-cation (StWarn).

StClass

The following messages can be found in the "StClass" field:

STCLASS_OK

No error or warning has been received from the device

handler.

STCLASS_ERROR_COMM The COMM DLL reports an error with the V.24, ECP or

USB channel. Further information can be found in the

"StCode" field.

STCLASS_ERROR_XYZ The

XYZ device handler reports an error. Further

infor-mation can be found in the "StCode" field.

StCode, StWarn

The messages in the "StCode" and "StWarn" fields are described in the sections for the

device handlers.

(12)

Status/error classes Message

handling

Status/error classes

The following table contains the current valid values for the Status Class:

Definition Value Description

STCLASS_OK 00 01–02

No error

reserved

STCLASS_ERROR_USB 03 Universal Serial Bus STCLASS_ERROR_1394 04 IEEE 1394 Multiplexer

STCLASS_ERROR_COMM 05 COMM Multiplexer/Protocol Handler STCLASS_ERROR_TKM 06 Ticket Door Module

STCLASS_ERROR_CDM 07 Cash Dispenser Module STCLASS_ERROR_IDU 08 ID Card Unit

STCLASS_ERROR_PIN 09 Softkey/PINpad STCLASS_ERROR_SEL 0A Special electronic STCLASS_ERROR_RCH 0B Return Code Handler

STCLASS_ERROR_INI 0C Error in INI Module. This error is reported only when the INI module is accessed directly.

STCLASS_ERROR_MDM 0E Money Door Module

STCLASS_ERROR_EDM 0F Encryption/Decryption Module (HW) STCLASS_ERROR_EDS 11 Encryption/Decryption Module (SW) STCLASS_ERROR_TLS 12 Trace and Error Logging

STCLASS_ERROR_MSS 13 MM and CIM-86 Security System STCLASS_ERROR_OPL 14 Operator Panel STCLASS_ERROR_PPD 15 Panel Protection Door

STCLASS_ERROR_DPS 17 Deposit Module STCLASS_ERROR_CNG 18 Cash Dispenser Module NG STCLASS_ERROR_EST 19 Error statistic

(13)

Message handling

Status/error classes

STCLASS_ERROR_CCDM 1A Cheque Cash Deposit Module STCLASS_ERROR_SCAN 1B Scanner Module STCLASS_ERROR_TRA 1C Transaction statistic STCLASS_ERROR_CNG_EXT 1D CSCCNG extended error codes STCLASS_ERROR_LDR 1E Firmware loader CNG

STCLASS_ERROR_LDR3 1F Firmware loader ND97

STCLASS_ERROR_CIT 20 Central ProPrint Module CSCWCIT STCLASS_ERROR_COUT 21 Coin-Out Module STCLASS_ERROR_CIN 22 Coin-In Module STCLASS_ERROR_RECO 23 Scanner Software RecoStar (S500) STCLASS_ERROR_SCO 24 Secure Cash-Out STCLASS_ERROR_BCD 25 Bundle Cash Deposit

STCLASS_ERROR_CCM 26 Chip Card Module

STCLASS_ERROR_P36 27 Paragraph 36 STCLASS_ERROR_SEP 28 Swiss Encryption Protocol STCLASS_ERROR_ZKA 29 ZKA 3.0 (only for Germany) STCLASS_ERROR_PSM 2A Power Suspend Mode Manager

STCLASS_ERROR_PPXD 2B ProPXD: Platform Extensions for Diagnostic STCLASS_ERROR_OPT 2C Online Personalization Terminal

STCLASS_ERROR_LDE 2D Firmware Loader EPP STCLASS_ERROR_RSA 2E RSA Encryption Module

STCLASS_ERROR_CBKM 2F Cartes Bancaires Key Management STCLASS_ERROR_SIBS 30 Security Module SIBS

STCLASS_ERROR_DFU 31 Device Firmware Upgrade STCLASS_ERROR_PRT 32 Printer

(14)

Status/error classes Message

handling

STCLASS_ERROR_ND94 34 Printer ND75 / ND75S / ND94 STCLASS_ERROR_ND79 35 Printer ND79

STCLASS_ERROR_ND05 37 Printer ND05 / PMxx / document reader module

STCLASS_ERROR_ND99 38 Printer ND99

STCLASS_ERROR_ND97 39 Printer ND97 / TH97 / TP01 / NP01 / TP05 / NP05 / TP09

STCASS_ERROR_HPEM 3A Printer HPEM STCLASS_ERROR_S500 3B Scanner SB500 STCLASS_ERROR_TSC 3C Scanner TOSCA STCLASS_ERROR_CM3K 3D Scanner CM3000 STCLASS_ERROR_TH21 3E Printer TH21 STCLASS_ERROR_PRTX 3F Printer Extensions STCLASS_ERROR_LMND9G 40 LMND9G Printer STCLASS_ERROR_LMTH21 41 LMTH21 Printer STCLASS_ERROR_LMFRAME 42 Print System Framework STCLASS_ERROR_LDND9G 43 Loader for printer ND9G STCLASS_ERROR_LMTP07 44 TP07 Printer Monitor

STCLASS_ERROR_R03 45 Printer Family RJ03 (receipt printers) STCLASS_ERROR_LMTH5X 46 TH5X Printer Monitor STCLASS_ERROR_LDTH5X 47 Loader for printer TH5X

STCLASS_ERROR_J03 48 Printer Family RJ03 (journal printers) STCLASS_ERROR_RKL 5F Remote Key Loading

STCLASS_ERROR_EDM_COMM 0F05 PIN: V.24 communication failure between hardware encryption module and PC STCLASS_ERROR_CDM_COMM 0705 IDCU: nested error of the MM module in the

(15)

Message handling

Status/error classes

STCLASS_ERROR_CDM_EDS 0711 IDCU: nested encryption error of the MM module during the encrypted communication between PC and CDM

STCLASS_ERROR_MSS_COMM 1305 Error in communication between MSS-DHL and CIM-86 or MM module

STCLASS_ERROR_MSS_EDS 1311 Problems with decryption of data with CIM-86 module

STCLASS_ERROR_CIT_COMM 2005 ProPrint: nested error of the CSCWCIT module in the connection with the attached devices

STCLASS_ERROR_CIT_LDR3 201F ProPrint: nested error of the CSCWCIT module during loading the firmware of the ND97 printer.

STCLASS_ERROR_P36_COMM 2705 P36: communication failure between the PC and the hardware for sampling the signature data.

Allocation of error codes

The error codes are allocated to the following areas:

Error codes Areas 0x0000 0x0000.0001 - 0x1FFF.FFFF 0x2000.1000 - 0x2000.1FFF 0x2000.2000 - 0x2000.2FFF 0x2000.3000 - 0x2000.37FF 0x2000.3800 - 0x2000.3FFF 0x2000.4000 - 0x2000.47FF 0x2000.4800 - 0x2000.4FFF 0x2000.8000 - 0x2000.FFFF 0x2800.0000 - 0x3FFF.FFFF 0x4000.0000 - 0xFFFF.FFFF No error occurred

Windows error codes

Global CSC error codes INI DLL error codes

Function canceled, global CSC codes Function canceled, DHL-specific codes Function time-out, global CSC codes Function time-out, DHL-specific codes DHL-specific error codes

CSC firmware codes

(16)

Error entry Message

handling

Error entry

The error entries of the CSC-W32/OS are entered by means of two tools:

WindowsNT Event Logging

The event logging system supplied with Windows NT can be used. The Event Viewer

allows you to view the errors of the CSC-W32 under the Application error area.

TLS-W32

Since no event logging system is available under Windows 95, the tool TLS-W32

supplied with the CSC-W32 is available. This tool has been ported from TLS/2 of the

CSC-O/OS product to Win32.

This tool is also available under Windows NT so that the user is free to decide, by a

generation in the CSC.INI, whether the CSC-W32 errors are logged in the

Windows NT event logging system or in the TLS-W32 system.

After installing the Return Code Handler, not only the hex codes of StClass, StCode and

StWarn are written into the log file, but also the appropriate definitions.

With the utility CSCHELP all information about an error listed in this manual can be read

online.

(17)

Global error codes

All global error messages, which are returned from the device handlers in "StCode", are

listed in this section. They are described in the include file CSCDEF.H. an entry in

"StClass" allocates the error message to the corresponding device handler.

CSC error codes

20001001 CSC_FUNCTION_NOT_IMPLEMENTED Reason:

The function is not implemented. Application:

Check application program. 20001003 CSC_INVALID_SPEC

Reason:

The function specification "CscDhlPara.Spec" given in the parameter block is invalid. Application:

Check application program. 20001004 CSC_INVALID_INLEN

Reason:

The length specified for the input buffer "CscDhlPara.InLen" in the parameter block is invalid. Application:

Check application program. 20001005 CSC_INVALID_OUTLEN

Reason:

The length specified for the output buffer "CscDhlPara.OutLen" in the parameter block is invalid. Application:

(18)

Global error codes

20001006 CSC_INVALID_LOGICAL_ID Reason:

The logical ID specified in the Open/GetRelease command is invalid. Application:

Check application program. Check the logical ID in Registry. Measure:

Consult the application programmer. Modify Registry if necessary. 20001007 CSC_INVALID_PID

Reason:

The process, which called this function of the device, is not identical with the process which opened the device.

Application:

Check application program.

20001009 CSC_DEVICE_ALREADY_OPENED Reason:

The device, on which an OPEN command was executed, is already opened non-shared. Application:

Check application program. Measure:

Check whether another application in the system has already opened this device. 2000100D CSC_CSCINI_DLL_NOT_FOUND

Reason:

The CSCWINI.DLL could not be found in the PATH. Normally <CSCROOT>\DLL. Measure:

Check whether CSCWINI.DLL is in the PATH. Normally <CSCROOT>\DLL. 2000100E CSC_CSCINI_DLL_OPEN_FAILED

Reason:

The CSCWINI.DLL could not be opened. Measure:

(19)

Global error codes

2000100F CSC_DHL_NOT_INITIALIZED Reason:

The device handler has not yet been initialized. Application:

Check application program. Execute CscXyzInit if required. 20001014 CSC_REL_NOT_AVAIL

Reason:

No release is currently available under the stated specification. Application:

Check application program. Retry job if necessary. 20001015 CSC_INVALID_COMMAND

Reason:

An attempt was made to execute a command which was not permitted or possible for this application or configuration.

Application:

Check application program 20001017 CSC_TOO_MANY_USERS

Reason:

This device has already been opened by the max. number of users in SHARED mode. Application:

Check application program

20001018 CSC_CSCEDS_DLL_NOT_FOUND Reason:

The CSCWEDS.DLL could not be found in the PATH. Normally <CSCROOT>\DLL. Measure:

Check whether CSCWEDS.DLL is in the PATH. Normally <CSCROOT>\DLL. 20001019 CSC_CSCEDS_DLL_OPEN_FAILED

Reason:

The CSCWEDS.DLL could not be opened. Measure:

(20)

Global error codes

2000101A CSC_CSCEDM_DLL_NOT_FOUND Reason:

The CSCWEDM.DLL could not be found in the PATH. Normally <CSCROOT>\DLL. Measure:

Check whether CSCWEDM.DLL is in the PATH. Normally <CSCROOT>\DLL. 2000101B CSC_CSCEDM_DLL_OPEN_FAILED

Reason:

The CSCWEDM.DLL could not be opened. Measure:

Report the error log of this entry to Service. 2000101D CSC_CSCCOMM_DLL_NOT_FOUND

Reason:

The CSCWCOMM.DLL could not be found in the PATH (normally <CSCROOT>\DLL). Measure:

Check whether CSCWCOMM.DLL is in the PATH (normally <CSCROOT>\DLL). 2000101E CSC_CSCCOMM_DLL_OPEN_FAILED

Reason:

The CSCWCOMM.DLL could not be opened. Measure:

Report the error log of this entry to Service. 20001021 CSC_INI_WRONG_INTERFACE

Reason:

Wrong value for INTERFACE in Registry. Measure:

Check the parameter INTERFACE in Registry. 20001022 CSC_CSCSEL_DLL_NOT_FOUND

Reason:

The CSCWSEL.DLL could not be found in the PATH (normally <CSCROOT>\DLL). Measure:

(21)

Global error codes

20001023 CSC_CSCSEL_DLL_OPEN_FAILED Reason:

The CSCWSEL.DLL could not be opened. Measure:

Report the error log of this entry to Service. 20001025 CSC_CSCRECO_DLL_NOT_FOUND

Reason:

The CSCRECO.DLL could not be found in the LIBPATH (normally <CSCROOT>\DLL). Measure:

Check whether CSCRECO.DLL is in the LIBPATH (normally <CSCROOT>\DLL). 20001026 CSC_CSCRECO_DLL_OPEN_FAILED

Reason:

The CSCRECO.DLL could not be opened. Measure:

Report the error log of this entry to Service. 20001027 CSC_DQF_DLL_NOT_FOUND

Reason:

The DQF.DLL could not be found in the LIBPATH (normally <CSCROOT>\DLL). Measure:

Check whether DQF.DLL is in the LIBPATH (normally <CSCROOT>\DLL). 20001028 CSC_DQF_DLL_OPEN_FAILED

Reason:

The DQF.DLL could not be opened. Measure:

Report the error log of this entry to Service. 20001029 CSC_CSC1394_DLL_NOT_FOUND

Reason:

The CSC1394.DLL could not be found in the LIBPATH (normally <CSCROOT>\DLL). Measure:

(22)

Global error codes

2000102A CSC_CSC1394_DLL_OPEN_FAILED Reason:

The CSC1394.DLL could not be opened. Measure:

Report the error log of this entry to Service. 2000102B CSC_RECO_NOT_INSTALLED

Reason:

RecoStar is not, or not correct installed. Measure:

Check installation of RecoStar.

Check wether AI*.DLL or TIFFTOBO.DLL is in the LIBPATH (normally <CSCROOT>\DLL). 20001420 CSC_INVALID_HANDLE

Reason:

The handle "CscDhlPara.hCsc" given in the parameter block is invalid. Application:

Check application program. 20001421 CSC_INVALID_DEVICE

Reason:

An illegal device number was transferred when the handle was created. Measure:

Report the error log of this entry to Service. 20001422 CSC_INVALID_PINDATA

Reason:

The memory area, to which "pInData" points, cannot be accessed. Application:

Transfer a legal memory area from the application program. Measure:

If the error occurred again, report the error log of this entry to service. 20001423 CSC_INVALID_POUTDATA

Reason:

(23)

Global error codes

20001424 CSC_DEVICE_LOCKED Reason:

The device handler is currently locked by another user. Application:

Check application program. If necessary, repeat the command. 20001425 CSC_DEVICE_NOT_LOCKED

Reason:

The device handler was not locked. Application:

Check application program. 20001426 CSC_INVALID_UNLOCK

Reason:

CscXyzUnlock was not activated by the thread which had locked the device. Application:

Check application program. 20001427 CSC_ACCESS_TIMEOUT

Reason:

An attempt was made to access a device which is currently occupied by another user. Application:

Repeat the command. Check the application program. 20003000 CSC_CANCELED

Reason:

The function of the device handler was cancelled from another thread with the command "CscXyzCancel".

Application:

This behaviour is usually correct because the application is informing the system via the CANCEL command that a particular event is not to be expected anymore.

(24)

Global error codes

20004000 CSC_TIMEOUT Reason:

The function, which calls the device handler, receives a logical timeout. It is not a COM line timeout. Application:

This operating system is event-controlled. It is thus possible that the expected event has not occurred within the timeout time given by the application. There is possibly no error log carried out. There are times, however, when an immediate reaction is expected from a device. If the expected reaction does not take place, an error message is returned to the application and an Entry is made in the error log.

Measure:

If the timeout is entered in the error log, the device should be checked.

INI error codes

20002001 INI_FUNCTION_NOT_IMPLEMENTED Reason:

The function called from the device handler is not implemented in CSCWINI.DLL. Measure:

Report the error log if this entry to Service. 20002003 INI_INVALID_SPEC

Reason:

The function specification "CscDhlPara.Spec" given in the parameter block is invalid. Measure:

Report the error log of this entry to Service. 20002004 INI_INVALID_INLEN

Reason:

The length "CscDhlPara.InLen" of the input buffer specified in the parameter block is invalid. Measure:

Report the error log of this entry to Service. 20002005 INI_INVALID_OUTLEN

Reason:

The length "CscDhlPara.OutLen" of the output buffer specified in the parameter block is invalid. Measure:

(25)

Global error codes

20002422 INI_INVALID_PINDATA Reason:

The memory area, to which "pInData" points, cannot be accessed. Application:

If the error occurred again, report the error log of this entry to Service. 20002423 INI_INVALID_POUTDATA

Reason:

The memory area, to which "pOutData" points, cannot be accessed. Application:

If the error occurred again, report the error log of this entry to Service. 20002903 INI_ID_ITEM_NOT_FOUND

Reason:

The keyword in Registry, specified by any function was not found. Application:

If CSCWINI.DLL was called directly from the application, check whether the parameters were passed correctly from the application.

Measure:

Check whether the required keyword exists in Registry. 20002904 INI_KEYWORD_NOT_FOUND

Reason:

The keyword specified with the "CscIniScanPara" function could not be found in Registry. Application:

If CSCWINI.DLL was called directly from the application, check whether the parameters were passed correctly from the application.

Measure:

(26)

Global error codes

20002905 INI_INVALID_BAUDRATE Reason:

An incorrect parameter for the baud rate has been entered in Registry. Measure:

Enter the correct baud rate for the device. 20002906 INI_INVALID_DATABITS

Reason:

An invalid parameter for the data bit count has been entered in Registry. Measure:

Enter the correct data bit count for the device. 20002907 INI_INVALID_STOPBITS

Reason:

An invalid parameter for the number of stopbits has been entered in Registry. Measure:

Enter the correct number of stopbits for the device. 20002908 INI_INVALID_PARITY

Reason:

Invalid parameters for the parity check have been entered in Registry. Measure:

Enter the correct parameters for the parity check for the device. 20002909 INI_INVALID_PROTOCOL

Reason:

Invalid parameters for the transmission protocol have been entered in Registry. Measure:

Enter the correct parameters for the transmission protocol for the device. 2000290A INI_INVALID_VALUE

Reason:

The assigned value is invalid. Measure:

(27)

Global error codes

2000290B INI_INVALID_ROOT Reason:

Invalid or not defined value for the environment variable CSCROOT. Measure:

Enter the correct value in Registry/CONFIG.SYS. 2000290C INI_CONFIG_ERROR

Reason:

The system can´t check whether to use the Registry or CSC.INI. Measure:

Check the CSC.INI for the existence of the identification item [CSCINI] and the keyword CONFIG=FILE or CONFIG=REGISTRY.

(28)

(29)

Return code handler (RCH)

StClass:

STCLASS_OK No

error

STCLASS_ERROR_RCH

Error of the CSCWRCH.DLL

StCode:

20008000 RCH_INVALID_ACTIVE_PARA Reason:

YES or NO are not specified for the ACTIVE parameter in Registry/CSC.INI. Application:

Correct Registry/CSC.INI. 20008001 RCH_INVALID_LANGUAGE

Reason:

The parameter for LANGUAGE in Registry/CSC.INI is longer than 3 characters. Application:

Correct Registry/CSC.INI. 20008002 RCH_INVALID_PTXTBUF

Reason:

The specified buffer or buffer length are invalid. Application:

Check buffer definition in application program. 20008004 RCH_INVALID_TXTBUF_LEN

Reason:

(30)

Return code handler (RCH)

20008005 RCH_INVALID_PCSCDHLPARA Reason:

Check buffer definition in application program. 20008007 RCH_INVALID_STCLASS

Reason:

The StClass specified for analysis is 0 (zero). Application:

Check STCLASS in the application program. 20008008 RCH_INVALID_FILE_ID

Reason:

An invalid file ID is in an error text file. Measure:

Check error text files. 20008009 RCH_INVALID_TREE

Reason:

An invalid flag is in an error text file. Measure:

Check error text files.

2000800A RCH_UNKNOWN_TXT_FILE Reason:

No file could be found for a specified StClass. Measure:

Check files in <CSCROOT>\RCH for completeness. 2000800B RCH_TXT_NOT_FOUND

Reason:

No text number could be found for a specified StClass, StCode or StWarn. Measure:

(31)

Return code handler (RCH)

2000800C RCH_ACTCODE_NOT_FOUND Reason:

The flag "#" for action code was not found within a text. Measure:

Check that files in <CSCROOT>\RCH are complete and up-to-date. 2000800D RCH_DEFINE_TXT_NOT_FOUND

Reason:

The flag "$S" for Define in human readable text was not found within a text. Measure:

Check that files in <CSCROOT>\RCH are complete and up-to-date. 2000800E RCH_THREAD_TIMEOUT

Reason:

The thread for reading the headers of all error text files was not completed within 60 seconds. Measure:

Check hardware, operating system, file system. 2000800F RCH_THREAD_CREATE_ERROR

Reason:

The thread for reading the headers of all error text files could not be started. Measure:

(32)

(33)

Error statistics (EST)

StClass:

STCLASS_OK No

error

STCLASS_ERROR_EST

Error of the CSCWEST.DLL

StCode:

2000B000 EST_INVALID_STCLASS Reason:

An incorrect StClass value was specified in the structure ESTCNTEXIST. Perhaps the StClass does not exist in the error statistics database.

Application:

Check the contents of the StClass field in the structure ESTCNTEXIST. If necessary update information about available StClass values by using the function "CscEstGetCntExist". 2000B001 EST_INVALID_STCODE

Reason:

An incorrect StCode value was specified in the structure ESTCNTEXIST. Perhaps the StCode does not exist in the error statistics database.

Application:

Check the contents of the StCode field in the structure ESTCNTEXIST. If necessary update information about available StCode values by using the function "CscEstGetCntExist". 2000B002 EST_INVALID_RANGE

Reason:

The contents of the RangeStart field was higher than the value in the RangeEnd field of the structure ESTCNTEXIST.

Application:

(34)

Error statistics (EST)

2000B003 EST_INVALID_COUNTER Reason:

No record with this combination of StClass/StCode/ModId is registrated in the error statistics database.

Application:

Request the actual registrated error counters by using the function "CscEstGetCntExist". 2000B004 EST_INVALID_ACTIVE

Reason:

An invalid expression follows the keyword ACTIVE in the section [CSCEST] of the file CSC.INI/Registry.

Measure:

Check the file CSC.INI/Registry. 2000B005 EST_INVALID_BUF_LEN

Reason:

An invalid expression follows the keyword BUF_LEN in the section [CSCEST] of the file CSC.INI/Registry.

Measure:

Check the file CSC.INI/Registry. The decimal value after the keyword BUF_LEN in the section [CSCEST] must be between 256 and 65536.

2000B006 EST_INVALID_PCSCDHLPARA Reason:

The memory location, to which the pointer "pCscDhlPara" points, cannot be accessed. Application:

Check the contents of the structure ESTCNTERROR when calling the function "CscEstCountError". 2000B007 EST_BUFFER_OVERFLOW

Reason:

The EST DH cannot enter more errors into the internal error buffer, because the buffer is full. Application:

Do not produce too many errors too fast. Measure:

Increase the size of the internal buffer by using the keyword BUF_LEN in the section [CSCEST] in the file CSC.INI/Registry.

(35)

Error statistics (EST)

2000B008 EST_THREAD_NOT_STARTED Reason:

The EST DH was not able to launch the thread that cyclically clears the internal buffer. Measure:

Reduce the system load or free resources to enable the start of another thread. 2000B009 EST_CORRUPT_FILE

Reason:

The file that contains the error statistics database is not of the expected format. Application:

Reset the whole database by using the function "CscEstReset" with the specification EST_RESET_ALL. Attention: All data will be lost.

2000B00A EST_TLS_ERROR Reason:

An error occurred when the EST DH tried to get a module ID from the TLS DH or the EST DH tried to flush the TLS information buffer.

Measure:

Check the TLS/Win installation. 2000B00C EST_CANNOT_OPEN_FILE

Reason:

The output file for receiving the plain text log could not be opened. Measure:

Check the filename provided for the function "CscEstPrintLog". 2000B00D EST_CANNOT_WRITE_FILE

Reason:

The output file for receiving the plain text log could not be written to. Measure:

Check the available space on the storage device or the availability of the printer, if the function "CscEstPrintLog" prints on a disk or to a printer.

2000B00E EST_OUT_OF_MEMORY Reason:

The DH EST was not able to allocate enough memory for the function "CscEstPrintLog". Measure:

(36)

(37)

Transaction statistics (TRA)

StClass:

STCLASS_OK No

error

STCLASS_ERROR_TRA

Error of the CSCWTRA.DLL

StCode:

2000C000 TRA_INVALID_SELECTIONMASK Reason:

The SelectionMask parameter contained an invalid value. Application:

Check the contents of the SelectionMask parameter in the structure TRACNTTRANS. 2000C001 TRA_UNKNOWN_GROUPNAME

Reason:

The group name that was provided by the application does not exist. Perhaps the database was reset since the last call to the function "CscEstGetTransExist".

Application:

Check the group name and eventually reread the available group names by using the function "CscEstGetTransExist".

2000C002 TRA_OUT_OF_MEMORY Reason:

The TRA DH ran into an internal memory limitation. Measure:

Report the error log of this entry to Service. 2000C003 TRA_CORRUPT_NAMEFILE

Reason:

The information contained in the namespace file CSCTRA.INI is inconsistent. Application:

(38)

Transaction statistics (TRA)

2000C004 TRA_SYNTAX_ERROR Reason:

The parsing routine detected a syntax error in one of the TRA files. Measure:

Check the *.TRA files.

2000C006 TRA_CANNOT_OPEN_FILE Reason:

The output file for receiving the plain text log could not be opened. Application:

Check the filename provided for the function "CscTraPrintLog". 2000C007 TRA_CANNOT_WRITE_FILE

Reason:

The output file for receiving the plain text log could not be written to. Measure:

Check the available space on the storage device or the availability of the printer, if the function "CscTraPrintLog" prints on a disk or to a printer.

(39)

COMM mutiplexer

StClass:

STCLASS_OK No

error

STCLASS_ERROR_COMM

Error of the CSCWCOMM.DLL

StCode:

2000FE06 COMM_INVALID_PROTOCOL Reason:

The COMM reports an invalid specification for the protocol.

If the error occurs with the use of LPT, then the parallel port does not meet the requirements for the selected transfer mode.

Application:

Use the protocol type from the COMM.H definition file when calling "CscV24Init". Measure:

If the error occurs with the use of LPT, then you have to check the port configuration (e.g. for the printers TH97 and ND97 the parallel port is to be configured for ECP in the BIOS.

2000FE07 COMM_WRITE_CANCELED Reason:

A COMM WRITE command is cancelled by the user. No entry is made in the error log. 2000FE08 COMM_WRITE_TIMEOUT

Reason:

A COMM WRITE command could not be executed in the specified monitoring time. Application:

Repeat the command if necessary. Measure:

(40)

COMM mutiplexer

2000FE09 COMM_READ_TIMEOUT Reason:

A COMM READ command could not be executed in the specified monitoring time. - Line connection, power supply not okay.

- Device faulty.

- Software configuration faulty. Application:

Check the line connection, power supply.

Check device (selftest, light-emitting diode, test program). 2000FE0A COMM_READ_CANCELED

Reason:

A COMM READ command is cancelled by the user. No entry is made in the error log. 2000FE0B COMM_PARITY_ERROR

Reason:

The COMM driver reports a parity error. The received data block is invalid. Measure:

If the error recurs, check the hardware. 2000FE0C COMM_GENERAL_FAILURE

Reason:

The COMM driver reports a general error. Measure:

Check the hardware and report the error log of this entry to Service. 2000FE0F COMM_PROTOCOL_VIOLATION

Reason:

The peripheral device did not answer in a specified monitoring time as expected. Reasons may be: a) Peripheral not attached or switched off

b) Peripheral was switched off while a connection was open c) Cable or peripheral hardware problem

Application:

Close the device and open it again. Measure:

(41)

COMM mutiplexer

2000FE13 COMM_CHAN_NOT_INITIALIZED Reason:

The channel was not initialized. Application:

Check the application program. Measure:

Initialize the channel before using it. 2000FE14 COMM_ACCESS_DENIED

Reason:

Access to port denied. The parallel port is already assigned exclusively by an appropriate driver command (e.g. IOCTL_PAR_CSC_SELECT_ECP_RESERVE).

Measure:

Fix the configuration or application error. 2000FE16 COMM_BREAK

Reason:

The COMM driver reports a break. Measure:

If the error recurs, check the hardware. 2000FE7A COMM_OVERRUN_ERROR

Reason:

The COMM driver reports a overrun error. Measure:

Check the hardware and report the error log of this entry to Service. 2000FE7B COMM_FRAMING_ERROR

Reason:

The COMM driver reports a framing error. Measure:

(42)

COMM mutiplexer

2000FE85 COMM_DRIVER_OPEN_FAILED Reason:

The COMM driver could not be opened. Measure:

Check serial device entry in Registry/CSC.INI. Check if additional COMM drivers are installed (e.g. "ROCKET.SYS"). Check COMM Hardware.

2000FE89 COMM_INVALID_PTXDATA Reason:

The pointer "pTxData" is illegal. Application:

Transfer a legal pointer to the multiplexer in the application program. 2000FE8B COMM_INVALID_OPEN_SPEC

Reason:

The called function is invalid for the used CscCommOpen specification. Application:

Use the definition in the COMM.H definition file. 2000FE8C COMM_NO_STX

Reason:

The peripheral device does not return an STX. Application:

Repeat the command and if necessary initialize the device again beforehand. Measure:

Check the hardware. 2000FE8D COMM_NO_ETX

Reason:

The peripheral device does not return an ETX. Application:

(43)

COMM mutiplexer

2000FE8E COMM_INVALID_BLK_LEN Reason:

The expected block length does not agree with the transmitted block length. Application:

Check the hardware.

2000FE8F COMM_INVALID_BLK_ID Reason:

The block ID is invalid. Application:

Check the hardware.

2000FE90 COMM_INVALID_DEV_ID Reason:

The received device ID does not agree with the transmitted device ID. Application:

Check the hardware.

2000FE91 COMM_INVALID_COMMAND Reason:

The received command specification does not agree with the transmitted command specification. Application:

(44)

COMM mutiplexer

2000FE92 COMM_INVALID_ACK_TYPE Reason:

The received acknowledge type is invalid (only ACK and NAK are valid). Application:

Check the hardware.

2000FE93 COMM_MAX_TX_RETRIES Reason:

The maximum number of repeat transmissions has been reached. Application:

Check the hardware.

2000FE94 COMM_MAX_RX_RETRIES Reason:

The maximum number of receive repeats has been reached. Application:

Check the hardware.

2000FE95 COMM_PROTOCOL_TX_TIMEOUT Reason:

The total protocol monitoring time during transmission has been exceeded. Application:

(45)

COMM mutiplexer

2000FE96 COMM_PROTOCOL_RX_TIMEOUT Reason:

The total protocol monitoring time during receive has been exceeded. Application:

Check the hardware.

2000FE97 COMM_PROTOCOL_POLL_TIMEOUT Reason:

The busy time transmitted from the peripheral device is exceeded. Application:

Check the hardware.

2000FE98 COMM_PROTOCOL_CANCELED Reason:

The protocol was cancelled. Application:

Check the application program. 2000FE9C COMM_INVALID_TXDATA_LEN

Reason:

The length in TxData is 0 (zero). Application:

Specify a legal length.

2000FE9D COMM_CSCISO_DLL_NOT_FOUND Reason:

The CSCWISO.DLL could not be found in the PATH (normally <CSCROOT>\DLL). Measure:

(46)

COMM mutiplexer

2000FE9E COMM_CSCISO_DLL_OPEN_FAILED Reason:

The CSCWISO.DLL could not be opened. Measure:

Report the error log of this entry to Service. 2000FE9F COMM_CSCUSB_DLL_NOT_FOUND

Reason:

The CSCWUSB.DLL could not be found in the PATH (normally <CSCROOT>\DLL). Measure:

Check whether CSCWUSB.DLL is in the PATH (normally <CSCROOT>\DLL). 2000FEA0 COMM_CSCUSB_DLL_OPEN_FAILED

Reason:

The CSCWUSB.DLL could not be opened. Measure:

Report the error log of this entry to Service. 2000FEB0 COMM_INVALID_DRIVER_CONF

Reason:

A configured driver (COM, CH, LPT) gets not the state running. Measure:

Report the error log of this entry to Service. 2000FEE0 COMM_P2_TX_NO_RESP_ON_ENQ

Reason:

The command could not be transmitted because the peripheral device did not answer. Measure:

Check the hardware.

2000FEE1 COMM_P2_TX_INVALID_RESP_ON_ENQ Reason:

The command could not be transmitted because the peripheral device did not answer as expected. Application:

(47)

COMM mutiplexer

2000FEE2 COMM_P2_TX_NAK_RECEIVED Reason:

The command could not be transmitted because the peripheral device announced that it is busy. Application:

Check the hardware if necessary.

2000FEE3 COMM_P2_TX_NO_VALID_RESP_ON_TEXT Reason:

The command could not be completely transmitted because the peripheral device did not answer as expected.

Application:

Initialize the device and repeat the transaction. Measure:

Check the hardware.

2000FEE4 COMM_P2_TX_MAX_RETRIES Reason:

The command could not be completely transmitted because the maximum number of repeat transmissions has been reached.

Application:

Check the hardware.

2000FEE5 COMM_P2_TX_ABORTED Reason:

The command could not be completely transmitted because the device asked for the termination of the transmission.

Application:

(48)

COMM mutiplexer

2000FEE6 COMM_P2_RX_CMD_TIMEOUT Reason:

The peripheral device did not answer in the specified monitoring time of the command. Application:

Check the hardware.

2000FEE7 COMM_P2_RX_ISO_TIMEOUT Reason:

The response of the device has not been completely received because one of the internal protocol monitoring times has been exceeded.

Application:

Check the hardware.

2000FEE8 COMM_P2_RX_INVALID_HEADER Reason:

The header of the response is invalid. Application:

Check the hardware.

2000FEE9 COMM_P2_RX_INVALID_DEVICE_ID Reason:

The received device ID does not agree with the transmitted device ID. Application:

Repeat the command and if necessary initialize the device again beforehand Measure:

(49)

COMM mutiplexer

2000FEEA COMM_P2_RX_INVALID_CMD_ID Reason:

The received command ID does not agree with the transmitted device ID. Application:

Check the hardware.

2000FEEB COMM_P2_RX_INVALID_CMD_SPEC Reason:

The received command specification does not agree with the transmitted command specification. Application:

Repeat the command and if necessary initialize the device again beforehand Measure:

Check the hardware.

2000FEEC COMM_P2_RX_CRC_ERROR Reason:

The response of the device has not been completely received because one of the transmission blocks could not be received without faults.

Application:

Initialize the device and repeat the transaction Measure:

Check the hardware.

2000FEED COMM_P2_NO_CMD_ACTIVE Reason:

A cancel command has been called while no command was active. Application:

Call the cancel command only when a cancelable command is active. 2000FEEF COMM_P2_CMD_NOT_CANCABLE

Reason:

A cancel command has been called while a not cancelable command was active. Application:

(50)

COMM mutiplexer

2000FEF0 COMM_P2_CMD_STILL_ACTIVE Reason:

The command could not be executed because another command was still active Application:

Repeat the command and if necessary initialize the device again beforehand. 2000FEF1 COMM_P2_CMD_CANCELLED

Reason:

The command was aborted by the user. No entry will be made in the error log. 2000FEF2 COMM_P2_CANCEL_STILL_ACTIVE

Reason:

The command could not be executed because a cancel command was still active. Application:

Repeat the command and if necessary initialize the device again beforehand. 2000FEF3 COMM_P2_CANCEL_NOT_SUCCESSFUL

Reason:

A cancel command could not be executed. Application:

Repeat the cancel command.

2000FEF4 COMM_P2_TX_CANCEL_TIMEOUT Reason:

The command could not be cancelled because an internal monitoring time has been exceeded. Application:

Check the hardware.

2000FEF5 COMM_P2_SYNCHRONISATION_ERROR Reason:

Internal error within the CSCWISO.DLL. Measure:

(51)

IEEE 1394

StClass:

STCLASS_OK No

error

STCLASS_ERROR_1394 Error of the CSCW1394.DLL

StCode:

2000FE09 I1394_READ_TIMEOUT Reason:

A IEEE 1394 read command could not be executed in the specified monitoring time. Application:

Check the hardware if necessary. 2000FE0A I1394_READ_CANCELED

Reason:

A IEEE 1394 read command is cancelled by the user. No entry is made in the error log. 2000FE89 I1394_INVALID_PDATA

Reason:

The pointer "pData" is illegal. Application:

Transfer a legal pointer to the device handler in the application program. 2000FE9C I1394_INVALID_DATASIZE

Reason:

The length in DataSize is 0 (zero). Application:

(52)

IEEE 1394

2000FE9D I1394_TS_DLL_NOT_FOUND Reason:

The I1394_TS.DLL could not be found in the PATH. Normally <CSCROOT>\DLL. Measure:

Check whether I1394_TS.DLL is in the PATH. Normally <CSCROOT>\DLL. 2000FE9E I1394_TS_DLL_OPEN_FAILED

Reason:

The I1394_TS.DLL could not be opened. Measure:

Report the error log of this entry to Service. 2000FE9F I1394_UB_DLL_NOT_FOUND

Reason:

The I1394_UB.DLL could not be found in the PATH. Normally <CSCROOT>\DLL. Measure:

Check whether I1394_UB.DLL is in the PATH. Normally <CSCROOT>\DLL. 2000FEA0 I1394_UB_DLL_OPEN_FAILED

Reason:

The I1394_UB.DLL could not be opened. Measure:

Report the error log of this entry to Service. 200A0020 I1394_ERROR_TIMEOUT

Reason:

Internal driver error: Driver responded timeout status. Application:

(53)

IEEE 1394

200A0100 I1394_ERROR_NO_MEMORY Reason:

Internal driver error: Out of memory. Application:

200A0210 I1394_ERROR_INVALID_DEVICE_STATE Reason:

Internal driver error: Device is not in working state. Application:

200A0300 I1394_ERROR_INVALID_PARAMETER Reason:

Internal driver error: Invalid parameter. Application:

200A0305 I1394_ERROR_INVALID_BUFFER_SIZE Reason:

Internal driver error: Size of buffer is invalid. Application:

(54)

IEEE 1394

200A8001 I1394_ERROR_DEVICE_NOT_FOUND Reason:

Internal driver error: Device not found. Application:

200A8010 I1394_ERROR_NO_SUCH_DEV_INSTANCE Reason:

Internal driver error: No such device instance. The IEEE 1394 driver could not be opened. Application:

Check device entry in Registry. Check if IEEE 1394 drivers are installed. Check IEEE 1394 Hardware. Check the hardware if necessary.

200B0100 I1394_ERROR_ABORTED Reason:

Internal driver error: The operation was cancelled/aborted by the miniport because it could not be performed (for example there is a critical hardware error that halted the adapter, or the miniport is unloading).

Application:

Check the hardware if necessary. 200B0200 I1394_ERROR_ADAPTER

Reason:

Internal driver error: A non-critical error occurred on the adapter that caused the request to fail. The error affected only this operation and the adapter is otherwise functioning normally.

Application:

(55)

IEEE 1394

200B0250 I1394_ERROR_ALREADY_OPEN Reason:

Internal driver error: The application has already opened the specified adapter. Application:

Check the hardware if necessary. 200B0270 I1394_ERROR_BR_LIMIT

Reason:

Internal driver error: The operation was cancelled because more bus resets occurred than the operation could tolerate.

Application:

Check the hardware if necessary. 200B0300 I1394_ERROR_BUS_RESET

Reason:

Internal driver error: The operation was cancelled because a 1394 bus reset took place. For example a queued asynchronous transaction must be failed because the target NodeID might not be the same after the bus reset.

Application:

Check the hardware if necessary. 200B0350 I1394_ERROR_CONFLICT

Reason:

Internal driver error: The operation could not be completed because there was a conflict. Application:

(56)

IEEE 1394

200B0370 I1394_ERROR_CRC Reason:

Internal driver error. Application:

Check the hardware if necessary. 200B0400 I1394_CRITICAL_ADAPTER_ERROR

Reason:

Internal driver error: A critical error occurred on the adapter that caused the request to fail. The adapter is not fully functional and the class driver should take corrective actions (closing an isochronous channel, resetting the adapter etc).

Application:

Check the hardware if necessary. 200B0500 I1394_ERROR_DEVICE_BUSY

Reason:

Internal driver error: The operation requested failed because the local adapter is busy. Application:

Check the hardware if necessary. 200B0572 I1394_ERROR_DMA

Reason:

(57)

IEEE 1394

200B0600 I1394_DRIVER_INTERNAL_ERROR Reason:

Internal driver error: The driver detected a bug in its execution logic (through assertions or sanity checks), and could not complete the operation.

Application:

200B0639 I1394_ERROR_DUPLICATE_CHANNEL Reason:

Internal driver error: The isochronous channel number is already in use. Application:

Check the hardware if necessary. 200B0645 I1394_ERROR_FIFO_OVERRUN

Reason:

Internal driver error: An isochronous operation failed because of a FIFO overrun. Application:

Check the hardware if necessary. 200B0658 I1394_ERROR_FIFO_UNDERRUN

Reason:

Internal driver error: An isochronous operation failed because of a FIFO underrun. Application:

(58)

IEEE 1394

200B0671 I1394_ERROR_GAP_COUNT Reason:

Internal driver error: The class driver detected that not all the self?ID packets that were transmitted after the last bus reset contained the same value in their gap_count field.

Application:

200B06B2 I1394_ERROR_INCORRECT_RESPONSE Reason:

Internal driver error: An outgoing response packet is not valid. Application:

200B0700 I1394_ERROR_INSUFFICIENT_RESOURCES Reason:

Internal driver error: An operation failed due to some lack of resources other than memory. Application:

200B0900 I1394_ERROR_INVALID_CHANNEL_TYPE Reason:

Internal driver error: The operation requested is not applicable to the channel type. Application:

(59)

IEEE 1394

200B0A00 I1394_ERROR_INVALID_CHANNEL_STATE Reason:

Internal driver error: The operation requested is not possible at the channel's current operating state.

Application:

Check the hardware if necessary. 200B0C00 I1394_ERROR_INVALID_HANDLE

Reason:

Internal driver error: The miniport adapter handle passed to the miniport does not identify one of its adapters.

Application:

200B0D00 I1394_ERROR_INVALID_ISOCHRONOUS_BUFFERS Reason:

Internal driver error: A validation check on a number of isochronous buffers failed. Application:

Check the hardware if necessary. 200B0D47 I1394_ERROR_INVALID_OFFSET

Reason:

Internal driver error: The 1394 address space offset specified was above the highest 1394 offset (0xFFFFFFFFFFFF), or the address range specified spanned the highest 1394 offset.

Application:

(60)

IEEE 1394

200B0F00 I1394_ERROR_INVALID_REQUEST Reason:

Internal driver error: The request passed to the miniport was invalid, and there was no other more specific error status for this operation.

Application:

200B0F50 I1394_ERROR_INVALID_RESPONSE Reason:

Internal driver error: An response packet was received that was invalid for the corresponding transaction request, or the class driver detected that an outgoing response is not complying with the rules set by the standard with regards to header information (destination NodeID, transaction code, data length).

Application:

Check the hardware if necessary. 200B0F73 I1394_ERROR_LOCK_FAILED

Reason:

Check the hardware if necessary. 200B1070 I1394_ERROR_NOT_FOUND

Reason:

Internal driver error: The requested item was not found. Application:

(61)

IEEE 1394

200B1100 I1394_ERROR_NOT_IMPLEMENTED Reason:

Internal driver error: The request passed to the miniport was valid, the adapter hardware supports the functionality but the miniport does not implement this feature.

Application:

Check the hardware if necessary. 200B1200 I1394_ERROR_NOTSUPPORTED

Reason:

Internal driver error: The request passed to the driver was valid, but the driver software or the adapter itself does not support the required functionality.

Application:

Check the hardware if necessary. 200B1300 I1394_ERROR_PENDING

Reason:

Internal driver error: The request is queued in the miniport and will be processed asynchronously. Application:

Check the hardware if necessary. 200B1313 I1394_ERROR_SELFID

Reason:

Internal driver error: The class driver detected that there was some structural/logical problem in the self?ID packets that were transmitted after the last bus reset.

Application:

(62)

IEEE 1394

200B132A I1394_ERROR_SIZE_LIMITATION Reason:

Internal driver error: The request cannot be transmitted because the payload size cannot be transmitted on the path to the destination node.

Application:

Check the hardware if necessary. 200B1350 I1394_ERROR_SPEED_LIMITATION

Reason:

Internal driver error: The request cannot be transmitted because the payload size is greater than the maximum allowed for the adapter's speed.

Application:

Check the hardware if necessary. 200B1409 I1394_ERROR_TOPOLOGY

Reason:

Internal driver error: The class driver detected that although there was no structural/logical problem in the self?ID packets that were transmitted after the last bus reset, the bus topology described by them is not valid.

Application:

200B1433 I1394_ERROR_TRANSACTION_FAILED Reason:

Internal driver error: A transaction request has been sent, its corresponding response was received, and the response code indicated that the transaction was not completed successfully.

Application:

(63)

IEEE 1394

200B1450 I1394_ERROR_UNSOLICITED_RESPONSE Reason:

Internal driver error: An application tried to transmit a response that did not have a matching request. This can happen if the response is indeed unsolicited, or if the application was so late that the request was timeout and an additional split transaction timeout occurred and the entry was cleared.

Application:

Check the hardware if necessary. 200B1500 I1394_ERROR_UNSUCCESSFUL

Reason:

Internal driver error: The requested operation failed and there is no other more specific error status for the situation.

Application:

Check the hardware if necessary. 200E0001 I1394_FAILED

Reason:

Internal driver error: Operation failed. Application:

Check the hardware if necessary. 200E0010 I1394_ERROR_NOT_SUPPORTED

Reason:

Internal driver error: Operation not supported. Application:

(64)

IEEE 1394

200E0011 I1394_ERROR_VERSION_MISMATCH Reason:

Internal driver error: API Version does not match. Application:

Check application.

200E0030 I1394_ERROR_REJECTED Reason:

Internal driver error: Operation rejected. Application:

Check the hardware if necessary. 200E0110 I1394_ERROR_POOL_EMPTY

Reason:

Internal driver error: Packet pool empty. Application:

200E0200 I1394_ERROR_DEVICE_NOT_PRESENT Reason:

Internal driver error: Device is removed. Application:

200E0220 I1394_ERROR_INVALID_POWER_STATE Reason:

Internal driver error: Requested power state transition not allowed. Application:

(65)

IEEE 1394

200E0280 I1394_ERROR_POWER_DOWN Reason:

Internal driver error: Operation rejected, device is powered down. Application:

Check the hardware if necessary. 200E0302 I1394_ERROR_INVALID_IOCTL

Reason:

Internal driver error: Invalid IO control code. Application:

200E0304 I1394_ERROR_INVALID_BYTE_COUNT Reason:

Internal driver error: Requested byte count doesn´t match buffer size. Application:

Check the hardware if necessary. 200E0310 I1394_ERROR_INVALID_INBUFFER

Reason:

Internal driver error: Input buffer too small. Application:

(66)

IEEE 1394

200E0320 I1394_ERROR_INVALID_OUTBUFFER Reason:

Internal driver error: Output buffer too small. Application:

Check the hardware if necessary. 200E0340 I1394_ERROR_BOUND_TO_THIS

Reason:

Internal driver error: Handle already used by an object of this type. Application:

Check the hardware if necessary. 200E0341 I1394_ERROR_BOUND_TO_OTHER

Reason:

Internal driver error: Handle already used by an object of another type. Application:

Check the hardware if necessary. 200E0342 I1394_ERROR_NOT_BOUND

Reason:

Internal driver error: Handle not associated with required object. Application:

(67)

IEEE 1394

200E0350 I1394_ERROR_BUS_RESET_OCCURED Reason:

200E0351 I1394_ERROR_INVALID_GEN_COUNT Reason:

200E0400 I1394_ERROR_INVALID_CONFIG_TYPE Reason:

Internal driver error: Invalid configuration info type. Application:

200E0401 I1394_ERROR_INVALID_INFO_TYPE Reason:

Internal driver error: Invalid local host info type. Application:

(68)

IEEE 1394

200E0402 I1394_ERROR_INVALID_PROP_TYPE Reason:

Internal driver error: Invalid local host property type. Application:

200E0403 I1394_ERROR_INVALID_LOCK_TYPE Reason:

Internal driver error: Unsupported type of lock operation. Application:

Check the hardware if necessary. 200E0404 I1394_ERROR_INVALID_SPEED

Reason:

Internal driver error: Unsupported speed selected. Application:

Check the hardware if necessary. 200E8002 I1394_ERROR_DEVICE_NOT_OPEN

Reason:

Internal driver error: Device not open. Application:

(69)

IEEE 1394

200E8003 I1394_ERROR_WAIT_TIMEOUT Reason:

Internal driver error: Request timeout interval has expired. Application:

200E8008 I1394_ERROR_INVALID_FUNCTION_PARAM Reason:

Internal driver error: Invalid parameter in function call. Application:

200E8020 I1394_ERROR_MEM_ALLOC_FAILED Reason:

Internal driver error: Memory allocation failed. Application:

(70)

(71)

Universal serial bus (USB)

StClass:

STCLASS_OK No

error

STCLASS_ERROR_USB Error

of the CSCWUSB.DLL

StCode:

20008000 USB_FALSE_DESCRIPTOR_TYPE Reason:

A unexpected descriptor was reported from the USB device. Measure:

Inform system administrator. 20008001 USB_DEVICE_NOT_FOUND

Reason:

Device not found. Application:

Check the hardware if necessary. 20008002 USB_INSUFFICIENT_MEMORY

Reason:

Not enough memory available. Measure:

Inform system administrator. 20008003 USB_ENDPOINT_NOT_FOUND

Reason:

(72)

Universal serial bus (USB)

20008004 USB_CREATE_DEVICE_LIST_FAILED Reason:

The creation of the list of USB devices failed. Measure:

Inform system administrator. 2000E001 USB_I_WIN_ERR

Reason:

The operating system returned an error. Measure:

Check the system error code in the log file. If necessary, inform system administrator. 2000E002 USB_I_INSTUSB_ERR

Reason:

The InstUsb tool returned an error. Measure:

Check the error entry that has been logged by InstUsb. If necessary, inform system administrator. 2000FE09 USB_READ_TIMEOUT

Reason:

A USB read command could not be executed in the specified monitoring time. Application:

Check the hardware if necessary. 2000FE0A USB_READ_CANCELED

Reason:

A USB READ command is cancelled by the user. No entry is made in the error log. 2000FE89 USB_INVALID_PDATA

Reason:

The pointer "pData" is illegal. Application:

CSCw32 Sys Eng1

System messages

Questions and suggestions

Do you have ...

... any questions or suggestions regarding

... any technical questions or problems?

this manual?

Please note the order number or the date

Please refer to the Wincor Nixdorf

of issue of this manual and refer it to:

Customer Care Center:

address: E-mail:

[email protected]

Wincor Nixdorf International GmbH

Handbuchredaktion BD P5

33094 Paderborn

Germany

System messages

CSC-W32 V2.0/52

Copyright © Information and trademarks

© Wincor Nixdorf International GmbH 2004

All rights, including rights of translation and

rights of reproduction by reprinting,

copying or similar methods, even of parts,

are reserved.

Any violations give rise to a claim for

damages.

All rights, including rights created by patent

grants or registration of a utility model or

design, are reserved. Delivery subject to

availability; right of technical modifications

reserved.

All names of hardware and software

products mentioned in this manual are

trade names and/or trademarks of their

respective manufacturers.

Contents

Preface ...1

Target group ...1

Summary of contents ...1

Notational conventions...2

Message handling...3

Status/error classes ...4

Allocation of error codes ...7

Error entry ...8

Global error codes ...9

CSC error codes ...9

INI error codes ...16

Return code handler (RCH)...21

Error statistics (EST) ...25

Transaction statistics (TRA) ...29

COMM mutiplexer ...31

IEEE 1394 ...43

Universal serial bus (USB) ...63

DFU / DFUX Loader (DFU) ...83

Power Suspend Mode Manager (PSM) ...87

Card reader unit (IDU)...89

Special electronics (SEL / SEV4)... 115

Softkey/PINpad (PIN) ... 127

Operator Panel (OPL) ... 133

CIT Control Panel (CIT)... 141

Encryption/Decryption Software (EDS) ... 143

Encryption/Decryption module (EDM) ... 147

Secure Cash-Out (SCO)... 163

RSA module... 167

Remote Key Loading ... 169

CBKM module... 173

Swiss Encryption Protocol (SEP)... 175

Security Module SIBS ... 181

Online Personalization Terminals (OPT) ... 185

EPP Firmware Loader (LDE) ... 193

ZKA 3.0 (ZKA) ... 205

Printer (general) ... 221

ND05 printer / PMxx / Document reader ... 227

Scanner module (SCAN) ... 237

ND71, ND74, ND98, ND9A, ND9C, ND9E, TH30 printer... 245

ND79 printer... 253

ND75, ND75S, ND94 printer... 257

ND99 printer ...275

TH21 printer ...281