This section contains a list of error messages and their codes.
Code |
Error message content |
Description |
---|---|---|
1001 |
XML Parsing error. |
Error that occurred when parsing the XML request. Check the XML syntax for your input data. |
1002 |
Missing required tag. |
Error the occurred due to missing of required information in the input
data, for example, a document
|
1003 |
Wrong SIETS storage. |
Error occurred due to incorrect name of the SIETS storage. Check if the SIETS storage name, IP address, and the port are correct. |
1004 |
Invalid user name. |
Error occurred due to incorrectly entered user name. For information on user administration, see the SIETS Administration and Configuration Guide. |
1005 |
User not allowed to login from that IP. |
Error occurred due to restriction to login from that IP. For information on user administration, see the SIETS Administration and Configuration Guide. |
1006 |
Incorrect password. |
Error occurred due to incorrectly entered password. For information on user administration, see the SIETS Administration and Configuration Guide. |
1008 |
Invalid command name. |
Error occurred due to incorrectly entered command name. Check the command name and if the SIETS API version corresponds to the SIETS server version. |
1009 |
System is busy. |
Error occurred due to a massive load. Check that there are enough resources for the SIETS server, or that there are no hardware problems. |
1010 |
Subsystem not responding. |
Error occurred due to a fatal error. Check if all SIETS server processes are running. For more information on SIETS server processes, see the SIETS Administration and Configuration Guide. |
1012 |
Requested document does not exist. |
Error occurred due to that a document with the ID does not exist in the SIETS storage for functions like |
1013 |
Memory allocation failed. |
Error occurred due to an internal error when trying to allocate memory. Check if there is enough RAM for the SIETS server. |
1014 |
Disk I/O error. |
Error occurred due to an input or output error. Check your hard disk for a damage or occupied disk space overflow. |
1016 |
Internal error. |
Error occurred due to a memory corruption. This is a fatal error, possibly caused by a hardware damage, kernel panic, or software error. |
1021 |
Document with that ID already exists. |
Error occurred due to that a document with such ID already exists in the
SIETS storage for the function |
1022 |
Corrupted data. |
Error occurred due to an internal error in the SIETS storage. It can be caused by hardware damage or a severe software error. |
For different SIETS versions the list of errors may slightly differ.
Problems that occur when working with SIETS can be reported to SIETS technical support.
To report a problem, provide the following to the technical support:
name of your company
SIETS license number
version of the SIETS server
SIETS log files
For contact information on technical support, see Contact Information.
For information on the SIETS log files, see the SIETS Administration and Configuration Guide.