A
Anthony
I wrote a custom add-in that has been developed and successfully
deployed to customer sites for over five years. It is written using the
COM add-in designer within the Microsoft Visual Basic 6.0 IDE. It has
evolved through each iteration of Microsoft Office, each security patch
(uses Redemption) and functionality change that these have brought
about.
The add-in will work for a number of hours. After a period of inactivity
the user will click on Outlook to view a message and Outlook will crash.
Checking the Application Event viewer results in the error described
below
Faulting application OUTLOOK.EXE, version 12.0.6504.5000, time stamp
0x49e7f47e, faulting module ntdll.dll, version 6.0.6001.18000, time
stamp 0x4791a783, exception code 0xc0000374, fault offset 0x000aada3,
process id 0x27d4, application start time 0x01ca1ee27730eea6.
I have seen the article "Add-in threading issue causes Outlook to crash
or hang" but have not been able to re-create the issue in order to
uncategorically remove my add-in as the culprit. I have even removed all
but the Genuine Office Advantage add-in and my add-in and outlook still
crashes.
The add-in has worked for a long time (pre-Outlook 2007) and hasn't
changed much.
Is this the .NET add-in multi-threading issue? If so, how can I tell my
customers their Microsoft add-ins are causing Outlook to crash, not my
add-in?
What else can I try? There seems to be very little about this out there,
can anyone help?
Regards,
Anthony
*** Sent via Developersdex http://www.developersdex.com ***
deployed to customer sites for over five years. It is written using the
COM add-in designer within the Microsoft Visual Basic 6.0 IDE. It has
evolved through each iteration of Microsoft Office, each security patch
(uses Redemption) and functionality change that these have brought
about.
The add-in will work for a number of hours. After a period of inactivity
the user will click on Outlook to view a message and Outlook will crash.
Checking the Application Event viewer results in the error described
below
Faulting application OUTLOOK.EXE, version 12.0.6504.5000, time stamp
0x49e7f47e, faulting module ntdll.dll, version 6.0.6001.18000, time
stamp 0x4791a783, exception code 0xc0000374, fault offset 0x000aada3,
process id 0x27d4, application start time 0x01ca1ee27730eea6.
I have seen the article "Add-in threading issue causes Outlook to crash
or hang" but have not been able to re-create the issue in order to
uncategorically remove my add-in as the culprit. I have even removed all
but the Genuine Office Advantage add-in and my add-in and outlook still
crashes.
The add-in has worked for a long time (pre-Outlook 2007) and hasn't
changed much.
Is this the .NET add-in multi-threading issue? If so, how can I tell my
customers their Microsoft add-ins are causing Outlook to crash, not my
add-in?
What else can I try? There seems to be very little about this out there,
can anyone help?
Regards,
Anthony
*** Sent via Developersdex http://www.developersdex.com ***