Hi, I'm unable to install Exchange 2007 RTM. During the prerequisites check the following error is logged: Error:There was a problem accessing the registry on this computer. This may happen if the Remote Registry service is not running; it may also indicate a network problem. I've checked everything, but the remote registry service is running, on both the local machine where exchange will be installed as well as on both domain controllers we have. Domain controllers are also running fine, so network problems are also not an option. Any ideas ? Now Exchange 2007 is finally there and I cannot install it.... Franc.

Hi, I fixed it. The binding order on the NICS was the issue. The server has a second network card which connects to the ISCSI backbone. This card only has TCP/IP enabled and no file and print sharing or Microsoft Client. However, this card was the first in the binding order list. I moved it to the bottom of the list and rerun setup and now setup continues. Franc.

I have the same problem, but I have only one network card.. Does anyone have an idea?

Be sure that you have Client for MS Networks enabled under your LAN TCP/IP settings.

Hi all ; i fixed the problem. it was issue of network cards. i allow file and print sharing and binding order of network cards. Finally, I found that this is because I remove Client for Microsoft Networks & File and Printer Sharing for Microsoft Networks on external NIC, after I restore to default setting, Exchange setup continues. Every thing is working fine now. thnximranrafique384@hotmail.com

I have enabled file sharing and Client for Microsoft Networks, and Remote Registry service is running but I'm still receiving this error. Any ideas?

open up the ExchangeSetupLog the most recent log file and cut and paste errors.

Hope this help 10:57:36.796: Starting Collecting Data phase.10:57:36.812: No mapping between account names and security IDs was done10:57:36.875: Error (Unexpected error [0x674CBB7E] while executing command '[Microsoft.Win32.RegistryKey]:penRemoteBaseKey([Microsoft.Win32.RegistryHive]::LocalMachine, [System.Net.Dns]::GetHostEntry([System.Net.Dns]::GetHostName()).HostName)'.) trying to process object [Microsoft.Win32.RegistryKey]:penRemoteBaseKey([Microsoft.Win32.RegistryHive]::LocalMachine, [System.Net.Dns]::GetHostEntry([System.Net.Dns]::GetHostName()).HostName), skipping object.10:57:37.953: Completed Collecting Data phase.10:57:37.968: Error (Rule name 'PreReq_fPassiveUninstallNoCMSPresentKey' referenced by rule 'PreReq_fPassiveUninstallNoCMSPresent' in input file is not defined) in format of rules in configuration file.10:57:38.046: Starting Postprocessing Rules phase.10:57:38.046: Completed Postprocessing Rules phase.

I am assuming that you're doing a local install of Exchange 2007 RTM or SP1. According to .NET MSDN reference http://msdn2.microsoft.com/en-us/library/microsoft.win32.registrykey.openremotebasekey.aspx, you need to have Remote Registry and Remote Administration services running. In fact in Powershell, you can simulate that command [Microsoft.Win32.RegistryKey]:penRemoteBaseKey([Microsoft.Win32.RegistryHive]::LocalMachine, [System.Net.Dns]::GetHostEntry([System.Net.Dns]::GetHostName()).Hostname) If you're running a windows firewall, make sure you have an exception for Remote Administration selected.

Hi Roman,yes, i am doin a local install of exchange 2007 SP1. Remote registry is running and I can access to the server trouh remote desktop (i am doing the setup trough remote desktop).Windows firewall is not running, but the same error ocurrs.When i execute the command in powershell the error is: Exception calling "OpenRemoteBaseKey" with "2" argument(s): "The network path was not found.At line:1 char:49+ [Microsoft.Win32.RegistryKey]:penRemoteBaseKey( <<<< [Microsoft.Win32.RegistryHive]::LocalMachine, [System.Net.Dns]::GetHostEntry([System.Net.Dns]::GetHostName()).Hostname)

What's the error returned by [System.Net.Dns]::GetHostEntry([System.Net.Dns]::GetHostName()).Hostname GetHostName should extract the hostname of your box (NetBIOS) and then GetHostEntry, based on your primary and additional suffixes, should resolve the machine's FQDN. Do both methods succeed?

Hi Roman,[System.Net.Dns]::GetHostName() returns server01[System.Net.Dns]::GetHostEntry([System.Net.Dns]::GetHostName()).Hostname returns server01.server01.mydomain.comWhen i installes Active Directory I choose like full DNS name for new domain "server01.mydomain.com", and the name of the computer was server01When I ping server01.server01.mydomain.com from the server i receive a correct answer.Thanks for your help!

is this box a domain controller?

Also, can you run get-service | select Name,Status | sort Status I'll compare with my vanilla box that I have installed Exchange 2007 successfully. Have you tried SP1 btw?

I had the same problem and got mine fixed. The remote registry was running and the proper checks in the nic properties. I changed the order of the nics in network connections/advanced/advanced settings/ then in the orderI put the external network card on top. It installed no problem.

yes, its a domain controller.The version I am trying to install is exchange 2007 SP1Change binding order didnt fix the problem.command result:Name Status---- ------ReportServer StoppedRpcLocator StoppedRDSessMgr StoppedRemoteAccess StoppedRSoPProv StoppedSNMPTRAP StoppedSpooler Stoppedsacsvr StoppedSCardSvr StoppedRasAuto StoppedMSSQLSERVER StoppedMSSQLServerADHelper Stoppedmsftesql StoppedMSIServer StoppedNetDDE StoppedNtmsSvc Stoppedxmlprov StoppedNetDDEdsdm StoppedNtLmSsp Stoppedvds StoppedVSS StoppedUMWdf StoppedUPS StoppedWebClient StoppedWmi StoppedWmiApSrv StoppedWinHttpAutoProxySvc StoppedWmdmPmSN StoppedTssdis Stoppedstisvc Stoppedswprv StoppedSQLBrowser StoppedSQLSERVERAGENT StoppedSysmonLog StoppedTrkSvr StoppedTrkWks StoppedThemes StoppedTlntSvr Stoppedmnmsrvc StoppedCOMSysApp StoppedImapiService StoppedDhcp Stoppedaspnet_state StoppedClipSrv Stoppedclr_optimization_v2.0.50727_32 StoppedIDriverT StoppedBrowser StoppedLmHosts StoppedLicenseService StoppedAppMgmt StoppedMessenger Stoppeddmadmin StoppedAlerter Stoppedose StoppedDNS RunningSNMP RunningSQLWriter RunningCryptSvc RunningDfs Runningdmserver RunningDcomLaunch RunningTermService RunningTapiSrv RunningAeLookupSvc Runningwinmgmt RunningALG RunningAdaptecStorageManagerAgent RunningWZCSVC Runningwuauserv RunningAudioSrv RunningBITS RunningCiSvc RunningWinDefend RunningW3SVC RunningW32Time RunningIISADMIN RunningPersits Software EmailAgent RunningNtFrs RunningIsmServ RunningProtectedStorage RunningRasMan RunningPlugPlay RunningPolicyAgent Runninglanmanworkstation Runninglanmanserver RunningMSDTC RunningMSFtpsvc RunningNetman RunningNla Runningkdc RunningNetlogon RunningSchedule Runningseclogon RunningSamSs RunningDnscache RunningShellHWDetection RunningSimpTcp RunningSENS RunningSharedAccess RunningRemoteRegistry Runninghelpsvc RunningHTTPFilter RunningHidServ RunningEventlog RunningERSvc RunningEventSystem RunningRpcSs Running

Carlos, I am still not seeing anything that sparks my eye. I've ran [Microsoft.Win32.RegistryKey]:penRemoteBaseKey( [Microsoft.Win32.RegistryHive]::LocalMachine,"dc1.mydomain.com") and it returns successfully. Can you connect to remote registry using regedit from another box, or even using "connect to remote registry" on the same box?

Hi Roman,at least I've found the problem. The service "TCP/IP netbios helper" must to be enabled and running.i appreciate your help!greetings,Carlos

Thank you for that reply! Changing the order worked for me.

I had the same issue, and starting both Server and Workstation services solved the problem ... So you can try this too.But be careful to security issues after doing this ... The server workstation opens backdoors by activating anonymous file sharing ...

My Remote Registry service was disabled so I couldn't uninstall my Exchange 2007. Enabling the service did the trick. Why didn't I think of that in the first place!WC