Exchange Server 2013: Failed to connect. Winsock error code: 10060, Win32 error code: 10060.

Dear All,
I have exchange server 2013 running with windows server 2012.
My email server have been send and receive email with internal and external as normal.
Today, i got the problem the email cannot send out to external and get the error below:
Please comment.
BR,
Khemarin
[email protected]

Hi Khemarin,
If it is Smarthost, are you able to telnet your smarthost using 25 port number?
Also please check your Send Connector setting.
http://technet.microsoft.com/en-us/library/aa998662(v=exchg.150).aspx
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Similar Messages

Exchange Server 2013 // MFCMAPI could connect with errors

While connecting with Exchange Server 2013 I have started facing problem with my application.
My application fails to connect to Exchange with below parameters, then i have tried using MFCMAPI to if everything is okay. MFCMAPI could connect with above errors.
And I have tried with program using below parameters, i still get network error from MAPI call. Can you kindly help, I can provide any additional
details needed.
___ props[prop_count].ulPropTag = PR_PROFILE_UNRESOLVED_NAME;
    props[prop_count].Value.lpszA   = <ProfileUnresolvedName>;
    prop_count++;
    props[prop_count].ulPropTag     = PR_PROFILE_UNRESOLVED_SERVER;
    props[prop_count].Value.lpszA   = <[email protected]>;
    prop_count++;
    // Setting this to TRUE causes OpenMsgStore() to fail with MAPI_E_UNCONFIGURED
    props[prop_count].ulPropTag      = PR_CONVERSION_PROHIBITED;
    props[prop_count].Value.b        = FALSE;
    prop_count++;
    props[prop_count].ulPropTag     = PR_PROFILE_CONFIG_FLAGS;
    props[prop_count].Value.l       = CONFIG_SERVICE /*| CONFIG_PROMPT_FOR_CREDENTIALS
| CONFIG_SHOW_CONNECT_UI */;
    prop_count++;
    props[prop_count].ulPropTag     = PR_DISPLAY_NAME;
    props[prop_count].Value.lpszA   = <Mailbox Profile Name>;
    prop_count++;
    //Above setting used to be sufficient to connect using RPC
    //Below parameters added to connect via HTTPS
    LPSTR pwszUser = "domain\\username"; //also tried
[email protected] AND username
    LPWSTR pwszPassword = L"paswword"; // Password has been encrypted using CryptProtectData
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_W;
   props[prop_count].Value.lpszW = L"https://ProxyHostname.domain";
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_AUTH_PACKAGE;
    props[prop_count].Value.l = RPC_C_AUTHN_NONE;      // RPC_C_HTTP_AUTHN_SCHEME_NTLM,
RPC_C_HTTP_AUTHN_SCHEME_BASIC
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_FLAGS;
    props[prop_count].Value.l = PRXF_ENABLED | PRXF_SSL;// | PRXF_IGNORE_SEC_WARNING; // | PRXF_IGNORE_SEC_WARNING;
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_PRINCIPAL_W;
    props[prop_count].Value.lpszW = L"msstd:certificateserverhostname.domain";
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PACKAGE;
    props[prop_count].Value.l = RPC_C_AUTHN_GSS_NEGOTIATE;
// RPC_C_AUTHN_WINNT, RPC_C_AUTHN_GSS_NEGOTIATE, RPC_C_AUTHN_NONE
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_USER_W;
    props[prop_count].Value.lpszA = pwszUser;
    prop_count++;
    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PASSWORD;
    props[prop_count].Value.bin.lpb = dataBlobOut.pbData;
    props[prop_count].Value.bin.cb = dataBlobOut.cbData;
    prop_count++;
    DB( (DB_PR _T("ConfigureExchangeService() About to configureMsgService\r\n"),
this ) );
    hres = lpServiceAdmin->ConfigureMsgService( exchUID, 0, config_flags, prop_count, props
    I still get MAPI_E_NETWORK not found
Are there any configuration changes need to be done on Exchange Server?
Is there any mistake in above parameters?
Kindly suggest.

You can refer Dave's blog post @
http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx
DeVa, M.S., {MSFT} Please remember to mark the replies as answers if they help

Exchange Server 2013 failing Readiness Checks

Here are the list of errors it reports
Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
My user is in the Enterprise Admins group.
Error:
The local domain needs to be updated. You must be a member of the 'Domain Admins' group and 'Organization Management' role group, or 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.LocalDomainPrep.aspx
My user is in the Enterprise Admins group and it is also in the Organization Management Role
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
I am
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
I am
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
I am
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
I am
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
I am
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
I am
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
I am
Error:
Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have been created but have not yet replicated to the local domain. Wait for replication to complete and then run setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
While this is showing up, I do have the Exchange objects availabe on all of my DCs in all of the sites.
Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Its currently at 2008 Which is the highest I can make it in my organization at this time.
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
I'm able to communicate with all the DCs from the machine I'm attempting to install exchange on.
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Has anyone encounterd this?
I've run Setup /PrepareSchema and Setup /PrepareAD on the DC in the site Exchange specified.
I have installed all of the Prereqs
Here's an example of my set up
One Forest
AwesomeCompany.net -
There's Two sites
Atlanta-HeadQuarters
Atlanta-DataCenter
and Two Sub Domains
HeadQuarters
DataCenter
Exchange Machine is in Atlanta-DataCenter Site and attached to DataCenter domain.
Exchange requested the /PrepareAD and /PrepareSchema be run on a Domain Controller in the root domain that is in site Atlanta-HeadQuarters.
Any guidance would be appreciated.

Hello,
Just for double confirm, please run “WhoAmI” in CMDlet and see if you are using a local admin account.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange Server 2013 failover design

Hello:
I'm designing a failover Exchange Server 2013 solution. I only need mail and calendar services.
I'm planning to put two physical servers with Windows Server 2012 R2 with (or without) Hyper-V to run one virtual machine in
each physical server.
I don’t have external storage device, I like to use database replication
Also, I have a physical third party anti-spam firewall
The questions:
I need one VM for Mailboxes and a separate one for CAS (4 VMs in total) or I can install 2 VMs with MBX+CAS in each VM server?
I need a third server to avoid brain duplication, or isn’t needed?
Exchange Server 2013 supports POP3 connections?
Thanks for your time, and sorry for my bad English!
Un saludo! Juan Segura

The questions:
I need one VM for Mailboxes and a separate one for CAS (4 VMs in total) or I can install 2 VMs with MBX+CAS in each VM server? - Definitely you can go for multi-role servers
to combine MBX+CAS and in fact that's
recommended except couple scenarios.
I need a third server to avoid brain duplication, or isn’t needed? You need a witness server but that can be non-Exchange server too. You need to add Exchange trusted subsystem
in Local Admin group of that server
Exchange Server 2013 supports POP3 connections? - Yes, you can have POP3 connections
Blog |
Get Your Exchange Powershell Tip of the Day from here

Connecting to Exchange Server 2013 using IMAP command gives authenication error

Hello All,
My application (it is a C# code) connects to Microsoft exchange server 2013 using POP3 and IMAP, processes the emails, marks as read and move to particular folder if it is processed successfully else to an different folder. In this sometimes,
I am getting authentication failed error from IMAP however same mail is processed when it is executed next time. Few times it is processed with out error. I am not sure what is causing this issue.We are connecting to IMAP using tcpIMAP command.
This is the same application which we used with exchange server 2010 now we are upgrading to exchange server 2013. I have verified that the setting of exchange 2010 and 2013 are the same.
To verify the IMAP command I created a sample application using C# which will try to connect to IMAP service and log in to exchange server 2013; it fails to authenticate the user after connecting for few times and then it starts to authenticate
successfully then again fails for few times and then authenticates. I am not sure why this is happening.
Please suggest how can I resolve this.
Thank you, Santha

Since I've upgraded to Snow Leopard I've also moved from Entourage 2008 to Mail, iCal & Addressbook with the new Exchange support.
My company exchange server is Exchange 2007.
Mail works fine except the occasional Mail crash.
iCal worked fine the first two days and then it came with an error the it cannot connect to the Exchange server and asks me to type my email address again. Doesn't work so I need to put my exchange calendar in iCal in offline. But now there is no syncing with the Echange server.
This only occurs when I add a meeting request in iCal.
My Exchange administrator has reset my mailbox on the Exchange server.
This helped for about 4 hours. Now it's the same problem.
I have a feeling the when you setup your exchange account in Mail it uses different settings for Mail and iCal with the autoconfig.
Anybody has a solution? My Exchange admin cannot find any problems on his side. Do I need to make changes on my iCal client or do we need to wait for OS 10.6.1 ?

Exchange Server 2013: no send/receive after failed CU1- CU2 and machine restore

Hi!
For several reasons, I decided to fully restore my Exchange Server 2013 machine today.
The machine is virtualized on Hyper-V.
I rebooted the server and recovered from backup and Exchange seems to be working fine. However, I cannot receive or send mail. If I try to send a message it goes to the "drafts" folder. OWA and EMC is working. I can not send mail between interna mailboxes
either. Outlook says disconnected.
When running the Exhchange Connectivity Analyzer, I get the following:
- Receive: Connection was successful but no banner was received.
- Send: Successfull. However when trying to send mail to external mailbox it does not reach that mailbox.
Mailflow was working perfectly at the time of the backup.
Help is much appreciated!
UPDATE 1: When telnet on local server i get SMTP banner. But not on other computers in same subnet.

OK. After fiddeling around in ADSIedit and trying to rebuild my Exchange environment I ended ut breaking it completely.
I then restored both my DC (Exchange schema CU2) and my EX (Exchange schema CU1). Scema Versions where the inconsistent as stated.
Then I uninstalled the KB2874216 successfully. After that i tried to Upgrade Exchange to CU2. The Upgrade failed at Mailbox Role: Mailbox Service With error Message:
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{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";
              $dispname = "Microsoft Exchange";
              $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0)
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if ($dbs.Length -ne 0)
                  $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                  if ($arbUsers.Length -ne 0)
                    $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;
              else
                if ($mbxs[0].DisplayName -ne $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)
                  Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                  set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;
                  # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.
                  # This can be remove after BUG(O15#2555914) is fixed.
                  if ($sysMbx.RetentionPolicy -eq $null )
                     $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});
                     set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;
              else
                Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");
            else
              write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."
        " was run: "Database is mandatory on UserMailbox. Property Name: Database".
Seems the problem was corrupted arbitrary system mailboxes from previous Exchange 2010 to Exchange 2013 migration.
The solution for me was to restore the corrupted arbitrary mailboxes using this
LINK. It is for 2010 but Works on 2013.
I am now currently on Exchange CU2 on both my EX server and on my DC. Now I have to check mail flow and will report back.

Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

Hi Team,
Need urgent help in resolution of following error:
Environment Details: VMware ESXi 5.5 (vMotion)
Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
Prerequisites: Installed
Error: Installation gives Error at Step 10 during installation of Mailbox Service
Error Details Below:
Error:
The following error was generated when "$error.Clear();
if ([Environment]::OSVersion.Version.Major -ge 6)
$WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
$reg= join-path (join-path $env:SystemRoot system32) reg.exe;
$servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
if ((get-service wsbexchange).Status -eq "Running")
Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
Exchange /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
/f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
" was run: "Process execution failed with exit code 1.".

Resolved ! :)
Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
Thanks to all.

Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

What am I trying to do?
I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
What am I running?
2 X DC on domain and forest functional level 2008R2 both writable
1 X fresh install of Windows 2012 R2 which is domain joined
What have I tried?
Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log
Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe
setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Making sure the following path has full permissions:
EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good
What have I noticed that is suspicious?
Microsoft Exchange Transport service will not start even though both of its dependences services have started:
Microsoft Filtering Management Service
Microsoft Exchange Active Directory Topology Service
It will eventually error with
“Windows could not start the Microsoft Exchange Transport Service on local computer
Error 1053: This Service did not respond to the start of control request in a timely fashion”
This error is from the GUI wizard itself:
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.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, 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)".
Exchange logs which have been written:
**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
[01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
'{ mydomain.com}'
[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, 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)
[01/20/2015 17:13:50.0288] [1] [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.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, 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)".
[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
Windows Event Viewer:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
in either the local site 'Default-First-Site' or the following sites:

Hi apl228,
1. Please make sure the IPv6 is enabled.
2. Please make sure the account that install Exchange server has Administrator permission.
3. Please make sure DNS has been configured correctly.
Thanks
Mavis Huang
TechNet Community Support

Exchange Server 2013: Installation fails

Migrating SBS 2008 to Windows Server 2012 R2 (no virtualization) and Exchange Server 2013 SP1
(1) ADprep on SBS 2008 went fine
(2) Installed necessary feature for Exchange (website “Part 1: Step-by-Step Exchange 2007 to 2013 Migration”)
A) the first time I installed Exchange 2013, the setup succeeded, however there were several ecp/WinRM errors.
B) restored Windows Server 2012 R2 to the state (2). Removed from AD (ADSI Edit)
… CN=Services; CN=Exchange; CN=First Organization; CN=Exchange Administrator Group; CN=Servers
delete new Win 2012 server
Run Exchange setup again:
The following error was generated when "$error.Clear();
if ($RoleStartTransportService)
start-SetupService -ServiceName MSExchangeTransport -MaxWaitTimeForRunningState 0:0:40
" was run: "Service 'MSExchangeTransport' failed to reach status 'Running' on this server.".
Checked:
- IPv6 is enabled, but was setup correctly after installing ADDS role)
- Administrators (Group) is a member of the Exch. Trusted Subsystem
Probably there is an AD problem, after the restoration (B) (bare metal) of the Win 2012 server.
Please help!
Fulco

Hi
the error states that the MSExchangeTransport service failed to start. Can you manually try starting the service and then run the setup again?
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.

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

Exchange Server 2013 installation error at Step 10/15

I try to install Exchange Server 2013 on a fresh install of Windows Server 2012.
Windows Server 2012, have already install on it:
AD CD
DNS
IIS
Exchange 2013 Prerequisites for Win.Server 2012 like described here
http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
And the (winner) error message is:
Exchange Server component Mailbox role: Client Access service failed.
Error: Error:
The following error was generated when "$error.Clear();
Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController
        " was run: "Could not grant Network Service access to the certificate with thumbprint ABC7C6378BF63CED166794CFBF410C73B29EDD3A because a cryptographic exception was thrown.".
I search online for a solution and I found many others with same problem but any solution yet. :(
If anyone can help me I am able to dedicate him my next ode.
Thank you,
Adrian

I am experiencing the same problem except that mine is definitely NOT a domain controller. The error code indicates that the process is attempting to grant Network Access to the Certificate during Setup, but fails.
"...Could not grant Network Service access to the certificate"
Exchange 2013 is being installed on Windows Server 2012 R2 but it is a member server with no domain responsibilities. Granting rights to the certificate during the Setup process is the root of the problem.
Here is the complete error comment:
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController
        " was run: "Could not grant Network Service access to the certificate with thumbprint 681FC4E2C66D726EFB91A8E0FF7FF6F98942C2F4 because a cryptographic exception was thrown.".

Exchange Server 2013 SP1 Standard: Installation failing can't progress

I'm trying to install Exchange Server 2013 and I keep getting this error and I am unable to progress, I can't find any support on the issue and frankly I don't want to/can't afford to spend $500 to ask Microsoft for technical support (what kind of racket
do they think they're running?).
The error message:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
Yet, I see no PushNotifications virtual directory or anything remotely related to that on IIS or in the inetpub folders and files. If I try to resume the set-up after this error I get:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The AD configuration for virtual directory 'PushNotifications' already exists in 'CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local', please remove this AD configuration manually.
Parameter name: VirtualDirectoryName".
And I have to remove this config using ADSI Edit, which just returns me to the first error.

1. Prodution
2. Just 1 DC for 1 site.
3. Setup.EXE
4. Matches SP1 version numbers
5. That's just what was made available to me via MSPP, the installer doesn't see any updates?
6. Here is the log files:
[03/23/2015 22:06:52.0940] [1] Setup failed previously while performing the action Install. Looking for the failed task with ID ClientAccessComponent___75f8c93d15314369983d33ec0742e189.
[03/23/2015 22:06:52.0941] [1] 131 tasks were found to run.
[03/23/2015 22:06:52.0941] [1] Processing component 'Client Access Configuration' (Configuring Mailbox role: Client Access service.).
[03/23/2015 22:06:52.0941] [1] Executing:
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
[03/23/2015 22:06:52.0955] [2] Active Directory session settings for 'New-PushNotificationsVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'SVR01.OFFICE.local', Preferred Global Catalog: 'SVR01.OFFICE.local', Preferred Domain Controllers: '{ SVR01.OFFICE.local }'
[03/23/2015 22:06:52.0956] [2] User specified parameters: -Role:'Mailbox' -DomainController:'SVR01.OFFICE.local'
[03/23/2015 22:06:52.0956] [2] Beginning processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:52.0999] [2] Searching objects "SVR02.OFFICE.local" of type "Server" under the root "$null".
[03/23/2015 22:06:53.0066] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:53.0068] [2] Processing object "SVR02\PushNotifications".
[03/23/2015 22:06:56.0763] [2] The properties changed on the object '' (CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local) are: "{ MetabasePath[msExchMetabasePath]='IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications', AuthenticationMethodFlags[msExchInternalAuthenticationMethods]='Ntlm, WindowsIntegrated', AuthenticationMethodFlags[msExchExternalAuthenticationMethods]='Ntlm, WindowsIntegrated', Id[distinguishedName]='SVR02\PushNotifications (Exchange Back End)', InternalAuthenticationMethods[msExchInternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, ExternalAuthenticationMethods[msExchExternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, OrganizationId[msExchOURoot, msExchCU]='' }".
[03/23/2015 22:06:56.0764] [2] Saving object "SVR02\PushNotifications (Exchange Back End)" of type "ADPushNotificationsVirtualDirectory" and state "New".
[03/23/2015 22:06:57.0073] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:57.0587] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:57.0591] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0378] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0378] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0386] [2] Ending processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:58.0388] [1] The following 1 error(s) occurred during task execution:
[03/23/2015 22:06:58.0388] [1] 0. ErrorRecord: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] 0. ErrorRecord: System.InvalidOperationException: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it. ---> System.Runtime.InteropServices.COMException: Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
at Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath)
at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, String moduleName, String moduleType, ExchangeVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetLiveIdBasicAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, ADExchangeServiceVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServiceVirtualDirectory`1.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewPushNotificationsVirtualDirectory.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[03/23/2015 22:06:58.0389] [1] [ERROR] The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
[03/23/2015 22:06:58.0389] [1] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0390] [1] [ERROR-REFERENCE] Id=ClientAccessComponent___75f8c93d15314369983d33ec0742e189 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03/23/2015 22:06:58.0390] [1] Setup is stopping now because of one or more critical errors.
[03/23/2015 22:06:58.0390] [1] Finished executing component tasks.
[03/23/2015 22:06:58.0406] [1] Ending processing Install-ClientAccessRole
It says it can not log on with the supplied details, but the account is an Administrator account with full privileges so I can't see why this would be the case.

Exchange Server 2013 Missing file on ISO install Error Code 1603

Hi all, a mystery needs solving any suggestions much appreciated:
We are trying to install Exchange Server 2013 on Windows 2012 server.
The ISO File being used is: SW_DVD9_Exchange_Svr_2013w_SP1_MultiLang_Std_Ent_MLF_X19-35118
All preparation and requisites in place.
During Stage 2 Copying files, we receive an error code 1603 and installation halts.
The error states:
Installing product F:\exchangeserver.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'Source file not found: F:\Setup\ServerRoles\ClientAccess\Owa\prem\version\resources\themes\base\0\microsoft.o365.controls.timeline.mouse.css.
Verify that the file exists and that you can access it.'.
We have verified that the Path in the error is correct and exists BUT the file is not present within the 0 folder.
We have downloaded the ISO from our Action Pack resources twice and attempted 4 separate installations.
We have tried both Mailbox/Client Access and Mailbox only installations.
The missing file: microsoft.o365.controls.timeline.mouse.css. Hopefully the only file misisng???
Any ideas anyone, could we source a different ISO or copy of the file or ?????
Many thanks in advance

Had the same issue with Exchange 2013 SP 1 Downloaded as an ISO from the Volume License Center, installing on a new Server 2012R2 STD box. I found the equivalent file in another ISO but discovered it was just an empty CSS file. So the easiest way is to not
bother trying to find the file but: 1) open notepad, 2) set save to "All Files", and 3) save an empty CSS file with that filename then place it in the directory indicated in the path given in the error. (Make sure it saves as
a CSS and not as a TXT.)
I reran the install and it completed without issue.

Http 500 internal server error exchange server 2013

Hello Everyone
Here is my little scenario.
i have a domain named contoso.com
i then installed exchange server 2013 in my environment. cas and mailbox server are on seperate box.
switched of my exchange servers for a week, during that period i changed the netbios name of my domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
a week later i switched on my exchange servers. during the same time i created two new servers one cas and the other mailbox
i now have 2 cas server and 2 mailbox server
problem now is that when i log into my ecp on one of my cas server using https://servername/ecp. after inserting my username and password i get http 500 internal error
although with exchange management shell i can connect to all the servers

-->switched of my exchange servers for a week, during that period i changed the netbios name of my
domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
Did you change your domain to toso.com? If yes then your first/previously installed exchange is broken. Exchange server is fully integrated with domain.
Renaming of domain is not supported in Exchange2007/2010/2013. (Even in Exchange2000/2003 you need some netbios name resolution. Check this for an info)
Anyway did you try login to the newly installed exchange (i.e. Exchange installed after Netbios rename)?
Try that first https://newserverip/ECP and https://newserverip/OWA (that is supposed to work), If
that works I suggest you try to uninstall the previously installed Exchange after moving the database using database portabilityand install again as new
server.
Please get back with the result.
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Issues trying to recover failed Exchange Server 2013 in a DAG

Having several issues attempting to recover a failed Exchange Server 2013. To start out, the failed server was mounted on a virtual server using hyper-v. The virtual server failed due to some hard drive partition issues and would no longer boot. As there
really was no purpose to having Exchange on a Virtual Server I decided to rename the host to the same name as the virtual server. I reset the name in AD and proceeded to rename the server. Then made sure all the necessary things were installed and proceeded
to do a recovery installation. I neglected to properly delete the old databases belonging to that server. I simply deleted the files off the hard drive instead of doing it properly. I should mention this is a two node plus witness server installation.Now,
it seems I cannot delete the former server in either ECP or command line. I have attempted to clean up the mess with the old databases but there is one that was mounted only on the failed server that I cannot remove. It seems until I can remove that, I cannot
remove the failed server from the DAG and do a recovery install. The steps shown in the tech net articles to remove a failed database have also failed. At this point I am wondering if I should just give up on the server name and do an install on a new server
name or if someone can give me some information on how to clean up the mess, that would be better I am sure. Here is a list of the things I have tried.
https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx and in this article, the item mentioned is not in ADSIedit.
http://exchangeserverpro.com/unable-remove-failed-server-dag-exchange-server-2010/
http://exchangeserverpro.com/exchange-2013-how-to-remove-dag-member/ This
article describes one of the problems I am having but the solution is not there.
Thanks to any and all who can offer advice.
Ronald C. Pope

Thank you for your answer. Running that command results in the following:
[PS] C:\Windows\system32>Remove-MailboxDatabase "Mailbox Database 0939719168"
This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or
arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database"Mailbox Database 0939719168". To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of
archive mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Archive. To get a list of all
public folder mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -PublicFolder. To get a
list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Arbitration.
To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID> -Archive. To disable a public folder mailbox so that you can delete the mailbox database, run the command
Disable-Mailbox <Mailbox ID> -PublicFolder. Arbitration mailboxes should be moved to another server; to do this, run
the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command
Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox.
Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID>
-Database "Mailbox Database 0939719168".
    + CategoryInfo          : InvalidOperation: (Mailbox Database 0939719168:DatabaseIdParameter) [Remove-MailboxDatab
   ase], AssociatedUserMailboxExistException
    + FullyQualifiedErrorId : [Server=EX01,RequestId=69b60793-fc4f-4dac-beb9-8c9afe381a36,TimeStamp=1/26/2015 6:28:34
   PM] 2BA41E0C,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveMailboxDatabase
    + PSComputerName        : ex01.<domain>com
I was able to disable the one mailbox that was listed for the database. I got the following error when attempting the command Get-Mailbox -Database"Mailbox Database 0939719168"
[PS] C:\Windows\system32>Get-MailboxPlan Database "Mailbox Database 0939719168"
Get-MailboxPlan : The term 'Get-MailboxPlan' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
+ Get-MailboxPlan Database "Mailbox Database 0939719168"
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-MailboxPlan:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
the public folder and archive switch simply return a command prompt leading me to believe that there are no public or archive boxes on that database.
Ron

Exchange Server 2013: Failed to connect. Winsock error code: 10060, Win32 error code: 10060.

Similar Messages

Maybe you are looking for