Attempting fresh install of Exchange 2007 SP1 Active CCR node on a Windows 2008 cluster and get an odd error at the end. "Failed to connect to the target server "servername". The exception message is "WMI exception occured on server 'servername.mydomain.com': Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))". [10/2/2009 12:21:23 PM] [2] Ending processing." Here are the last few bits of the install log: [10/2/2009 12:21:23 PM] [2] Searching objects "theservername" of type "Server" under the root "$null". [10/2/2009 12:21:23 PM] [2] Previous operation run on domain controller 'USSPW032.mydomain.com'. [10/2/2009 12:21:23 PM] [2] Processing object "theservername\First Storage Group". [10/2/2009 12:21:23 PM] [2] [ERROR] Unexpected Error [10/2/2009 12:21:23 PM] [2] [ERROR] Failed to connect to the target server "theservername". The exception message is "WMI exception occured on server 'theservername.mydomain.com': Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))". [10/2/2009 12:21:23 PM] [2] Ending processing. [10/2/2009 12:21:23 PM] [1] The following 1 error(s) occurred during task execution: [10/2/2009 12:21:23 PM] [1] 0. ErrorRecord: Failed to connect to the target server "theservername". The exception message is "WMI exception occured on server 'theservername.mydomain.com': Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))". [10/2/2009 12:21:23 PM] [1] 0. ErrorRecord: System.InvalidOperationException: Failed to connect to the target server "theservername". The exception message is "WMI exception occured on server 'theservername.mydomain.com': Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))". [10/2/2009 12:21:23 PM] [1] [ERROR] Failed to connect to the target server "theservername". The exception message is "WMI exception occured on server 'theservername.mydomain.com': Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))". [10/2/2009 12:21:23 PM] [1] Setup is halting task execution because of one or more errors in a critical task. [10/2/2009 12:21:23 PM] [1] Finished executing component tasks. [10/2/2009 12:21:23 PM] [1] Ending processing. I have Exchange Org Admin rights. And in fact can install a stand alone mailbox server just fine. Anybody seen anything like this before? Thanks

Hi,Please check of you can access the wmi from the other server mentioned in the log. Also check the event logs for the servers for errors.Regards,Johanblog: www.johanveldhuis.nl

Sounds like your firewall is blocking WMI access. You can either disable the firewall which of course is not recommended, or run the following command to allow WMI: netsh advfirewall firewall set rule group="Remote Administration" new enable=yesMVP | MCSE:M | MCITP: Enterprise Messaging Administrator | MCTS: OCS + Voice Specialization | http://www.shudnow.net

Check info: 1. Is there any error event in the application log on the exchange server? 2. You can ping the “servername.mydomain.com”, right? 3. Is your domain a disjointed namespace environment? 4. Which permissions have been granted to the account that performed the installation? Troubleshooting: 1. Please do a Nslookup to the node and see if it’s coming up with right IP address 2. Please run a DCDIAG on the nodes for the general checking 3. Please verify if the account for the installation has the full access permission of “servername.mydomain.com” via ADUC 4. Please verify carefully about A record for “servername.mydomain.com” on the DNS server, problematic A record will cause the same issue Resources: Data Path Security Reference

Ok first of all, sorry for not getting back to this earlier. For more information. 'theservername.mydomain.com' is the name of the CMS of the Exchange install (sorry I wasn't clear on that before). 1. I can do a Nslookup on the CMS name and can ping it. 2. DCDiag is not seeing any major issues. 3. The account doing the installation is a local admin on the physical node doing the install and does indeed have full access to the CMS computer object in active directory 4. The 'servername.mydomain.com' mentioned in the error is not an A record, but a C-name. Would this really cause a problem? It certainly resolves fine. I will try adding the name as an A record and see if that cures us. Thanks for your feedback guys. Very much appreciated. I apologize for not replying earlier.

It was indeed the A Record Issue. Ok, so can someone explain to me why this is? Why a C-Name is not allowed. Also, once we get everything installed, is it possible for us to revert back to C-Name? Or will that break things? Again why? Thanks so much for your help.

Martin,I think it's the same as mentioned in this blog about the File Share Witness:http://msexchangeteam.com/archive/2008/04/03/448615.aspxRegards,Johanblog: www.johanveldhuis.nl