Problem: Errors may be reported during user or device registration. 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.
Problem: This error displays during registration.
Explanation: This happens if you use an incorrect username or password while carrying out SSO based registration.
Solution: Check to make sure you are using the correct user name and password.
Problem: This error displays during registration.
Explanation: This indicates that the security configuration passed from the application installed on the device does not match for the application in SAP Mobile Server.
Solution: Verify that the correct auto registration template is used.
Explanation: This can happen if the physical device was already registered, and is being reregistered to SAP Mobile Server.
Solution: You must first delete the existing device through the available API, then reregister the device.
Problem: This exception can be thrown during application registration or unregistration.
Explanation: The exception is typically thrown when the timeout parameter value is set too low.
Problem: During registration, the application fails without waiting for the registration process to complete.
Explanation: This can happen if the user exits the application before the registration process has had time to complete, but could happen for an unknown reason.
Solution: In either case, the user can restart the application and retry the registration process. If the problem recurs frequently, the developer should check the application to make sure register(), async is set correctly.
Problem: During unregistration, the application fails without waiting for the unregistration process to complete.
Explanation: This can happen if the user exits the application before the registration process has had time to complete, but could happen for an unknown reason.
Solution: In either case, the user can restart the application, then retry unregistration process. If the problem recurs frequently, the developer should check the application to make sure unregister(), async is set correctly.
Problem: The administer deletes an application connection in SAP Control Center before the user has unregistered the application from the device.
Explanation: This is a timing issue.
Solution: The application user can register the application again to create the connection, but does not need to unregister the application.
Problem: The administer deletes an application in SAP Control Center before the user has unregistered the application from the device.
Explanation: This is a timing issue.
Solution: Once the administrator restores the application, the application user can register the application again.