Exchange installation error c0070005 Access Denied
Posted on 2006-06-05
This problem has been haunting me for the last 6 weeks. I initially configured Exchange 2003 to run on a standalone server with Windows Sharepoint services on a Windows 2003 R2 server. Sharepoint seemed to conflict with Outlook Web Access--I could no longer use OWA from the server. I tried repairing the installation with no success. Long story short, I decided to start from scratch and made a mistake. I completely reformatted the server and installed a fresh installation of Windows 2003 R2 Enterprise Server without first running the /removeorg command. When I attempted to install Exchange again on the fresh server, I (of course) could not because the Active Directory schema had already been extended. At that point, I found the MS KB article for manually deleting Exchange from the AD schema. I did this and was then able to run /forestprep and /domainprep (which previously would not run). Now, however, when I ran Exchange setup after extending the schema again, I receive the c0070005 error "Access is denied" with the "f:\titanium... etc" error in the Exchange setup log. I tried modifying the registry in accordance with the MS KB article regarding registry remote access--but the problem persisted.
I went back to scratch, ran dcdiag and netdiag and started getting errors on almost every test. So, I decided to do something a little more drastic. My PDC also runs a DFS namespace and was generating errors--so I demoted it (a Backup Domain Controller exists), transferred all operations roles to the BDC and reformatted and rebuilt the machine. I then promoted it back to a PDC, reestablished the DFS namespace, and ran and tested the server for a week. I solved all of the dcdiag and netdiag problems and am no longer generating any errors on my PDC. Both of my domain controllers seem to be operating without error. During this process I renamed the PDC to avoid any schema conflicts during role transfers. I then reformatted and rebuilt my Exchange server to-be and renamed it as well. All of my windows servers were at this point running fresh installs of Win 2003 R2 Enterprise server.
So, today, I tried to install Exchange 2003 again. Dcdiag and netdiag showed no errors. My domain account had all the proper priveleges. I ran /forestprep and /domainprep and proceeded to install, but received the c0070005 error "Access is Denied" for "Microsoft Exchange System Management Tools" and "Microsoft Exchange Messaging and Collaboration Services". I'm utterly confused. I applied the MS QB 329229 solution and retried setup with no success.
What could be happening here? I have 2 DCs--one in City X on a 192.168.0.0 net, and one in City Y on a 192.168.2.0 net. They're connected through a dedicated VPN tunnel between the routers servicing the networks. The only error that I am occasionally receiving on these DCs is a WINS replication error. This is infrequent. Otherwise, they seem to be perfectly healthy.
Network traffic is heavy during the day. Could this be a schema replication issue? Is it simply taking an unusually long time for the schema changes to propagate? Should I run /removeorg and delete all Exchange references and try again? I do get a "compatability" warning when I try to run any element of Exchange setup "this version of Exchange has known compatability issues with this version of Windows." Could this be related? I did not receive this warning prior to upgrading from Windows 2003 Server to Windows 2003 R2 Server.
Any advice would be appreciated. I can clarify any and all points in this topic.