• Sign in
 
  •  
  • MSDN Blogs
  • Microsoft Blog Images
  • More ...

  • Blog Home
  • About
  • Email Blog Author
  • Share this
  • RSS for posts
  • Atom
  • RSS for comments
  • CDO (25)
  • Code Snippet (43)
  • Custom Providers (17)
  • Debugging (7)
  • DevMsgTeam (301)
  • Documentation (109)
  • DST (8)
  • EWS (7)
  • Exchange (109)
  • Gotchas (97)
  • Hotfix (28)
  • MAPI (240)
  • MAPI Download (54)
  • MFCMAPI (101)
  • MSDN (59)
  • Non Dev (11)
  • OOM (17)
  • Outlook (171)
  • Outlook 2007 Auxiliary Reference (45)
  • Outlook Integration API (12)
  • Protocol Docs (20)
  • PST/OST (23)
  • Referrals (8)
  • Vista (12)
  • WrapPST (18)
Links:
  • Download MFCMAPI
  • MFCMAPI on Facebook
  • Troubleshooting Outlook Crashes
  • Office Update Center
  • Developer Messaging Team Blog
This site is provided "AS IS" with no warranties, and confers no rights. Use of included code samples are subject to the terms specified in the Terms of Use.
Archives
  • May 2013 (3)
  • April 2013 (1)
  • March 2013 (2)
  • February 2013 (2)
  • January 2013 (2)
  • December 2012 (4)
  • November 2012 (2)
  • October 2012 (2)
  • September 2012 (1)
  • August 2012 (3)
  • June 2012 (2)
  • May 2012 (1)
  • April 2012 (3)
  • March 2012 (3)
  • February 2012 (3)
  • January 2012 (1)
  • December 2011 (3)
  • November 2011 (1)
  • October 2011 (3)
  • September 2011 (1)
  • August 2011 (1)
  • July 2011 (4)
  • June 2011 (3)
  • May 2011 (3)
  • April 2011 (3)
  • March 2011 (5)
  • February 2011 (1)
  • January 2011 (2)
  • December 2010 (1)
  • November 2010 (4)
  • October 2010 (1)
  • September 2010 (3)
  • August 2010 (5)
  • July 2010 (3)
  • June 2010 (3)
  • May 2010 (1)
  • April 2010 (3)
  • March 2010 (3)
  • February 2010 (3)
  • January 2010 (2)
  • December 2009 (3)
  • November 2009 (5)
  • October 2009 (4)
  • September 2009 (5)
  • August 2009 (5)
  • July 2009 (11)
  • June 2009 (6)
  • May 2009 (5)
  • April 2009 (3)
  • March 2009 (18)
  • February 2009 (10)
  • January 2009 (3)
  • December 2008 (2)
  • November 2008 (2)
  • October 2008 (5)
  • September 2008 (4)
  • August 2008 (10)
  • July 2008 (6)
  • June 2008 (8)
  • May 2008 (2)
  • April 2008 (4)
  • March 2008 (2)
  • February 2008 (2)
  • January 2008 (5)
  • December 2007 (3)
  • November 2007 (2)
  • October 2007 (3)
  • September 2007 (1)
  • August 2007 (4)
  • July 2007 (5)
  • June 2007 (3)
  • May 2007 (4)
  • April 2007 (1)
  • March 2007 (6)
  • February 2007 (3)
  • January 2007 (2)
  • December 2006 (4)
  • November 2006 (3)
  • October 2006 (1)
  • August 2006 (1)
  • June 2006 (5)
  • May 2006 (5)
  • December 2005 (1)
  • November 2005 (4)
  • October 2005 (2)
  • September 2005 (1)
  • April 2005 (3)
  • December 2004 (2)
  • September 2004 (2)
  • August 2004 (3)
  • July 2004 (3)

This Just In: MAPI and Windows Server 2008 Now Get Along

MSDN Blogs > SGriffin's MAPI Internals > This Just In: MAPI and Windows Server 2008 Now Get Along

This Just In: MAPI and Windows Server 2008 Now Get Along

Stephen Griffin - MSFT
2 Jun 2008 11:02 AM
  • Comments 49

The MAPI/CDO download package now works on Windows Server 2008 and Vista. The main blocker to getting this to work was the fact that in Windows Server 2008 and Vista, mapi32.dll was marked as a system file. Any attempt to replace it would be blocked or undone. Exchange's MAPI has always replaced mapi32.dll with its own version, so it couldn't work on those operating systems.

The fix is modify Exchange's MAPI to take advantage of the MAPI Stub Library mechanism. We moved Exchange's MAPI binaries out of system32/syswow64 and placed them under C:\Program Files\ExchangeMAPI ("Program Files (x86)" on a 64 bit machine). We also renamed Exchange's mapi32.dll binary. It's now called ExMAPI32.dll.

Some notes:

  • If you've installed an earlier version of this download on a machine and wish to upgrade, you must uninstall the earlier version first. It will not upgrade in place, and may even claim to have successfully installed.
  • Mapi32.dll in the system directory should be version 1.0.xxxx. If it's 6.5.xxxx, then the stub is not in place. Use FixMAPI.exe to correct this before installing the updated MAPI download.
  • The version number of the Windows Server 2008/Vista compatible download is 06.05.8022.0.
  • MAPI and CDO are still 32 bit only - it will install and work on a 64 bit machine, but only when used from a 32 bit program.
  • MAPISVC.inf in the system directory will be updated with Exchange's providers, but the date may not be changed. I just noticed this when testing the installer on a machine here.
  • The installer adds the MAPI install directory to the PATH statement. This MUST NOT be removed. It is required to allow DLL dependencies to work correctly.
  • Session 0 Isolation causes problems with our fix to the deleted profile issue. With that fix in place, a normal user (who lacks SeCreateGlobalPrivilege) wouldn't be able to use MAPI at all. So we modified the fix to attempt the global namespace first (which will fail for a normal user), then fall back to a local namespace. This means it is possible for a normal user to log on to a server twice with Terminal Services and delete a profile from one session that is in use under another session. To help identify this scenario, there's a new error code which will be seen by MAPI applications if this happens: MAPI_E_PROFILE_DELETED (0x80040204).
  • The download enters Extended Support in April 2009. That doesn't mean the download will be removed then, but don't expect updates to it.

Update: Looks like the Ehlo blog picked this up. Welcome Ehlo readers! I was involved in getting this update done, so lemme know if you have any questions.

  • 49 Comments
Exchange, MAPI, Documentation, Hotfix, CDO, MAPI Download, DevMsgTeam, Vista
Comments
  • Sridhar
    3 Jun 2008 12:45 PM

    Stephen,

    Any time period  for 64 bit MAPI release  ??

    Regards

    Sridhar

  • Stephen Griffin - MSFT
    3 Jun 2008 1:18 PM

    There have been no announcements regarding a 64 bit MAPI.

  • J
    3 Jun 2008 1:43 PM

    Has anything else changed in this update or is it just introducing Windows Server 2008/Vista support?

  • Stephen Griffin - MSFT
    3 Jun 2008 1:53 PM

    In addition to the session 0 isolation issue, we also fixed an unreported crash scenario. The move from system32 to program files is a fairly large and potentially destabilizing move though. You should definitely test your applications with this update.

  • SGriffin's [MSFT] WebLog
    4 Jun 2008 1:08 AM

    Well, that didn't take long. We just released of the latest MAPI download this weekend and yesterday

  • JP
    11 Jun 2008 2:20 PM

    It appears that one of the new dll's is changing the current working directory of the loading process to "C:\Program Files\ExchangeMAPI" and breaking some applications.

    Also, adding this directory to the path will not work in all/most cases since windows\system32 precedes it.  Uninstalling the previous version (7974) did not remove the dll's from the windows\system32 directory... perhaps that is why the current working directory is changed?

  • Stephen Griffin - MSFT
    11 Jun 2008 2:36 PM

    I didn't think we were changing the working directory, but I'll check on that. On the uninstall, if an application was using the DLLs then they'd have to be scheduled for deletion on reboot - perhaps that's why the uninstall failed?

  • JP
    11 Jun 2008 3:04 PM

    I just did a quick test program and its MAPIInitialize() that's changing the directory.

  • Lev
    20 Jun 2008 5:59 PM

    is there a new version of MERGEINI that would work with WS 08?

    http://support.microsoft.com/kb/294470

  • Stephen Griffin - MSFT
    20 Jun 2008 6:13 PM

    Wow - haven't seen that tool in ages. All it does is simple text manipulation. In fact, since mapisvc.inf is nothing more than a .ini file, the Windows INI functions work (http://msdn.microsoft.com/en-us/library/ms725501(VS.85).aspx). See HrSetProfileParameters in the MFCMAPI code.

  • RDMTECH
    30 Jun 2008 5:15 PM

    I just installed Backup Exec 12 on my 2008 server running Exchange 2007.  I have been bouncing back and forth between Microsoft and Symantec trying to get v12 to restore mail boxes.  Symantec is blaming MAPI and Microsoft insists MAPI is configured properly.  Based on your notes everything appears correct, but Symantec believes that having MAPI32.DLL and MAPISTUB.DLL (both v1.0.2536) in the SysWOW64 folder is an issue.  I am stuck in the middle with no clue what to do.

  • Stephen Griffin - MSFT
    30 Jun 2008 6:04 PM

    Send me a mail with your case number and I can check on the status from our side.

  • SGriffin's MAPI Internals
    30 Jul 2008 10:37 AM

    Sorry for not posting this sooner - I just found out about it today. As I noted previously , we recently

  • SGriffin's MAPI Internals
    25 Aug 2008 12:04 PM

    We recently released a downloadable Exchange System Manager (ESM) for Exchange 2003 which can be installed

  • Chuck
    23 Oct 2008 3:56 PM

    The ESM for Vista won't install on a W2K8/x64

    machine.  It complains "You are not running Vista".  Will there be an update to correct his?

    Thanks.................Chuck

Page 1 of 4 (49 items) 1234
Leave a Comment
  • Please add 7 and 4 and type the answer here:
  • Post
  • © 2013 Microsoft Corporation.
  • Terms of Use
  • Trademarks
  • Privacy & Cookies
  • Report Abuse
  • 5.6.426.415