I'm attempting to install Beta2 Exchange 2007 and am having some significant problems that I'm hoping someone here can help with. The server I'm using is an ASUS+OPTERON based white-box with a 240GB SATA RAID 5 array for the store, a 20GB PATA drive for the OS and 4GB of RAM. I have installed (for testing purposes) Windows 2003 Server with all service packs and updates. The entire installation was a bare-metal build-out. I will deploy Server 2003 x64 when our copy arrives (it's in transit atm) and plan to later deploy Longhorn server when that configuration is supported by the beta. Currently I have built the machine and fully installed the OS including updates. I have installed the MMC 3.0 and the latest Monad shell as instructed by the installation documentation. The next phase is where my errors occur. While attempting to run "SETUP /PrepareAD", the process (after copying files) aborts with the message, "Exchange Server Setup Encountered an error." Checking the Application log in Event Viewer reveals: Event ID: 2152 (Source: MSExchangeADAccess; Category: Devices)The description for Event ID ( 2152 ) in Source ( MSExchangeADAccess ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ExSetup.exe, 2280, 1753, Error 6d9 from HrGetServersForRole. Event ID: 4999 (Source: MS Exchange Common; Category: Devices)The description for Event ID ( 4999 ) in Source ( MSExchange Common ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 2280, E12, RTL-x86, 08.00.0605.015, ExSetup, M.E.S.Common, M.E.S.C.OrganizationName.Initialize, System.FormatException, 273d, 08.00.0605.016. Event ID: 5000 (Source: Microsoft Exchange Server; Category: None)The description for Event ID ( 5000 ) in Source ( Microsoft Exchange Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: e12, rtl-x86, 08.00.0605.015, exsetup, m.e.s.common, m.e.s.c.organizationname.initialize, system.formatexception, 273d, 08.00.0605.016, NIL, NIL. I can't go anywhere until I figure this out, any help would be appreciated! Brett D. Leuszler MCSE

Hi,I haven't seen the errors you mention so the following questions are on general principles grounds.I assume you configured Active Directory successfully on the machine before starting Exchange 2007 install? Were there any indications of problems?Are you able to use the AD GUI tools as you would expect?BTW which role(s) were you attempting to install? Were you using the basic or custom install options?Andrew Watt MVP

The machine is not a DC. I was told that it was inadvisable to have Exchange on a DC. The computer JOINED the domain just fine though. I am planning to deploy all roles except the edge on this server, but this is like the very first step for installation (preparing Active Directory). We have not used MSExchange in our enterprise to this point, so it is a ground-up installation and I'm stuck at Step #1: "SETUP /PrepareAD". :( -Brett

Can you take a look at %systemroot%\ExchangeSetupLogs\ExchangeSetup.log and see if you spot anything there? Look for ERROR lines. Thanks, ~vivek

Turns out, the folder is located in "C:\", despite %systemroot% being "C:\Windows". In any event, here is the content of the log (from the most recent attempt, all previous attempts are also logged, but they match this one verbatim, so I'm saving space by just posting the last): [26/07/2006 11:12:26 AM] [0] **********************************************[26/07/2006 11:12:26 AM] [0] Starting Microsoft Exchange 2007 Setup[26/07/2006 11:12:26 AM] [0] **********************************************[26/07/2006 11:12:26 AM] [0] Setup version: 08.00.0605.016.[26/07/2006 11:12:27 AM] [0] Command Line Parameter Name='nologo', Value='null'.[26/07/2006 11:12:27 AM] [0] Command Line Parameter Name='preparead', Value='null'.[26/07/2006 11:12:27 AM] [0] Command Line Parameter Name='sourcedir', Value='D:\Build Files\Exchange2007\Install Files'.[26/07/2006 11:12:27 AM] [0] Command Line Parameter Name='fromsetup', Value='null'.[26/07/2006 11:12:27 AM] [0] ExSetup was started with the following command line: '/NoLogo /preparead /sourcedir:D:\Build Files\Exchange2007\Install Files /FromSetup'.[26/07/2006 11:12:29 AM] [0] Setup is choosing the domain controller to talk to[26/07/2006 11:12:30 AM] [0] Setup is picking a local domain controller...[26/07/2006 11:12:30 AM] [0] Setup has chosen the local domain controller lml5.lac-mac.com for initial queries[26/07/2006 11:12:30 AM] [0] ForestPrep has either not been run, or has not replicated to this domain controller; setup will try the schema master domain controller lml5.lac-mac.com[26/07/2006 11:12:30 AM] [0] The schema master domain controller is available[26/07/2006 11:12:30 AM] [0] The schema master domain controller is in the local domain; so setup will use lml5.lac-mac.com[26/07/2006 11:12:30 AM] [0] Setup is choosing a Global Catalog...[26/07/2006 11:12:30 AM] [0] Setup has chosen the Global Catalog Server lml5.lac-mac.com.[26/07/2006 11:12:30 AM] [0] Setup will use the domain controller 'lml5.lac-mac.com'.[26/07/2006 11:12:30 AM] [0] Setup will use the global catalog 'lml5.lac-mac.com'.[26/07/2006 11:12:30 AM] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lac-mac,DC=com'.[26/07/2006 11:12:30 AM] [0] Exchange organization container for the organization is 'CN={335A1087-5131-4D45-BE3E-3C6C7F76F5EC},CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lac-mac,DC=com'. AFAIK there's no "Error" lines indicated... Thanks to everyone for helping out here! -Brett

So I assume that this issue is dead in the water then? -Brett

Did you run prepareAD (and possible wait for replication if its a large / slow topology) before running setup again? Thanks, ~vivek

I have completely flattened the server, then I installed Server 2003 R2 x64 followed by all service packs and updates. I have joined the domain and I have installed IIS. Monad and MMC have both been installed. The next step is to run "setup /PrepareAD". The following is the result: D:\Build Files\64-bit>setup.com /PrepareAD Welcome to Microsoft Exchange Server 2007 Unattended Setup Preparing Exchange Setup Copying Setup Files ......................... COMPLETED Exchange Server setup encountered an error. D:\Build Files\64-bit> Here is the resulting "ExchangeSetup.log" file (located in "C:\ExchangeSetupLogs\"): [01/08/2006 4:46:45 PM] [0] **********************************************[01/08/2006 4:46:45 PM] [0] Starting Microsoft Exchange 2007 Setup[01/08/2006 4:46:45 PM] [0] **********************************************[01/08/2006 4:46:45 PM] [0] Setup version: 08.00.0605.016.[01/08/2006 4:46:45 PM] [0] Command Line Parameter Name='nologo', Value='null'.[01/08/2006 4:46:45 PM] [0] Command Line Parameter Name='preparead', Value='null'.[01/08/2006 4:46:45 PM] [0] Command Line Parameter Name='sourcedir', Value='D:\Build Files\64-bit'.[01/08/2006 4:46:45 PM] [0] Command Line Parameter Name='fromsetup', Value='null'.[01/08/2006 4:46:45 PM] [0] ExSetup was started with the following command line: '/NoLogo /PrepareAD /sourcedir:D:\Build Files\64-bit /FromSetup'.[01/08/2006 4:46:49 PM] [0] Setup is choosing the domain controller to talk to[01/08/2006 4:46:51 PM] [0] Setup is picking a local domain controller...[01/08/2006 4:46:52 PM] [0] Setup has chosen the local domain controller lml5.lac-mac.com for initial queries[01/08/2006 4:46:53 PM] [0] ForestPrep has either not been run, or has not replicated to this domain controller; setup will try the schema master domain controller lml5.lac-mac.com[01/08/2006 4:46:53 PM] [0] The schema master domain controller is available[01/08/2006 4:46:53 PM] [0] The schema master domain controller is in the local domain; so setup will use lml5.lac-mac.com[01/08/2006 4:46:53 PM] [0] Setup is choosing a Global Catalog...[01/08/2006 4:46:53 PM] [0] Setup has chosen the Global Catalog Server lml5.lac-mac.com.[01/08/2006 4:46:53 PM] [0] Setup will use the domain controller 'lml5.lac-mac.com'.[01/08/2006 4:46:53 PM] [0] Setup will use the global catalog 'lml5.lac-mac.com'.[01/08/2006 4:46:53 PM] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lac-mac,DC=com'.[01/08/2006 4:46:53 PM] [0] Exchange organization container for the organization is 'CN={335A1087-5131-4D45-BE3E-3C6C7F76F5EC},CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=lac-mac,DC=com'. We have only 2 DC's, and the other one (not LML5) is located at a remote site. In Active Directory Users and Computers, when connected to LML5, there is no new information visible. This remains true even a day after the install. It does not appear that setup is actually doing ANYTHING to AD before it dies, and despite the message, "Exchange Server Setup Encountered an Error", no error seems apparent in the SetupLog. The following three entries also appear in the Application Event Log on the server (3 seconds apart, starting at 4:46:50pm): Error Type: Error / EventID: 2152 / Source: MSExchangeADAccess / Category: Devices / Description: The description for Event ID ( 2152 ) in Source ( MSExchangeADAccess ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ExSetup.exe, 2168, 1753, Error 6d9 from HrGetServersForRole. Error Type: Error / EventID: 4999 / Source: MSExchangeCommon / Category: Devices / Description: The description for Event ID ( 4999 ) in Source ( MSExchange Common ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 2168, E12, RTL-AMD64, 08.00.0605.015, ExSetup, M.E.S.Common, M.E.S.C.OrganizationName.Initialize, System.FormatException, 8a25, 08.00.0605.016. Error Type: Error / EventID: 5000 / Source: Microsoft Exchange Server / Category: None / Description: The description for Event ID ( 5000 ) in Source ( Microsoft Exchange Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: e12, rtl-amd64, 08.00.0605.015, exsetup, m.e.s.common, m.e.s.c.organizationname.initialize, system.formatexception, 8a25, 08.00.0605.016, NIL, NIL. From the timestamps of the Event log, these errors occurred during the time covered by the SetupLog, but were not reported there for whatever reason. This is a complete summary of where I am currently with this problem. -Brett

Thanks Brett. I've sent this issuealong to some folks internally to look at. Can you please open a connect bug for this please? Thanks, ~vivek

From the gurus. Its probably a DNS issue. He needs to make sure he can contact a DC and GC and the machine knows what AD site it is in. He can do this by running DCDiag and NETDiag. If this does not seem to do it, please open a connect issue (or open one anyway to help us improve this case). Thanks,~vivek

A couple of points: First: From the "ExchangeSetupLogs" file above: [01/08/2006 4:46:52 PM] [0] Setup has chosen the local domain controller lml5.lac-mac.com for initial queries[01/08/2006 4:46:53 PM] [0] ForestPrep has either not been run, or has not replicated to this domain controller; setup will try the schema master domain controller lml5.lac-mac.com[01/08/2006 4:46:53 PM] [0] The schema master domain controller is available[01/08/2006 4:46:53 PM] [0] The schema master domain controller is in the local domain; so setup will use lml5.lac-mac.com[01/08/2006 4:46:53 PM] [0] Setup is choosing a Global Catalog...[01/08/2006 4:46:53 PM] [0] Setup has chosen the Global Catalog Server lml5.lac-mac.com.[01/08/2006 4:46:53 PM] [0] Setup will use the domain controller 'lml5.lac-mac.com'.[01/08/2006 4:46:53 PM] [0] Setup will use the global catalog 'lml5.lac-mac.com'. Since LML5 is the correct server for all functions indicated (Global Catalog, PDCe, Schema Master etc), and since it obviouslyfound LML5 for each of these roles, in what regard is a DNS failure indicated? (FYI: LML5 is also our main DNS server and is the DNS server specified on the Exchange machine for DNS queries). The logs seem to indicate that the Exchange server can contact it's GC and a (the) DC just fine... Second: How do I "open a connect issue"? (pls be kind, I'm new to this system!) Thanks! -Brett

Brett, can you attach the crash dumps if they are available? They should be in the %systemdrive%\Dumps directory. You can file issues using http://connect.microsoft.com, I believe you just sign on with the same account that you used to register for the beta.

What about an ADsite, though? Have you defined AD Sites in the AD Sites & Services console and attached IP subnets to those sites? Remember that Exchange 2007 is dependant upon the AD Routing topology (no more Exchange Routing Groups), so you really have to make sure that your AD is set up properly.

Just a thought having had a similar problem....Run the BPA directly off the install media (needs .NET FW V2) either from the server or from the DC and just run a basic Health Check scan and check the Information Items. It gives a great starting point before you install anything. I got in this situation after running everthing manually and got a bit further, but it appears to be related to a de-installafter the first serverinstall went wrong and the remove seemed to take outthe Exchange Groups etc ..but not the Org record. I am going to do some more on thisnext week and try and get some decent logs to send in.

I think i am in the same boat, finds the GC fine in the earlygoing, then punks out during the test-setupHealth process,here are my logs: Starting Microsoft Exchange 2007 Setup**********************************************Setup version: 08.00.0605.016.Command Line Parameter Name='mode', Value='Install'.Command Line Parameter Name='sourcedir', Value='e:\'.Command Line Parameter Name='fromsetup', Value='null'.Setup is choosing the domain controller to talk toSetup is picking a local domain controller...Setup has chosen the local domain controller SBROGAN-NGITW2K3T42.welcome2Exch2007.com for initial queriesForestPrep has either not been run, or has not replicated to this domain controller; setup will try the schema master domain controller SBROGAN-NGITW2K3T42.welcome2Exch2007.comThe schema master domain controller is availableThe schema master domain controller is in the local domain; so setup will use SBROGAN-NGITW2K3T42.welcome2Exch2007.comSetup is choosing a Global Catalog...Setup has chosen the Global Catalog Server SBROGAN-NGITW2K3T42.welcome2Exch2007.com.Setup will use the domain controller 'SBROGAN-NGITW2K3T42.welcome2Exch2007.com'.Setup will use the global catalog 'SBROGAN-NGITW2K3T42.welcome2Exch2007.com'.No exchange configuration container was found for the organization. Message: 'Could not find the Exchange Configuration Container.'.The following roles are unpacked: The following roles are installed: The local server does not have any Exchange Binaries installed.Exchange Organization name is required for this modeSetup will use the path 'e:\' for installing the product.The server's cluster type: 'None'.The requested cluster type: 'None'.The installation mode is set to: 'Install'.AD Initialization status : 'True'.Schema Update Required Status : 'True'.Organization Configuration Update Required Status : 'True'.Domain Configuration Update Required Status : 'True'.Applying default role selection stateSetup is determining what org-level operations to perform.Because setup has detected that it is required, setup is adding the argument PrepareLegacyExchangePermissions.Because setup has detected that it is required, setup is adding the argument PrepareSchema.Because setup has detected that it is required, setup is adding the argument PrepareOrganization.Because setup has detected that it is required, setup is adding the argument PrepareDomain.Setup will run from path 'C:\WINDOWS\Temp\ExchangeSetup'.InstallModeDataHandler has 3 DataHandlersSetup is determining what org-level operations to perform.Because setup has detected that it is required, setup is adding the argument PrepareLegacyExchangePermissions.Because setup has detected that it is required, setup is adding the argument PrepareSchema.Because setup has detected that it is required, setup is adding the argument PrepareOrganization.Because setup has detected that it is required, setup is adding the argument PrepareDomain.Setup will run from path 'C:\WINDOWS\Temp\ExchangeSetup'.InstallModeDataHandler has 4 DataHandlersSetup is determining what org-level operations to perform.Because setup has detected that it is required, setup is adding the argument PrepareLegacyExchangePermissions.Because setup has detected that it is required, setup is adding the argument PrepareSchema.Because setup has detected that it is required, setup is adding the argument PrepareOrganization.Because setup has detected that it is required, setup is adding the argument PrepareDomain.Setup will run from path 'C:\WINDOWS\Temp\ExchangeSetup'.InstallModeDataHandler has 5 DataHandlersValidating options for the 0 requested rolesValidating options for the 0 requested rolesSetup is determining what org-level operations to perform.Because setup has detected that it is required, setup is adding the argument PrepareLegacyExchangePermissions.Because setup has detected that it is required, setup is adding the argument PrepareSchema.Because setup has detected that it is required, setup is adding the argument PrepareOrganization.Because setup has detected that it is required, setup is adding the argument PrepareDomain.Because the value was specified, setup is setting the argument OrganizationName to the value E2K7.**************Setup will run the task 'test-setuphealth'Setup launched task 'test-setuphealth -DomainController:'SBROGAN-NGITW2K3T42.welcome2Exch2007.com' -DownloadConfigurationUpdates:$true -ExchangeVersion:'8.0.605.16' -Roles:'Global' -ScanType:'PrecheckInstall' -SetupRoles:'Global' -PrepareDomain:$null -PrepareLegacyExchangePermissions:$true -PrepareOrganization:$true -PrepareSchema:$true' Beginning the task's processing.Executing command ''.Processing one object in the task.Ending the task's processing.Setup will run the task 'test-setuphealth'Setup launched task 'test-setuphealth -DomainController:'SBROGAN-NGITW2K3T42.welcome2Exch2007.com' -DownloadConfigurationUpdates:$false -ExchangeVersion:'8.0.605.16' -Roles:'Bridgehead' -ScanType:'PrecheckInstall' -SetupRoles:'AdminTools','Bridgehead','ClientAccess','Mailbox' -TargetDir:'C:\Program Files\Microsoft\Exchange Server'' Beginning the task's processing.Executing command ''.Processing one object in the task.[ERROR] There is no Global Catalog in the domain in which you are trying to install the Exchange Server[WARNING] The 32-bit version of Exchange Server 2007 is not supported for production use.Ending the task's processing.

Whensetup.exe exited suddenlyI had to cleanup left over registry keys for exchange, and then use CLI insteadSetup.com /mode:Install /roles:Mailbox /on:org1It then worked.

Hi ! hope this works around ! make sure that the user account responsible for installing Exchange server 2007is a member of schema Admins and whether schema is registered or not in the DC if not then register it "register schema in the actual DC (in the run dialog box type "regsvr32 schmmgmt.dll") " check whether "Remote registry" service (services.msc in run dialog box) is started in the DC, if not then start but letthe startup typebe manual further if "nslookup " command works fine then stop the dns service (net stop dns) and then startit again(net start dns) after the above proc. get in the "gpupdate" command in the run dialog box and try to install the exchange 2007 now. Please revert with latest jitendra

Hi; We encounter error in Event Viewer after run the setup.com /PrepareAD Event ID 2152 MSExchangeADAcess Catogery: Devices The local computer may not have the necessary registry information ro message DLL files to display messages from a remotecomputer. You may be able to use the /AUXSOURCE=flag to retrieve this description; see Help and support for details. The following information is part of the event: ExSetupUI.exe, 3656, 1753, Error 6d9 from HrGetServersForRole. Does it relate to AD or what? We have run dcdiag and netdiag and all the test is passed. Can someone advised us on this issue and is there any KB link to reslove this issue.....

I had this same problem too. I got around it by running the setup.com /prepareschema and setup.com /preparead on the DC itself rather than on the machine where I was trying to install Exchange 2007. Don't know what the problem was since I could connect to AD fine from that machine, but once I ran the prepares directly on the DC then the install proceeded like it should have originally on the destination Exchange 2007 server. Anyway, this threat looks a bit old, but thought I would post this in case it could help somebody else.

Where can I find a fix for the Event ID posted below?Date: 12/23/2008Time: 8:37:32 AMType: ErrorSource: MSExchange CommonCategory: GeneralEvent ID: 4999Description:Watson report about to be sent to dw20.exe for process id: 7212, with parameters: E12, c-RTL-AMD64, 08.01.0336.000, M.E.Imap4, M.E.D.Common, M.E.D.G.OutboundCodePageDetector.AddText, System.ArgumentNullException, 5ca, 08.01.0336.000. ErrorReportingEnabled: True