DC Restart when start installing Exchange 2013 CU6

I have a domain installed on windows server 2012 R2 with function level 2008 R2 and when i try to install "as a administrator" Update for exchange 2013 CU6 or CU5 DC restart and am facing this error :
Error:
The following error was generated when "$error.Clear();
install-CannedAddressLists -DomainController $RoleDomainController
" was run: "Microsoft.Exchange.Data.Directory.ADTransientException: Failed to reconnect to Active Directory server Make sure the server is available, and that you have used the correct credentials. ---> System.DirectoryServices.ActiveDirectory.ActiveDirectoryServerDownException:
Active Directory server is not available. Please retry at a later time.
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnectionFromPool(ConnectionPoolType connectionPoolType, ADObjectId domain, String serverName, Int32 port, Boolean& serverConnectionPresentButDownOrDisconnected)
at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential)
at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, NetworkCredential networkCredential, String serverName, Int32 port)
at Microsoft.Exchange.Data.Directory.ADDataSession.GetConnection(String preferredServer, Boolean isWriteOperation, String optionalBaseDN, ADObjectId& rootId, ADScope scope)
at Microsoft.Exchange.Data.Directory.ADDataSession.GetWritableConnection(String preferredServer, ADObjectId identity, ADRawEntry scopeDeterimingObject)
I already prepare AD and Schema before start install
Please Advice Thanks

Hi Midoooz
Thank you for your question.
Do you install the Exchange Server on the DC?
From you posted error, I think you can try to make your exchange server in maintenance mode, then you can try install exchange CU6.
You can refer to the following link:
http://support2.microsoft.com/kb/2713696
Note:
Stop Maintenance Mode on the computer that is running Exchange Server after the Exchange Server 2013 CU6 upgrade is completed.
If there are any questions, please let me know.
Best Regard,
Jim

Similar Messages

Error Installing Exchange 2013 CU6

setup startup give me this error
Method 'get_MultifactorRegistrationEnabled' in type 'Microsoft.Exchange.Data.Directory.SystemConfiguration.PushNotificationApp' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' does
not have an implementation.
Have you any suggestion to solve it?

Here the result!
Display Name Name Install State
[X] Active Directory Domain Services AD-Domain-Services Installed
[X] Application Server Application-Server Installed
[X] .NET Framework 4.5 AS-NET-Framework Installed
[X] Windows Process Activation Service Support AS-WAS-Support Installed
[X] HTTP Activation AS-HTTP-Activation Installed
[X] DHCP Server DHCP Installed
[X] DNS Server DNS Installed
[X] Fax Server Fax Installed
[X] File And Storage Services FileAndStorage-Services Installed
[X] File and iSCSI Services File-Services Installed
[X] File Server FS-FileServer Installed
[X] Storage Services Storage-Services Installed
[X] Print and Document Services Print-Services Installed
[X] Print Server Print-Server Installed
[X] Internet Printing Print-Internet Installed
[X] Remote Access RemoteAccess Installed
[X] DirectAccess and VPN (RAS) DirectAccess-VPN Installed
[X] Routing Routing Installed
[X] Web Server (IIS) Web-Server Installed
[X] Web Server Web-WebServer Installed
[X] Common HTTP Features Web-Common-Http Installed
[X] Default Document Web-Default-Doc Installed
[X] Directory Browsing Web-Dir-Browsing Installed
[X] HTTP Errors Web-Http-Errors Installed
[X] Static Content Web-Static-Content Installed
[X] HTTP Redirection Web-Http-Redirect Installed
[X] WebDAV Publishing Web-DAV-Publishing Installed
[X] Health and Diagnostics Web-Health Installed
[X] HTTP Logging Web-Http-Logging Installed
[X] Custom Logging Web-Custom-Logging Installed
[X] Logging Tools Web-Log-Libraries Installed
[X] ODBC Logging Web-ODBC-Logging Installed
[X] Request Monitor Web-Request-Monitor Installed
[X] Tracing Web-Http-Tracing Installed
[X] Performance Web-Performance Installed
[X] Static Content Compression Web-Stat-Compression Installed
[X] Dynamic Content Compression Web-Dyn-Compression Installed
[X] Security Web-Security Installed
[X] Request Filtering Web-Filtering Installed
[X] Basic Authentication Web-Basic-Auth Installed
[X] Centralized SSL Certificate Support Web-CertProvider Installed
[X] Client Certificate Mapping Authentic... Web-Client-Auth Installed
[X] Digest Authentication Web-Digest-Auth Installed
[X] IIS Client Certificate Mapping Authe... Web-Cert-Auth Installed
[X] IP and Domain Restrictions Web-IP-Security Installed
[X] URL Authorization Web-Url-Auth Installed
[X] Windows Authentication Web-Windows-Auth Installed
[X] Application Development Web-App-Dev Installed
[X] .NET Extensibility 4.5 Web-Net-Ext45 Installed
[X] ASP Web-ASP Installed
[X] ASP.NET 4.5 Web-Asp-Net45 Installed
[X] CGI Web-CGI Installed
[X] ISAPI Extensions Web-ISAPI-Ext Installed
[X] ISAPI Filters Web-ISAPI-Filter Installed
[X] FTP Server Web-Ftp-Server Installed
[X] FTP Service Web-Ftp-Service Installed
[X] FTP Extensibility Web-Ftp-Ext Installed
[X] IIS Hostable Web Core Web-WHC Installed
[X] Management Tools Web-Mgmt-Tools Installed
[X] IIS Management Console Web-Mgmt-Console Installed
[X] IIS 6 Management Compatibility Web-Mgmt-Compat Installed
[X] IIS 6 Metabase Compatibility Web-Metabase Installed
[X] IIS 6 Management Console Web-Lgcy-Mgmt-Console Installed
[X] IIS 6 Scripting Tools Web-Lgcy-Scripting Installed
[X] IIS 6 WMI Compatibility Web-WMI Installed
[X] IIS Management Scripts and Tools Web-Scripting-Tools Installed
[X] Management Service Web-Mgmt-Service Installed
[X] .NET Framework 3.5 Features NET-Framework-Features Installed
[X] .NET Framework 3.5 (includes .NET 2.0 and 3.0) NET-Framework-Core Installed
[X] .NET Framework 4.5 Features NET-Framework-45-Fea... Installed
[X] .NET Framework 4.5 NET-Framework-45-Core Installed
[X] ASP.NET 4.5 NET-Framework-45-ASPNET Installed
[X] WCF Services NET-WCF-Services45 Installed
[X] HTTP Activation NET-WCF-HTTP-Activat... Installed
[X] Message Queuing (MSMQ) Activation NET-WCF-MSMQ-Activat... Installed
[X] Named Pipe Activation NET-WCF-Pipe-Activat... Installed
[X] TCP Activation NET-WCF-TCP-Activati... Installed
[X] TCP Port Sharing NET-WCF-TCP-PortShar... Installed
[X] Group Policy Management GPMC Installed
[X] Ink and Handwriting Services InkAndHandwritingSer... Installed
[X] Media Foundation Server-Media-Foundation Installed
[X] Message Queuing MSMQ Installed
[X] Message Queuing Services MSMQ-Services Installed
[X] Message Queuing Server MSMQ-Server Installed
[X] RAS Connection Manager Administration Kit (CMAK) CMAK Installed
[X] Remote Server Administration Tools RSAT Installed
[X] Feature Administration Tools RSAT-Feature-Tools Installed
[X] Failover Clustering Tools RSAT-Clustering Installed
[X] Failover Cluster Management Tools RSAT-Clustering-Mgmt Installed
[X] Failover Cluster Module for Windows ... RSAT-Clustering-Powe... Installed
[X] Failover Cluster Command Interface RSAT-Clustering-CmdI... Installed
[X] WINS Server Tools RSAT-WINS Installed
[X] Role Administration Tools RSAT-Role-Tools Installed
[X] AD DS and AD LDS Tools RSAT-AD-Tools Installed
[X] Active Directory module for Windows ... RSAT-AD-PowerShell Installed
[X] AD DS Tools RSAT-ADDS Installed
[X] Active Directory Administrative ... RSAT-AD-AdminCenter Installed
[X] AD DS Snap-Ins and Command-Line ... RSAT-ADDS-Tools Installed
[X] DHCP Server Tools RSAT-DHCP Installed
[X] DNS Server Tools RSAT-DNS-Server Installed
[X] Fax Server Tools RSAT-Fax Installed
[X] Print and Document Services Tools RSAT-Print-Services Installed
[X] Remote Access Management Tools RSAT-RemoteAccess Installed
[X] Remote Access GUI and Command-Line T... RSAT-RemoteAccess-Mgmt Installed
[X] Remote Access module for Windows Pow... RSAT-RemoteAccess-Po... Installed
[X] RPC over HTTP Proxy RPC-over-HTTP-Proxy Installed
[X] Telnet Client Telnet-Client Installed
[X] User Interfaces and Infrastructure User-Interfaces-Infra Installed
[X] Graphical Management Tools and Infrastructure Server-Gui-Mgmt-Infra Installed
[X] Desktop Experience Desktop-Experience Installed
[X] Server Graphical Shell Server-Gui-Shell Installed
[X] Windows Identity Foundation 3.5 Windows-Identity-Fou... Installed
[X] Windows Internal Database Windows-Internal-Dat... Installed
[X] Windows PowerShell PowerShellRoot Installed
[X] Windows PowerShell 3.0 PowerShell Installed
[X] Windows PowerShell 2.0 Engine PowerShell-V2 Installed
[X] Windows PowerShell ISE PowerShell-ISE Installed
[X] Windows Process Activation Service WAS Installed
[X] Process Model WAS-Process-Model Installed
[X] Configuration APIs WAS-Config-APIs Installed
[X] Windows Server Backup Windows-Server-Backup Installed
[X] WINS Server WINS Installed
[X] WoW64 Support WoW64-Support Installed

Large ETLTraces files after Exchange 2013 CU6

After installing Exchange 2013 CU6, you may notice the Exchange Drive is consumed a lot than before and the size is increasing rapidly. After troubleshooting, you may find everything is running properly and
there is no issues with your Exchange Server.
Then you need to check whether the files in the following location is the root cause:
C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Diagnostics\logfie
C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Diagnostics\ETLTraces
(You may find log files like “DocumentProcessingTrace_XX.etl )
Prior to CU6, there is not ETLTrace folder listed in this location and there are log folders however the log file has files no exceeding 7 MB size.
Post upgrade, there comes the ETLTrace folder and the files in this folder are close to 50 MB and the log files folder have log files exceeding 50 MB size.
This is a designed behavior in Exchange CU6, if you have limited hard drive space, as a workaround solution, we can safely remove or move the location of these lo files:
Before doing the changes, please firstly stop the health monitoring service. To Change the Log File Path, the Registry Key value is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Search Foundation for Exchange\Diagnostics
To Change the ETLTrace path the registry Value is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\16.0\Search\Diagnostics\Tracing
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

@Simon_Wu, I tried your solution. However after a couple of days the logs were moved back to the original, default location. It looks like the server has a process which checks for hacks and undoes any attempts to change the path.
Interestingly the altered Registry entries remained altered, however the files were switched back to the default location. It generates just over 1Gb of logs per day on a largely idling Exchange 2013 CU7 server with 350 mailboxes.
Go figure!
What I found to work consistently and reliably is to replace default folders with junction points to another folder on another drive.
I also found that these files are created by a process which runs under the System process (PID 4), therefore you'll need to restart the server in Safe Mode to replace the default folders with junction points.

Problem with Exchange 2010 Public Folders after installing Exchange 2013 in my environment.

I currently have an Exchange 2010 server with all the roles installed. Before installing Exchange 2013, I was able to launch the Public Folder Management Console but now I get an error. When I installed Exchange 2013, I got an error saying I
had a instance of Exchange 2000 or Exchange 2003, but I didn't have any of these servers left. There was still something in AD referencing my old server. I went into ADSIedit and deleted an old administrative group. This deletion caused my access
to my public folders to get messed up. I followed this article, http://blog.bruteforcetech.com/archives/766, and I was able to gain access back in my outlook client but I still can't see the public folders in OWA. I also get this error when
trying to access either Default or System Public Folders. "Cannot complete the operation because there isn't an available public folder database on server 'ExchangeServer'. It was running the command 'get-publicfolder - getchildren -identity '\'
-server 'ExchangeServer' "
My Public Folder Database exists and is mounted. Any help is appreciated.

Hi Belinda,
Thank you for responding. Yes you do understand my problem correctly. One correction is that after deleting this entry in ADSIEdit, we couldn't access public folders at all either in Outlook or OWA. I followed these steps in the below article:
http://blog.bruteforcetech.com/archives/766
After following these steps and recreating the entry on FolderHieachies in ADSI edit, I was able to gain access to the public folders again through Outlook, but still can't see them in OWA and can't access them in Public Folder Management Console.
Here are the results to your requests:
et-PublicFolder -Recurse | Format-List Name
Name : IPM_SUBTREE
Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRAT
GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
+ FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
[PS] C:\Windows\system32>Get-PublicFolder -Identity \NON_IPM_SUBTREE -Recurse | Format-List Name
Name : NON_IPM_SUBTREE
Name : EFORMS REGISTRY
Can't get the public folder database using legacy distinguished name '/O=HEROIX CORPORATION/OU=EXCHANGE ADMINISTRATIVE
GROUP (FYDIBOHF23SPDLT)/CN=CONFIGURATION/CN=SERVERS/CN=EXCHANGE2010/CN=MICROSOFT PUBLIC MDB'.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], TaskInvalidOperationException
+ FullyQualifiedErrorId : B546E0B0,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
Also the msExchOwningPFTree attribute should be correct because this was edited with the correct value when I followed the instructions in the above article:
CN=Public Folders,CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Heroix Corporation,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hero,DC=net

Exchange 2013 CU6 migration batch

Hello
After install exchange 2013 cu6 server to root domain in multiple domain environment I cant move mailbox from exchange 2007 to new server because migration batch search mailbox only root domain controller.
ADTopology list all child domain dc without error.
setup /ps and /pad run without error.
but new-moverequest working.
please help.
Udvozlettel:Sneff Gabor

Hi
It might be a bug in the GUI as powershell is working. Did you also update exchange 2007 to its latest rollup?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Reading Exchange Online tenant version failed due to an exception when trying to install Exchange 2013 in a hybrid environment.

We currently have an Exchange 2010 hybrid install and we have migrated all of our email accounts to Office 365. Now, I want to do an on-premise install of Exchange 2013 to better manage the hybrid setup. When I try to install Exchange 2013 it
asks for my O365 credentials to do a hybrid check but always fails with the above message. I've done quite a bit of searching but haven't come up with anything useful.
Here is what appears in the exchange setup log:
[09/22/2014 15:48:27.0024] [0] Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log for more information.
[09/22/2014 15:48:27.0024] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,
[09/22/2014 15:48:27.0024] [0] Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,
[09/22/2014 15:48:27.0147] [0] Session=Tenant Total Cmdlet Time=1.6931035s
[09/22/2014 15:48:27.0148] [0] Microsoft.Exchange.Management.Deployment.HybridConfigurationDetection.HybridConfigurationDetectionException: Reading the Exchange Online tenant version information failed due to an exception. Please check the Exchange setup log
for more information. ---> System.TypeLoadException: Could not load type 'Microsoft.Exchange.Data.Directory.DirectoryBackendType' from assembly 'Microsoft.Exchange.Data.Directory, Version=15.0.0.0, Culture=neutral,

Hi,
I recommend you post this in
office 365 forum also, as they should have more professional knowledge on hybrid deployments
and you may get effective solution timely.
In addition, I found a similar thread for you reference:
http://community.office365.com/en-us/f/156/t/255739.aspx
According to the reply of this thread, if you run the HCW (Hybrid Configuration Wizard) to deploy the Exchange Hybrid environment, there will generate an HCW log
file for this deployment.
Additional troubleshooting information is available in the Update-HybridConfiguration log file located at C:\Program Files\Microsoft\Exchange Server\V1*\Logging\Update-HybridConfiguration\HybridConfiguration****.log
Best regards,
Niko Cheng
TechNet Community Support

MS KB3011140 breaks information store in Exchange 2013 CU6

Hello,
Last night Microsoft KB 3011140 was inadvertently installed on our Exchange 2013 CU6 server. I just want to warn everyone that you should be very cautious with this update. Upon reboot, the information store would crash, recover, then crash and
recover, infintly. End user symptoms are the pop up bubble in the lower right regarding Outlook lost connectivity to Exchange server, then a few minutes later Outlook restored connectivity to Exchange, rinse and repeat.
This constant up and down would cause many freezes and slowness in Outlook. The last time we had this issue was when we went to CU6. Microsoft tech support though free of charge installed a patch Exchange2013-KB2997209_2997847-x64.en.msp and
that fixed our problem. They left the patch for us, so I thought I would try to re-run this. It progressed for awhile and then rolled back saying it encountered an unexpected error (what else is new?).
So I removed KB 3011140 which took about 35 minutes to do and upon reboot Exchange is back up and running.
The only side effect I am noticing today is Lync 2013 is asking for Exchange credentials and EWS Internal / EWS External URI's are not populated, however I have no issues reading my conversation history and calendar in Lync. I need to reboot my machine
yet but other people have started reporting the same thing.

Hi KJSTech1,
Thanks for your generous sharing and glad to know it works after recycling the MSExchangeServicesAppPool.
It's really hard to say why the patch cause this issue, since I didn't find someothers has the same issue. Thanks for your reporting.
Thanks
Mavis Huang
TechNet Community Support

Exchange 2013 CU6 event id 1003

Installed cu6, after that OWA and ECP stopped to work, with a redirection loop, when I check my eventlogs I see thousands of this error message:
RpcHttp] An internal server error occurred. The unhandled exception was: System.MissingMethodException: Method not found: 'System.String Microsoft.Exchange.Security.Authentication.IIdentityExtensions.GetSafeName(System.Security.Principal.IIdentity)'.
at Microsoft.Exchange.HttpProxy.ProxyModule.<>c__DisplayClasse.<OnEndRequest>b__d()
at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
Cant find a workaround, anyone else seen this error?

Maybe this can help someone.
v
Replaced SharedWebConfig files under the location "V15\FrontEnd\HttpProxy"
v
Added the missing permission on Exchange Back End Web Site by comparing the same with our lab
v
On IIS
è Exchange Back End
è Changed Physical Path
è it to "V15\ClientAccess"
v
Still after which we couldn’t browse OWA under Exchange Back End using Port 444 but found that ECP works fine
v
Replaced the SharedWebConfig file from working Exchange 2013 CU6 under the location "V15\ClientAccess"
v
Ran IISReset
v
Confirmed that OWA and other virtual directories as well started working fine without any issues

Getting Error while installing Exchange 2013 on server 2012

Error During Exchange 2013 Mailbox Transport
Role Install On Server 2012
Exchange
Server forums
>
Exchange
Server 2013 - Setup, Deployment, Updates, and Migration
Question
1
Sign
in to vote
I was installing Exchange 2013 on Server 2012. The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin. There has never been an Exchange instance on this domain. I got past
the prerequisite checks, and the installer showed 15 steps, so I walked away. When I came back, I saw this:
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: "Unable to set shared config DC.".

Hi Deepak,
From the error description, I would like to clarify the following things:
1. Please ensure that IPv6 on the network adaptor is turned on.
2. Please check if the account that you used to install Exchange has necessary permissions to perform the installation.
3. Make sure that DNS is configured correctly.
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Installation Error Installing Exchange 2013 CU3 on Server 2012

Hello,
When Installing Exchange 2013 on server 2012 I get the following error during Step 1 of 8 of Transport Service. I have installed and unistalled Exchange a few times, restarted the machine manually and removed exchange from AD, etc. to no avail.
Any suggestions will be very much appreciated.
Thank You.
VK
Error:
The following error was generated when "$error.Clear();
          install-MsiPackage `
          -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASDat.MSI") `
          -LogFile ($RoleSetupLoggingPath + "\InstallASDat.msilog") `
          -PropertyValues ("ALLUSERS=1") `
          -UpdatesDir $RoleUpdatesDir
        " was run: "Installing product C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASDat.MSI failed. This action is only valid for products that are currently installed. Error
code is 1605.".

Martina,
Thank you for your response. KB says that Machinepolicy and Userpolicy are to be set to Undefined and that is what I have.
Windows PowerShell
Copyright (C) 2013 Microsoft Corporation. All rights reserved.
PS C:\Users\Administrator> get-executionpolicy –list
Scope
ExecutionPolicy
MachinePolicy
Undefined
UserPolicy
Undefined
Process
Undefined
CurrentUser
Undefined
LocalMachine
RemoteSigned
VK

Re-install Exchange 2013

I started a basic install of Exchange 2013 on Windows 2012 on a network with an existing Exchange 2007 (SBS 2008) org.
Things went well with prerequisites and AD Prep but the actual install ended up freezing up. I ran it on a VM with 2GB RAM and all I can guess is that services couldn't start etc with only that much RAM. I did the install through a remote desktop session
and when I returned after kicking off the install process that session was completely frozen up with a black screen. All I could do was reboot the server. I noticed messages that implied the completely new/blank Exchange install was unhappy with 2GB so I raised
it to 10GB, but still things just didn't work. Most significantly I couldn't even load the Management Console replacement web site. I just would get 404 not found.
Thinking the original install never completed properly I simply deleted the VM, re-created a new one with the same config (and 10GB RAM) with the same name, joined the domain, installed pre-requisites and re-started the install, but now I'm getting
"Exchange Server in an inconsistent state. Only disaster recovery mode is available. Please use Setup /m:RecoverServer"...
Of course now I get other errors because "Disaster Recovery setup needs access to the mailbox database drive (prior install location)" etc. and of course I have no backups or anything because there was nothing but deployed install media on the
prior server.
How do I re-install? Do I need to clean up AD references to the prior install?
Regards,
Steve Ware

Hello,
Yes. You should check if the uncompleted exchange server is in AD. If it is in AD, please remove it and then reinstall it.
And you can remove the VM, and create a new VM, and then install new exchange server whose name is different from the uncompleted exchange server.
Additional article for your reference.
Install Exchange 2013 in an Existing Exchange 2007 Organization
http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Installé Exchange 2013 on win 2k8R2

hello please i have this error msg when installing exchange 2013 on win 2k8R2 on the maibox step
$error.clear(); start-SetupService -ServiceName MSExchangeSubmission was run: service MSExchangeSubmission failed to reach status Running on this server..
i done every thing that i see in the forum always nothing

yes i install all the prerequisites for exchange am on 2k8R2 do i need to install the both
office filter pack

Exchange 2013 CU6 update cannot pass preresquites?

When I go to update our Exchange 2013 server to CU6 (from CU5) I get the following error:
I was doing something with the Tasks, which cannot be scheduled anymore. How do I fix this?
Thanks
Error:
The following error was generated when "$error.Clear();
try
$Target = $env:COMPUTERNAME
try
$exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup will continue.";
if ($exSrv -eq $null)
Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive. Setup will continue.";
return
Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup can not continue.";
throw;
" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Error:
The following error was generated when "$error.Clear();
try
$Target = $env:COMPUTERNAME
try
$exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup will continue.";
if ($exSrv -eq $null)
Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive. Setup will continue.";
return
Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup can not continue.";
throw;
" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Error:
The following error was generated when "$error.Clear();
try
$Target = $env:COMPUTERNAME
try
$exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup will continue.";
if ($exSrv -eq $null)
Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive. Setup will continue.";
return
Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."
Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
catch
Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup can not continue.";
throw;
" was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Based on "Was Run" error it looks like you don't have permission to store something in AD. Can you try putting server into maintenance mode first and see if you can?
http://windowsitpro.com/blog/installing-exchange-2013-cu1-dag-member-servers-some-care-and-maintenance-mode-required
http://vanhybrid.com/2013/11/28/script-putting-exchange-server-2013-into-maintenance-mode/
If server goes into maintenance mode successfully then re-run the setup...

Throttling policy not working on Exchange 2013 CU6

Hi,
We have a test throttling policy to restrict a mailbox to send at most 2 messages
per minute in our live Exchange 2013 CU6 enviroment. It was associated to a test mailbox. We have separated installed 2 mailboxe and 2 cas server roles in our enviroment. I have checked latest CU-s (7 & 8) but these are
not fixing any related bugs.
We tried lots of workaround (see below list) and solutions to fix this but it is still not working with outlook MAPI and OWA client.
Throttling policy not working
smtp service restart
RPC Client Acces service restart
The policy details:
Get-ThrottlingPolicy low_rate_limit |fl *limit*
MessageRateLimit : 2
RecipientRateLimit : 1000
Get-mailbox [email protected] | fl ThrottlingPolicy
ThrottlingPolicy : low_rate_limit
Do you have any idea what is the problem?
Thank you in advance.
br,
Zoltan

Hi Zoltan,
Base on my research, you need to configure the MessageRateLimit parameter on receive connector also.
The MessageRateLimit parameter specifies the maximum number of messages that can be sent by a single client IP address per minute. The default value for a Receive connector configured in the Transport service on a Mailbox server is
unlimited. The default value for a Receive connector configured on an Edge server is 600 messages per minute. The valid input range for this parameter is 1 to 2147483647. To remove the message rate limit on a Receive connector, enter a value of
unlimited.
https://technet.microsoft.com/en-us/library/bb125140(v=exchg.150).aspx
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Installing Exchange 2013 CU 6 failed

Hello, we have a big problem with installing CU6 on a new installed exchange 2013 server. Here's the error message:
Error:
The following error was generated when "$error.Clear();
          if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
          if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
          $sysMbx = $null;
          $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
          $dispName = "Microsoft Exchange";
          Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
          $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
          if ($mbxs.Length -eq 0)
          Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
          $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
          if ($dbs.Length -ne 0)
          Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
          $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
          if ($arbUsers.Length -ne 0)
          Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
          $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
          else
          if ($mbxs[0].DisplayName -ne $dispName )
          Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
          Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
          $sysMbx = $mbxs[0];
          # Set the Organization Capabilities needed for this mailbox
          if ($sysMbx -ne $null)
          # We need 1 GB for uploading large OAB files to the organization mailbox
          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
          set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true
-MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
          Write-ExchangeSetupLog -Info ("Configuring offline address book(s) for this mailbox");
          Get-OfflineAddressBook | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012)
-ge 0 -and $_.GeneratingMailbox -eq $null} | Set-OfflineAddressBook -GeneratingMailbox $sysMbx.Identity;
          else
          Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
          else
          Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
        " was run: "Microsoft.Exchange.ProvisioningAgent.RusException: Failed to generate proxy address. Additional information:
General Error.
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckReturnCode(ReturnCode rc)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckProxy(RecipientInfo pRecipientInfo, String pwszProxyAddr)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CheckSingleProxy(ProxyAddressTemplate baseAddress, RecipientInfo recipientInfo, ProxyAddress oldProxyAddress)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.GenerateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
globalCatalogSession, IEnumerable`1 baseAddresses, IEnumerable`1 oldProxies, RecipientInfo recipientInfo, ADRecipient recipient, LogMessageDelegate logger)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CreateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
globalCatalogSession, IEnumerable`1 baseAddresses, ADRecipient recipient, LogMessageDelegate logger)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateEmailAddresses(List`1 allPolicies, ADRecipient recipient, LdapFilterProvider filterProvider)
   at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateRecipient(ADRecipient recipient)
   at Microsoft.Exchange.ProvisioningAgent.DefaultRUSProvisioningHandler.UpdateRecipient(ADRecipient recipient)
   at Microsoft.Exchange.ProvisioningAgent.RUSProvisioningHandler.UpdateAffectedIConfigurable(IConfigurable writeableIConfigurable)
   at Microsoft.Exchange.Provisioning.ProvisioningLayer.UpdateAffectedIConfigurable(Task task, IConfigurable writeableIConfigurable, Boolean checkProvisioningLayerAvailability)
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()
   at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
After this error message, the exchange installation is incomplete, there is no repair possible. Also remove the installation is not possible because there is an incomplete update installed.
Any ideas how to solve this?

Hi,
From the description of the error “ Microsoft.Exchange.ProvisioningAgent.RusException: Failed to generate proxy address. Additional information: General Error. ”
Appeared to have some valid proxy address. Please check if there are invalid characters in the admin account proxy address.
To find the proxy address, take the following steps:
Open ADUC, Click View in the menu then click
Advanced Features.
Navigate to yourOrganization >> Users, choose the admin account, right-click to
Properties.
Under Attributes Editor tab, find the proxyaddresses
Attribute, then check the address.
Hope this will be helpful for you.
Best Regards.

DC Restart when start installing Exchange 2013 CU6

Similar Messages

Maybe you are looking for