Best Practices for Avoiding Common Registration and Activation Errors

Avoid common problems encountered when registering connections, and activating applications once the connection is registered.

Application activation –
- The value of the Server address, Relay Server address, Port, and Company ID, sent from the application (device) must all be correct – if not, when registering an application to SAP Mobile Server, an error (in this case for an incorrect Relay Server address) similar to:
```
Error: 558 Message: 'Could not connect to server. 
Verify Relay Server URL Template'.
```
  is returned.
- The value of the username or password/activation code sent from the device must be correct – if not, the error:
```
Error: 580 Message: 'TM Error:InvalidAuthenticationParameters'.
```
  is returned when attempting to activate/register the application.
- For BlackBerry, Android, Windows Mobile, and iOS native object API applications, if an application is deleted from SAP Control Center, when the client application calls startConnection(), the following callback is triggered inside the ApplicationCallback handler:
```
void onConnectionStatusChanged(int connectionStatus, int errorCode, String errorMessage);
errorCode = 580 
errorMessage = "Error: 580 Message: 'TM Error:InvalidAuthenticationParameters'" 
```
  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 the topic startConnection in the Developer Guide for your platform for details.
- Use the clearServerVerificationKey() method in your application to avoid registration problems when moving from one server to another – 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 may encounter the error:
```
 584: Wrong public key
```
  if you do not use clearServerVerificationKey() in ODP applications.
- 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 and you can safely ignore these initial 404 errors.
  If the 404 errors continue to occur after successful application activation or if device registration never completes, verify the UrlSuffix setting of the application's ConnectionProperties object
User or device registration –
- If a physical device is already registered and is to be reregistered in SAP Mobile Server, you must first delete the existing device through the available API, then reregister – if you attempt to register an already registered device without first deleting the device, the error:
```
14853: Wrong user name for this device. 
```
  is returned.
  Note: The error:
```
14899: Unknown error. 
```
  can be returned for a variety of reasons, including the same registration problem that generates error code 14853.
- Use correct credentials when registering single-sign on (SSO) based registration – if you use incorrect username or password while carrying out SSO based registration, the error:
```
14814 Message: MMS Authentication Failed .
```
  is returned.
- The security configuration on the device and SAP Mobile Server must match – during registration, the error:
```
14850 Message: Auto registration template not found .
```
  is returned when the security configuration passed from the application installed on the device does not match that for the application in SAP Mobile Server.