Olk2003 displaying an error message

  • Thread starter Thread starter Johnsaida
  • Start date Start date
J

Johnsaida

Hi,
I have developed an outlook addin(using vb6.0) which gives an extra
functionality, when user clicks replyall button.
I have installed this addin for both olk2000 and olk2003.
In olk2000 the addin is working good.But in olk2003 i am getting the
following error when i closed and open the outlook.
"Outlook Experienced a serious error the last time the add-in
'replyalladdin' was opened.Would you like to disable this
addin?................................."
I have tried a lot to get the solution,but i could not.
It will be greate to help me to find a permament solution for this problem.
Many Thanks,
John
 
Johnsaida said:
Hi,
I have developed an outlook addin(using vb6.0) which gives an extra
functionality, when user clicks replyall button.
I have installed this addin for both olk2000 and olk2003.
In olk2000 the addin is working good.But in olk2003 i am getting the
following error when i closed and open the outlook.
"Outlook Experienced a serious error the last time the add-in
'replyalladdin' was opened.Would you like to disable this
addin?................................."
I have tried a lot to get the solution,but i could not.
It will be greate to help me to find a permament solution for this problem.
Many Thanks,
John
Click to expand...
 
There's no way to tell what's happening from the outside. In general that
warning means that your addin crashed Outlook or ran into an unhandled
exception. All exceptions in COM addins must be handled in some way.

You need to do a lot of error logging to see what errors are being fired
where and when and if they are being handled.

You can also see if anything you are doing is OK in Outlook 2000 and
restricted in Outlook 2003, although in general Outlook 2000 is actually
stricter than Outlook 2003 is.
 
Hi Ken Slovak,
Let me say thanks for immediate reply to my post.
I have handiled all exception and
I am not restrictng any thing in outlook2003.The code which has been
compiled in outlook2000 being installed in both olk2000 and olk2003.When i
checked in Eventlog i have noticed one of the following error
messages(olk2003 only)

"Faulting application outlook.exe, version 11.0.8169.0, stamp 465f28e3,
faulting module msvbvm60.dll, version 6.0.97.97, stamp 4549bd5e, debug? 0,
fault address 0x000cc91d."
OR
Faulting application outlook.exe, version 11.0.8169.0, stamp 465f28e3,
faulting module outllib.dll, version 11.0.8169.0, stamp 465f2870, debug? 0,
fault address 0x000b9c1f.
OR
Faulting application outlook.exe, version 11.0.8169.0, stamp 465f28e3,
faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0, fault
address 0xff087881.

I have checked all the versions and i have tested the addin in different
machines.Please help me to identify the root cause and resolution for the
same.

Many Thanks,
John
 
Are any other addins at all running on the Outlook 2003 system? If so
disable them all other than your addin and see if the same thing occurs.

It's hard to tell from those event log entries without analyzing a crash
dump, which only MS can really do since they don't release the Outlook
symbols, but that VB6 runtime error makes me guess that something is
accessing the Outlook object model on a background thread. That's guaranteed
to crash or hang Outlook, and will cause that error. It also usually leads
to Outlook disabling the VB6 addin even if it's not the code that does that
access. That's due to how the stack is set on those background thread calls
and the fact that the VB6 runtime is the first to feel the effects of the
crash.

Do you actually see any Outlook crashes, where Watson comes up?

If this doesn't help you might need to open a support case with MS to get
the crash dumps analyzed.
 
Hi Ken Slovak,
I am very hapy to see your answer.But one thing i need to clarify is, the
eror message is not occuring in all the machines in which the addin was
installed.In some machines only it is occuring.
In one machine i have reinstalled the outlook2003 Service Pack 3 and clicked
the'Detect and Repair' button in the Help Menu of Outlook.After doing this
that error message was not appeared.I dont know what is happend in this
action.

But it is not feasible if the error occured in more number of client
machines(Say 100).Do you have any clue to get permanent solution.It would be
greate if you give response on this.
Many Thanks,
John
 
Not being a mind reader I have no specific answers to provide. You need to
see what differences are there in computers where you don't have the problem
and where you do. If that doesn't help my guess is that you will need to
open a support incident with MS and let them analyze the crash dumps.
 
Back
Top