Debug Assertion Failed (a blast from the past?)

[jfmoore]

We run a number of Zimbra servers here and on one of our servers we have a client reporting that sporadically they are getting a "Debug Assertion Failed! message."

Here are the details:
Client 6.0.5737.3
Server 6.0.3_GA_1912
Client is Outlook 2007, fully patched, running on Windows XP fully patched.

Yes, I do realize that it is time to upgrade the client and the server. But in the meantime, I would like to figure out what is happening.

I have read through bugzilla and this forum (most of the posts were from 2007 and 2008 and on earlier releases and that is why this is so strange that it is happening now).

==========================
Microsoft Visual C++ Debug Library
Debug Assertion Failed!

Program: C:\program files\microsoft office\office 12\outloook.exe
File: c:\src\gnr-603\mapi\src\sharingaddin\addin.cpp
Line: 1823

Expression: g_pAddinInstance
==========================

The client is remote right now so I cannot get any log files. I can always try to get those tomorrow. I am aware of some of the Macro and outcmd.dat and registray suggestions as well as checking on the sharing enabled option under Help---Disabled Items. Unfortunately none of those fixes are working.

Could this be easily fixed by installing a more recently Outlook Connector version? Would that work again an older server version (such as what we are running?

[jfmoore]

Quick update.

I managed to get a hold of the user remotely and he checked some settings for me.

He did not have any entries listed under Help-->Disabled Items.
When he clicks on File and then Open there is no option to open another users mailbox.
When he right clicks on Inbox and goes to Properties there is no Sharing Tab.

So this would indicate that the Sharing Addin is disabled, right? Is this wiki still the valid fix for these types of situations?

EnableSharingAddin - Zimbra :: Wiki

[jfmoore]

Followed the wiki but nothing in that worked:

Nothing was in Disabled Items
The registry key was already set properly.
Deleted the outcmd.dat file.
Checked again on the LoadBehavior key.

Ran a repair and that solved the problem but I am at a loss as to what caused this issue in the first place.

I would really like to better understand what is happening here. To have to run a Repair is easy but I don't want to have to have people doing this again and again. Does anybody know what causes this?

[jfmoore]

I have gone ahead and opened a Case for this issue as it is happening more frequently. I've copied the details of my post into the case and also uploaded a Log file to the Case.