Return codes

Every transaction sent to 1010data returns an XML response containing at least a return code and its corresponding message. The error codes and messages are described here.

Return codes

A nonzero value in the <rc> tag indicates there was an error in processing your transaction. The error can be related to the syntax or semantics of the XML content submitted to the server. The codes are designed to give programs the ability to gracefully deal with errors without having to interpret the contents of the <msg> tag. Possible return codes are as follows:

Table 1. Return codes and messages
Error code <rc> Message <msg>
0 Success

Your transaction completed successfully

1 Unclassified error
2 XML error
3 Missing user identification

You did not provide a UID in the POST request.

4 Invalid user identification

The user ID you provided was invalid.

5 Already logged in

The user ID specified already has an established 1010data session.

6 Missing transaction type
7 Invalid transaction type
8 Missing element
9 Invalid element value
10 Invalid element contents
11 Missing attribute
12 Invalid attribute name
13 Invalid attribute value
14 Invalid directory name
15 No such directory
16 Invalid table name
17 No such table
18 No such directory or table
19 Directory already exists
20 Table already exis ts
21 No query specified
22 Not currently implemented for Quick Queries
23 Too many values
24 Empty table
25 Problem saving table
26 Cannot save into 'uploads' directory
27 Problem deleting table
28 Problem saving file
29 Duplicate column names
30 Duplicate table names
31 No FTP permission
32 Not enough available space left in your account.
33 Problem moving table or directory
34 Problem modifying table or directory attributes
35 Not Logged in
36 <cols> contains columns that do not appear in result
37 You do not own the specified group
38 System is busy
39 You are not at an authorized IP address
41 1010data is unavailable

A nonzero value in the <rc> tag indicates there was an error in processing your transaction. The error can be related to the syntax or semantics of the XML content submitted to the server. The codes are designed to give programs the ability to gracefully deal with errors without having to interpret the contents of the <msg> tag.