Viewing VMR sync template results
To view the status of ongoing or completed VMR template synchronization processes, go to .
You are shown the details of the most recent or in-progress run of each VMR synchronization template. Information shown includes:
- run status e.g. Initializing sync: connecting to LDAP, Syncing, Sync succeeded
- number of VMRs 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 warning message it generated. Typical warnings 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 been reassigned 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 a different template). In this case, the alias will be 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: 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 will be updated with the new settings generated from the template. |
| Sync template clash: overwriting conference created by another template |
This occurs when a template generates a VMR name that already exists, and that VMR was created via a different template. In this case, the existing VMR with that name will be updated with the new settings generated from the template. |
| 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 vmr_name, error and vmr_data which will help to identify the VMR, the field and source LDAP data that is causing the problem. |
All of the warning messages generated from a sync run can be viewed in the Administrator log () as described below.
Viewing all historical sync results via the Administrator log
To view all historic details of completed VMR template synchronization processes:
- Go to the Administrator log ().
-
Search for Beginning VMR Sync or Completed VMR Sync to see details of the start end and events corresponding to every VMR template synchronization process that has occurred.
Alternatively you can search for vmrsync to see details of all log entries relating to VMR synchronization processes.
More information
For more information about bulk-provisioning VMRs from an LDAP-accessible database, see: