[LEGACY] Understanding the Synchronization Engine service log

Document created by user.oxriBaJeN4 Employee on Sep 15, 2015Last modified by user.oxriBaJeN4 Employee on Dec 2, 2015
Version 2Show Document
  • View in full screen mode

Applies to: version 2.9.1 and earlier.

Mimecast Synchronization Engine version 2.8.0 and later releases of the Mimecast Synchronization Engine 2.x branch.

The Mimecast Synchronization Engine runs as a Windows service, bridging between your organization's LAN and the Mimecast cloud. When troubleshooting and monitoring Exchange tasks it is important to know what to look for and when to look for it.

 

Log Locations

By default the Mimecast Synchronization Engine service log can be found in the C:\Program Files\Mimecast\SynchronizationEngine\log\service directory on the host server.

 

If the log files are not found in this location, open the Directories tab of the Site Configure utility to find the log location.

site_config_dir.png

 

 

Check that the Synchronization Engine service is running

The Mimecast Synchronization Engine service writes one service log per day. The naming convention for the current log is YYYYMMDD.log. Service logs are periodically uploaded to Mimecast, once this has happened the naming convention changes to YYYYMMDD-uploaded.log.

 

It is possible to assume that the service is running by checking for the presence and modified date of a file named YYYYMMDD.log in the log Mimecast Synchronization Engine log directory.

Where YYYY is the current year. MM, is the current month, DD is the current date.

 

For example, the log file for the 3rd April 2015 would be named 20150403.log

It is also possible to view the status of the Mimecast Synchronization Engine service using the Site Configure utility, the Services Windows Administrative Tool or the sc query command line application.

 

Check a task has started

The Mimecast Synchronization Engine service logs consistent strings in log lines when a task started, the table below provides examples of the strings to search for to check if a specific task has started.

 

FeatureString
Mailbox Folder Replication

Search for log lines containing:

 

MMS

 

AND

 

ClassicExtensionExecutor|waiting for extension to exit voluntary

Calendar Replication

Search for log lines containing:

 

CAL

 

AND

 

ClassicExtensionExecutor|waiting for extension to exit voluntary

Mailbox Storage Management

Search for log lines containing:

 

MCS

 

AND

 

ClassicExtensionExecutor|waiting for extension to exit voluntary

Managed Folders

Search for log lines containing:

 

FBR

 

AND

 

ClassicExtensionExecutor|waiting for extension to exit voluntary

File Archiving

Search for log lines containing:

 

FSR

 

AND

 

ClassicExtensionExecutor|waiting for extension to exit voluntary

Lync Instant Messaging Archiving

Search for log lines containing:

 

IMA

 

 

AND

 

ClassicExtensionExecutor|waiting for extension to exit voluntary

Exchange Ingestion

Search for log lines containing:

 

IOW

 

AND

 

ClassicExtensionExecutor|waiting for extension to exit voluntary

Active Directory Sync

Search for log lines containing:

 

ADR

 

AND

 

ClassicExtensionExecutor|waiting for extension to exit voluntary

 

Check a task has completed

 

FeatureString
Mailbox Folder Replication

Search for log lines containing:

 

MMS

 

AND

 

TaskExit called, scheduedTaskId: ####, message {task_result}

 

Where #### is a unique numeric value and task_result is a message specific to that execution.

Calendar Replication

Search for log lines containing:

 

CAL

 

AND

 

TaskExit called, scheduedTaskId: ####, message {task_result}

 

Where #### is a unique numeric value and task_result is a message specific to that execution.

Mailbox Storage Management

Search for log lines containing:

 

MCS

 

AND

 

TaskExit called, scheduedTaskId: ####, message {task_result}

 

Where #### is a unique numeric value and task_result is a message specific to that execution.

Managed Folders

Search for log lines containing:

 

FBR

 

AND

 

TaskExit called, scheduedTaskId: ####, message {task_result}

 

Where #### is a unique numeric value and task_result is a message specific to that execution.

File Archiving

Search for log lines containing:

 

FSR

 

AND

 

TaskExit called, scheduedTaskId: ####, message {task_result}

 

Where #### is a unique numeric value and task_result is a message specific to that execution.

Lync Instant Messaging Archiving

Search for log lines containing:

 

IMA

 

AND

 

TaskExit called, scheduedTaskId: ####, message {task_result}

 

Where #### is a unique numeric value and task_result is a message specific to that execution.

Exchange Ingestion

Search for log lines containing:

 

IOW

 

AND

 

TaskExit called, scheduedTaskId: ####, message {task_result}

 

Where #### is a unique numeric value and task_result is a message specific to that execution.

Active Directory Sync

Search for log lines containing:

 

ADR

 

AND

 

TaskExit called, scheduedTaskId: ####, message {task_result}

 

Where #### is a unique numeric value and task_result is a message specific to that execution.

Attachments

    Outcomes