asked on

Error during Exchange 2013 install

I am adding the first Exchange 2013 to and Exchange 2007 infrastructure and I an getting an error in Step 8"

Step 8 of 15 Mailbox Role: Transport Service

Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;

while($currTime -le $timeout)
{
$setSharedCDCErrors = @();
try
{
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

if($successfullySetConfigDC)
{
break;
}
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
}
catch
{
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
}

Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
}

if( -not $successfullySetConfigDC)
{
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
}
" was run: "System.Exception: Unable to set shared config DC.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Will Szymkowski

What do the logs say? Also have you checked the event viewer as well? Were you able to perform the schema update properly? Have you checked ADSIEdit.msc to ensure that the schema object for Exchange 2013 have been updated?

Check Schema Version

Will.

nourben

ASKER

Schema and AD prep were successful

I see this in the event logs

Log Name: Application
Source: MSExchangeADTopology
Date: 4/18/2015 4:30:29 PM
Event ID: 2142
Task Category: Topology
Level: Error
Keywords: Classic
User: N/A
Computer: Exch13server.domain.com
Description:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=1936) Forest domain.com. Topology discovery failed, error details
No Minimal Required Number of Suitable Directory Servers Found in Forest domain.com Site Default-First-Site-Name and connected Sites..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeADTopology" />
<EventID Qualifiers="49156">2142</EventID>
<Level>2</Level>
<Task>3</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-18T20:30:29.000000000Z" />
<EventRecordID>103910</EventRecordID>
<Channel>Application</Channel>
<Computer>Exch13server.domain.com</Computer>
<Security />
</System>
<EventData>
<Data>Microsoft.Exchange.Directory.TopologyService.exe</Data>
<Data>1936</Data>
<Data>domain.com</Data>
<Data>No Minimal Required Number of Suitable Directory Servers Found in Forest domain.com Site Default-First-Site-Name and connected Sites.</Data>
</EventData>
</Event>

nourben

ASKER

And this

Log Name: Application
Source: MSExchange ADAccess
Date: 4/18/2015 4:30:29 PM
Event ID: 4027
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: Exch13server.domain.com
Description:
Process ExSetupUI.exe (PID=5184). WCF request (Set Config DC domain.com) to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost)) failed. Make sure that the service is running. In addition, make sure that the network ports that are used by Microsoft Exchange Active Directory Topology service are not blocked by a firewall. The WCF call was retried 3 time(s). Error Details
No Minimal Required Number of Suitable Directory Servers Found in Forest domain.com Site Default-First-Site-Name and connected Sites.
at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.Discover()
at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.DoWork(CancellationToken cancellationToken)
at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.Execute(CancellationToken joinedToken)
at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.<>c__DisplayClass6.<StartExecuting>b__4()
at System.Threading.Tasks.Task.Execute()
at Microsoft.Exchange.Directory.TopologyService.TopologyDiscoveryManager.EndGetTopology(IAsyncResult ar)
at Microsoft.Exchange.Directory.TopologyService.TopologyService.InternalEndSetConfigDC(IAsyncResult result)
at Microsoft.Exchange.Directory.TopologyService.TopologyService.ExecuteServiceCall(Action action)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange ADAccess" />
<EventID Qualifiers="49156">4027</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-04-18T20:30:29.000000000Z" />
<EventRecordID>103911</EventRecordID>
<Channel>Application</Channel>
<Computer>Exch13server.domain.com</Computer>
<Security />
</System>
<EventData>
<Data>ExSetupUI.exe</Data>
<Data>5184</Data>
<Data>Set Config DC domain.com</Data>
<Data>TopologyClientTcpEndpoint (localhost)</Data>
<Data>3</Data>
<Data>No Minimal Required Number of Suitable Directory Servers Found in Forest domain.com Site Default-First-Site-Name and connected Sites.
at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.Discover()
at Microsoft.Exchange.Directory.TopologyService.ADTopologyDiscovery.DoWork(CancellationToken cancellationToken)
at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.Execute(CancellationToken joinedToken)
at Microsoft.Exchange.Directory.TopologyService.Common.WorkItem`1.<>c__DisplayClass6.<StartExecuting>b__4()
at System.Threading.Tasks.Task.Execute()
at Microsoft.Exchange.Directory.TopologyService.TopologyDiscoveryManager.EndGetTopology(IAsyncResult ar)
at Microsoft.Exchange.Directory.TopologyService.TopologyService.InternalEndSetConfigDC(IAsyncResult result)
at Microsoft.Exchange.Directory.TopologyService.TopologyService.ExecuteServiceCall(Action action)</Data>
</EventData>
</Event>

nourben

ASKER

Domain Controllers are Windows 2003 R2 64bit

ASKER CERTIFIED SOLUTION

K B

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

nourben

ASKER

Checked IPv6 back on
Installing on a separate server
DNS is set properly
2 NICs, just disabled the non used one
Tried again, still faling

K B

Are you using HOSTS files for some reason?
How many domains in this forest?
Did you have a Domain Controller die on you that you didn't have an opportunity to properly demote?
Move server to an empty OU and block inheritance of all Group Policies then run GPUPDATE /FORCE
Turn off UAC for now.
Reboot
From elevated command prompt on new exchange server run
- NSLOOKUP newexchangeservername.domain.com (correct IP?)
- set L which DC are you authenticating to (LOGONSERVER)?
- Telnet to the resulting DC (LOGONSERVER) on port 389 and 53 to make sure you can access LDAP and DNS
(set your primary DNS to LOGONSERVER on what will be new exchange server)
- Run nltest /dsgetsite
- Run nltest /dclist

what happens when you run this on your DC?
Elevated CMD prompt
Repadmin /syncall /APedq
any errors?

http://prajwaldesai.com/how-to-install-exchange-server-2013/

K B

make sure your binding order has the main NIC at the top.

Is Exchange 2007 patched SP3 all rollups?
make sure that you give your enterprise/domain admin account all Exchange administrator rights too.

Sudhir Bidye

verify if no ad replication errors exists in your environment. also check if timesync between your dc's and new exchange server is fine.