4.5.9 ZCO crashed with Debug message.

[azilber]

Hi,

The new 4.5.9 connector crashes with a debug message on addin.cpp. I've opened a new support case: #00017286

I can't track down why it crashes. One time it had something to do with the BB Desktop. When BB Desktop was shut down, everything seems ok. Now it's happening to me, and I'm not running the BB Desktop.

The specific error is:

Debug Assertion Failed!

Program: C:\PROGRA~1\MICROS~2\OFFICE11\OUTLOOK.EXE
File: c:\src\frank\mapi\src\sharingaddin\addin.cpp
Line: 1717

Expression: g_pAddingInstance

[phoenix]

See if the details in this bug report help.

[azilber]

The registery change seems to have fixed it.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\SharingAddin.Addin]
"FriendlyName"="Zimbra Sharing Addin"
"Description"="Zimbra Outlook Sharing Addin"
"LoadBehavior"=dword:00000003
"CommandLineSafe"=dword:00000000

Though this is still a bug. The installer should change this registery key during the install/upgrade.

[fsiegel]

Also, for the future, make sure you don't have more than one copy of sharingaddin.dll on your desktop where the PATH variable could pick up the wrong one. See bug 21274. This was fixed in our next release, 4.5.10, and in version 5.

[azilber]

Originally Posted by fsiegel

Also, for the future, make sure you don't have more than one copy of sharingaddin.dll on your desktop where the PATH variable could pick up the wrong one. See bug 21274. This was fixed in our next release, 4.5.10, and in version 5.

No other sharingaddin.dll's were hanging around my system. But, applying the Office 2003 SP3 reset the registery key back and I had to re-apply the fix.

[azilber]

Originally Posted by azilber

The registery change seems to have fixed it.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\SharingAddin.Addin]
"FriendlyName"="Zimbra Sharing Addin"
"Description"="Zimbra Outlook Sharing Addin"
"LoadBehavior"=dword:00000003
"CommandLineSafe"=dword:00000000

Though this is still a bug. The installer should change this registery key during the install/upgrade.

The following little script will make sure it all works:


create a Zimbra-Sharing.reg file with the contents of the code above.
create a fixzco459.cmd file that can be accessed via a shared drive with the contents of the code below.

@echo off
echo "%USERNAME%, make sure Outlook is shut down"
pause
echo Loading Reg fix
\\<share server>\<shared path>\Zimbra-Sharing.reg
echo "Deleting: %APPDATA%\Microsoft\Outlook\outcmd.dat"
del "%APPDATA%\Microsoft\Outlook\outcmd.dat"

And startup outlook.

I was going to either make an installer wrapper or rebuild the zco msi with this fix, but I just don't have that luxury right now.

Enjoy!

[kilrathi]

I've followed the above instructions and I am still getting the same debug error on this workstation. I've experimented with Connection version 4.5.7 and 4.5.10 and the results are the same each time. I've reinstalled Outlook and the connector. I am still receiving this error message every time an email is sent from this workstation. Please help me fix this.

Outlook 2003
Windows Xp Pro
Zimbra 4.5.7

[henry]

"the same" is not enough
I'd like to have the details.
First i need steps to reproduce.
Version of the Outlook connector.
Screenshot of the debug dialog.

[kilrathi]

I've solved this problem but wanted to add my solution here to help any others who are experiencing this problem as well. Apparently Office Service Pack 3 is the culprit in this. Upon installing Microsoft Office SP3 it disabled the Zimbra Sharing Addin, thus causing the debug error. To fix this you have to re-enable the addin through outlook.

In outlook go to Help -> About -> Disabled Addins
Re-enable the Zimbra sharing addin
Restart outlook

Debug error gone. I've restarted the machine and outlook several times to verify.

I am running Outlook 2003 SP3 (11.8169.8172) and the Zimbra Outlook Connector (4.5.7_GA_1310_4.5.373). Windows Xp Sp2.

[rusty]

I have someone with this same problem. A screen shot of the dialog box showing the error is already part of this thread in an earlier post. Mine looks exactly the same.

I suspect that the client was upgrading Outlook Connector 4.5.9 just after a Outlook crash and although the program looked like it was closed, there was an outlook.exe process still running.

I have removed and re-installed connector, and I have done a Detect and Repair in Outlook to no avail.