Batch Processing error codes
Error code |
Description |
---|---|
1-50 |
Fatal errors |
100-199 |
File read/write errors |
200-299 |
Batch Processing errors |
300-399 |
Configuration errors |
Code |
Description |
---|---|
1 |
Calling JobMode function failed. Function '§§' not implemented! |
|
Critical error – the JobMode specified in the configuration file does not exist Check the value of the variable JobMode_<SCRIPTNAME>. |
2 |
Required [§§] not defined in INI File. |
|
The required variable §§ was not found in the INI file. The script cannot continue without it. |
3 |
Error in INI file [§§] Line: [§§] No '=' found. |
|
An error has occurred in the INI file. A row without an equal sign was detected, which is not a comment, either. The script cannot determine how to interpret this. |
100 |
Couldn't create directory: [§§] §§ |
|
The specified directory could not be created. |
101 |
Couldn't create file: [§§] §§ |
|
The specified file could not be created. |
102 |
Couldn't create LogFile [§§] §§ |
|
The specified log file could not be created. |
103 |
Couldn't create StopJobFile [§§] §§ |
|
The “stop job” file which signals to stop automatic processing for resolving an issue via a manual intervention could not be created. |
104 |
Couldn't read amount information file [§§] |
|
The file <CheckInfoAmountFileName> could not be read. This can only happen if <CheckInfoAmountFile> is true. |
105 |
Couldn't read input directory [§§] |
|
Data from the given directory could not be read. |
106 |
Couldn't remove directory [§§] |
|
The specified directory could not be deleted. |
107 |
Couldn't open file [§§] |
|
The specified file could not be opened. |
108 |
Couldn't remove file [§§] |
|
The specified file could not be deleted. |
109 |
Couldn't read INI-File [§§] §§ |
|
The specified INI file could not be read or found. |
110 |
File copy failed! (§§) [§§]->[§§] |
|
Copying the specified file from the specified source to the specified target directory failed. |
111 |
Different file size after copy! (§§) [§§]->[§§] |
|
The file resulting from a copy operation had a different size than the original file. |
112 |
Can't move file! (§§) [§§]->[§§] |
|
The specified file could not be moved between the specified locations. |
113 |
Different file size after move! (§§) [§§]->[§§] |
|
The file resulting from a move operation had a different size than the original file. |
114 |
§§ Source [§§] is not a directory! |
|
An existing directory was expected but no directory was specified in the function call. This indicates an error in the Batch Processing scripts. |
115 |
Can't move directory! (§§) [§§]->[§§] §§ |
|
Moving the specified directory failed. The error message states the reason given by the operating system. |
120 |
File '§§' not found for [§§] |
|
The specified file, which is required, is missing. |
121 |
Directory '§§' not found for [§§] |
|
The specified directory, which is required, is missing. |
122 |
Couldn't detect free space in directory [§§] |
|
Determining the free space failed. This can be caused by an unsupported operating system / file system platform, e.g. if neither the command “df” (Linux) nor the command “dir” (Windows) is available. |
123 |
Not enough free space in directory [§§]. Free Space: [§§ MB] Required [§§ MB] |
|
The parameter “MinimumDiskFreeSize” can be used to set a required minimum value. A script initially checks the available size in the target directory and stops execution, if there is not enough space. |
130 |
Writing to file [§§] failed |
|
The specified file could not be written, which can be caused by missing permissions. |
200 |
StopJobFile exists for Spool [§§] |
|
Further execution has been stopped, since a stop job file was detected. To restart execution, this file must first be deleted in the log directory. |
201 |
Found directory in Spool, expected a file [§§] |
|
A directory was found in a spool directory instead of a file that was expected. In the current JobMode no directory must exist in the spool directory. |
202 |
No Indexfiles found! |
|
No indexing files with the specified file type extension <IndexFileExtension> could be found. |
203 |
Found file, expected a directory [§§] |
|
In the specified directory a file was found but a directory was expected. Since this JobMode requires a directory, execution is stopped. |
210 |
Sum of Directories [$$] does not match AmountFile [§§] |
|
The number of directories does not match the number given in the AmountFile. |
220 |
File Size 0 Byte for §§ [§§] |
|
The file size is 0, which is not allowed if <ZeroByteFileCheck> is active. |
221 |
LastModificationTime Check failed for §§ [§§] |
|
The specified file is younger than the minimum <LastModificationTime> given in the configuration file. |
230 |
Directory not empty !!! Check [§§] |
|
The directory contains data although it should be empty. This error often occurs if a script is restarted a second time. |
231 |
Empty input directory found [§§] |
|
The input directory is empty although it should contain data. |
232 |
Wrong format of [§§]! §§ |
|
The detected value is of the wrong format or type. This can happen, for example, during archiving if further information is extracted from a directory name. |
240 |
Existing Indexfile [§§] without Datafile [§§] |
|
The specified document data file is missing for the specified indexing file. |
241 |
File [§§] in input dir is older than allowed by MaxFileAgeInInputDir! |
|
The specified file in the input directory is older than <MaxFileAgeInInputDir>. This implies that a document data file was stored in the input directory without a matching indexing file. |
250 |
Too many documents in Spool. Maximum is [§§]. §§ |
|
Too many files have been detected in the spool, which prohibits archiving. It may help to activate the batch mode (<SplittingEnableMultiDocDir>), or to reduce the number of files in the Initialize step. |
251 |
Value §§ is out of range, should be 1 to [§§] |
|
The value of the variable is out of the allowed range. |
252 |
There are [§§] entries in split definition [§§], but there are [§§] IndexValues in the IndexFile |
|
The number of entries in the split configuration file does not match the number of elements found in the indexing file. |
253 |
Compressed mode requires attached documents! No document found or specified! §§ |
|
An expected document is missing. Probably there is a mistake in the <FileField> configuration. |
255 |
IndexValue [§§] exceeded MaxLength! [§§]>[§§] in Line [§§] IndexValue [§§] |
|
A value in the indexing file exceeds the maximum length. |
256 |
FormatPositions specifies use of format rule [§§], but item [§§] is not defined in split definition |
|
In the value of <FormatPositions> a formatting rule is referenced which does not exist in the configuration file. For example, if in <FormatPositions> the value 5 is referenced, the following related parameters must be specified: Format5Type, Format5Input, and Format5Output. |
257 |
Unknown Format Rule Type [§§] specified for Format?Type |
|
An unknown format type is specified in the split configuration file. The values DATE, TIME, and REPLACE are currently supported. |
258 |
Number of fields in [§§] does not match number of fields in [§§] |
|
The number of elements must be the same in both configuration parameters, which is not the case here. |
270 |
FastArchiver Execution failed! §§ |
|
FastArchiver execution failed. Check the specified path which must point to the location of the executable. |
271 |
ImaFileApi Execution failed! §§ |
|
ImaFileAPI execution failed. Check the specified path which must point to the location of the executable. |
272 |
ImaFileApi – UpdateByKeyValues Error, see [§§] for details |
|
An error occurred during the execution of ImaFileAPI. Further details can be taken from the log file. |
273 |
Couldn't execute command [§§] §§ |
|
An error occurred during the execution of the command. |
274 |
[§§] directories could not be archived. |
|
During the attempt to store data in ImageMaster an error occurred and some directories could not be archived. A detailed list of the directories is contained in the log files. |
275 |
Command [§§] returned exit code [§§] §§ |
|
An error occurred in the execution of the command. The return code from the operating system is given. |
280 |
Can not find mandatory XML attribute e[§§] |
|
An obligatory XML attribute is missing, which is specified in the parameter <PrepXMLInputElementList>. |
290 |
[§§] IDs have been reported, expected [§§] |
|
An unexpected number of IDs was returned by the Report step. This can happen if the report statement mistakenly targets at multiple rows or at none row at all (affected rows != 1). |
300 |
InitValue §§='§§' is not valid boolean! |
|
A Boolean value is expected in the configuration file. The following values are supported, where case does not matter: The “true” value can be represented by one of: true, yes, ja, y, j or 1 |
301 |
InitValue §§='§§' is not valid Number99 value! |
|
An integer number value is expected in the configuration file which must be in the range from 1 to 99. |
302 |
InitValue §§='§§' is not valid path value! |
|
A path value is expected in the configuration file but the given value does not represent be a path. |
303 |
InitValue §§='§§' is not valid number! |
|
A number value is expected in the configuration file, but characters other than digits 0-9 or the characters plus (+), minus, (-) or the decimal point was encountered. |
304 |
InitValue §§='§§' has no valid value for §§! |
|
There is an invalid value in the configuration file. Check the format and make sure that there is no character encoding issue, e.g. with invisible control characters or special characters causing the issue. |
305 |
Error in Ini-File [§§] Index value: [§§] Could not replace <§§> |
|
An undefined variable was referenced in a value assignment, for example: DataInputPath = <ColdInputBaseDirectory>/<SpoolType> Error message: Error in Ini-File [cold.sample.ini] Index value: [DataInputPath] Could not replace <SpoolType> The variable <SpoolType> could not be evaluated. In this example the cause is a typo because the correct spelling of the supported variable ends with an “e”: <SpoolType>. |
310 |
Invalid list of arguments |
|
There is an unexpected number of parameters. |
320 |
Input mask not accepted. Check §§=[§§] |
|
A value specified in the configuration file is invalid. Check the acceptable format. |
321 |
Input mask [§§] has different length than value [§§]. Check §§ |
|
The length of value specified in the configuration file is invalid. It must match the incoming value length. |
330 |
Could not connect to e-mail server [§§]! |
|
The connection to the specified e-mail server failed. |
340 |
Could not connect to SQL server [§§]! |
|
The connection to the specified SQL server failed. |
341 |
Error executing SQL Statement [§§] §§ |
|
An error was raised by a SQL statement. Details are given in the message. |
342 |
No row affected by SQL Statement [§§] |
|
The SQL command has affected no row but at least one row should have been affected. An expected entry in the database may be missing. |
UNDEF |
Error Message undefined! |
|
Displaying an error message failed because it does not exist. Check the error message sources. |