The following table lists the SDK response codes, cause for failure, and solution wherever applicable:
|
SDK Response Code |
Description |
Possible Cause for Failure |
|
|---|---|---|---|
|
0 |
The SDK has successfully sent the request and has received the response from the server or vice-versa. Note: This does not imply that the transaction was successful. |
N/A
|
|
|
|
|||
|
1 |
Internal error occurred in SDK due to some unexpected reason. |
Possible Cause: |
|
|
2 (Returned by SDKNotInitializedException) |
SDK not initialized successfully. |
Possible Cause: Solution:
|
|
|
|
|||
|
3 (Returned by SDKAlreadyInitializedException) |
SDK is already initialized. |
Possible Cause: |
|
|
4 |
The configuration file, whose absolute path is provided as the input to the initialization API cannot be read. |
Possible Cause: Solution: Possible Cause: Solution: |
|
|
5 (Returned by ServerUnreachableException) |
The SDK is not able to send requests to the configured server. |
Possible Cause: Solution: Possible Cause: Solution: Possible Cause: Solution: |
|
|
6 |
Buffer sent through the output structure is not sufficient. |
Possible Cause: Solution:
|
|
|
|
|||
|
7 (Returned by InvalidSDKConfigurationException) |
The SDK configuration is incorrect. |
Possible Cause: Solution: Possible Cause: Solution: |
|
|
999 (Returned by SDKInternalErrorException) |
Internal error. |
Possible Cause: |
|
Copyright © 2013 CA.
All rights reserved.
|
|