Zarafa cached logging for Outlook

From Zarafa wiki

(Difference between revisions)
Jump to: navigation, search
m (Create compressed synclogs)
(Making a server log for the offline profile)
 
(One intermediate revision not shown)
Line 50: Line 50:
  C:\Users\%USERNAME%\AppData\Local\Temp\synclog_<number>.txt.gz
  C:\Users\%USERNAME%\AppData\Local\Temp\synclog_<number>.txt.gz
-
'''NOTE: Compressed log files will NOT be complete until Outlook is closed, so typically log .gz files are of size 0 bytes.'''
+
'''NOTE: Compressed log files will NOT be written to disc until Outlook is closed, so typically log.gz files are of size 0 bytes.'''
== Making a server log for the offline profile ==
== Making a server log for the offline profile ==
Line 73: Line 73:
log_timestamp          =      1
log_timestamp          =      1
</pre>
</pre>
 +
 +
'''Please make sure the C:\temp\ location does exist and is writable'''
== Possible messages in the log ==
== Possible messages in the log ==

Latest revision as of 08:48, 29 November 2012

In rare occasions it can occur that some items are missing in outlook when Zarafa is in cached mode.

To debug this a synclog may be created. There are two forms of synclogs:

  1. Uncompressed - This will create one uncompressed log file, where new data will be appended at the end.
  2. Compressed - This will create one compressed log file for each Outlook session. So whenever Outlook is started a new log will be created.


Be aware that enabling any form of synclogging after one has determined that items are missing, will not help in debugging why those items are missing. It might however assist in finding the cause of items missing in the future. This means that a synclog is only of value if it was used during a synchronization in which items got lost. Therefore it is advised to enable compressed synclogs as they have less impact on performance and disk usage because the logging must be enabled until new items are lost during synchronization.

Contents

Create an uncompressed synclog

NOTE: Please do NOT use uncompressed log since it slows down Outlook, use compressed synclog only.

Open regedit and create the following keys:

Location: HKEY_CURRENT_USER\Software\Zarafa\Client
Name: SyncLog
Type: DWORD (32-bit)
Value data: 1 to activate, 0 to disable
Base: Decimal
Location: HKEY_CURRENT_USER\Software\Zarafa\Client
Name: SyncLogLevel
Type: DWORD (32-bit)
Value data: 6
Base: Decimal

NOTE: Setting the SyncLogLevel to anything less than 6 makes it unsuitable for debugging.

The uncompressed synclog can be found at:

C:\Documents and Settings\%USERNAME%\Local Settings\Temp\synclog.txt

Or for Vista/Windows 7 at:

C:\Users\%USERNAME%\AppData\Local\Temp\synclog.txt

Create compressed synclogs

Open regedit and create the following key:

Location: HKEY_CURRENT_USER\Software\Zarafa\Client
Name: SyncOptions
Type: DWORD (32-bit)
Value data: 15
Base: Decimal

If a SyncOptions value is already present, the existing Value should be bitwise orred with 8 instead of just setting it to 15.

Compressed synclogs can be found at:

C:\Documents and Settings\%USERNAME%\Local Settings\Temp\synclog_<number>.txt.gz where <number> is the unix timestamp of when the log was created.

Or for Vista/Windows 7 at:

C:\Users\%USERNAME%\AppData\Local\Temp\synclog_<number>.txt.gz

NOTE: Compressed log files will NOT be written to disc until Outlook is closed, so typically log.gz files are of size 0 bytes.

Making a server log for the offline profile

Create a file named 'server.cfg' in the Zarafa client directory.

By default the Client is installed in 'C:\Program files\Zarafa\Zarafa Outlook Client\'

Add the following lines into server.cfg:

# Logging method (syslog, eventlog, file)
log_method              =       file

# Logfile (for log_method = file, '-' for stderr)
log_file                =     C:\temp\zarafa-serverlog.txt

# Loglevel (0=no logging, 5=full logging)
log_level               =       6

# Log timestamp - prefix each log line with timestamp in 'file' logging mode
log_timestamp           =       1

Please make sure the C:\temp\ location does exist and is writable

Possible messages in the log

Out-of-sync issue

  • Upgrade to the newest Zarafa
  • Create a new profile
  • If there are still issues, send an email to support@zarafa.com
Personal tools