# SDS - Troubleshooting Sync Operations

Symptom | Probable Cause | Solution
The Sync operation has not displayed any signs of progress for more than one hour (that is, the operation appears to be hung). | Your Internet Explorer session is timing out before the Sync operation is complete. | Install the required Internet Explorer registry file on your PC. The registry file extends your Internet Explorer session and prevents it from timing out before the Sync is complete. Refer to Mitel Knowledge Base article 07-3849-01068 on Mitel Online for instructions.
Specified data has not been synchronized after you complete a Start Sharing operation. | The Start Sharing operation does not synchronize all the shared data across the elements. Only data in the Network Elements form and Cluster Element Definition form are sync'd. It adds the element to the sharing community (member elements) and begins the sharing of data at the specified scope. | If you want to synchronize the shared system form data across the elements, you should compare the forms and then perform a Sync operation. See Comparing Forms and Synchronizing Data.
Synchronizations take too long. | Traffic on the network is slowing the rate of record updates. | Perform the synchronization during a period of low network traffic (for example, after business hours).
Large amounts of data are being synchronized across many elements. | Perform concurrent synchronizations to reduce the amount of time required to complete the synchronizations.
After a sync operation, large numbers of data distribution update errors appear in the SDS Distribution Errors form. | The remote element did not get the updates because the network connection to that element was down. | Fix the network issue. Retry the distribution updates. See Resolving Pending Updates or Errors.
Many data distribution update errors appear in SDS Distribution Errors form after a concurrent sync operation. | During a concurrent synchronization, both the master and member elements reject changes coming from other network elements. Rejected changes create distribution update errors on the master element. | Resolve update errors.
Cannot sync from the local element to a remote element. | The IP addresses assigned to the elements in the Network Elements form are not unique. | Ensure that each element in the Network Elements form is assigned a different IP address.
The system name or type for the network element on the local and remote nodes do not match. | Ensure that the same system name or type is assigned to the element in the Network Elements forms of both the local and remote element.
Cannot sync with the remote element (transport error). | SDS is disabled on the remote element. | Enable SDS in the System Options form of the remote element.
Network connectivity is broken. | Fix network issue.
Synchronization fails due to a form interdependency rule violation. | A synchronization may fail if you attempt to synchronize a form before a form that it is dependent on is completed. For example, you might be unable complete the ARS Digits Dialed form until the ARS Routes form has been completed. | Synchronize the form data in order of form dependency.
Errors show that data has been distributed to a network element in a way that is not consistent with the data in the Remote Directory Number form. | An administrator made an incorrect entry in the Remote Directory Number form at an element somewhere in the network and the change has been distributed. | Delete the inconsistent record from the Remote Directory Number form, and reprogram it appropriately.
Synchronization or form compare fails with the following log: An attempt was made to send too much data via SDS to another system. The attempt failed and likely caused an SDS Sync or Compare to fail. Please see the corrective action resources available by searching in the online help for "message buffer size". | SDS is attempting to send too much data in one message (message buffer oversize condition). | Add the bulkMessageBlockSize <size> parameter to the /config/dataservices/SDSDSCtrlr.cfg file, increasing the <size> from the default 1560 to the required value; for example, 2200. Contact Mitel Technical Support for details. NOTE: This action decreases the system memory size available after a sync.

Related Topics

- Viewing Data Distribution Errors

- Resolving Pending Updates or Errors

- Troubleshooting Sync Operations