Unwired Server examines the EIS code received in a server response message and maps it to a logical HTTP error code, if a corresponding error code exists. If no corresponding code exists, the 500 code is assigned to signify either a Sybase Unwired Platform internal error, or an unrecognized EIS error. The EIS code and HTTP error code values are stored in log records.
The following is a list of recoverable and non-recoverable error codes. Beginning with Unwired Platform version 1.5.5, all error codes that are not explicitly considered recoverable are now considered unrecoverable.
| Error Code | Probable Cause |
|---|---|
| 409 | Backend EIS is deadlocked. |
| 503 | Backend EIS down or the connection is terminated. |
| Error Code | Probable Cause | Manual Recovery Action |
|---|---|---|
| 401 | Backend EIS credentials wrong. | Change the connection information, or backend user password. |
| 403 | User authorization failed on Unwired Server due to role constraints (applicable only for MBS). | N/A |
| 404 | Resource (table/webservice/BAPI) not found on Backend EIS. | Restore the EIS configuration. |
| 405 | Invalid license for the client (applicable only for MBS). | N/A |
| 412 | Backend EIS threw a constraint exception. | Delete the conflicting entry in the EIS. |
| 500 | SUP internal error in modifying the CDB cache. | N/A |
Beginning with Unwired Platform version 1.5.5, error code 401 is no longer treated as a simple recoverable error. If the SupThrowCredentialRequestOn401Error context variable is set to true (which is the default), error code 401 throws a CredentialRequestException, which sends a credential request notification to the user's inbox. You can change this default behavior by modifying the value of the SupThrowCredentialRequestOn401Error context variable in Sybase Control Center. If SupThrowCredentialRequestOn401Error is set to false, error code 401 is treated as a normal recoverable exception.