The following table summarizes API status codes.
Status Code |
Indicates |
0 |
Successful method execution. |
1 |
No description found for specified column. |
2 |
No field descriptions for this table. |
3 |
Process interruption. |
4 |
Field truncated, receiving field too small. |
5 |
End-of-set indicator (EDAFETCH). |
6 |
Timeout. |
7 |
End of transmission. |
8 |
Field overflow. |
9 |
Method not complete in non-block mode. |
10 |
Default trace initialization failure. |
-1 |
Invalid EID. |
-2 |
Too many identifiers. |
-3 |
Invalid SID. |
-4 |
Too many SCBs allocated. |
-5 |
SCB not initialized. |
-6 |
SCB already initialized. |
-7 |
Unable to initialize connector. |
-8 |
Unable to close connector. |
-9 |
Unable to connect to server. |
-10 |
Unable to disconnect from server. |
-11 |
Data send failure. |
-12 |
Data receive failure. |
-13 |
Operation not permitted in this context. |
-14 |
Insufficient memory available for this operation. |
-15 |
Invalid parameter value. |
-16 |
Tuple alignment error. |
-17 |
Invalid user ID or password. |
-18 |
Internal API error. |
-19 |
Method not available. |
-20 |
Expired password. |
-21 |
Invalid new password. |
-22 |
Encryption version mismatch. |
-23 |
Connection no longer valid. |
-24 |
Invalid server code page. |
-25 |
Statement has not been prepared (EDAEXECUTE). |
-26 |
Invalid server. |
-27 |
Invalid statement. |
-28 |
Invalid Unit of Work. |
-29 |
Invalid message attachment. |
-30 |
Invalid protocol. |
-31 |
Cannot send message. |
-32 |
User ID already in use. |
-33 |
User resource limit reached. |
-34 |
Communications timed out. |
-35 |
Invalid user ID. |
-36 |
Revoked user ID. |
-37 |
Server reports communications error. |
-38 |
Invalid license key. |
-39 |
Invalid Metadata |
-40 |
Invalid Service |
| iWay Software |