The Mobility Connector does not start
Possible Cause:
The GroupWise Connector is not running.
Action:
Start the GroupWise Connector.
Possible Cause:
The Synchronizer services are not running.
Possible Cause:
A Web server is running on the Synchronizer server. Web servers typically use ports 80 and 443. These ports need to be available for use by the Mobility Connector for communicating with mobile devices.
Action:
Stop and disable the existing Web server or other application that is using ports 80 and 443 on the Synchronizer server.
Possible Cause:
You manually modified the following configuration file:
/etc/datasync/syncengine/connectors.xml
You introduced an error in the XML coding.
Action:
Review the changes you made to the connectors.xml file to make sure that they are correctly coded.
Action:
Revert to a backup of the connectors.xml file that works correctly, then try the modifications again.
Initial device synchronization fails
Possible Cause:
The mobile device fails to connect to the Synchronizer server because you have configured it for a secure SSL connection and the certificate is not working properly.
Possible Cause:
The Mobility Connector is not getting the information it needs from the GroupWise Connector.
Action:
Make sure that the user has already been added to the GroupWise Connector.
Action:
Make sure that the user has a valid GroupWise account.
Possible Cause:
The user’s GroupWise user ID is different from the user’s LDAP user name.
Possible Cause:
Varied.
Action:
Remove the user from the Mobility Connector and the GroupWise Connector, then add the user to both connectors again.
Data does not transfer between the Mobility Connector and a mobile device
Possible Cause:
Varied.
Action:
Remove the user from the Mobility Connector and the GroupWise Connector, then add the user to both connectors again.
Some items never synchronize to the mobile device
Possible Cause:
Some events automatically synchronize to mobile devices. Other events do not synchronize to mobile devices unless users request them. The user has not yet requested the optional events.
Action:
None. This is normal. The unsynchronized events eventually expire.
Possible Cause:
The Mobility Connector might not be transferring the events to the mobile device.
Action:
Check the user’s synchronization status, as described in Section 4.3, Monitoring User Synchronization Status. Observe the column and the column to see if progress is still being made.
If events are still transferring to the device, wait while the process completes.
If events are not transferring to the device, restart the Mobility Connector.
Possible Cause:
The user’s GroupWise mailbox contains a damaged message, or the user’s mailbox is damaged. Mailbox damage can cause the GroupWise Connector to synchronize unusable data to the Mobility Connector.
Possible Cause:
Varied.
Action:
Remove the user from the Mobility Connector and the GroupWise Connector, then add the user to both connectors again.
Data does not match between the GroupWise mailbox and the mobile device
Possible Cause:
Varied.
Action:
Have the user remove the account from the mobile device and re-add the account on the mobile device.
Address book synchronization fails
Possible Cause:
Varied.
Action:
Have the user remove the account from the mobile device and re-add the account on the mobile device.
Possible Cause:
Varied.
Action:
Have the user remove the account from the mobile device and re-add the account on the mobile device.
The specific actions suggested above have not resolved a synchronization problem
Possible Cause:
Varied.
Action:
Perform the following procedure to start over for a particular mobile device user, similar to rebooting a computer:
-
Remove the user’s account from the mobile device.
-
Remove the user from the Mobility Connector.
-
Restart the Synchronizer services.
-
Add the user to the Mobility Connector.
-
Add the user’s account to the mobile device.
Status information on the Mobility Connector Monitoring Information page in Synchronizer Web Admin is not correct
Possible Cause:
The Mobility Connector created during installation of the Mobility Pack was deleted and you manually re-added the Mobility Connector.