What's the best way to get the mapi32.dll to match what is on the Exchange servers?
I currently have a very out of date mapi file, that I need to get updated to the latest version. From what I've seen on the search results, it's not a good idea to use regsrv for this file, and I'm fine with that, but I do need some method of installing it that hopefully isn't too time consuming. I basically have to make the suggestion to our outsourced vendor that handles my BES, so I can't say for certain that they have the Exchange Mangement tools on there or not, but I'm hoping they do. If they don't, obviously they should install that, but if they do, what do I do then?
Tool...
Sponsored Links
Please Login or Register to Remove these Advertisements!
when i initially setup my BPS the mapi versions were the same, this thread prompted me to check again and now i notice that my exchange server is at 6.5.7638.1 and my BPS is at 6.5.6944.0
What is the process to get them equal again? I am not sure what KB Update on the exchange server bumped up the MAPI32.dll version.
I have but what do you mean by make them all the same? It's my understanding that you can't just copy and paste one version over the other. So i guess that's where i'm stuck, how do I get the version on my exchange server thats newer to match the version thats on my BPS thats older?
Sorry, you do what I suggested in my previos post only after you apply same SP and post that SP on the BES. Then you search and see if the mapi32.dll differ in version. then you do what I suggested.
I would be careful about copying/pasting mapi32.dll and registering it. Applying Exchange 2003 SP2 on your BES should be sufficient. If it did not update anything then you either installed the wrong thing or the install botched.
Re-install SP2 and that should update the mapi32.dll.
Yes you are both right but sometimes that other mapi32.dll is NOT updated when applying sp but only the one in bin folder. I know it is not right way but is there are other way to do it?
The only time I see mapi32.dll in a folder other than Exchsvr\bin is when there was another MAPI app installed like Outlook. The BES is only concerned with the mapi32.dll in that folder, it should be anyways.
I once talked to guys at homeland security who did this on 2 BES they Fubared. Complete MAPI degradation. The BES works for a bit and eventually MAPI just dumps and gives out.
I have mapi32.dll in both locations on the BES, system32 and Bin folder. But the one BES care about is the system32 one. They should be both the same version but had in past problems with mismatch that causes exact problems he described in his post. Beats me why.
I'm not sure why mapi32.dll updates in one folder and not the other. A re-install of SP2 might fix it. If not, you could always uninstall ESm and reinstall it and apply SP2.
You would not believe how many I've talked to that install Outlook to get MAPI on the BES.
They always say "it's worked for a year now". Hehehehe, always makes me laugh.
Maybe Microsoft cold shed some light as to why mapi32.dll does not always update/register in the same folder.
Would be nice to know.
You can always look in the MAGT log to see what version of mapi32.dll is registered and where. As long as the right one is registered it should be ok.
I just checked brand new server installs have mapi32.dll in both locations. And MAGT logs shows the one in system32 that is registred. So you are saying you have only in BIN folder? Have you searched for it? See link: BlackBerry Search Results
I just checked brand new server installs have mapi32.dll in both locations. And MAGT logs shows the one in system32 that is registred. So you are saying you have only in BIN folder? Have you searched for it? See link: BlackBerry Search Results
Are you installing BES on a 64 bit version of Windows Server 2003?
BES 4.1.4 - Exchange 2003
8800 and my trusty 8700r.
To change your PIN to FFFFFFFF, drop the BB in a lake.