Exchange 2013 ECP 500 Error

We are in the beginning phase of migrating from Exchange 2010 to Exchange 2013. When I login to the exchange 2013 admin console and navigate to servers it does not show me any of my servers. When I navigate to mailflow-receive connectors I receive a 500
error. When I run the powershell command to get-receiveconnectors it shows me the correct exchange 2013 connectors. I checked IIS and the permissions appear to be correct. Not sure where to look to resolve the issue.

Hi,
From your description, I would like to verify if you can see all the Exchange servers when running the Get-ExchangeServer cmdlet. If yes, the issue should be ECP virtual directory, you can remove this problematic ECP virtual directory and create a new
ECP virtual directory to check the result.
For your reference:
New-EcpVirtualDirectory
https://technet.microsoft.com/en-us/library/dd351218(v=exchg.150).aspx
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

Similar Messages

  • Exchange 2013 ECP "500 Unexpected Error" after Updates

    Hi *,
    after installing the latest Server 2012 Updates, i get the error "500 Unexpected Error" when i try to Login to the Exchange ECP. There wer no changes to the URL or front-/backend.
    I also tried the Workaround focussed over here: http://social.technet.microsoft.com/Forums/exchange/en-US/777b51ee-330d-43cc-a56e-4614d44aed7b/unable-to-access-owa-or-ecp-something-went-wrong-or-500-unexpected-error?forum=exchangesvrclientsentries but
    there were no entries like CN=Services at the ADSI edit.
    Best Regards
    Max @ Magelan Support

    Hi Max,
    Please double check the port bindings are correct.
    Please try to run lodctr /r and reset IIS as administrator.
    Found a similar thread for your reference:
    Unable to access ECP. -  "500 unexpected error"
    http://social.technet.microsoft.com/Forums/en-US/b4b7c47e-cde4-4c62-8bb1-91a5430d4814/unable-to-access-ecp-500-unexpected-error?forum=exchangesvrclients
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 ECP 503 error

    I have a problem with my two Exchange 2013 servers. There are no mailboxes on the servers, because we are just beginning our migration from Exchange 2007. We are running Exchange 2013 SP1 on Server 2012R2
    When I try to access ecp/owa on ex01 (https://localhost or https://ex01.domain.local), I am presented with a login page, but after entering my credentials,
    I get a 503 error:
    Service Unavailable HTTP Error 503. The service is unavailable
    On ex02, I can RDP to the server and log into ecp/owa just fine. However, if I log in (https://ex02.domain.local) from another computer (like my PC), I get the
    same credential page and 503 error.
    I verified the following:
    All of the application pools and Exchange services are started
    I do not have any instances of event 2280 in the Application log
    I have also restarted the server
    Local security policy shows that Administrators and Backup Operators have "Allow log on locally" permission
    This feels like a permissions issue in IIS, but I'm not sure.
    My ECP virtual directory settings (both servers) look like this:
    InternalAuthenticationMethods : {Basic, Fba}
    BasicAuthentication : True
    WindowsAuthentication : False
    DigestAuthentication : False
    FormsAuthentication : True
    LiveIdAuthentication : False
    AdfsAuthentication : False
    OAuthAuthentication : False
    ExternalAuthenticationMethods : {Fba}
    Why won't ex01 let me log in and why would the login on ex02 work from the server, but 503 from my machine? Thanks.

    Hi,
    From your description, I would like to clarify the following things for troubleshooting:
    1. Make sure that the services are running under the Local System account.
    2. Ensure that the mailbox database that you want to access are mounted. Besides, the account you use to access ECP should have a mailbox in the Exchange server you are accessing.
    Hope my clarification can be helpful to you.
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Amy Wang
    TechNet Community Support

  • Exchange 2013 ECP/OWA Error 503 Service Unavailable

    Hi,
    Hoping that someone can clarify or assist with an issue relating to Exchange 2013 CU3..
    Both roles installed on a single 2012 server, mailboxes created, able to login to ECP/OWA using ht tps://servername.int.domain.com/ecp using the out of the box internally generated SSL certificate.
    Virtual directory internal and external settings for all directories were configured to be ht tps://mail.domain.com/owa /ecp /EWS etc and a UCC certificate (containing mail.domain.com, autodiscover.domain.com)from GoDaddy was imported and assigned to
    IIS and SMTP, internal DNS records were setup internally and externally for mail.domain.com and full propagated, Outlook Anywhere enabled and configured to mail.domain.com, external access configured for all virtual directories
    The issue is that ECP and OWA can only be accessed internally by the full internal server FQDN URL ht tps:// serverame.int.domain.com/ecp whereas it should be accessible at this point by ht tps:// mail.domain.com/ecp
    Error received both internal and external when trying ht tps://mail.domain.com / owa / rpc etc is error 503 Service Unavailable
    I know that the ECP and OWA sites are up and running as I can login and do anything by internal servername URL but no joy at all using the external (which is to be used for internal clients aswell for seamless access)
    The only way it works is by adding a host name to the 2 x 443 bindings in IIS for the front end website and set it to mail.domain.com but this means autodiscover.domain.com internally and externally wont work
    Is this normal and required for Exchange 2013 or is there a way to resolve this?
    Thanks in advance!

    Hi,
    I found a article might help you, for you reference:
    http://support.microsoft.com/kb/2619402
    Generally, this error occurs if the application pool that is associated with the web application doesn't start.
    To troubleshoot this issue, follow these steps:
    In Event Viewer, view the System log to find errors from the Microsoft-Windows-WAS source. An event is frequently logged in the System log if the application pool fails to start.
    If you don't find any relevant events in the System log, search for relevant entries in the HTTPERR log file. The httperr1.log file is located in the following system folder:
    c:\windows\system32\logfiles
    In the file, search on "503" to locate any relevant information about why the application pool failed. For example, you may see an entry that resembles the following:
    2011-12-08 18:26:42 ::1%0 6721 ::1%0 443 HTTP/1.1 GET /owa 503 3 N/A SharePoint+Web+Services+Root
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Fresh install of Exchange 2013. 500 Internal error after trying to login via ECP

    Hi folks,In the process of migrating someone from their onsite infrastructure to Cloud ( local city's datacentre). They currently have AD/File+ Print (2008R2) with Exchange on same VM (yeah I know and I am fixing this with new move) and Terminal Server (2008R2).Cloud move will have Server 2012 R2 AD/F+P, Exchange 2013 SP1 on Server 2012 R2 and RDS on Server 2012 R2 VM's. Have setup VPN between the onsite infrastructure and Cloud VM's. AD/DC are in sync. Exchange has been installed with both mailbox and CAS roles after doing Schema & Domain prep and Domain updates. Exchange server and AD/DC in Cloud are joined to onsite infrastructure domain. Exchange on cloud is using cloud AD/DC's DNS.
    Cloud AD/DNS can ping onsite AD/PDC fine. Cloud Exchange can ping onsite TS fine but it cannot ping onsite AD/DNS. This is my 2nd issue. Onsite AD/PDC...
    This topic first appeared in the Spiceworks Community

    This is Exchange 2013 Sp1 or CU5 ?
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 OWA Login Error HTTP 500

    I installed Exchange 2013 on Windows Server 2012.
    After restarting the Host I could not login into owa or ecp the login screen showed up but after entering my correct credentials I would get a
    HTTP 500 Error on https://localhost/owa/auth.owa
    The error persited after multiple reboots of the Exchange server.
    Some googling revealed to me that this might be caused by the Forms Based Authentication Serivce not running.
    But looking at the Services List I cant seem to even locate it. (I believe that the service belongs to MS-exchange 2010 only)
    Anyone got any idea why this might happen or could give me the exact name of the service or help solve the problem.
    tnx

    Hi
    Anonymous Authentication is enable and SSL is checked on but enabling those you said above gave me this error :
    challenge-based and login redirect-based authentication cannot be used simultaneously
    here is the result of executing those commands:
    Identity                      : SRV01-EX2013\ecp (Exchange Back End)
    InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
    BasicAuthentication           : False
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : False
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    Identity                      : SRV01-EX2013\ecp (Default Web Site)
    InternalAuthenticationMethods : {}
    BasicAuthentication           : False
    WindowsAuthentication         : False
    DigestAuthentication          : False
    FormsAuthentication           : False
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    Identity                      : SRV01-EX2013\owa (Exchange Back End)
    InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
    BasicAuthentication           : False
    WindowsAuthentication         : True
    DigestAuthentication          : False
    FormsAuthentication           : False
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    Identity                      : SRV01-EX2013\owa (Default Web Site)
    InternalAuthenticationMethods : {Basic, Fba}
    BasicAuthentication           : True
    WindowsAuthentication         : False
    DigestAuthentication          : False
    FormsAuthentication           : True
    LiveIdAuthentication          : False
    AdfsAuthentication            : False
    OAuthAuthentication           : False
    ExternalAuthenticationMethods : {Fba}
    please help !
    thank you in advance

  • Exchange 2013 ECP and DAG issue

    Good Day,
    We have Exchange 2013 setup in Coexistence with Exchange 2007. Everything is working well except for two small issues I have noticed.
    Current Setup of 2013:
    SiteA:
    2x CAS Servers on Windows 2012 R2 configured with windows NLB (Internet Facing).
    2x MBX servers Configured in a DAG also running on Windows 2012 R2.
    SiteB:
    2x CAS Server on Windows 2012 R2.
    2x MBX servers Configured in a DAG also running on Windows 2012 R2.
    Issues I am having:
    Issue 1:
    When working on the ECP:
    I can do all tasks on servers in the same site but get some errors when trying to do tasks on servers in the other site.
    When trying to Activate a DB copy on the DAG at SiteB I get "The Microsoft Exchange Replication service does not appear to be running on Server name"
    And just trying to go to the properties of a server at SiteB "An error occurred while accessing the registry on the server servername"
    This happens vice versa.
    I can access all servers on the same site but not between sites with some tasks.
    I have made sure firewall is disabled and remote registry is indeed running but no luck.
    From a network perspective all ports are open between the sites.
    Issue 2:
    When I reboot a DAG member with the active mailbox databases for testing outlook connectivity I get two issues.
    Then I cannot access ECP at all until the server is up again.
    Outlook keeps staying on trying to connect until it is reopened.
    Any Ideas?
    I will gladly give more information if needed.
    Thank You
    Riaan Rourke
    Senior System Engineer

    Since I don't see this with Hyper-V I'll assume this is on ESX. Please let me know it that's not correct.
    In terms of virtualization best practices - whose list was that :) 
    There are multiple configuration things that you *MUST* do when using WLBS on ESX.  It will depend upon multiple things in the environment.  I'd start with this
    http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1556
    Fix that, and chances are the other item will be also remediated.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2010 SP3 cohabitation Exchange 2013 ecp?exchver=15 from external not work

    Hi
    i have installed an exchange 2013 cohabitation with exchange 2010 for migration. outlookanywere,ecp,owa, autodiscovery...etc are configurered
    when i try to connect to the eac or owa internaly its work, but when i try to do externaly https://mail.mydomain.com/ecp?exchver=15
    i have error 302, 301 to many redirections
    how can i fix this
    thanksin advance

    Hi,
    Generally, status 301 means that the resource (page) is moved permanently to a new location. Please refer to Sneff_Gabor's suggetsion to check the Redirect setting s for OWA and ECP in IIS manager.
    Additionally, please provide more information about your issue and collect any error logs for further troubleshooting.
    Regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 ECP redirects to 2010 OWA still

    I have a new Exchange 2013 SP1 server on a 2012 R2 OS where I've installed both Mailbox and Client Access roles in an existing Exchange 2010 environment.  Initially ran into some DNS issues that caused errors installing the Client Access server, but
    I fixed those, removed Exchange 2013 and reinstalled with no errors.  In every scenario so far, trying to access the ECP redirects you to the 2010 OWA.  I have been scouring threads for hours and tried everything I've seen, but to no avail.  I
    have tried:
    1) Using the https://<Exchange_2013_CAS_FQDN>/ecp?ExchClientVer=15 URL, which still
    redirects to the 2010 OWA
    2) Creating a new user account with all of the same rights as the domain admin but has no mailbox, which redirects to the 2010 OWA and throws an error that there is no mailbox.
    3) Setting the domain in IIS authentication settings for the ECP on both the 2013 and 2010 server.
    Does anyone have any ideas here on what to try next?

    Try creating a mailbox for the administrative account on the Exchange 2013 server or moving the existing mailbox.
    I've seen issues like you're experiencing in various forms before myself, though not exactly as you've reported.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2013 ECP Login fails HTTP 404 Requested URL: /owa/auth/logon.aspx

    Hi,
    One of our Exchange servers stopped allowing access to OWA and ECP. I have now managed to get OWA working but ECP is still failing. When connecting to ECP using https://servername/ecp/ it asks me for my username and password. After hitting enter it shows
    me an error page:
    Server Error in '/owa' Application.
    The resource cannot be found.
    Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.
    Requested URL: /owa/auth/logon.aspx
    URL in the address bar while on this screen: https://exchangeserver:444/owa/auth/logon.aspx?url=https://exchangeservera:444/ecp/&reason=0
    Question: When the URL points to servername:444/owa/auth/logon.aspx - Is it trying to find the logon.aspx in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\auth? There is no such file in that directory?
    I have removed and recreated the ECP and OWA virtual directories several times.
    I am trying to login using a domain administrator account.
    Thanks,

    Hi,
    Is there any Exchange server 2010 coexistence with your Exchange 2013 server? If it is, please try the URL
    https://CAS15-NA/ecp?ExchClientVer=15 to access ECP.
    Also run the following to check your OWA and ECP virtual directories:
    Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Authentication*
    Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Authentication*
    And make sure the Basic and Forms authentications are enabled in
    Default Web Site and Ntlm, WindowsIntegrated
    authentication methods are enabled in
    Exchange Back End. Then restart IIS service by running
    iisreset /noforce from a command prompt window.
    If the issue persists, please collect any event logs or IIS logs for further analysis.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 EAC shows "error Sorry, your request couldn't be completed. Try deleting the cookies from your browser, and then sign in again. If the problem continues, contact your helpdesk."

    Hi,
    My Exchange 2013 Hybrid environment is at CU5 level. Multiple administrators have started experiencing the error message
    "error
    Sorry, your request couldn't be completed. Try deleting the cookies from your browser, and then sign in again. If the problem continues, contact your helpdesk."
    It only started two weeks ago and did not coincide with any infrastructure changes. The message occurs when clicking anything on the EAC GUI and it eventually allows you to perform the operation but only after the message
    pops up a few times.
    I have tried clearing the browser cookies, history, etc. Note that using the Office 365 EAC does not yield the same messages and it only happens in IE (IE 11).
    Thanks.

    Hi,
    From your description, please make sure that the "Require SSL" is checked in IIS Manager -> Sites -> Exchange Back End -> ECP -> SSL Settings.
    What's more, ensure that EAC site is added to the “Compatibility Mode”.
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2013 ECP issues

    I have 4 Exchange server, 2 CAS and 2 MBX. Migrated from 2010.
    Everything works perfectly, but sometimes users can't change their password. If I move them to another database, sometimes it works, sometimes it doesn't. Then opening from a different computer, works or doesn't. I can't seem to find a way for it to always
    work or never work....driving me nuts.
    Both CAS servers seem to have the problem, no mailboxes are hosted on Exchange 2010 anymore.
    Already tried to reset the ECP virtualdirectory, nothing changes.
    When I change the web.config file, it gives a different error messages, but still weird.
    Error is: 
    Server Error in '/ecp' Application.
    Runtime Error
    Description: An exception occurred while processing your request. Additionally, another exception occurred while executing the custom error page for the first exception. The request has been terminated.

    Hi,
    Is there any error message when users couldn't change their password?
    Please use EXBPA to check the health of Exchange 2013 server.
    Besides, please check if there is any error in the application log.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 SP1 Installation Errors I Cannot Resolve

    Good Afternoon All -
    Note:  I updated this post an hour after posting.  Still no solution, but please see updated info at end of this post)
    I'm trying to introduce Exchange into an existing, small environment.  The server I'm trying to install it onto is an SBS 2011 server (single server.)  Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
    had attempted to uninstall it before.  Yes, it's being installed onto a server with a DC.  I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
    Before I started, I made sure all Exchange data had been removed.  I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
    When I try to install Exchange 2013 SP1, I get the below errors.  I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one.  I've restarted the server many times when making
    changes or applying various updates and still get flagged to restart during installation.  I've tried the SBS 2011 repair disc as well, but had many issues with it.  In all honesty, the whole server needs to be wiped and re-installed, but
    cannot do at this point.
    Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below.  Also below are system specs.  The only edit I made in them is a find/replace for server and domain name.
    ExchangeSetupLogs Folder
    System Specs
    Xeon E31270 3.4Ghz
    16gb RAM
    Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
    C:\ - RAID 1 = 500gb
    D:\ - SATA HDD = 320gb
    E:\ - SATA HDD = 320GB
    Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
    Any help would be appreciated - Thanks!
    Error:
    This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
    Without this update, the Outlook Anywhere feature may not work reliably.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspx
    Error:
    There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then
    run Setup again.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
    Error:
    The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.aspx
    Error:
    This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from
    http://go.microsoft.com/fwlink/?LinkId=260990.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
    Error:
    An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
    Windows Server 2008 R2 SP1 or later and Windows Server 2012.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    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
    Ben K.
    UPDATE
    I just tried fixing a few things and tried again.  Still no luck.  Below is what I changed as well as the errors received.  Only option was Retry.  Can I just not install it onto this environment?
    What I Changed
    Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
    Installed KB2619234 for Outlook Anywhere
    Installed 12 updates - Server fully patched
    Exchange Setup Errors
    Error:
    An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
    Windows Server 2008 R2 SP1 or later and Windows Server 2012.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    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
    Thanks Guys -

    Hi,
    Agree. Windows Server 2011 SBS x64 can be the problem.
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange 2013 SP1 prerequ errors

    Current installation. 4 Exchange 2013 machines on Server 2008 R2 platform (VM with Hyper-V), all have CAS and mailbox role installed. DAG across all for servers. 2 servers
    reside in main datacenter and 2 on a DR site.
    The Exchange installation is at CU 2 and working.<o:p></o:p>
    We have 2 domain controllers in the main datacenter (win 2008 R2) and 2 domain controllers in the DR site (Win 2012 R2).<o:p></o:p>
    DCDIAG checks out fine on all. Network is fine for all.
    Running SP1 installation on the Exchange servers in the DR site results in prerequisites in a bunch of errors which all stem from one root issue: <o:p></o:p>
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.<o:p></o:p>
    Running the same on the main site (DC= Win 2008 R2) completes prereq for SP1 with no errors.
    So the difference is that the 2 Exchange servers on the DR site have Win 2012 R2 for their domain controllers and fail.<o:p></o:p>
    Any advise?<o:p></o:p>
    Gerhard Waterkamp ACSLA Inc.

    No, I am not done.
    The situation is that on the DR site SP1 on 2 Exchange 2013 servers (on 2008 R2) using Windows 2012 R2 Domain controllers does not install.
    Error messages: ( a whole bunch more, but all related to this)
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.
    It is not resolved but still open.
    Gerhard Waterkamp ACSLA Inc.

  • Exchange 2013 management shell error

    The problem am facing is that when I opened the Exchange management shell on my  Exchange 2013  server locally it would fail to connect.The following error is receiving with Administrator account.I add another account in Organization
    Management Permission  it connect successfully.
    following is error
    Failed to connect to an Exchange server in the current site.
    Enter the server FQDN where you want to connect.: mail.abc.com
    VERBOSE: Connecting to mail.*.*.
    New-PSSession : [mail.abc.com] Connecting to remote server mail.abc.com failed with the following error message :
    WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the
    computer mail.abc.com. Verify that the computer exists on the network and that the name provided is spelled
    correctly. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
       gTransportException
        + FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed
    [PS] C:\Windows\system32>

    Hi wert
    Thank you for your question.
    We could run Set U to make sure the logon user is domain administrator, because we use another account logon without any problems. We could check if some permissions are missing for administrator.
    We could refer to the following steps to delete administrator profile to check if the issue persist:
    Open up "Control Panel | System and Security | System"
    In the dialog click on "Advanced system settings" (requires Admin rights)
    The "System Properties" dialog will be displayed
    Make sure you are in the "Advanced" register
    In the "User Profiles" section click on "Settings"
    The "User Profiles" dialog is displayed
    Select administrator account and Delete it.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

Maybe you are looking for