36.7 Synchronization logs
Prev | Chapter 36 Support for ActiveSync | Next

## 36.7 Synchronization logs

The entire synchronization process can be monitored and logged by using special tools. These tools can be found both in the Kerio MailServer's administration console and in the mobile device. This section provides description and settings instructions for these tools:

### Synchronization logging in Kerio MailServer

Kerio Administration Console includes a special option in the Debug log (for details on the Debug log and its options, see section 25.9 Debug log). The traffic log can be started as described below:

1. In the Kerio MailServer's administration console, go to the Logs → Debug section.

2. Right-click on the log window to open the pop-up menu.

3. Click on Messages.

4. In the Logging Messages dialog box, select ActiveSync Synchronization.

   Figure 36.3. The Debug log settings

5. Click OK to confirm settings.

Once the log is set, run the synchronization of the device and the server to make the log.

If needed, synchronization log can also be saved, as follows:

1. Logs can be saved in a file in the Logs → Debug section.

2. Right-click on the created log and choose Save log from the pop-up menu.

3. In the Save Log dialog, select a path where the file will be saved, choose a file format (TXT or HTML) and confirm the dialog (see figure 36.4 Saving a log).

   Figure 36.4. Saving a log

### Logging synchronization on mobile devices

On Windows Mobile, the ActiveSync application includes special logs for each synchronization performed that can be helpful when solving traffic issues. Logs can be enabled/disabled in the Advanced section of the ActiveSync application.

Windows Mobile stores logs in `\Windows\Activesync`. Each synchronization process is saved in a stand-alone file whereas the three most recent logs are kept in the directory mentioned above. Names of the log files are:

`Exchange Server0.txt`

`Exchange Server1.txt`

`Exchange Server2.txt`

These logs may be helpful especially when solving issues in cooperation with the Kerio Technologies technical support.

Prev | Up | Next
36.6 Removing a device from the administration of mobile devices | Contents | 36.8 Troubleshooting