Exchange Server 2013 CU3 Installation Error - Fresh Installation

Hi All,
I am trying to install Exchange 2013 CU3 on Windows Server 2012 Datacenter Edition. This is New Server Forest build.
Forest Function Level and Domain functional Level is Windows Server 2008 R2
As part of this Fresh installation, I have tried to install CAS Server Role first on the server.
I have full admin (Schema,Entp, Domain) Previliges and installed MS recomended pre-requesities successfully.
Set the Powershell Execution policy as unrestricted.
But, When i run setup file using GUI option. I am getting the below error. I would like to know whether this is ignorable for installation or how to fix the issue.
Error:
Warning:
Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type
initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
Task execution result should not be affected.
Warning:
Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type
initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
Task execution result should not be affected.
Warning:
Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for
'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution
result should not be affected.
Note: Server OS hardening policy has been applied in this server as per company security policy and Symantec A/V also installed in this server.
Regards
Manoj

Hi,
Same Error for Mailbox Server also.
Stopped the Symantec AV Service and Tried. But result is same.
02/18/2014 06:39:06.0018] [0] Active Directory session settings for 'Get-OrganizationRelationship' are: View Entire Forest: 'True', Configuration Domain Controller: 'TESTPRADC01.Domain.LOCAL', Preferred Global Catalog: 'TESTPRADC01.Domain.LOCAL', Preferred
Domain Controllers: '{ TESTPRADC01.Domain.LOCAL }'
[02/18/2014 06:39:06.0050] [0] User specified parameters:
[02/18/2014 06:39:06.0050] [0] Beginning processing Get-OrganizationRelationship
[02/18/2014 06:39:07.0157] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Error" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution
result should not be affected.
[02/18/2014 06:39:07.0391] [0] [ERROR] Couldn't find the Enterprise Organization container.
[02/18/2014 06:39:07.0469] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
Task execution result should not be affected.
[02/18/2014 06:39:07.0610] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
Task execution result should not be affected.
[02/18/2014 06:39:07.0688] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
Task execution result should not be affected.
[02/18/2014 06:39:07.0688] [0] Ending processing Get-OrganizationRelationship
[02/18/2014 06:39:07.0766] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task
execution result should not be affected.
[02/18/2014 06:39:08.0015] [0] Active Directory session settings for 'Get-AcceptedDomain' are: View Entire Forest: 'True', Configuration Domain Controller: 'TESTPRADC01.Domain.LOCAL', Preferred Global Catalog: 'TESTPRADC01.Domain.LOCAL', Preferred Domain Controllers:
'{ TESTPRADC01.Domain.LOCAL }'
[02/18/2014 06:39:08.0015] [0] User specified parameters:
[02/18/2014 06:39:08.0015] [0] Beginning processing Get-AcceptedDomain
[02/18/2014 06:39:08.0078] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Error" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution
result should not be affected.
[02/18/2014 06:39:08.0078] [0] [ERROR] Couldn't find the Enterprise Organization container.
[02/18/2014 06:39:08.0140] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
Task execution result should not be affected.
[02/18/2014 06:39:08.0202] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
Task execution result should not be affected.
[02/18/2014 06:39:08.0265] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
Task execution result should not be affected.
[02/18/2014 06:39:08.0265] [0] Ending processing Get-AcceptedDomain
[02/18/2014 06:39:08.0327] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task
execution result should not be affected.
[02/18/2014 06:39:08.0327] [0] While running the On-Promises test, either Get-AcceptedDomains or Get-OrganizationRelationship return a null value.
[02/18/2014 06:39:08.0717] [0] Finished loading screen WelcomePage.
[02/18/2014 06:45:23.0242] [0] Finished loading screen EULAPage.
[02/18/2014 06:45:26.0908] [0] Finished loading screen RecommendedSettingsPage.
[02/18/2014 06:45:30.0012] [0] Setup is determining what organization-level operations to perform.

Similar Messages

Cannot Access EAC/ECP on exchange server 2013 after installation

Hi,
I can not Cannot Access EAC/ECP on exchange server 2013 after installation . Error 404.4 code 0x80070002
Help!
Thanks,

Hi Florin
Did you try accessing EAC by using below link
https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15
Please access EAC via Internal URL: https://<CASServerName>/ecp
Finally ensure that you have logged in as administrator as well as this might be problem as well
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Exchange Server 2013 Toolbox MMC Error ConsoleInitialize.ps1 not recognised

Hello, after installing and configuring Exchange 2013 during a migration from 2010 (with both versions still running), I am now receiving a ConsoleInitialize.ps1 System.Management.Automation.RemoteException exception when trying to run the Management Toolbox
(I am really after the Queue Viewer).
This is the same when trying to connect locally on the server and remotely on a client computer with Management Tools installed - I can use EMC without any errors locally or remotely.
I have tried various fixes found around the net, including:
Changing the Identity of the Classic and DefaultAppPools in IIS and resetting - from LocalSystem to ApplicationPoolIdentity
Adding the roles to Exchange Organisation Management in AD
Disabling SSL on the Powershell virtual Directory and setting auth to anonymous
I have not tried recreating the Powershell virtual directory as mentioned on a few sites, as I have not been able to test that in the lab, and I am not sure how it affects the powershell session that I am doing it from.
The only thing that I can think that could be an issue is that Ex2010 is still up and running, could it be that Management Tools is looking at the old server, instead of the new?
Can anyone point me in the right direction with this one?
I can post more info if required.
Thank you.
Xpost here: http://serverfault.com/questions/666054/exchange-server-2013-toolbox-mmc-error-consoleinitialize-ps1-not-recognised

Hi,
If the EMS and EMC work properly, I think the powershell cannot be the problem. Is it possible to build up a new Exchange 2013 Server in test environment and make a replacement of
the ConsoleInitialize.ps1 file?
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Backing up Exchange Server 2013 CU3 with Windows Server Backup Program

Looking at configuring Windows Server Backup Program to backup Exchange Server 2013 CU3 which is a member a DAG Group using a specific Backup Domain Account.
From my understanding from the following technet Article" Using Windows Server Backup to Backup and Restore Exchange Data" at http://technet.microsoft.com/en-us/library/dd876851(v=exchg.150).aspx I cannot use wbadmin.exe has it uses an older
unsupported version of Powershell.
My question is what are the minimum AD rights required for an AD account needed to be able to backup/restore Exchange Datastore using Windows Server Backup Program in Windows Server 2012?
Thanks,
NIck

Hi Sathish,
After looking at your response, it all make sense except when I look at what exchange right assigned via RBAC. I understand that the backup service account will require access to the exchange databases
to be able to backing and restoring them. After looking at the different roles
I'm wondering if I require to assign both the Databases roles for Backing up the databases and the Disaster Recovery Role as well to be able to restore the databases has well as having a mailbox on the exchange
server for the backup service account?
Below is explanation of the roles via the ECP
Database Role
This role enables administrators to create, manage, mount and dismount mailbox and public folder databases on individual servers.
Disaster Recovery
This role enables administrators to restore mailboxes and database availability groups in an organization.
Thanks,
Nick

Upgrade Exchange server 2013 to CU7 error

Dear Microsoft Team
I have Exchange server 2013 SP1 and upgrade it to CU5 it is working normal
But wen I try to Upgrade it to CU7 I got this error massage
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)".
Best Regards
Rawa Zangana

Hi Rawa Zangana,
According to the error message, it seems that the Global Catalog not reachable from DC.
Please perform following steps.
1. Port 3268 listened on DC.
2. Enable Global Catalog role on all DCs.
3. Restart Exchange Server 2013 CU5.
4. Check whether Event 2080 found on all DCs, Event 2080 means that AD connectivity works fine.
5. Repeat CU7 installation.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Mail flow completely broken after upgrading Exchange Server 2013 CU3 (Build 775.38) to Exchange Server 2013 SP1 (Build 847.32)

internal mail flow completely broken.
external mail flow completely broken.
i upgraded exchange server as follows:
1. setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
2. setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
3. upgraded the exchange server with GUI installer
also considered this: http://support.microsoft.com/kb/2938053/en-us
receive connectors :
Transport Service couldn't start, then i disabled hub transports, and it starts, but no mail flow on port 25. according to this:
http://social.technet.microsoft.com/wiki/contents/articles/24056.what-the-crash.aspx
i didn't have any success to fix mail flow, any solution?

Hi Alireza
The above tech-net http://social.technet.microsoft.com/wiki/contents/articles/24056.what-the-crash.aspx
will be applicable only if we get these events in the app log 1019,1018,1036,4999
You can check the transport service is running in which service account - Local or network
It should be running in network account by default.
You can run get-transportagent and check if there are any transport agents installed
If you find them then disable all the transport agents that you have installed on the Exchange servers by running disable-transportagents
Disable the antivirus if you have any installed.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com

Exchange Server 2013 CU3 Update

Hello All,
I need to upgrade Exchange server 2013 CU1 to CU3. I need the details procedure. Please suggest regarding this issue.
Thanks

Are you aware that
SP1 (CU4) is available?
Step by Step Screencasts and Video Tutorials

Exchange Server 2013 CU7 Installation Issue

Error:
The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
                try
                    # Need to configure the ETL traces before the fast service is installed. This will ensure that when the service comes up
                    # it will have the necessary trace session setting available to read from the registry
                    $fastPerfEtlTraceFolderPath = Join-Path -Path $RoleBinPath -ChildPath "\Search\Ceres\Diagnostics\ETLTraces"
                    $fastDiagnosticTracingRegKeyPath = 'HKLM:\SOFTWARE\Microsoft\Office Server\16.0\Search\Diagnostics\Tracing'
                    if(-not(Test-Path -Path $fastPerfEtlTraceFolderPath))
                        $null = New-Item $fastPerfEtlTraceFolderPath -Type 'Directory' -Force
                    if (-not(Test-Path -Path $fastDiagnosticTracingRegKeyPath))
                        $null = New-Item -Path $fastDiagnosticTracingRegKeyPath -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'TracingPath' -PropertyType 'string' -Value $fastPerfEtlTraceFolderPath
-Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'TracingFileName' -PropertyType 'string' -Value 'DocumentProcessingTrace'
-Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'DocumentParserSuccessLogMessage' -PropertyType 'Dword' -Value 1 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'DocumentParserLoggingNoInitialisation' -PropertyType 'Dword' -Value 1 -Force
                    # Max trace folder size 50 * 100 = 5GB
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'MaxTraceFileSize' -PropertyType 'Dword' -Value 50 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'MaxTraceFileCount' -PropertyType 'Dword' -Value 100 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'UseGeneralSwitch' -PropertyType 'Dword' -Value 1 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'GeneralSwitch' -PropertyType 'Dword' -Value 1 -Force
                catch
                    # ETl tracing is not critical. Info only log
                    Write-ExchangeSetupLog -Info ("An exception ocurred while trying to Configure the FAST ETL traces. Exception: " + $_.Exception.Message);
                try
                    $fastFusionRegKeyPath = 'HKLM:\SOFTWARE\Microsoft\Office Server\16.0\Search\FlightControl'
                    if (Test-Path -Path $fastFusionRegKeyPath)
                        Remove-ItemProperty -Path $fastFusionRegKeyPath -Name 'fusion_new_enabled' -Force -ErrorAction SilentlyContinue
                        Remove-ItemProperty -Path $fastFusionRegKeyPath -Name 'fusion_old_enabled' -Force -ErrorAction SilentlyContinue
                        Remove-ItemProperty -Path $fastFusionRegKeyPath -Name 'fusion_compare_outputs' -Force -ErrorAction SilentlyContinue
                catch
                    # Removing new fusion keys is not critical. Info only log
                    Write-ExchangeSetupLog -Info ("An exception ocurred while trying to remove the fast new fusion reg keys. Exception: " + $_.Exception.Message);
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $dataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                # Remove previous SearchFoundation configuration
                &$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;
                # Re-add the SearchFoundation configuration
                try
                    # the BasePort value MUST be kept in sync with dev\Search\src\OperatorSchema\SearchConfig.cs
                    &$command -action i -baseport 3800 -dataFolder $dataFolderPath -silent;
                catch
                    $errorMsg = "Failure configuring SearchFoundation through installconfig.ps1 - " + $_.Exception.Message;
                    Write-ExchangeSetupLog -Error $errorMsg;
                    # Clean up the failed configuration attempt.
                    &$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;
                # Set the PowerShell Snap-in's public key tokens
                try
                    $PowerShellSnapinsPath = "HKLM:\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\";
                    $FastSnapinNames = @("EnginePSSnapin", "HostControllerPSSnapIn", "InteractionEnginePSSnapIn", "JunoPSSnapin",
"SearchCorePSSnapIn");
                    $officePublicKey = "71E9BCE111E9429C";
                    $exchangePublicKey = "31bf3856ad364e35";
                    foreach ($fastSnapinName in $FastSnapinNames)
                        $fastSnapinPath = $PowerShellSnapinsPath + $fastSnapinName;
                        $assemblyNameProperty = Get-ItemProperty -Path $fastSnapinPath -Name "AssemblyName" -ErrorAction SilentlyContinue;
                        if ($assemblyNameProperty -ne $null -and (-not [string]::IsNullOrEmpty($assemblyNameProperty.AssemblyName)))
                            $newAssemblyName = $assemblyNameProperty.AssemblyName -ireplace ($officePublicKey, $exchangePublicKey);
                            Set-ItemProperty -Path $fastSnapinPath -Name "AssemblyName" -Value $newAssemblyName;
                catch
                    # Info only log
                    Write-ExchangeSetupLog -Info ("An exception ocurred while configuring Search Foundation PowerShell Snapin. Exception: " + $_.Exception.Message);
        " was run: "System.Exception: Failure configuring SearchFoundation through installconfig.ps1 - Error occurred while configuring Search Foundation for Exchange.System.ServiceModel.EndpointNotFoundException:
Could not connect to net.tcp://exchange.domain.com:3803/Management/InteractionEngine. The connection attempt lasted for a time span of 00:00:02.0470060. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.0.0:3803.
---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.0.0:3803
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Microsoft.Ceres.CoreServices.Admin.INodeOperationsManagementAgent.AddNamedNode(String node)
   at Microsoft.Ceres.Exchange.PostSetup.NodeManager.DeployInterationEngineNode()
   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.Install(String installDirectory, String dataDirectoryPath, Int32 basePort, String logFile, Boolean singleNode, String systemName, Boolean attachedMode)
   at CallSite.Target(Closure , CallSite , RuntimeType , Object , Object , Object , Object , Object , Object , Boolean )
   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)".
Al

Hi,
Agree with ED.
The key message is “Could not connect to net.tcp://exchange.domain.com:3803/Management/InteractionEngine.
The connection attempt lasted for a time span of 00:00:02.0470060. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.0.0:3803”
You need to check why it’s block. Any firewall or the port is listened by other processes.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange server 2013 setup encounter error

anyone pls help me, i'm ready setup few time still facing same error.
Error:
The following error was generated when "$error.Clear();
if ($RoleCustomerFeedbackEnabled -ne $null)
$organizationConfig = get-OrganizationConfig;
if ($organizationConfig.CustomerFeedbackEnabled -ne $False)
Set-ExchangeServer -Identity $RoleFqdnOrName -CustomerFeedbackEnabled $RoleCustomerFeedbackEnabled;
" was run: "Property CustomerFeedbackEnabled can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).".

Hi,
First, please make sure you have installed all the required prerequisites. For Exchange 2013 prerequisites, please refer to this
article.
Then please verify if there is a legacy server via ADSIEDIT. If there is a legacy object, please delete this legacy object. In registry editor, remove the watermark key and action key from the following path and then reinitiate the setup to check the result.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\HubTranportRole
If the issue persists, to narrow down the issue, I recommend you check the setup log for related error message.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange Server 2013 CU3 OWA and TMG logoff process.

Hi folks,
I just wanted to quickly check if the intent behind Greg Taylor's deliberate choice of words in
this article are still current, or if we can expect to have a resolution in the SP1 timeframe?
Specifically, I'm referring to Greg's CU1 update early-ish in the article where he states:
"The release of Exchange 2013 RTM CU1 changed the way OWA logoff works, such that the TMG change recommended in this post no longer applies. At the current time there is no way to catch and force logoff at TMG when TMG is generating the form,
instead users should be educated to close their browser window (as the pop-up tells them when they click Sign Out from within OWA).".
Given the "current time" of his update was CU1, is there any update as to whether something more meaningful than the pop-up is going to be put in place? While it's more symbolic than anything else, it's off-putting to
the users to still see their e-mail panel after having chosen to "log off".
Cheers,
Lain

Hi,
Thanks for your update.
Generally, the official clarification can be released after the SP update’s release. We can keep an eye on the Exchange Teamblog to see if there are any new updates for your question.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange server 2013 showing some error on event Log ( "DCOM" and "MSExchangeMapiMailboxAppPool" )

Error : DCOM was unable to communicate with the computer ADCB.ABCD.net using any of the configured protocols; requested by PID 2bec (c:\windows\system32\inetsrv\w3wp.exe).
Error: A process serving application pool 'MSExchangeMapiMailboxAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '2412'. The data field contains the error number.
Please suggest

Hi Parvez,
According to the error message, I understand that the Event error 10009 is received on DC. Please correct me if there is any misunderstand.
To solve this issue, please follow the steps below:
a. Please ensure that the remote computer is online.
b. This problem maybe the result of a firewall blocking the connection.
c. Other reasons for the problem might be found in the Extended RPC error information that is available in Event Viewer.
More details in the following article:
Event ID 10009 — COM Remote Service Availability
http://technet.microsoft.com/en-us/library/cc774368(WS.10).aspx
If the Remote server contains some 32 bit Applications, please make sure that each Application Pool in IIS, under "Advanced Settings" has "Enable 32 bit Application" set to "True".
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange Server 2013 Content Index is in "Unknown" state.

Hi Experts,
We have two Exchange Server 2013 CU3 installed in our customer premises 6 months back on top of Windows Server 2012 OS.
From last week, we are getting the content index status as "Unknown" while checking the "Get-Mailboxdatabasecopystatus".
We have tried to reseed the database by using "update-mailboxdatabasecopy -identity <db> -deleteexistingfiles then we came to know the server is not responding on port 3863.
Attached image is for your reference.
Need support from experts to resolve at the earliest.
Regards,
Santhosh
Santhosh Sivaraman MCITP: Microsoft Exchange Server 2007/2010 | MCSE/MCSA

Hi,
I had the same issue and was able to solved by recreate the search index component on the mailbox servers
Recreate the Search Foundation from scratch
Stop and disable the search services and rename the Data Folder "C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data"
Open power shell and navigate to C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Installer
Run the command : .\installconfig.ps1 -action I -dataFolder "c:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data"
Output should be like
[PS] C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Installer>.\installconfig.ps1 -action I -dataFolder "C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\Data"
Configuring Search Foundation for Exchange....
Successfully configured Search Foundation for Exchange
Rename the Index files for the database that are active on the node .
Start the Search Services
Removed a configuration entry that refers to the ContentSubmitters group. This entry is present in four XML files. Each file is called WcfConfigurator.
you can find each file in the following folder:
%ExchangeInstallPath%\Bin\Search\Ceres\HostController\Data\Nodes\Fsis\NODENAME\Configuration\Local
Here, “%ExchangeInstallPath%” is the Exchange installation root path, and the placeholder NODENAME represents one of the following names. (There is one name for each of the four files that are to be edited.)
AdminNode1
ContentEngineNode1
IndexNode1
InteractionEngineNode1
These are text files. You can use Notepad or any other convenient plain text editor to change them. Make sure that you make only the change that is described here.
Each file contains at most one line that contains the following: <AuthorizedRole>ContentSubmitters</AuthorizedRole>
Remove this line, and then save the file. Repeat this operation for each of the four files, and then restart the Microsoft Exchange Search Host Controller service.
Found the Index files in Crawling state as expected instead of Unknown.
Once all the Active copies are healthy and still the copies in failed and suspended state, then you can reseed the catalog files only using the below command
Update-MailboxDatabaseCopy -Identity BD\MBserver –CatalogOnly
Good Luck..
Regards,
Ayman Saleh

Exchange Server 2013 restarts frequently after Cumulative Update 3 is installed

Hi All,
In our Environment Exchange Server 2013 CU3 is installed and restarts every alternate days.Below are the details
Event Id : 6008
The previous system shutdown at 03:13:44 on ‎12-‎06-‎2014 was unexpected.
Evend Id : 1001
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xfffffa800e9a8080, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061214-30108-01.
Event 41, Kernal Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Can somebody help me through this because it was causing severe to our organization and restarts frequently as well.

Hello,
Try following solutions:
http://support.microsoft.com/kb/2883203/en-us
http://itsalwaysmyproblem.com/2013/08/27/exchange-2013-and-bugcheck-0x000000ef/
Also installing CU5 may be helpful.
Hope it helps,
Adam
www.codetwo.com
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
find the answer faster.

Exchange Server 2013 Installation error

Hi Support,
I have try to install exchange server 2013 on server 2012. after configure active directory when try to install exchange server command Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\system32>CD\
C:\>E:
E:\>cd pradeep\Ex Setup 2013
E:\pradeep\EX Setup 2013>Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseT
erms
Welcome to Microsoft Exchange Server 2013 Unattended Setup
Copying Files...
File copy complete. Setup will now collect additional information needed for
installation.
Performing Microsoft Exchange Server Prerequisite Check
Prerequisite Analysis FAILED
A reboot from a previous installation is pending. Please restart the system
and then rerun Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150
)/ms.exch.setupreadiness.RebootPending.aspx
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
E:\pradeep\EX Setup 2013>

Hi ,
Please have a look in to the error message
"A reboot from a previous installation is pending. Please restart the system
and then rerun Setup."
Reboot the server and try again .
Please reply me if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Installation error for Exchange Server-2013

I am trying to install exchange server-2013 on my Windows server-2012
machine. I have configured per-requisite applications and develop the server environment with active directory roles.
At my readiness check option, it shows the following error:-
"An unsupported operating system was detected . Exchange server-2013 client access and mailbox server roles support windows server -2008R2 SP1 or later and windows server-2012".
I am not using any V-machine or option. So how do i resolve the issue to install the Exchange server-2013? Please help me.
Regard
Azad
Azadur Sarker 6, Seaford street Stoke-on-Trent, ST4 2EU

Hi I found after promoting the exchange server as a Domain controller re-installing AD prep and running extending Schema completed successfully , I'm now able to get rid of exchange cmdlet logs event id and can successfully see and connect through the
exchange 2013 management shell
"Get-Exchangeserver"
However still not able to connect to https://localhost/eac and when i re-run setup
01-28-2014 21:10:16.0804] [0] Starting Microsoft Exchange Server 2013 Setup
[01-28-2014 21:10:16.0804] [0] **********************************************
[01-28-2014 21:10:16.0804] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[01-28-2014 21:10:16.0804] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[01-28-2014 21:10:16.0804] [0] Setup version: 15.0.516.32.
[01-28-2014 21:10:16.0804] [0] Logged on user: TESTLAB\Administrator.
[01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='sourcedir', Value='D:\'.
[01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='mode', Value='Install'.
[01-28-2014 21:10:16.0882] [0] RuntimeAssembly was started with the following command: '/sourcedir:D: /mode:Install'.
[01-28-2014 21:10:17.0085] [0] The following roles are installed: BridgeheadRole AdminToolsRole
[01-28-2014 21:10:17.0726] [0] Setup is choosing the domain controller to use
[01-28-2014 21:10:17.0820] [0] The MSExchangeADTopology has a persisted domain controller: Exch2013.Testlab.labyyz.testnet.rim.net
[01-28-2014 21:10:18.0023] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use Exch2013.Testlab.labyyz.testnet.rim.net
[01-28-2014 21:10:18.0023] [0] Setup is choosing a global catalog...
[01-28-2014 21:10:18.0023] [0] Setup has chosen the global catalog server Exch2013.Testlab.labyyz.testnet.rim.net.
[01-28-2014 21:10:18.0023] [0] Setup will use the domain controller 'Exch2013.Testlab.labyyz.testnet.rim.net'.
[01-28-2014 21:10:18.0023] [0] Setup will use the global catalog 'Exch2013.Testlab.labyyz.testnet.rim.net'.
[01-28-2014 21:10:18.0023] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0038] [0] Exchange organization container for the organization is 'CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0054] [0] Setup will search for an Exchange Server object for the local machine with name 'EXCH2013'.
[01-28-2014 21:10:18.0210] [0] Exchange Server object found : 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0210] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[01-28-2014 21:10:18.0210] [0] The following datacenter roles are unpacked:
[01-28-2014 21:10:18.0210] [0] The following roles are installed: BridgeheadRole AdminToolsRole
[01-28-2014 21:10:18.0210] [0] The local server has some Exchange files installed.
[01-28-2014 21:10:18.0226] [0] Server Name=EXCH2013
[01-28-2014 21:10:18.0242] [0] Setup will use the path 'D:\' for installing Exchange.
[01-28-2014 21:10:18.0257] [0] Setup will discover the installed roles from server object 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0257] [0] 'BridgeheadRole' is installed on the server object.
[01-28-2014 21:10:18.0257] [0] The installation mode is set to: 'Install'.
[01-28-2014 21:10:39.0632] [0] An Exchange organization with name 'TestLab' was found in this forest.
[01-28-2014 21:10:39.0632] [0] Active Directory Initialization status : 'True'.
[01-28-2014 21:10:39.0632] [0] Schema Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] Organization Configuration Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] Domain Configuration Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] The locally installed version is 15.0.516.32.
[01-28-2014 21:10:39.0632] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[01-28-2014 21:10:39.0664] [0] Applying default role selection state
[01-28-2014 21:10:39.0710] [0] Setup is determining what organization-level operations to perform.
[01-28-2014 21:10:39.0710] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
[01-28-2014 21:10:39.0710] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[01-28-2014 21:10:39.0710] [0] InstallModeDataHandler has 0 DataHandlers
[01-28-2014 21:10:39.0710] [0] RootDataHandler has 1 DataHandlers
[01-28-2014 21:10:40.0273] [0] Finished loading screen IncompleteInstallationDetectedPage.
[01-28-2014 21:11:08.0117] [0] Setup is determining what organization-level operations to perform.
[01-28-2014 21:11:08.0117] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
[01-28-2014 21:11:08.0117] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[01-28-2014 21:11:08.0117] [0] InstallModeDataHandler has 0 DataHandlers
[01-28-2014 21:11:08.0117] [0] RootDataHandler has 1 DataHandlers
[01-28-2014 21:11:08.0335] [0] Finished loading screen SetupProgressPage.
[01-28-2014 21:15:30.0513] [0] End of Setup
[01-28-2014 21:15:30.0513] [0] **********************************************

Exchange Server 2013 CU3 Installation Error - Fresh Installation

Similar Messages

Maybe you are looking for