Local Failure Notice

[cdenley]

We just migrated to zimbra, but several outlook users have received messages like this while using the outlook connector.

Local Failures were detected. No action is required.
This e-mail was generated for technical support purposes.

Sync Type: Initial Sync

Sync Token (before request): no sync token

Sync Token (most current): 9651

Store: Zimbra - <user's name>

Computer Name: <computer name>

Version: 5.0.2817.11

Error IDs:
id (6741) type(message) message(failed to synchronize this item)

Everything seems to work, and the messages don't seem to repeat. What does this mean exactly? Is the connector unable to read certain messages? How can I determine which message and why? Would the message still be available in the web interface?

Apparently you can prevent messages by adding a registry key, but I would assume the message indicates an issue I should be aware of, but doesn't explain it very well.

[jonesrn]

We are having the same problem and have much the same questions. However, I noticed that another poster had the same problem earlier this month:

Outlook Connector and "Local Failure Notice"

I'm still trying to figure out how to do the logging that is recommended.

[fsiegel]

This local failure means that you got some kind of exception somewhere, and we could not synchronize the message to Outlook. This can happen for any number of reasons. The message id is 6741, and it is undoubtedly still on the zimbra server, and available from the web client interface. To check, you can do the following command:

http://<server>/service/user/~/?id=<zimbra-id>&fmt=sync

Substitute your server name for <server> and 6741 for <zimbra-id>. Note that if you are using a secure connection, it will be https:

The best way to find out what is going on is to enable logging. To do this, run ZCOLogCtl.exe, which is located along with the other zco dlls, in C:\Program Files\Common Files\System\MSMAPI\1033. Check the boxes for Enable Logging and Http Logging. You can choose a path for your log files if you want. Restart Outlook, and log files will be created in the directory that was specified. If the error happens again, you can post that log file.

Note that in the upcoming 5.0.12 version, more information will be attached to local failure messages which will make it easier to see what's going on.