Exchange Server 2013 - 550 5.7.1 Unable to Relay

Hi Guys,
I have recently setup Exchange 2013, I have been having an issue were the Emails that we are attempting to send are getting stuck in the 'Drafts' box. I decided to use Telnet to see if I could send emails that way but much to my disappoint I was unable to
send emails to external contacts using Telnet getting the following error '550 5.7.1 Unable to relay'.
For my external server lookup I have my internal DNS Server for the DNS and my internal DNS Servers forward DNS Requests to Google's Public DNS Servers (8.8.8.8 and 8.8.4.4). I have tried removing Google's DNS Settings and just using my internal servers
and using Google's DNS Server and not our internal DNS Settings.
Does anyone have any suggestion on what might be causing this issue. I have been working through the solution in other posts on other web sites but so fare not much luck.
Kind Regards
Thomas Park
Network Engineer   
TPark IT Technician

Hi,
Please check whether the Windows services that Exchange requires on a server have started via Test-Servicehealth. Especially Exchange Transport service and Mailbox transport service.
Please add the IP address of our DNS server for testing.
Please also re-configure our Relay Connector, found a useful article for your reference:
How to Configure a Relay Connector in Exchange Server 2013
http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
If still not working unfortunately, please trace these messages via Message Tracking to check whether there is any error. If has, please post the details for the further troubleshooting.
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

  • Server Response: 550 5.7.1 Unable to relay

    SBS 2011 I have exchange 2010,
    Internally Outlook send/ Receive working fine-- Local Ip address.
    Owa Send/Receive working fine.
    But remote user can receive the Emails, But cant send the emails.
    Subject 'tes'
    Server Error: 550
    Server Response: 550 5.7.1 Unable to relay
    Server: 'xxx.xxx.xxx.xxx'---- Public IP address
    Windows Live Mail Error ID: 0x800CCC79
    Protocol: SMTP
    Port: 25
    Secure(SSL): Yes
    How to fix this issue ?

    Hi,
    Did you create a relay connector to allow to relay in Exchange? About how to create a relay connector, you can refer to the following article.
    How to Configure a Relay Connector for Exchange Server 2010
    http://exchangeserverpro.com/how-to-configure-a-relay-connector-for-exchange-server-2010/
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    To allow a device to use Exchange to relay a message to an outside recipient, you also need the ms-Exch-SMTP-Accept-Any-Recipient attribute.
    Get-ReceiveConnector -Identity relayconnector | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Server error: '550 5.7.1 Unable to relay' with authoritative domain

    Hi,
    When trying to send email to external clients from outlook with (POP accopunts)with authoritative domain email address. we are receiving "Server error: '550 5.7.1 Unable to relay"Where internal emails are going properly.It use to work early &
    it stopped suddenly yesterday we did not made any changes in SMTP.
    We are able to send & Receive emails with our own domain facing  problem only with authoritative domain email address.
    Regards,
    Perumal P

    Hi,
    I recommend you refer to the following article to configure the outlook 2010/2013 using IMAP or POP3, and check the result:
    Set Up Outlook 2010 for IMAP or POP Access to Your E-Mail Account
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Error 550 5.7.1 unable to relay with SMTP PORT 25 Exchange 2013

    Hi All,
    I know this issue has been posted for a while, but still can't resolved issue. We've new Exchange 2013 SP1 (CU4) installation, everything is working properly, the OWA, Exchange Client Connection, SMTP/POP with SSL, except with SMTP Using Port 25 Non-Encrypted
    Connection.  
    If I'm using the SMTP Port 25 without TICK "My Outgoing Server (SMTP) Requires authentication", I've got the error: "550 5.7.1 Unable to relay", but if I TICK the option above, my message will be deliver without any error, how do i get
    rid this problem, I need to UN-TICK the option above for the time being, since we've hundreds email account, I want to avoid to educate and tell the user and even remote their PC, just to configure this issue, it will drive me crazy, we're going to use the
    Exchange Client Connection in the future, If everything is smooth and ok.
    I research this problem on the Internet and of course with TECHNET, but still can't, anyone can help me on this?
    fyi, I tried so many things, delete the default the Default Front End Transport for Port 25, it also not fix my issue.
    Thx
    Irwan

    Hi
    You can paste the output of below result
    Get-receiveconnector | fl name,bindings,PermissionGroups
    I think your default receive connector should be missing out some permissions.
    Also try to see if you get any message on protocol logs and paste them too
    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 Thanks Sathish
    (MVP)

  • Exchange Server 2013 In Windows Server 2012 - unable to logon EXchange Administrator Center (EAC)

    Hi All,
    I Just installed Exchange Server 2013 in Windows Server 2012 and trying to connect Dynamics CRM 2013 (DNS).
    The Installations Success full but unable to load the EAC page by using the following URL
    https://servername:port/owa/auth/logon.aspx
    I have cross checked in Exchange/owa/auth folder don't have the "logon.aspx" file 
    But the auth folder have the "logoff.aspx" 
    I installed many time freshly in separate WS-2012 but it not contains that logon.aspx 
    I want access the Exchange Administrator Center 
    Please Help me to solve it 
    IIS Exchange (Missing of logon.aspx)
    SRKD0808

    Hi All,
    I sorted out this problem 
    Actually we have to run these 2 commands in Domain Control, But what i did  I just run this
    1) setup /PrepareSchema /IAcceptExchangeServerLicenseTerms
    Command in Domain Control we don't need to run the 2nd command, Because I already try to installed exchange 2013 very first time it success and after some modifications
    it gone.
    That time it will ask you to provide Organization name, Once you give that it will create the Organization name in Domain control and it will save the settings when
    you install first time 
    Because of this reason It is failing to run these 2 command
    Finally what i did I just revert back my Domain control snapshot & Exchange server as well 
    Then i started freshly Installation in DC and Exchange server 2013 successfully installed 
    URL http://servername/ecp/default.aspx
    Whole Process will be here 
     Exchange Server 2013 Step by Step Installation In Windows Server 2012
    SRKD0808

  • How can I clone a completed Exchange Server 2013 in a Lab Enviroment?

    I was having great time with my Exchange Server 2013 until I tried to clone it to avoid fresh installation of another Exchange 2013 server. Steps taken
    (1)Clone the Exchange1 and turn it off
    (2) Brought the Clone Exchange2, renamed it, change the IP configurations,
    (3) Re-ran the ADprep/Doamin prep
    (4) Checked the ASDIedit to verify the Schema/configuration in AD
    (5) Restarted I and was able to logon to the Exchange2
    (6) Brought up the Exchange1, but unable to logon because the name was no longer in AD database
    What I did to fix this:
    (7) Rejoin the Exchange1 to the domain - and was able to logon
    (8) Unable to access ECP or OWA of any of the two servers.
    (9) Errors received - Fix the configuration file of the application
    My Question - How to I fix the configuration file as suggested (via powershell or GUI or ASDIedit.msc)?
     

    Unless you are cloning an entire environment, and then bringing it up in a seperate isolated environment, it is not supported to simply clone an Exchange Server, and then bring it online in an existing environment and rename it to save on setup and configuration
    time.
    You can script the setup and configuration of Exchange through Powershell, either with scripts or with another product controlling it - something like
    System Center Orchastrator.
    From the script side of things there are many available on peoples blogs. Check
    here.
    Edit: and to be clear, there is no need to re-run any prep tasks against Active Directory when installing a new Exchange Server, unless you are installing into a new domain as part of your Forest.
    Oliver
    Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

  • 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 issue

    Dear Experts,
    Thanks in advance...
    I am not able to Install Exchange server 2013. I have tried my best to Install but not success. Please find my system configuration.
    Dell Laptop Intel I5 1.7 GHZ
    RAM -8GB
    Vmware workstation 9.
    Steps I followed
    Created a VM inside Vmware and Installed windows 2012 Std. Edition
    Memory assigned to VM is 1 GB
    All prerequisites completed and tried to Install Exchange server 2013 SP1
    During installation it asked me to select the  role to Install and I selected Mailbox server role and CAS
    Exchange setup process started at 3 P.M till 9 P.M setup was not finished finally setup process halt and I got the error  setup could not completed .
    Please find the logs for your reference.............
    04/13/2015 08:41:02.0303] [0] **********************************************
    [04/13/2015 08:41:02.0303] [0] Starting Microsoft Exchange Server 2013 Service Pack 1 Setup
    [04/13/2015 08:41:02.0303] [0] **********************************************
    [04/13/2015 08:41:02.0303] [0] Local time zone: (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi.
    [04/13/2015 08:41:02.0303] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
    [04/13/2015 08:41:02.0328] [0] Setup version: 15.0.847.32.
    [04/13/2015 08:41:02.0328] [0] Logged on user: WIN-4D2C2JMF5R1\Administrator.
    [04/13/2015 08:41:02.0336] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
    [04/13/2015 08:41:02.0368] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
    [04/13/2015 08:41:02.0600] [0] Command Line Parameter Name='sourcedir', Value='C:\Softwares\Exch-13'.
    [04/13/2015 08:41:02.0615] [0] Command Line Parameter Name='mode', Value='Install'.
    [04/13/2015 08:41:02.0632] [0] RuntimeAssembly was started with the following command: '/sourcedir:C:\Softwares\Exch-13 /mode:Install'.
    [04/13/2015 08:41:02.0632] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
    [04/13/2015 08:41:05.0504] [0] Finished loading screen CheckForUpdatesPage.
    [04/13/2015 08:41:13.0567] [0] Starting file's copying...
    [04/13/2015 08:41:13.0599] [0] Setup copy files from 'C:\Softwares\Exch-13\Setup\ServerRoles\Common' to 'C:\Windows\Temp\ExchangeSetup'
    [04/13/2015 08:41:13.0794] [0] Finished loading screen CopyFilesPage.
    [04/13/2015 08:41:15.0033] [0] Disk space required: 1826493368 bytes.
    [04/13/2015 08:41:15.0033] [0] Disk space available: 46620041216 bytes.
    [04/13/2015 08:42:55.0484] [0] Finished loading screen InitializingSetupPage.
    [04/13/2015 08:42:55.0484] [0] File's copying finished.
    [04/13/2015 08:43:13.0922] [0] Setup is choosing the domain controller to use
    [04/13/2015 08:43:28.0885] [0] Setup is choosing a local domain controller...
    [04/13/2015 08:43:32.0221] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory server 
    is not available. Error message: Active directory response: The LDAP server is unavailable. 
    See the Exchange setup log for more information on this error.
    [04/13/2015 08:43:32.0335] [0] [ERROR] Active Directory server 
    is not available. Error message: Active directory response: The LDAP server is unavailable.
    [04/13/2015 08:43:32.0366] [0] [ERROR] The LDAP server is unavailable.
    [04/13/2015 08:43:32.0366] [0] Setup will use the domain controller ''.
    [04/13/2015 08:43:32.0366] [0] Setup will use the global catalog ''.
    [04/13/2015 08:43:32.0596] [0] No Exchange configuration container was found for the organization. Message: 'Active Directory server 
    is not available. Error message: Active directory response: The LDAP server is unavailable.'.
    [04/13/2015 08:43:32.0707] [0] The following roles have been unpacked:
    [04/13/2015 08:43:32.0721] [0] The following datacenter roles are unpacked:
    [04/13/2015 08:43:32.0739] [0] The following roles are installed:
    [04/13/2015 08:43:32.0739] [0] The local server does not have any Exchange files installed.
    [04/13/2015 08:43:32.0834] [0] Server Name=WIN-4D2C2JMF5R1
    [04/13/2015 08:43:33.0032] [0] Setup will use the path 'C:\Softwares\Exch-13' for installing Exchange.
    [04/13/2015 08:43:33.0084] [0] The installation mode is set to: 'Install'.
    [04/13/2015 08:43:51.0460] [0] Exchange organization name is required for this mode.
    [04/13/2015 08:43:51.0460] [0] Active Directory Initialization status : 'False'.
    [04/13/2015 08:43:51.0472] [0] Schema Update Required Status : 'False'.
    [04/13/2015 08:43:51.0472] [0] Organization Configuration Update Required Status : 'False'.
    [04/13/2015 08:43:51.0472] [0] Domain Configuration Update Required Status : 'False'.
    [04/13/2015 08:43:51.0536] [0] Applying default role selection state
    [04/13/2015 08:43:51.0565] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:43:51.0565] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:43:51.0565] [0] InstallModeDataHandler has 0 DataHandlers
    [04/13/2015 08:43:51.0565] [0] RootDataHandler has 1 DataHandlers
    [04/13/2015 08:43:52.0848] [0] CurrentResult launcherbase.maincore:90: 0
    [04/13/2015 08:43:53.0067] [0] Finished loading screen WelcomePage.
    [04/13/2015 08:44:06.0654] [0] Finished loading screen EULAPage.
    [04/13/2015 08:44:10.0679] [0] Finished loading screen RecommendedSettingsPage.
    [04/13/2015 08:44:13.0814] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:13.0814] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:13.0814] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:13.0844] [0] InstallModeDataHandler has 8 DataHandlers
    [04/13/2015 08:44:14.0048] [0] Finished loading screen RoleSelectionPage.
    [04/13/2015 08:44:18.0619] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:18.0619] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:18.0619] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 9 DataHandlers
    [04/13/2015 08:44:18.0632] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:18.0632] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:18.0632] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 10 DataHandlers
    [04/13/2015 08:44:18.0632] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:18.0632] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:18.0632] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 11 DataHandlers
    [04/13/2015 08:44:18.0648] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:18.0648] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:18.0648] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:18.0648] [0] InstallModeDataHandler has 12 DataHandlers
    [04/13/2015 08:44:22.0644] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:22.0644] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:22.0644] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:22.0644] [0] InstallModeDataHandler has 13 DataHandlers
    [04/13/2015 08:44:22.0644] [0] Setup is determining what organization-level operations to perform.
    [04/13/2015 08:44:22.0644] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
    [04/13/2015 08:44:22.0644] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
    [04/13/2015 08:44:22.0656] [0] InstallModeDataHandler has 14 DataHandlers
    [04/13/2015 08:46:00.0423] [0] Finished loading screen InstallationSpaceAndLocationPage.
    [04/13/2015 08:46:28.0427] [0] Finished loading screen ExchangeOrganizationPage.
    [04/13/2015 08:46:30.0221] [0] Finished loading screen
    Regards
    Biswajeet

    Hi,
    Please find the DC Health check report.
    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.
    C:\Users\Administrator>dcdiag
    Directory Server Diagnosis
    Performing initial setup:
       Trying to find home server...
       Home Server = EX-13
       * Identified AD Forest.
       Done gathering initial info.
    Doing initial required tests
       Testing server: Default-First-Site-Name\EX-13
          Starting test: Connectivity
             ......................... EX-13 passed test Connectivity
    Doing primary tests
       Testing server: Default-First-Site-Name\EX-13
          Starting test: Advertising
             ......................... EX-13 passed test Advertising
          Starting test: FrsEvent
             ......................... EX-13 passed test FrsEvent
          Starting test: DFSREvent
             ......................... EX-13 passed test DFSREvent
          Starting test: SysVolCheck
             ......................... EX-13 passed test SysVolCheck
          Starting test: KccEvent
             ......................... EX-13 passed test KccEvent
          Starting test: KnowsOfRoleHolders
             ......................... EX-13 passed test KnowsOfRoleHolders
          Starting test: MachineAccount
             ......................... EX-13 passed test MachineAccount
          Starting test: NCSecDesc
             ......................... EX-13 passed test NCSecDesc
          Starting test: NetLogons
             ......................... EX-13 passed test NetLogons
          Starting test: ObjectsReplicated
             ......................... EX-13 passed test ObjectsReplicated
          Starting test: Replications
             ......................... EX-13 passed test Replications
          Starting test: RidManager
             ......................... EX-13 passed test RidManager
          Starting test: Services
             ......................... EX-13 passed test Services
          Starting test: SystemLog
             An error event occurred.  EventID: 0x0000272C
                Time Generated: 04/14/2015   18:01:37
                Event String:
                DCOM was unable to communicate with the computer fec0:0:0:ffff::1 us
    ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
    m32\dcdiag.exe).
             An error event occurred.  EventID: 0x0000272C
                Time Generated: 04/14/2015   18:01:49
                Event String:
                DCOM was unable to communicate with the computer fec0:0:0:ffff::2 us
    ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
    m32\dcdiag.exe).
             An error event occurred.  EventID: 0x0000272C
                Time Generated: 04/14/2015   18:02:02
                Event String:
                DCOM was unable to communicate with the computer fec0:0:0:ffff::3 us
    ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
    m32\dcdiag.exe).
             ......................... EX-13 failed test SystemLog
          Starting test: VerifyReferences
             ......................... EX-13 passed test VerifyReferences
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test
             CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test
             CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : NETMAGIC
          Starting test: CheckSDRefDom
             ......................... NETMAGIC passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... NETMAGIC passed test CrossRefValidation
       Running enterprise tests on : NETMAGIC.IN
          Starting test: LocatorCheck
             ......................... NETMAGIC.IN passed test LocatorCheck
          Starting test: Intersite
             ......................... NETMAGIC.IN passed test Intersite
    Regards
    Biswajeet

  • 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.

  • 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 - DAG Failure

    Exchange server 2013 with two Mailbox server role and One CAS server role with DAG Enabled on it.
    Exchange server went live with 150 Mailbox on both the server distributed evenly.
    Both mailbox server lost connectivity and unable to communicate with CAS server. 
    Outlook and OWA user unable to connected to their mailboxes.
    Both the Mailbox server went down disrupting the mailflow.
    Later found that Cluster Node wasnt responding in timely fashion. Had to remove the Mailboxes from the DAG and later remove the DAG configuration.
    Disable Replication network on each of the mailbox server and rebooted it.
    Re gain network connectivity to the Mailboxes and they are back on online.
    What could be the issue. 
    Both mailbox server are rich in resources which can be ruled here 

    Hello,
    According to your description, your network configure may be issue.
    We recommend you assign static IP address for cluster server to check the result.
    Cara Chen
    TechNet Community Support

  • Exchange server 2013 proxy authentication

    Hi All,
    I wanted to know what is the recommended proxy authentication for exchange server 2013. 
    I have observed the following from different proxy authentications:
    1. Negotiate: By default, the proxy authentication is set to negotiate and uses anonymous as Log on network security(un-encrypted MAPI)
    2. Basic: It always prompts for the user credentials and uses encrypted MAPI.
    3. NTLM: Use negotiate at MAPI level by default
    Please provide me some information on different authentication mechanisms and the one which is recommended to use. 
    Thanks,
    Srinivas.

    Hi Srinivas,
    According to my knowledge, there are my views below:
    Basic authentication: If you select this authentication type, Outlook will prompt for username and password
    while attempting a connection with Exchange.
    NTLM authentication: If you select this authentication type, exchange does not prompt users for a user
    name and password. The current Windows user information on the client computer is supplied by the browser through a cryptographic exchange involving hashing with the Web server. If the authentication exchange initially fails to identify the user, the browser
    will prompt the user for a Windows user account user name and password. So, when Outlook is trying to connect to Exchange and if the machine is domain joined, there isn’t a need to provide password.
    Negotiate authentication: Enabled by default in Exchange 2013. This is a combination of Windows integrated
    authentication and Kerberos authentication. If we employ negotiate authentication, exchange will authenticate the client using NTLM authentication type and if unable to verify authenticity, will challenge the client to authenticate using a username and password.
    And you could set the authentication type like this:
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    The command below for your reference:
    Get-OutlookAnywhere | Set-OutlookAnywhere -InternalHostname "internalServer.contoso.com" -InternalClientAuthenticationMethod Ntlm -InternalClientsRequireSsl $true -ExternalHostname "externalServer.company.com" -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $true -IISAuthenticationMethods Negotiate,NTLM,Basic
    If you have any further questions, please let me know.
    Best regards,
    Eric

  • 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

  • Exchange Server 2013: Outook Clients and OWA keeps on disconnecting/connecting every 5-10 mins

    We have a new exchange server 2013 installed but also has exchange 2007 up.
    MX records are now pointing to the new exchange server, all were working ok after DNS records were changed but after the weekend it Outlook clients and OWA keeps on disconnecting and reconnecting from exchange.
    Exchange 2013 CU6
    Anybody else experienced the same?

    hi Jheycie,
    can you please check if you have .local and .com (different internal and external domain)
    almost similar thread.. it worked for me
    http://social.technet.microsoft.com/Forums/office/en-US/cc7d2300-0e1f-499f-a8f1-97f84687b6cc/emails-stuck-in-outlook-have-to-restart-transport-service?forum=exchangesvrgeneral
    http://social.technet.microsoft.com/Forums/office/en-US/9b9bf607-f882-4f73-a7b2-611ace3f3115/users-unable-to-connect-to-exchange-unless-they-close-and-reopen-outlook?forum=exchangesvrgeneral
    MARK AS USEFUL/ANSWER IF IT DID
    Thanks
    Happiness Always
    Jatin

  • Exchange Server 2013 Service Pack Upgrade - Outlook connectivity issue

    Hi,
    After upgrading to Exchange Server 2013 service pack 1, we are unable to connect via Outlook 2010 or Outlook 2013. Outlook Web Access is working fine though. We have followed all the instructions, and have applied Outlook upgrades, but the issue remain the
    same. Outlook was working fine before the upgrade.
    Have we missed out something. I would highly appreciate if someone can help out? I'm not sure if this is the known issue as I can't seem to find anything on the internet.
    Already applied the transport fix.
    Thanks in advance!

    Hi,
    According to your description, your Outlook 2010 and Outlook 2013 come across the connectivity issue.
    To narrow down the issue, I’d like to recommend the following troubleshooting:
    1. Check if the issue happens on all Outlook users
    2. Check the Outlook Anywhere connectivity by using ExRCA:
    https://testconnectivity.microsoft.com/
    Additionally, MAPI over HTTP is only supported when you use Outlook 2013 sp1 and Exchange 2013 sp1 at the same time. Since the issue also happens on Outlook 2010 client, we can firstly try the above troubleshooting.
    If you have any question , please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

Maybe you are looking for