Problem: Errors may be reported when activating applications. Many of these problems can be avoided through proper development or configuration practices.
See Best Practices for Avoiding Common Registration and Activation Errors in Mobile Application Life Cycle.
Error: 558 Message: 'Could not connect to server. Verify Relay Server URL Template'.is returned.
Explanation: This error may indicate that the Server address, Relay Server address, Port, and Company ID, sent from the application (device), are not correct.
Solution: Verify that these values are all set correctly.
Problem: The authentication parameters submitted by the device application are not valid.
Explanation: The username or password/activation code sent from the device may not be correct.
Solution: Enter the correct username or activation/registration code on the device.
void onConnectionStatusChanged(int connectionStatus, int errorCode, String errorMessage); errorCode = 580 errorMessage = "Error: 580 Message: 'TM Error:InvalidAuthenticationParameters'"
Explanation: This can happen for Android, BlackBerry, iOS, and Windows Mobile native object API applications, if an application is deleted from SAP Control Center.
Solution: To continue using the application, unregister and re-register the application. You lose the previous subscription on the server-side. Delete the client database and perform another initial synchronization. See startConnection in the Developer Guide: <Device Platform> Object API Applications for your platform for details.
Problem: When you have registered a device on one SAP Mobile Server, then try to connect the same device to a different SAP Mobile Server you encounter error: 584: Wrong public key.
Explanation: This may happen for ODP applications if you do not use the clearServerVerificationKey() method in your application. This method helps avoid registration problems when moving from one server to another.
Solution: Reengineer the mobile application to use the clearServerVerificationKey() method.
Problem: During initialization, you receive multiple 404 errors Page Not Found errors.
Explanation: During initialization, the client may try several URLs in an attempt to discover the correct path to the SAP Mobile Platform server. During these attempts, 404 errors Page Not Found may occur and are reported to the OnHttpCommunicationError callback. This is expected behavior.
Solution: You can safely ignore these messages. If the 404 errors messages continue to occur after successful application activation, or if device registration never completes, verify the UrlSuffix setting of the application's ConnectionProperties object.