Viewing LDAP sync template results

To view the status of ongoing or completed LDAP template synchronization processes, go to Status > LDAP sync status.

You are shown the details of the most recent or in-progress run of each LDAP synchronization template. Information shown includes:

  • run status e.g. Initializing sync: connecting to LDAP, Syncing, Sync succeeded
  • number of VMRs, devices and users that were created, deleted, updated and unchanged
  • number of warnings
  • last updated date and time.

If necessary, you can select a template to view the details of the last error/warning message it generated. Typical messages include:

Warning Comment
Error syncing with LDAP This can occur if Pexip Infinity fails to connect to, or authenticate with, the LDAP server. In which case the Pexip Infinity support log will provide more information. Alternatively, this can be caused by invalid syntax in the template's LDAP user filter or LDAP user search DN fields.
Alias clash: alias held by an existing conference has not been assigned to the newly synced conference

This occurs when a template generates an alias that is identical to an existing alias that is already assigned to another VMR (either created manually or via another mechanism).

In this case, the alias is not reassigned to the VMR currently being created/updated.

Duplicate alias: attempting to create the same alias more than once for the same conference This occurs when the template attempts to create the same alias more than once for the same conference. Check the alias patterns for your template.
Conference clash: not overwriting manually created conference

This occurs when a template generates a VMR name that already exists, and that VMR was created manually.

In this case, the existing VMR with that name is left unchanged.

Sync template clash: not overwriting conference created by another mechanism

This occurs when a template generates a VMR name that already exists, and that VMR was created via another mechanism such as a different template or VMR Scheduling for Exchange.

In this case, the existing VMR with that name is left unchanged.

Validation error when creating conference

This occurs if the synchronization tries to set a field to an invalid value (e.g. a PIN containing letters rather than numbers, or an empty VMR name).

The error message will include some addition parameters such as Conference, Error and Data which will help to identify the VMR, the field and source LDAP data that is causing the problem.

Validation error when creating device

This occurs if the synchronization tries to set a field to an invalid value (such as an empty alias).

The error message will include some addition parameters such as Device-Alias, Error and Data which will help to identify the device alias, field and source LDAP data that is causing the problem.

Sync template clash: not overwriting device created by another template

This occurs when a template generates a device alias that already exists, and that alias was created via another template.

In this case, the existing device alias is left unchanged.

Device clash: not overwriting manually created device

This occurs when a template generates a device alias that already exists, and that alias was created manually.

In this case, the existing device alias is left unchanged.

Sync template clash: not overwriting User created by another template

This occurs when a template generates a user email address that already exists, and that user record was created via another template.

In this case, the existing user record is left unchanged.

User clash: not overwriting manually created User

This occurs when a template generates a user email address that already exists, and that user record was created manually.

In this case, the existing user record is left unchanged.

All of the warning messages generated from a sync run can be viewed in the Administrator log (Status > Administrator log) as described below.

Viewing all historical sync results via the Administrator log

To view all historic details of completed LDAP synchronization processes:

  1. Go to the Administrator log (Status > Administrator log).
  2. Search for ldap.sync to see details of all log entries relating to all VMR, device and user synchronization processes.

    Note that you will see "Beginning" and "Completed" log entries for VMR, device and user syncing even if the template is not configured to perform both types of syncing. This is because all sync processes are always performed in case they need to delete VMRs, devices or users from previous synchronizations.

More information

For more information about bulk-provisioning VMRs and devices from an LDAP-accessible database, see: