while troubleshooting backups I have encountered "How to use MFCMapi to test Microsoft Exchange Server Messaging API (MAPI) functionality and administrator access. http://seer.entsupport.symantec.com/docs/291357.htm" and when running this tool on exchange server [session / logon and display store table] I get an error: Error: code: MAPI_E_CALL_FAILED == 0x80004005Function :: MAPIInitialize(&mapiInit)File .\MapiObjects.cppLine 106this started after installing RU9in a similar thread http://social.technet.microsoft.com/forums/en-US/exchangesvrdevelopment/thread/bac08966-6f0f-4509-8dba-46d814679c99/there was indication that Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 are required, but in my case this was installed and we even reinstalled it with no luck.any ideas?

I'm not sure on this one but could I just give you a word of warning. Be very very careful with this tool. It can be a final resort tool, but it should be used with extreme caution as it can cause issues with the stability of the database. What backup problem are you having? Shaun

symantec support used it to troubleshoot GRT backups. I need to fix this MAPI issue before they can resume their case... all we need is to be able to logon and display store table, which is not presently working.

Hi,0x80004005 used to inidicate limited or no access to the resource. Did you make sure that you have full permissoins on the database you are trying to open or the profile being used has access to the database? If you are trying to open some other user's mailbox using MFCMAPI you can grant yourself full mailbox access permissions on it and then try. Additionally, download the latest version of MFCMAPI from codeplex.I presume it is Exchange 2007.Milind Naphade | MCTS:M (Exchange 2007 and 2010) | http://www.msexchangegeek.com

account is indeed domain admin and has all neccessary permissions on exchange - as described this worked fine before the RU install.Thanks for suggesting to check for new version - symantec's link was indeed previous release.Symantec asked me to use the x64 version of MFCMAPI given our CCR cluster is running w2k8 x64, but I've noticed that if I use the x86 version of MFCMAPI - it works. Could they be wrong? should we be using the x64 version? their app is x64 too, but MAPI and CDO are still 32 bit only as far as I know so how on earth did it work before!?it work in MFCMAPI x86, but they want x64 version working too!?I've installed v6.0.0.1015 of MFCMAPI x64 from codeplex, which is latest stable september release and I still get an error although somewher different:MAPIIntialize failed with error 0x80004005 == MAPI_E_CALL_FAILED.Here are some known causes for this.1 - Windows Mail or Outlook Express (which do not implement Extended MAPI) is registered as the Default Mail Client.See http://msdn.microsoft.com/en-gb/library/dd162409.aspx for information on setting the Default Mail Client.2 - The bitness (32 or 64 bit) of MFCMAPI does not match the bitness of Outlook.See http://mfcmapi.codeplex.com for the latest 32 bit and 64 bit builds of MFCMAPI.In file .\MapiObjects.cppOn line 113any ideas?

Per my knowledge, office product wont have 64 bit version until office 2010. So, 64-bit MFCMAPI doesnt work

they still think there is a problem with exchange - even when using the x86 version of MFCMAPI if you click on MDB - open other users mailbox then a series of errors pop up:Error: Code: MAPI_E_FAILONEPROVIDER == 0x8004011DFunction File .\MAPIStoreFunctions.cppLine 48Error: Code: MAPI_E_FAILONEPROVIDER == 0x8004011DFunction CallOpenMsgStore( lpMAPISession, NULL, &pRow->aRow[ulRowNum].lpProps[EID].Value.bin, MDB_WRITE, lppMDB)File .\MAPIStoreFunctions.cppLine 744Error: Code: MAPI_E_NOT_FOUND == 0x8004010FFunction OpenMessageStoreGUID(lpMAPISession,pbExchangeProviderPrimaryUserGuid,&lpPrivateMDB)File .\MAPIStoreFunctions.cppLine 623Error: Code: MAPI_E_NOT_FOUND == 0x8004010FFunction OpenOtherUsersMailboxFromGal( lpMAPISession, lpAddrBook, &lpMailboxMDB)File .\MainDlg.cppLine 658any idea what those are?

0x8004011D means that there is no provider loaded, most likely EMSMBD32.dll which is the store provider. The result is an inability to logon to the store. MAPI_E_FAILONEPROVIDER has multiple causes, with different resolutions depending on the cause: If theres a super account that can log into to all mailboxes launches MFCMAPI, make sure that the mail profile of the super account is set up in online mode, otherwise MFCMAPI may crash, this is very important The super account shouldnt be a member of any Administrative Groups (Domain Admins or Enterprise Admins) in order to avoid permission issues due to inherited DENYs for Receive As (Full Mailbox Access) permissions MFCMAPI requires that the super account be given the Exchange View Only Administrator role in order to enumerate the store in order to open another user's mailbox from within the same MFCMAPI session. Outlook does not require the Exchange View Only Administrator role to open another user's mailbox but MFCMAPI does Please use EMS to grant "Send As" permission at the domain or OU level, and Receive As permission at the organizational level: Add-ADPermission "DN of Domain or OU" -User "Domain\Super Account" -ExtendedRights "send as" -InheritedObjectType user Get-OrganizationConfig | Add-AdPermission -user DOMAIN\Super Account" -ExtendedRights Receive-As After allowing time for replication if needed, you can do get-mailboxdatabase | get-adpermission" again and you should see that right inheriting down to all yourmailbox storesJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Thanks James,We only started experiencing this issue after we patched the machines few days agopresently MFCMAPI works fine under the main administrator domain admin account, but not under any other, which is why we have changed the account under which the backups run.Symantec insist that the account they backup exchange with should be member of Administrators, backup operators and domain admins.

If your organization has "Send As" and "Receive As" permissions configured as "deny" at the organization level, inherited "deny" permissions can cause the MAPI Logon verification test to fail. The backup software may require being the member of admin groups, but for MFCMAPI, please try to use a new account, as the suggestions aboveJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

I too have come across this issue. I found it was caused because I answered "No" to the question "Do you have any client computers running Outlook 2003 and earlier or Entourage in your organization?" during the installation of Microsoft Exchange 2007. I fixed this by uninstalling Microsoft Exchange MAPI Client and Collaboration Data Objects 1.2.1 (ExchangeMapiCDO) and installing Microsoft Outlook 2007 (or 2010 32-bit) on the computer. The errors then disappeared from MFCMapi. I assume the issue is caused by ExchangeMapiCDO masquerading as an Outlook 2003 client during connection to the Exchange server, which in this Exchange configuration is not supported. The MAPI client installed by Outlook 2007/2010 x86 establishes a connection that is supported in this Exchange configuration.