This is bug 33321, which I have just fixed in 5.0.16. Unfortunately, the fix is just to fix the crash. We now put out an error message telling you that your Outlook installation is probably corrupted, your MAPI32.dll file is bad, and that you should re-install office.
What is happening is that we are trying to determine the location of our .zdb file so that we can name our map file (.idm). We look deep into MAPI for this location, and if MAPI is corrupt, we don't get the right thing back. We were crashing on this check -- now we know there is a problem, and we put out the dialog box and don't crash.
I would love to get to the bottom of why this happens, and figure it out so that users don't have to uninstall and reinstall office, which is a pain. Your Groupwise stuff gives me a clue.
As to what to do, you might try looking for all the versions of MAPI32.dll on your machine both before the problem (pre-Groupwise) and then after and see what changed. Then maybe you can just replace the MAPI32.dll with the old one and you might get lucky.
There is a also a program called FixMAPI which might work.
You also might do a web search, looking for Groupwise and MAPI32.dll. I'm sure there are a ton of hits. Maybe something there will show you how to resolve this without having to reinstall Office.
Let me know what happens. I've wanted to get to the bottom of this for a long time, but have never been able to reproduce it in house.
Thanks  |