Most of you have realized by now that Exchange 2007 doesn't include MAPI "in the box". We're supporting two ways to put MAPI on an Exchange 2007 server:
Some of you have noticed as well that with Exchange 2007, you don't have to have a Public Folder store. What happens when you try to connect to an Exchange 2007 server that doesn't have a Public Folder store?
With Outlook 2007, you connect with no problem. Earlier versions of Outlook get this error:
"Your Exchange Server administrator has blocked the version of Outlook that you are using. Contact your administrator for assistance."
MAPI applications will get the error MAPI_E_FAILONEPROVIDER if they're using any version of MAPI except the version supplied by Outlook 2007.
So what's a developer to do? Are you locked in to Outlook 2007's MAPI? Why did we provide a MAPI download if it won't even work?
Exchange 2007 blocks all MAPI providers earlier than Outlook 2007 when Public Folders are not available. This is because all of the earlier clients assume Public Folders will be available and will experience failures if allowed to connect. For customers whose code does not depend on Public Folders, a new flag has been made available to allow this check to be bypassed.
Right now, the only version of MAPI which supports this new flag is the MAPI download.
Details on the new flag:
#define CONNECT_IGNORE_NO_PF ((ULONG)0x8000)
This is set in the PR_PROFILE_CONNECT_FLAGS property on the global profile section.
The global profile section can be accessed by calling OpenProfileSection with pbGlobalProfileSectionGuid, which is defined in edkmdb.h.
When this flag is set, Exchange 2007 will not check if public folders are available when logging on. Use of this flag can be demonstrated with MAPI Editor:
Update - 4/17/07 Removed inadvertent assertion that there is a build of Exchange 2003 MAPI that understands this flag. If such a build does become available I'll update again.
kevin - did you try the steps I gave for MFCMAPI? They describe exactly what you need to do.
In my exchange 2007 setup even after downloading "ExchangeMapiCdo.EXE" MAPI code is failing during GetMessageStore with error code "HRESULT: 8004011d" . Any idea whats wrong?
I can only guess you didn't set CONNECT_IGNORE_NO_PF correctly on the profile.
If you've been bit by the problems with the web download of CDO 1.21 returning a 8004011D when trying
Stephen, is there a true 64 bit version of MAPI32.dll for use with x64 applications? We are running a 64 bit app and MAPIInitialize returns E_FAIL. The MAPI/CDO download for Exchange 2007 does not fix this either
MAPI is 32 bit only. We don't make a 64 bit MAPI right now.
Hello Stephen, do we have any opportunity to install .PST provider without Outlook. If yes, how we can do this? And another one what is the latest version of pst provider is available for NT4?
Exchange's MAPI includes an ANSI only PST provider. As for NT4 - um - maybe you could install the Exchange 5.5 system manager?
Is there a way to access Personal Store (PST) wihtout having Outlook installed? Reason: Take out the
One quick question regarding the MAPI download. Is it true, that this version of mapi32.dll does not return the STORE_UNICODE_OK flag in the PR_STORE_SUPPORT_MASK property? Even if the store supports UNICODE, the flag is never set. Forcing MAPI_UNICODE works as expected, but how can i find out if a store is really UNICODE capable?
I looked in the code and it doesn't appear Exchange's implementation of MAPI is aware of the STORE_UNICODE_OK flag. As far as MAPI_UNICODE is concerned, calls that don't support it will always let you know...
One of my customers reported that using the MAPI download , they were unable to get a referral from Exchange
I have modified the user profile as you said (using MFCMAPI) but when i try to get the store mailbox table on exchange server 2007 i get the error for HrQueryAllRows function :
"MAPI_E_NOT_INITIALIZED == 0x80040605".
The user has admin privileges and I even tried with the administrator also.
I am getting this error after logging in and got the IEXCHANGEMANAGER and the when i use HrQueryAllRows function. I thought something must be wrong with my code so i used MFCMAPI. it also gives the same error:
"MAPI_E_NOT_INITIALIZED == 0x80040605
Function m_lpContentsTable->QueryColumns( 0, &lpOriginalColSet)"
What might be the problem?
I've seen people follow the steps incorrectly and set the prop on the wrong profile section. Try again, and make sure to follow each step carefully. Do not use "Open Profile Section" as a shortcut.
Also - after you set the flag, make sure the hex value is 0x8002.
Yes I have double checked the steps for modifying and also verified the PR_PROVIDER_UID of 13DBB0C8AA05101A9BB000AA002FC45A. I opened the correct profile, and there was only one service : MSEMS. After modifying the flag i verified that the value is 0x8002. but still i get the same error.
Is it the problem with server configuration or am i missing some dll files?