The MAPI/CDO download package now works on Windows Server 2008 and Vista. The main blocker to getting this to work was the fact that in Windows Server 2008 and Vista, mapi32.dll was marked as a system file. Any attempt to replace it would be blocked or undone. Exchange's MAPI has always replaced mapi32.dll with its own version, so it couldn't work on those operating systems.
The fix is modify Exchange's MAPI to take advantage of the MAPI Stub Library mechanism. We moved Exchange's MAPI binaries out of system32/syswow64 and placed them under C:\Program Files\ExchangeMAPI ("Program Files (x86)" on a 64 bit machine). We also renamed Exchange's mapi32.dll binary. It's now called ExMAPI32.dll.
Update: Looks like the Ehlo blog picked this up. Welcome Ehlo readers! I was involved in getting this update done, so lemme know if you have any questions.
Outlook won't run? What does Outlook have to do with Symantec's backup solution?
I am having problems with Symantec seeing the Exchange 2007 information store on a Server 2003 64 bit server. After talking with Symantec, they are stating that mapi is not configured correctly. If I go to system information, software environment and loaded modules, mapi32 module is not loading. I have loaded Microsoft Mapi and CDO 1.2.1. Any ideas?
Go back to Symantec and ask them to resolve the issue.
They say it's not their problem since mapi32 module is not loading. They state it's a Windows mapi issue.
And telling their customers to go away and figure it out on their own is wrong. If Symantec needs help getting their application to work with MAPI, then Symantec needs to open a case with us.
I'm just wondering why the mapi module will not load. I have another server with the same setup and the module is loading fine.
Symantec will need to answer that - it's their process and I don't know anything about it. For instance, I can't tell you if they're even trying to load it - maybe they're not even trying. I'll tell you that mapi32 is the wrong module to look for - it's called exmapi32 in the Exchange MAPI download.
The exmapi maodule isn't loaded either. Symantec states that it not their module but a windows module. The module that loads correctly on another server is mapi32 1.0.2536.0 (srv03_sp1_rtm.050324-1447) from that it looks like something that was loaded with SP1 and not by symantec.
Whoever you're talking to is clearly confused. You should ask to have your case escalated.
It already has been escalated. They are stating this is a Microsoft issue and cannot go any further without Microsoft involvement.
Is there a way for me to test if mapi is functioning correctly on this server?
I have not seen postings here since Jan, so I hope this blog is still active.
I am running Windows 2008 and I have installed CDO/Mapi 1.2.1 and it all went well. However, I am running Redemption and when I start a Mapi Session with Redemption, I get an error message stating that the sessions cannot be opened. I've got a couple of questions:
1- After installing the mapi libraries, do I need to create a profile of some sort in order to get Mapi working?
2- Is there any other setup that has to be done in order for the mapi interface to work?
Thatch - The 27 other posts I've put up this year so far don't count?
You're asking a question about Redemption. You should ask the maker of Redemption about his product.
We have installed MAPI CDO 1.2.1 using administrator account, we then logon using Besadmin account to install BlackBerry Enterprise Server Express. We are having issue creating mapi profile with error: "An error occurred while initializing a MAPI session" .
When i logon using administrator account, i am able to create mapi profile just fine.
We then uninstall MAPI CDO 1.2.1, rename all the mapi32.dll file to mapi32.old and logon using besadmin account to re-install it.
Installation completed, however mapi32.dll file did not get created even after we ran the fixmapi.exe. And we are still unable to create mapi profile.
Then we logon using administrator account to re-install MAPI CDO 1.2.1, mapi32.dll get created. However we still have the same issue creating mapi profile using besadmin account.
I also notice that MAPISVC.inf does not exist in system32 folder it older exist in syswow64
We checked the exchangemapi folder, all files are there including exmapi32.dll
Windows SBS standard 2008 x64
BES 5.0.2 Express
Can anyone please advise what might be wrong?
Thanks for taking the time to work on this and to post your findings. I think I can say that Symantec Backup Exec needs to figure out a better way to connect to Exchange if they want to keep their customers. We're looking for a suitable replacement due to issues just like this.