[SOLVED] upgrade Outlook Connector / Outlook Crash / sync failing

[moetiker]

How to make an upgrade of Outlook Connector without troubles.

Most of the time after an upgrade as now from 5.0.6 to 5.0.10 I have big troubles to get Outlook stable again.

Now Outlook is crashing after it is open up. I find out that I can delete the profile and make a new one. after this it's working again.

What are the steps to debug the crashing outlook after an upgrade and failing syncing?

thanks Manuel

ps: I did remove the dump

[fsiegel]

If you're crashing, there should be a crash dump created in the Temp\zco-cores folder. [Documents and Settings\<username>\Local Settings\Temp\zco-cores. If the dump isn't very big (200K or so), you can post it here, and I can analyze it. If it is huge, then you can send it to support.

If it's 5.0.10, it's possible you are running into bug 32309, which has been fixed in 5.0.11. The dump will tell us.

[moetiker]

Thanks for your answer. where can I download the fixed version 5.0.11?
I did upload the dump in my first message

[fsiegel]

Sorry -- I didn't see your crash dump. I just looked at it, and yes, it is bug 32309. 5.0.11 is not out yet. It is in a patched version of 5.0.10 -- not sure what the procedure is getting that. If you're really interested in getting that, I can check into it.

The issue is that in 5.0.10, the default behavior when getting a local failure is to send the local failure to the Inbox as well as the Local Failures folder. The problem here is with a delegate store -- it's trying to send it to the inbox and crashing. It doesn't always crash, but you seem to be in that state.

What you can do is to add this DWORD value to the Windows registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Zimbra\turnOffInboxFai lures

Set it to 1.

Local Failures will now only go to the Local Failures folder, as before. You will no longer crash.

Let me know how this works.

[fsiegel]

Note that the registry value should be:

HKEY_LOCAL_MACHINE\SOFTWARE\Zimbra\turnOffInboxFai lures

[moetiker]

it looks good. in my test account, the real test will be tomorrow. holding finger crossed....

it works in production to. thanks for your help. I think this should be published in a patch or new version.
the bug generated about 5h work !!!