Can't install mailbox role from Exchange Server 2007 SP1 onto a fresh Windows Server 2008 R2 installation
I'm rebuilding my test domain with all the latest and greatest. I'm starting with my combo domain controller / exchange box. Wiped it, did a fresh install of Windows Server 2008 R2, and got it set as a domain controller. I went to install Exchange Server 2007 with SP1 (the version thats on the MSDN subscriber downloads area) and everything was fine until it went to install the mailbox role, and I got an access denied error (The error code was 3221684229. The message was Access is denied.)I looked at the Exchange Server install logs, and I see the following relevant section. How do I fix this?[11/4/2009 9:12:45 AM] [2] ++++ Starting interpreter on file C:\Program Files\Microsoft\Exchange Server\Setup\data\admin.ins ++++ -- ID:31258 --[11/4/2009 9:12:45 AM] [2] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <CreateKey:MSExchangeMig> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <CreateKey:MSExchangeMigDS> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <CloseKey:> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application\MSExchangeMig> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <ReplaceExpandString:EventMessageFile;C:\Program Files\Microsoft\Exchange Server\bin\mlmig32.dll> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <ReplaceExpandString:ParameterMessageFile;C:\Program Files\Microsoft\Exchange Server\bin\mlmig32.dll> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <ReplaceExpandString:CategoryMessageFile;C:\Program Files\Microsoft\Exchange Server\bin\mlmig32.dll> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <ReplaceDword:TypesSupported;7> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <CloseKey:> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application\MSExchangeMigDS> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <ReplaceExpandStringSystem:EventMessageFile;dapi.dll> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <ReplaceDword:TypesSupported;7> -- ID:31259 --[11/4/2009 9:12:45 AM] [2] Interpreting line <CloseKey:> -- ID:31259 --[11/4/2009 9:12:46 AM] [2] Interpreting line <OpenClassesKey:Interface\> -- ID:31259 --[11/4/2009 9:12:46 AM] [2] Interpreting line <CreateKey:{FD8256D0-FD15-11CE-ABC4-02608C9E7553}> -- ID:31259 --[11/4/2009 9:12:46 AM] [2] CInsParser::ScProcessLine (f:\08.01.0240\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199) Error code 0XC0070005 (5): Access is denied.[11/4/2009 9:12:46 AM] [2] Processing file 'C:\Program Files\Microsoft\Exchange Server\Setup\data\admin.ins', at or near line 31 (CreateKey:{FD8256D0-FD15-11CE-ABC4-02608C9E7553}) -- ID:31111 -- CInsParser::ScProcessLine (f:\08.01.0240\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488) Error code 0XC0070005 (5): Access is denied.[11/4/2009 9:12:46 AM] [2] Registry file name: 'C:\Program Files\Microsoft\Exchange Server\Setup\data\admin.ins' CRegistryManager::ScProcessFile (f:\08.01.0240\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125) Error code 0XC0070005 (5): Access is denied.[11/4/2009 9:12:46 AM] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\admin' CBaseAtom::ScRunRegistryFile (f:\08.01.0240\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379) Error code 0XC0070005 (5): Access is denied.[11/4/2009 9:12:46 AM] [2] Leaving CBaseAtom(Exchange System Management Snap-ins)::ScRunRegistryFile[11/4/2009 9:12:46 AM] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\admin' CBaseAtom::ScAddRegistryKeys (f:\08.01.0240\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249) Error code 0XC0070005 (5): Access is denied.[11/4/2009 9:12:46 AM] [2] Leaving CBaseAtom(Exchange System Management Snap-ins)::ScAddRegistryKeys[11/4/2009 9:12:46 AM] [2] CAtomAdmin::ScAddRegistryKeys (f:\08.01.0240\sources\dev\admin\src\udog\exsetdata\components\admin\a_admin.cxx:106) Error code 0XC0070005 (5): Access is denied.[11/4/2009 9:12:46 AM] [2] Leaving CAtomAdmin::ScAddRegistryKeys[11/4/2009 9:12:46 AM] [2] CBaseAtom::ScAdd (f:\08.01.0240\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639) Error code 0XC0070005 (5): Access is denied.[11/4/2009 9:12:46 AM] [2] Leaving CBaseAtom(Exchange System Management Snap-ins)::ScAdd[11/4/2009 9:12:46 AM] [2] Service = '' CBaseServiceAtom::ScAdd (f:\08.01.0240\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203) Error code 0XC0070005 (5): Access is denied.[11/4/2009 9:12:46 AM] [2] Leaving CBaseServiceAtom(Exchange System Management Snap-ins)::ScAdd[11/4/2009 9:12:46 AM] [2] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\08.01.0240\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535) Error code 0XC0070005 (5): Access is denied.[11/4/2009 9:12:46 AM] [2] ScSetupAtom (f:\08.01.0240\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897) Error code 0XC0070005 (5): Access is denied.[11/4/2009 9:12:46 AM] [2] Leaving ScSetupAtom[11/4/2009 9:12:46 AM] [2] [ERROR] An error occurred. The error code was 3221684229. The message was Access is denied..[11/4/2009 9:12:46 AM] [1] The following 1 error(s) occurred during task execution:[11/4/2009 9:12:46 AM] [1] 0. ErrorRecord: An error occurred. The error code was 3221684229. The message was Access is denied..[11/4/2009 9:12:46 AM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221684229. The message was Access is denied..[11/4/2009 9:12:46 AM] [1] [ERROR] An error occurred. The error code was 3221684229. The message was Access is denied..[11/4/2009 9:12:46 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
November 5th, 2009 6:05pm

Exchange 2007 on Windows 2008 R2 is not yet supported but will be soon... Supporting Exchange 2007 on Windows Server 2008 R2 http://msexchangeteam.com/archive/2009/11/04/453026.aspx Amit Tank MVP: Exchange Server | MCTS: Microsoft Exchange Server 2010, ConfigurationMCITP: EMA | MCSA: M | Blog: http://ExchangeShare.WordPress.com
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2009 6:27pm

Thanks for the info - I did find this elsewhere as well. The release dates puts me in a bit of a conundrum.I'm trying to upgrade everything in my environment, and I would gladly deploy Exchange Server 2010, but its only still in the release candidate stage.By the way, I know its not supported, but I actually got the mailbox role to finally install by running setupin compatibility mode on Windows Server 2008 R2. It broke horribly when I tried to upgrade Exchange Server 2007 to SP2, so I'm rethinking the installs.If I deploy Exchange Server 2010's release candidate on a windows server 2008 R2 machine, will I be able to then turn around and apply the actual Exchange Server 2010 RTM, or do I have to restage the box yet again?
November 5th, 2009 8:00pm

Yes. However you can wait for some more time since RTM is ready and may be available soon in the market... Exchange Server 2010 Release Candidate Available Today! http://msexchangeteam.com/archive/2009/08/17/451974.aspx In place upgrade from Exchange Server 2010 Release Candidate to Exchange Server 2010 RTM: You can start planning and deploying your Exchange Server 2010 test environment today knowing that it will be possible to perform an in place upgrade with the final version expected to be available later this year. You won't need to reinstall your servers or reconfigure your Exchange settings once you have deployed the Release Candidate. This will save you time while allowing you to start evaluating the latest product capabilities now. Exchange 2010 is Code Complete and on its way to General Availability http://msexchangeteam.com/archive/2009/10/08/452775.aspx We are happy to announce that Exchange 2010 is Code Complete! Our senior leadership team has signed off on the final code, and it has been sent to our early adopters for one final look before its public release. This Release to Manufacturing (RTM) milestone means we are on our way to general availability and the launch at TechEd Europe 2009 (http://www.microsoft.com/europe/teched/) in early November. Amit Tank MVP: Exchange Server | MCTS: Microsoft Exchange Server 2010, ConfigurationMCITP: EMA | MCSA: M | Blog: http://ExchangeShare.WordPress.com
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2009 8:08pm

you can fix it easily open C:\Program Files\Microsoft\Exchange Server\Setup\Data\admin.ins and delete everything under OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\ApplicationCreateKey:MSExchangeMigCreateKey:MSExchangeMigDSCloseKey: that file is in charge of unified messaging, so, if you're not using this in your org, you can still use exchange 2007 in 2008 R2 server. UM is still working, anyway. don't listen to that marketing b... um...lie. :)
December 13th, 2009 11:47pm

Laugh. It didnt matter. Exchange 2010 came out on MSDNthe *very* next day. Why he couldnt tell me just wait till Monday, but had to be vague about it was annoying. Ive seen real soon be as long as two months. I rebuilt the domain for the third time in three days once it came out.
Free Windows Admin Tool Kit Click here and download it now
December 15th, 2009 6:01pm

you're lucky. in my case, i stuck in Exch 2007 and 2008R2. my client got licenses for both of them, and wish to use benefits of 2008R2 and keep using Exch 2007. and ms exchange team just told us, that they will add 2008R2 support in SP3 for exch 2007, which will happen in next July!!! i understand, that you probably solved that problem, but i hope this will help anyone, who will google for it.
December 15th, 2009 10:10pm

you can fix it easily open C:\Program Files\Microsoft\Exchange Server\Setup\Data\admin.ins and delete everything under OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application CreateKey:MSExchangeMig CreateKey:MSExchangeMigDS CloseKey: that file is in charge of unified messaging, so, if you're not using this in your org, you can still use exchange 2007 in 2008 R2 server. UM is still working, anyway. don't listen to that marketing b... um...lie. :) Well done Dekado! Worked fine for me as well at my VMware Workstation environment. Thanks!!!Eduardo Antunes - NOS Team Lead - Dell Brasil
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2010 8:40am

Impressive Dekado!! - worked like a charm for me.
June 15th, 2010 3:58am

Awesome, worked for me. Thanks,
Free Windows Admin Tool Kit Click here and download it now
June 16th, 2010 6:53am

you can fix it easily open C:\Program Files\Microsoft\Exchange Server\Setup\Data\admin.ins and delete everything under OpenMachineKey:SYSTEM\CurrentControlSet\Services\EventLog\Application CreateKey:MSExchangeMig CreateKey:MSExchangeMigDS CloseKey: that file is in charge of unified messaging, so, if you're not using this in your org, you can still use exchange 2007 in 2008 R2 server. UM is still working, anyway. don't listen to that marketing b... um...lie. :) Hey this worked for me as well. Does it give any problems in future. I have this setup currently in my labs. Intend to use it for future testing. but if this gives any problems with compatibility, well i would rather change my labs. Let me know.
September 20th, 2010 1:42pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics