Environment
Novell Data Synchronizer Mobility Pack 1.2.1
Situation
User stuck in Sync-Validate for a long time
User goes to synced state after a long time
ERROR: "Initial Sync validation failed for user" in the default.pipeline1.mobility-AppInterface.log
Resolution
After a user is added to the Mobility Connector, it moves through the following state
Syncing-Init - In this state, emails/calendar/contacts are being pulled from GroupWise to Mobility Database
Sync-Validate - In this state, it tries to validate the data that was downloaded from GroupWise to Mobility Database. It compares the count of items in GroupWise with the count in Mobility Database.
Synced -
Syncing-Init - In this state, emails/calendar/contacts are being pulled from GroupWise to Mobility Database
Sync-Validate - In this state, it tries to validate the data that was downloaded from GroupWise to Mobility Database. It compares the count of items in GroupWise with the count in Mobility Database.
Synced -
- If the count of emails/calendars/contacts in Mobility Database is 75% or greater as compared to GroupWise, the Mobility-Connector moves it to the Synced State. The default.pipeline.mobility-Appinterface.log file in this case would show a message similar to "Initial sync for user cn=et0,ou=cust,o=my is complete"
- If the count of emails/calendars/contacts in Mobility Database is less than 75% as compared to GroupWise, Mobility Connector will query GroupWise every 5 minutes for 2 hours. If after 2 hours, it is still less than 75% it will move it to Synced State. The default.pipeline.mobility-Appinterface.log file in this case would show a message similar to "Initial Sync validation failed for user:cn=et0,ou=cust,o=my"
Initial Sync Validation failed means that some data from GroupWise did not make it to the mobility database because of some issues. Please try running GWCHECK on the user account and if needed, re-initialize the user account again.