Cannot Install Exchange 2013 on Windows 2012 DC Server!?

Hi,

when i try to install my Exchange 2013 on a Windows 2012 Server i become the following error at the Transport Service Tab:

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: "Unable to set shared config DC.".



  • Edited by gizmoxxx Sunday, October 28, 2012 6:28 PM
October 28th, 2012 9:24pm

Is the server a domain member?

Free Windows Admin Tool Kit Click here and download it now
October 28th, 2012 10:43pm

Yes, it is the DC :) I try to install it on a DC
October 29th, 2012 12:50am

It is against best practice to install Exchange on a DC.
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2012 2:15am

i know that, but i need to do some tests. so i need the exchange on the DC.


  • Edited by gizmoxxx Monday, October 29, 2012 7:21 AM
October 29th, 2012 10:21am

I get exactly the same error, but I try to install Exchange 2013 on a member server (Windows Server 2012), not a domain controller.

So the DC does not seem to be the problem...

Free Windows Admin Tool Kit Click here and download it now
October 29th, 2012 3:52pm

I did this too in the Preview environment and it worked just fine.

Based on those log entries, a few things to check:

  • I'm assuming you're logged in as the domain Administrator account right? If not, make sure the account has the necessary permissions to perform the install.
  • Check Services MMC and make sure everything set to Automatic is Started.
  • One thing I've noticed is that the Network adapter when you perform a Status does not show a DNS server, even though in the primary DNS properties it has 127.0.0.1. Try changing this to the ACTUAL IP address of the server.

With these in place, give it another whirl and see what happens!

October 29th, 2012 7:13pm

This happened to me....

Did you turn off IPv6 on the network adaptor?

If so, turn it back on and run setup again - worked for me....

  • Proposed as answer by Jetze Mellema Monday, November 12, 2012 8:43 AM
  • Marked as answer by gizmoxxx Monday, November 12, 2012 2:33 PM
Free Windows Admin Tool Kit Click here and download it now
October 29th, 2012 7:42pm

This happened to me....

Did you turn off IPv6 on the network adaptor?

If so, turn it back on and run setup again - worked for me....

Yes, i tuned Off IPV6 on the Server, i will try it again with ipv6 tuned on....
October 29th, 2012 8:27pm

Hello,

This issue can occur when:

Problem with DC, might DNS misconfigure.

Permission, check that you have the correct permission.

Install the CAS first then Mailbox.

Eli.

Free Windows Admin Tool Kit Click here and download it now
October 29th, 2012 11:06pm

Also make sure you have all the prerequisites installed correctly.
October 30th, 2012 2:23am

Yes, i tuned Off IPV6 on the Server, i will try it again with ipv6 tuned on....

Hi gizmoxxx,

Any updates?

Also as Technet said:

Exchange servers fully support IPv6 networks. Therefore, even if you aren't using IPv6, you don't need to disable IPv6 on your Exchange servers

IPv6 Support in Exchange 2013

http://technet.microsoft.com/en-us/library/gg144561(v=exchg.150).aspx

Free Windows Admin Tool Kit Click here and download it now
October 30th, 2012 9:55am

Hi,

after that i become the following error:

10.29.2012 00:49:27.0196] [1] [WARNING] An unexpected error has occurred and a Watson dump is being generated: The following error was generated when "$error.Clear(); 
            if ($RoleProductPlatform -eq "amd64")
            {
                $useAttachMode = $false;
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                $dataFolderPath = $fastDefaultDataFolderPath;
                
                if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                {
                    $useAttachMode = $true;
                }
                else
                {
                    if ($RoleIsDatacenter -eq $true)
                    {
                        $preferredDataFolderPathRoot = "D:\";
                        if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                        {
                            $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                            {
                                $useAttachMode = $true;
                            }
                        }
                    }
                }
                
                if ($useAttachMode -eq $true)
                {
                    &$command -action a -dataFolder $dataFolderPath -silent;
                }
                else
                {
                    try
                    {   
                        &$command -action i -dataFolder $dataFolderPath -silent;
                    }
                    catch
                    {
                        $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $errorMsg;
                        &$command -action u -silent;
                        try
                        {
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                            {
                                [System.IO.Directory]::Delete($dataFolderPath, $true);
                            }
                        }
                        catch
                        {
                            $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath + " - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $deleteErrorMsg;
                        }
                    }
                }
            }
        " was run: "Couldnt attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnt contain old nodes belonging to the system 'Fsis'.".
[10.29.2012 00:49:27.0196] [1] [ERROR] The following error was generated when "$error.Clear(); 
            if ($RoleProductPlatform -eq "amd64")
            {
                $useAttachMode = $false;
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                $dataFolderPath = $fastDefaultDataFolderPath;
                
                if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
                {
                    $useAttachMode = $true;
                }
                else
                {
                    if ($RoleIsDatacenter -eq $true)
                    {
                        $preferredDataFolderPathRoot = "D:\";
                        if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))
                        {
                            $dataFolderPath = Join-Path -Path $preferredDataFolderPathRoot -ChildPath "ExchangeSearchData";
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                            {
                                $useAttachMode = $true;
                            }
                        }
                    }
                }
                
                if ($useAttachMode -eq $true)
                {
                    &$command -action a -dataFolder $dataFolderPath -silent;
                }
                else
                {
                    try
                    {   
                        &$command -action i -dataFolder $dataFolderPath -silent;
                    }
                    catch
                    {
                        $errorMsg = "Failure running SearchFoundation installconfig.ps1 - " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $errorMsg;
                        &$command -action u -silent;
                        try
                        {
                            if ([System.IO.Directory]::Exists($dataFolderPath))
                            {
                                [System.IO.Directory]::Delete($dataFolderPath, $true);
                            }
                        }
                        catch
                        {
                            $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath + " - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $deleteErrorMsg;
                        }
                    }
                }
            }
        " was run: "Couldnt attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnt contain old nodes belonging to the system 'Fsis'.".
[10.29.2012 00:49:27.0196] [1] [ERROR] Couldnt attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnt contain old nodes belonging to the system 'Fsis'.
[10.29.2012 07:22:19.0920] [0] End of Setup
[10.29.2012 07:22:19.0920] [0] **********************************************

October 30th, 2012 11:04am

Based on the error:

                           $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath + " - " + $_.Exception.Message;
                            Write-ExchangeSetupLog -Error $deleteErrorMsg;
                        }
                    }
                }
            }
        " was run: "Couldnt attach the data folder 'C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data'. Path doesnt contain old nodes belonging to the system 'Fsis'.".

It looks like setup is getting further than before but because you've doing a reinstall there's problems with your environment. You're going to have to remove Exchange 2013, do some cleanup, and try again.

I spent the whole past weekend doing just that, even saw the same error.

I've thrown a post up on my site:

http://memphistech.net/?p=264

Down at the bottom under Uninstall and Cleanup, it shows what objects to remove after the Uninstall.

Good luck!


  • Edited by thetootall Tuesday, October 30, 2012 9:19 PM
  • Marked as answer by gizmoxxx Monday, November 05, 2012 1:11 PM
Free Windows Admin Tool Kit Click here and download it now
October 31st, 2012 12:17am

This happened to me....

Did you turn off IPv6 on the network adaptor?

If so, turn it back on and run setup again - worked for me....

Thanks, this was the solution for me!
  • Marked as answer by gizmoxxx Monday, November 12, 2012 2:33 PM
November 10th, 2012 8:50pm

This happened to me....

Did you turn off IPv6 on the network adaptor?

If so, turn it back on and run setup again - worked for me....

Thanks, this was the solution for me!

yes, it appears this helped the OP also....

Unfortunately, he has marked another post as the solution, which is actually a solution to a subsequent problem...

This is going to confuse other people coming to this thread looking a the first couple of posts....

  • Marked as answer by gizmoxxx Monday, November 12, 2012 2:33 PM
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2012 11:25am

Enable IPv6 in your default adapter properties...
November 19th, 2012 3:44pm

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: "Unable to set shared config DC.".

Free Windows Admin Tool Kit Click here and download it now
January 29th, 2013 3:49pm

Hi, remember that enabling IPV6 checkbox from the Network Properties is not all, this can help you... 

http://support.microsoft.com/kb/929852

Greating!


April 29th, 2013 8:26pm

Thanks..indeed it worked..but it's not working while IPV6 is disabled..any idea..

Free Windows Admin Tool Kit Click here and download it now
April 20th, 2014 8:58pm

This happened to me....

Did you turn off IPv6 on the network adaptor?

If so, turn it back on and run setup again - worked for me....

Thanks, this was the solution for me!
This did not help me... IPv6 was already on.
July 20th, 2014 10:21pm

this not worked for me, and I'm not installing on DC. installing on another server.
Free Windows Admin Tool Kit Click here and download it now
February 17th, 2015 6:09am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics