 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Connectivity / July 2008MAPI/CDO app needs concurrent access to E2K3 and to E2K7 on WS08
Surely I am not the first to get into this, but here goes: My current environment is Exchange 2003 SP2 (both on Windows Server 2003 SP2), using CDO and MAPI 6.5.7651.61 on both servers. Store.exe is also 6.5.7651.61. I am slowly migrating users to Exchange 2007 SP1 (running on Windows Server 2008) and will have a period of coexistence where there will be BES (MAPI/CDO app) users on each version of Exchange. Since Exchange 2007 does not include CDO or MAPI libraries, they have to be installed. The only version of CDO and MAPI that is supported on Windows Server 2008 is 6.5.8022.0. This means that I have to update CDO and MAPI on my BES server, so that they match versions. I would also then need to update CDO and MAPI on my Exchange 2003 server for the same matching requirement. Per MS KB929751, CDO.dll 6.5.7888 and above cannot access Store.exe unless Store.exe is 6.5.7652.9 and above. This means that I have to update my E2K3 Store.exe via hotfix KB929751, KB944254, KB948744 or KB951619. If I choose the most recent, which makes sense if you read the progression of hotfixes, you end up replacing Store.exe (and related files) with version 6.5.7653.36. So I have to install on E2K3 Store.exe version 6.5.7653.36 and CDO and MAPI versions 6.5.8022.0. This means I have matching CDO and MAPI between all three servers, and that my Store.exe is accessible from the new versions. For obvious reasons, changing Store.exe and CDO/MAPI on my existing Exchange server is risky and I have to make sure that the combination of the versions will work. Can somebody please comment on this coexistence issue before I proceed? Thanks, Brit I'm going to be doing this myself soon. I have a T-Support contract with RIM so I asked them not too long ago. They pointed me to their KB article 14502: "How to migrate the BlackBerry Enterprise Server from Microsoft Exchange Server 2000 or Microsoft Exchange Server 2003 to Microsoft Exchange Server 2007" http://www.blackberry.com/btsc/articles/563/KB14502_f.SAL_Public.html > Surely I am not the first to get into this, but here goes: > [quoted text clipped - 47 lines] > > Brit Yes, I had read that too, but they do not treat the case involving WS08 and how doing so ends up causing Store.exe to need a new version. It would be nice to get something official from RIM about this new-but-soon-to-be-everywere scenario. Can you reopen the T-support case to get them to answer that question? -Brit > I'm going to be doing this myself soon. I have a T-Support contract with RIM > so I asked them not too long ago. They pointed me to their KB article 14502: [quoted text clipped - 55 lines] > > > > Brit Sure. I'll let you know what they say. > Yes, I had read that too, but they do not treat the case involving WS08 > and [quoted text clipped - 73 lines] >> > >> > Brit Michael, Thanks...I really appreciate your help! -Brit Still waiting on a reply. I updated the case twice on their support site and just a few hours ago received a "if you don't reply to this case, we'll close it in two days" e-mail from them. I sent a reply stating the questions again and according to the support site my "technical support associate is waiting for more information from the Network Operations Group." > Michael, > > Thanks...I really appreciate your help! > > -Brit This was the reply: Once the BlackBerry service account mailbox has been migrated to Exchange 2007, we recommend that you install the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 on the BlackBerry Enterprise Server. Doing this will require you to stop BlackBerry Enterprise Server services until the process is completed. Once the services are started again you can expect message delays do to mailbox rescans. 1. Stop BlackBerry services. 2. Uninstall Exchange System Manager from the BlackBerry Enterprise Server. 3. Perform a search for MAPI32.dll and cdo.dll and rename any cdo.dll and MAPI32.dll files from the system32 folder and the program files\exchsrvr\bin folder to a .bak file extension. 4. Download Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1. You will want to download ExchangeMapiCdo.EXE. This can be found at https://www.microsoft.com/downloads/details.aspx?FamilyID=94274318-27c4-4d8d-9bc 5-3e6484286b1f&DisplayLang=en 5. Install ExchangeMapiCdo.EXE 6. Resolve the MAPI profile for the BlackBerry service account mailbox on the BlackBerry Enterprise Server by going to Start > Programs > BlackBerry Enterprise Server > BlackBerry Server Configuration > BlackBerry Server tab > Edit the MAPI. 7. Restart the BlackBerry Enterprise Server > Michael, > > Thanks...I really appreciate your help! > > -Brit Michael, Thanks for staying on them. I still can't tell from their response if they understand the WS08 part of the question...specifically that WS08 requires a newer version than the .EXE provides, and the BES version should always be the same or newer than that of the Exchange server. It really surprises me that we have to try so hard to get our point across and yet the response is lacking in the most critical part. If you hear anything else, let me know. I will probably synthesize all this info and cut my own path. I'll post back anything relevant to my little project. -Brit > This was the reply: > [quoted text clipped - 26 lines] > > > > -Brit That's RIM for you. They're cryptic in many respects. I think I'm going to stop all the BES services, move the mailboxes of my BES users in one batch along with the BESAdmin mailbox from 2003 to 2007, then uninstall the Exchange 2003 management tools and install the latest CDO/MAPI 2007 components on the BES. Then hopefully after a BES restart everything will "just work" but I doubt it. :) > Michael, > [quoted text clipped - 49 lines] >> > >> > -Brit The fun continues. I was reading the release notes for BES 4.1 SP6 (which fixes, among other things, the PDF attachment service bug) and came across these two known issues. (sigh) ActiveSync 1, BES 0.... 1. SDR 190930 Microsoft has recently released MAPI and CDO client download version 6.5.8022. If you install the MAPI and CDO client download version 6.5.8022 without completely uninstalling previous versions of the MAPI and CDO client download (including the associated .DLL files), users might experience unexpected behavior with the message lists and the calendars on their BlackBerry devices. Workaround 1. Stop the BlackBerry Enterprise Server and any other processes that use the MAPI and CDO files. 2. Uninstall the current version of the MAPI and CDO files. 3. Verify that the following files are not present in C:\Windows\System32 (or any other directory in the path): • CDO.DLL • EMSABP32.DLL • EMSMDB32.DLL • EMSUI32.DLL • EMSUIX32.DLL • GAPI32.DLL • MAPISP32.EXE • MSPST32.DLL • WMSUI32.DLL 4. Run FixMapi.exe (in C:\Windows\System32). 5. Install the MAPI and CDO client download version 6.5.8022. 6. Restart the BlackBerry Enterprise Server and any other processes that use the MAPI and CDO files. Note: If you run the BlackBerry Enterprise Server setup application after completing the steps above, when the setup application displays the pre-installation checklist, an error displays indicating that the MAPI and CDO files were not detected. This error displays because the MAPI and CDO files for version 6.5.8022 are installed in a different directory than in previous versions. This error does not prevent the BlackBerry Enterprise Server setup application from completing successfully. For more information, visit http://www.microsoft.com/downloads/details.aspx?FamilyID=E17E7F31-079A-43A9-BFF2- 0A110307611E&displaylang=en. 2. SDR 182839 If your organization uses a mixed messaging environment with Microsoft Exchange 2003 and Microsoft Exchange 2007, users are only able to check the availability of meeting invitees that use the same version of Microsoft Exchange. > Michael, > [quoted text clipped - 49 lines] >> > >> > -Brit |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.