ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Mirror Database error with the Schemus LDAP Synchronization tool

book

Article ID: 161357

calendar_today

Updated On:

Products

Email Security.cloud

Issue/Introduction

You are using trying to run a Schemus synchronization but the synchronization fails due to a mirror database error message.

This synchronization has been aborted because it was not possible to update the mirror database.

Cause

The most likely reason for this error is multiple installs of the Schemus tools running on different servers or the synchronization shown was attempted from a different Windows user account from the previous synchronization.

Environment

This applies to all of the operating systems shown below that are running the Schemus LDAP Synchronization tool version 1.47 or 1.5.

  • Windows Vista
  • Windows7
  • Windows 8
  • Windows 10
  • WIndows 2003
  • Windows Server 2008r2
  • Windows Server 2012r2

Resolution

This file is found in the following location.  (Note some of the folders may be hidden)

Windows XP & Server 2003:

C:Documents and Settings\All Users\Application Data\Schemus\configurations[Configuration name]\syncdata.sus
C:Documents and Settings\All Users\Application Data\Schemus\configurations[Configuration name]\uers.sus
C:Documents and Settings\All Users\Application Data\Schemus\configurations[Configuration name]\groups.sus

Windows Vista, 7, 8, 10, & Server 2008, 2012:

C:\ProgramData\Schemus\configurations[Configuration name]\syncdata.sus
C:\ProgramData\Schemus\configurations[Configuration name]\users.su
C:\ProgramData\Schemus\configurations[Configuration name]\group.sus

You can either:

  • delete the above file(s) (in which case a full synchronization will be performed)
  • change the permissions for the configurations\[Configuration Name] folder so that both accounts have full access;
  • always use the same account to perform the synchronization;
  • change the file permissions for configurations\[Configuration Name]\syncdata.sus (in which case the same problem will occur the next time a different user performs the synchronization)