It could be other addins causing a fault, it could be a script stopper, it
could be some other addin interfering with something your addin is doing
causing a fault in your own addin.

Shared addins in .NET that aren't shimmed to use their own namespaces will
disable all other shared addins like that if they fault.

About the only things that you can do are a thorough code review and using
an error log file as well as remote debugging and examining the event logs.
I can't offer anything more specific.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


wrote in message
ups.com...
In my situation the disabled add-in does not appear in Help | About |
Disabled items. Instead it's missing from the COM Add-Ins window.
According to http://msdn2.microsoft.com/en-us/library/ms269003.aspx and
http://msdn2.microsoft.com/en-us/library/ms268871.aspx , that's called
a "soft disable". These articles also square with your contention that
an unhandled exception is the likely culprit.

Most of our customers do not encounter this problem. It's just this one
organization. At the risk of sounding like I'm fishing or being too
general, is there anything that is environment specific that can
trigger an unhandled exception like this that is practically
unreproducible anywhere else?