on Nov 24, 2015Applies to: version 3.0.0 and later.
The Mimecast Synchronization Engine runs as a Windows service, bridging between your organization's LAN and the Mimecast cloud. When troubleshooting and monitoring Synchronization Engine 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:\ProgramData\Mimecast Synchronisation Engine\logs directory on the host server.
- The files found in the root of this directory are generic logs about the service.
- The service log that contains specific details about your Site are found in the ACCOUNTCODE subdirectory
- Where ACCOUNTCODE is your unique Mimecast account code as found in the Administration | Account | Account Settings menu item in the Administration Console.
Checking 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.
| Feature | String |
|---|---|
| Mailbox Folder Replication | Search for log lines containing: MMS AND executing task |
| Calendar Replication | Search for log lines containing: CAL AND executing task |
| Mailbox Storage Management | Search for log lines containing: MCS AND executing task |
| Managed Folders | Search for log lines containing: FBR AND executing task |
| File Archiving | Search for log lines containing: FSR AND executing task |
| Lync Instant Messaging Archiving | Search for log lines containing: IMA AND executing task |
| Exchange Ingestion (BETA) | Search for log lines containing: IOW AND executing task |
| Active Directory Sync | Search for log lines containing: ADR AND executing task |
Checking a Task Has Completed Successfully
| Feature | String |
|---|---|
| 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 (BETA) | 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. |