We just announced a new release of the MAPI Download that’s pretty much mandatory if you want to work with Exchange 2010. You’ll also need to get and apply Rollup 1 (RU1) for Exchange 2010.
Details about the MAPI Download:
The new MAPI Download fixes a number of problems MAPI had with Exchange 2010:
If I identify other issues fixed by the updated MAPI download, I’ll add them in here.
[Update: 12/14/09] Forgot to mention that you'll still need these tweaks for your profile, but you don't have to disable encryption anymore.[Update: 12/21/09] Added information about admin access to PF.
Is the Outlook Mapi layer also updated?
If not how is it possible to use the corrected Mapi on a workstation where Outlook is intalled?
It's not possible. It never has been possible and never will be possible to install both the Exchange MAPI download and Outlook on the same machine. This update corrects problems the Exchange MAPI download had connecting to Exchange 2010. Outlook's MAPI did not have these problems and did not need an update.
Outlook's Mapi seems to have problem with the following apis: GetmailboxTable and GetPublicFoldersTable.
They work with Exchange 4 5 5.5 2000 2003 2007 but not with 2010.
The new MapiDownload solve the problem.
For the following resons I don't understand why the Mapi download cannot be installed on a workstation where Outlook is already installed:
- MAPI and CDO are now optional components when installing Outlook.
- as I understand the Mapi32 Stub Library purpose is to let you install more than one version of Mapi on the same workstation
This Exchange MAPI download can not and does not correct any problems in Outlook's MAPI. If Outlook's MAPI is having a problem with Exchange 2010, you should consider opening a case with a repro scenario so we can investigate it.
MAPI is not an optional component of Outlook. The MAPI Stub library is irrelevent. We do NOT allow Exchange's and Outlook's MAPI to be installed on the same machine (it's even blocked in the Exchange download's installer). When people force them on the same box, the only benefit they get is a machine where MAPI applications crash more often. Don't do it.
Thank you Scott.
I was unclear the Mapi download of course doesn't correct any problem with Outlook's Mapi but it corrects a problem that existed on the previous version of the Mapi download with the GetMaillboxTable Api.
My goal is not to use both stack at the same time but to solve a problem that still exists on the Outlook's Mapi when the Getmailboxtable api is called.
The problem can be reproduced by using MFCMapi as described here:
I'm not familiar with the problem. AFAIK, no customer has opened a case reporting it. You should consider doing so if it's something you need fixed.
I am updating an application which is using MAPI and is working without problems for all previous versions of Exchange Server. However, I can not get it to work with Exchange 2010. The MFCMAPI is showing exactly the same problems. I have several questions:
1. Previous exchangemapicdo download packages were installed in Windows\SYSWOW64 directory and the new one is installed in Program Files(x86)\ExchangeMapi. Why is this?
2. There is no MAPI32.dll any more among the files extracted from the package (before there was). Is it replaced with EXMAPI32.dll?
3. Because of 1. and 2., I have copied all the files to SYSWOW64 and renamed exmapi32.dll to mapi32.dll (the newest version 8147). Also installed the exchange rollup 1. Unfortunately I still have no success at getting it to work. MFCMAPI (as is also my application) is always failing on OpenDefaultMessageStore with MAPI_E_FAILONEPROVIDER error 0x4008011D.
4. Also, where should all this be tried at? I am doing it on the server where the CAS is located. Another interesting thing is that I can not initialize MAPI until I specify the AD server as the exchange server instead of exchange server which is hosting CAS(only then the AD server gets resolved to CAS server)... this is done from MFCMAPI.
1,2 - That change was made over a year ago, you must not have tested since then: http://blogs.msdn.com/stephen_griffin/archive/2008/06/02/this-just-in-mapi-and-windows-server-2008-now-get-along.aspx
3 - Very bad idea. Don't do it.
4 - You have to tweak your profile: http://blogs.msdn.com/stephen_griffin/archive/2009/09/02/exchange-2010-and-the-mapi-download.aspx
Thank you Stephen. I opened a support request regarding the problem.
You are correct, I have not been testing for more than a year since eveything was working for previous releases:) Thx for the explanation. I have tried everything on two new environemnts and there it is working. However on the first one I am still having the same problems, seems like a Administrator account permission problem to me?
1. Let's say if I wanted to access mailboxes and browse mailbox table using some other account (not Administrator). What kind of permissions and where should I assign to that user in order to be able to access mailboxes through that MAPI profile. I have tried doing this on the environments that are working, by assigning the same permissions that the Administrator has to a new account, but I get again the 80040111d error. If I new this, maybe I could check what is wrong with Administrator on the first environment.
2. Another thing I would like to know is which server should be specified as exchange server when creating the profile? It seems that it always gets resolved to the CAS server for which that users mailbox database is registered to (RpsClientAccessServer). Is this true?
3. Can DAG and active/passive copy replication be transparent for MAPI? Can we somehow get all mailboxes on a DAG listed when getting mailbox table. Because I always get ony the mailboxes on the specific server(even if I specify DAG server). I only get mailbox listed on the server where its particulare database is currently active and not on the others.
I downloaded the Outlook 2010 beta and tried to get the mailbox table (both with MFCMAPI and my own implementation) but I get the MAPI_E_CALL_FAILED. Since I can not install the CDOMAPI 1.2.1 on this machine (CDOMAPI-Outlook incompatibility) I have no way of getting the mailbox table from an Exchange 2010 server.
I am able to get the mailbox table for all other versions of Exchange and I can get the mailbox table from Exchange 2010 if I use the CDOMAPI 1.2.1 on the machine.
What is your recommendation on getting the mailbox table from a machine that does not have CDOMAPI 1.2.1 installed?
Any help will be appreciated.
Yuval - Exchange 2010 no longer supports the interface used by Outlook's implementation of GetMailboxTable. The MAPI download uses a different implementation which is still supported. If you want to get this addressed, your best course of action is to open a case under a Premier contract and request a fix.
I met a problem when I used MFCMAPI. I can not initialize MAPI if I use mailbox server or cas server as the server.
I have to specify the AD server as the exchange server instead of exchange server. It always reports the error "the name could not be resolved. Network problems are preventing...".
DC, mailbox and CAS server: windows 2008 R2 enterprise.
Exchange server 2010: RTM+RU1.
MAPI: the latest version 6.5.8147
IPV6 was banned on all the servers.
Is the problem caused by windows 2008 R2? I tested a similar environment on window 2008 SP2, it works.
be very very careful with latest MAPICDO-version (6.5.8153.0 from 1/12/2010) for Exchange 2010.
It is more than buggy and in one word: Showstopper
Same code works perfect since years with previous MAPICDO-version under Exchange 2003 & 2007.
Does anyone also made same experience?