IDS Synchronization Error Handling

Synchronization errors are listed in the server manager Event Logs and identified in the IDS Managed Detained queue.

Synchronization errors are also indicated in the Manage IDS Connections page. If the domain is invalid, the connection for the domain is highlighted in red, and the Last Synchronization field, indicates that an error occurred.

If a power outage occurs during synchronization, the system does not attempt to re-synchronize on boot-up. Instead, the system attempts to run the exact same synchronization sequence again on the next interval. You can also click the Sync link if you don't want to wait for the next interval. Additionally, any user entries that were created during a synchronization before the power interruption are sent to the detained updates queue, provided that the user already exists in the MiCollab database.

Error

Possible Cause

Corrective Action

Only a subset of the desired directory service data fields are being updated on MiCollab after an IDS synchronization. In the detained queue certain fields are blank even though they are mapped correctly.

If the Global Catalogue Port option is enabled, it reduces the number of fields that are mapped to the MiCollab user records. Certain attributes, for example employeeType, are not visible when connection is made to the global catalogue.  

Delete the Global Catalogue Port and perform an IDS synchronization.
OR
If you want to use global attribute, map the MiCollab attributes to unused attributes in the global catalogue. To determine what attributes are available in the global catalogue, run the following query in the MiCollab server console:

ldapsearch -x -h <AD server address>  -b "cn=Schema,cn=Configuration,<your domain's DN/distiunguished name>" -D <Distinguished name of account with read priviledges> -w "<password>" "(&(objectClass=attributeSchema)(isMemberOfPartialAttributeSet=TRUE))" lDAPDisplayName

"Failed to contact server(s)"

Mitel Certificate Authority (CA) is not installed on directory server.

Install Mitel Certificate Authority (CA) on directory server. Then, reboot of the AD server