The 1,000,000 Dollar Question about Fixing MAPI
Hello,
I do email migrations from one system to another, and often people want to go to Microsoft Outlook. That works most of the time. Sometimes, people cannot migrate into Outlook because GroupWise was installed on this same machine, and GroupWise uses its own version of MAPI. Sometimes, a reinstall of Outlook prevents MAPI conflicts, but other times it does not. If I completely uninstlal the GroupWise client from a machine and leave Outlook, I could still have connection problems to Outlook because GroupWise left its mapi files behind. Sometimes, if I then uninstall Outlook and reinstall it then I have no connection problems. But, this is not true all of the time.
I need to learn more about MAPI. If there are problems with MAPI because of incompatible versions e.g. GroupWise and Outlook on the same machine, what is the best way to make sure MAPI is the correct one for Outlook?
Also, it seems that sometimes that Windows will keep its own version of MAPI and fight with GroupWise or even Outlook if the version has changed.
What are the files related to MAPI? If I need to fix it (without running fix mapi) what can I do to ensure the MAPI version is the compatible version for Outlook without having to reinstall Outlook or run Outlook repair, which does not always work?
Good luck with this one LOL.
Thanks,
John
I do email migrations from one system to another, and often people want to go to Microsoft Outlook. That works most of the time. Sometimes, people cannot migrate into Outlook because GroupWise was installed on this same machine, and GroupWise uses its own version of MAPI. Sometimes, a reinstall of Outlook prevents MAPI conflicts, but other times it does not. If I completely uninstlal the GroupWise client from a machine and leave Outlook, I could still have connection problems to Outlook because GroupWise left its mapi files behind. Sometimes, if I then uninstall Outlook and reinstall it then I have no connection problems. But, this is not true all of the time.
I need to learn more about MAPI. If there are problems with MAPI because of incompatible versions e.g. GroupWise and Outlook on the same machine, what is the best way to make sure MAPI is the correct one for Outlook?
Also, it seems that sometimes that Windows will keep its own version of MAPI and fight with GroupWise or even Outlook if the version has changed.
What are the files related to MAPI? If I need to fix it (without running fix mapi) what can I do to ensure the MAPI version is the compatible version for Outlook without having to reinstall Outlook or run Outlook repair, which does not always work?
Good luck with this one LOL.
Thanks,
John
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
There was no definite answer for my question. This really is a difficult question, and I think it is problematic for many. PSICOP's suggestion on using on comparing snapshots is probably the best thing to do if there are no other choices.
ASKER
It is good to hear from you. We've had the GroupWise and Outlook discussion before, and it is a delight to see your view of Lookout hasn't changed lol. I have multiple vmware images for testing, and this is one of the reasons for my question. Aside from the loading order of these email clients, I would like to know what happens in the backend with MAPI. If I had an easy tracer program then that would help. What I am still unclear about is what files, in addition to MAPI32.DLL, are related to MAPI. If I needed to manually fix MAPI or find a way to bounce between MAPI versions, how would I do that?
Thanks. By the way, what to you think about the Novell Acquisition? I am curious about the future of GroupWise and what it will evolve into.
John