Troubleshoot

Use troubleshooting tips to isolate and resolve common issues.

See Troubleshooting Sybase Unwired Platform for information about troubleshooting issues for Workflow package and other Sybase Unwired Platform components.

• HTTP Error Codes
  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.
• Recovering from EIS Errors
  After sending a JSON request to Unwired Server, if you receive in the response log message an EIS code which is recoverable, the mobile workflow client throws a TransformRetryException or ResponseRetryException, as is appropriate.
• Mapping of EIS Codes to Logical HTTP Error Codes
  A list of SAP® error codes mapped to HTTP error codes. By default, SAP error codes that are not listed map to HTTP error code 500.
• Credentials Are Lost after User Successfully Passes Activation Screen
  User logs in successfully on Activation screen, but is no longer logged in at some point after that.
• Mobile Workflow Exception Handling
  Describes how to handle a blocked mobile workflow.
• Unable to Deploy Workflow
  Problem: When generating the Mobile Workflow package, you get an error that the Mobile Workflow package cannot be deployed similar to this: