Outlook 2000 Runtime Error! when closing Outlook

[Kanaan]

Hi,

I have a user who gets the following error when he exits Outlook and I cannot find this exact scenario on Microsoft TechNet:

Microsoft Visual C++ Runtime Library
Runtime Error!
Program: c:\program files\mic...\outlook.exe
abnormal program termination

Any ideas out there?
Thanks much!
Phil

 

[dhcolvin]

What service pack are you on? I have seen this issue with earlier versions of Outlook and I updated to SP3 via the Office Update page and it fixed my problem. I would check that first and then go from there.

 

[Kanaan]

It is Outlook 2000 SP3.

 

[smah]

This might be a good candidate for 'Detect & Repair' from the help menu.

 

[dhcolvin]

Ok then...have you looked in your Add-In Manager to see if anything is checked? I have seen an issue where an add-in has caused all sorts of havoc. If you do not know where the add-in manager is: tools, options, other, advanced options, click on add-in manager tab. That would be my next guess as to what is causing this. I have had zero luck with the detect and repair...no clue if anyone has had luck with it but I have yet to get help from that tool.

 

[Kanaan]

Hmmmm...

Well, detect and repair did not work so I removed and reinstalled Office 2000 completely and re-applied SP1 and SP3. This was also to no avail.

The user's add-ins in Outlook are the same as the rest of the company's users.

I did observe that this error only occurs when that user is logged in. I did not experience the error when I logged in and used Outlook on his PC.

Perhaps there is something with his profile. I may rename his profile and have the system create a new one for him the next time he logs in.

 

[cmeagan656]

The problem is only with one user? Sounds like a corrupt Outlook profile. Try deleting the profile and recreating it.

Cheers.

 

[Kanaan]

Actually, what I meant was rename and recreate his Win2K profile under Docs and Settings. I did try to delete his Outlook profile and recreating it to no avail.

Deleting his Win2K profile and having him log in again did the trick!!!

Thanks so much for all of your advice!