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.

Similar Messages

  • EXCHANGE 2013 - ECP AND OWA INTERNAL ERROR 500 - NEW INSTALL

    Really hoping someone can help me here.
    I first installed 2012 OS and 2013 exchange and users were getting 'Unable to open your default folder' when trying to open outlook. After much googling and nothing working I decided to put 2008 R2 on the server with 2013 Exchange. Now i am running into massive
    issues. 
    Firstly i get Internal Errror 500 after putting in credentials for ECP and OWA. I did notice that it is also defaulting straight to this URL after entering password https://localhost/owa/auth.owa
    I check the management shell and that connects without any issues. I also logged on to a computer to see what it did. After autodiscover it is not able to log onto server and then it looks like it is look for the old server information from previous server.
    Any help would be appreciated. Can i do another reinstall of OS and how am i meant to remove the previous data that it seems the server has found?

    Hi,
    According to your description, I understand that cannot login internal ECP\OWA with error 500, also autodiscover failed.
    If I misunderstand your concern, please do not hesitate to let me know.
    I notice that autodiscover “looks like it is look for the old server information from previous server”, have you installed multiple version Exchange in your environment?
    Please run below command to double check the virtual directory configuration:
    Get-OutlookAnywhere | FL Identity,*Host*,*Auth*
    Get-OwaVirtualDirectory | FL Identity,*url*,*auth*
    Get-EcpVirtualDirectory | FL Identity,*url*,*auth*
    Get-WebServicesVirtualDirectory | FL Identity,*url*,*auth*
    Get-ClientAccessServer | FL Identity,*URI*,*auth*
    Then, open IIS and check on the Application Pools to view whether MSExchangeOWAAppPool and MSExchangeECPAppPool is running on .NET Framework v4.0, and recycle virtual directory for test.
    Additional, here’s a thread about “Removing Old Exchange and installing a new one”, for your reference:
    https://social.technet.microsoft.com/forums/exchange/en-US/46ca107c-7ece-4da7-8aea-46b705793f37/removing-old-exchange-and-installing-a-new-one
    Thanks
    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]
    Allen Wang
    TechNet Community Support

  • Exchange 2013 MP and DAG

    Hi.
    We got strange issue with Exchange 2013 MP. Some components in DAG are in state "Not monitoring". For example:
    "Exchange 2013 Service Components" on DAG members not motitored:
    Mailbox Count in organization is null:
    And DAG object is in the "Not monitored" state too.
    MP was installed as described in documentation (account, profile, etc.).
    Proxy on DAG members enabled.
    Any ideas how to troubleshoot this issue?
    P.S. MP - 15.0.665.19, Exchange - CU6

    Hi,
    I would like to suggest you recheck Exchange 2013 Management Pack Pre-requisites and Considerations.
    Before importing the Exchange 2013 MP into System Center Operations Manager, there are some pre-requisites that have to be met:
    You have one of the following versions of System Center Operations Manager deployed in your organization:
    System Center Operations Manager 2012 RTM or later
    System Center Operations Manager 2007 R2 or later
    You have already deployed SCOM agents to your Exchange Servers.
    The SCOM agents on your Exchange Servers are running under the local system account.
    The SCOM agents on your Exchange Servers are configured to act as a proxy and discover managed objects on other computers.
    If you are monitoring Exchange Server 2013 Database Availability Groups (DAGs), ensure that all DAG members are monitored by Operations Manager.
    You may refer to the link below for more details:
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/monitoring-exchange-2013-scom-2012-part2.html
    Regards,
    Yan Li
    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]

  • Exchange 2013 CU6 with DAG - ECP Delete does not go to soft-delete state, retention policy ignored

    I am not sure if this is a BUG or this is as intended.  Typically if a mailbox is 'deleted' from the EAC or ECP console the user account is disabled and the mailbox is marked for removal (soft-delete) until the retention policy expires the item (default
    30 days). However we deleted a mailbox and the mailbox was purged immediately as well as the user was moved to the hidden recycle bin in Active Directory.
    We replicated this issue twice in a DAG environment, we do not have this issue in a non-DAG environment.
    Question:  Other than restoring from the backup, is there a way to recover the mailbox?
    Thank You,
    -Jake
    Jacob Evans Jake of All Trades

    Hi,
    I tested in my lab, Exchange 2013 CU1 with DAG deployed, if I deleted a mailbox from EAC, then it would be a disconnected mailbox and the associated Active Directory user account was also deleted. I could find it under the Disconnected Mailbox.
    Was the mailbox logged ever?
    If you delete a mailbox that you never log in, it won't show as disconnected mailbox.
    And for the question :"Question:  Other than restoring from the backup, is there a way to recover the mailbox?", I'm afraid you have to recover from backup.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Exchange 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension

    I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.
    1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box
    on our system".
    2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.
    I've followed this post as a guide but it hasn't resolved my issue.
    https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86
    My Exchange environment looks like this:
    Site 1:
    exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
    exch2 - CAS/Mailbox, part DAG13
    exch3 - CAS/Mailbox, part of DAG13
    Site 2:
    exch2dr - CAS/Mailbox, part of DAG13
    exch3dr - CAS/Mailbox, part of DAG13
    DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.
    Any help is greatly appreciated. I'd love to get rid of Unity. 
    EDIT:
    I just found this event in the event logs:
    The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP",
    but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

    9.1.2 I think it is, we upgraded to avoid the known DNS bug
    I cant see how to PM you either
    The crux of it was outlined below with some tweaks
    http://blogs.technet.com/b/canitpro/archive/2014/04/30/step-by-step-integration-between-exchange-2013-um-and-cisco-unified-communication-manager.aspx
    As we have multiple combined role servers, our trunks are set up as follows:
    1. 1 x CAS Trunk - contains all CAS Servers on port 5060
    2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068
    On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks
    Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)
    Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same
    as any other CAS based service - point to 2013, and it will handle the rest

  • Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

    Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
    I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
    Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
    Error look like - cannot find exchange server.
    I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
    Someone have the same problem with migrated mailbox? How to solve it?
    Truly, Valery Tyurin

    You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
    Moreover, you can try this utility (
    http://www.exchangemigrationtool.com/ ) to accomplish this task.

  • Exchange 2013 migration and Lync server

    hi guys,
    i wanna upgrade my exchange 2010 to 2013 in our company.
    but i faced with a question
    will exchange migration has effect on Lync server an should i reinstall it again in our caompany or not?
    plz help me 
    thanks guys

    Hi,
    you will need to config IM in OWA for Exchange 2013 server.As i can remember voice and everything else should be fine.
    Here is a guide for enabling IM in OWA:
    http://www.expta.com/2010/09/how-to-integrate-lync-server-2010-with.html
    Just remember to point DNS to the New Exchange 2013 server and it should be fine.
    Please 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. Thank you! Off2work

  • Exchange 2013 MBX in DAG along with Hyper-V and Failover Cluster

    Hi Guys! I've tried to find out an answer of my question or some kind of solution, but with no luck that's why I am writing here. The case is as follows. I have two powerful server boxes and iSCSI storage and I have to design high availability
    solution, which includes SCOM 2012, SC DPM 2012 and exchange 2013 (two CAS+HUB servers and two MBX servers).
    Let me tell you how I plan to do that and you will correct me if proposed solution is wrong.
    1. On both hosts - add Hyper-V role.
    2. On both hosts - add failover clustering role.
    3. Create 2 VMs through failover cluster manager, VMs will be stored on a iSCSI LUN, the first one VM for SCOM 2012 and the second one for SCDPM 2012. Both VMs will be added as failover resource.
    4. Create 4 VMs - 2 for CAS+HUB role and 2 for MBX role, VMs will be stored on a iSCSI LUN as well.
    5. Create a DAG within the two MBX servers.
    In general, that's all. What I wonder is whether I can use failover clustering to acheive High Availability for 2 VMs and at the same time to create DAG between MBX-servers and NLB between CAS-servers?
    Excuse me for this question, but I am not proficient in this matter.

    Hi,
    As far as I know, it’s supported to create DAG for mailbox server installed in hyper-v server.
    And since load balance has been changed for CAS 2013, it is more worth with DNS round robin instead of NLB. However, you can use NLB in Exchange 2013.
    For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/jj898588(v=exchg.150).aspx
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange server 2013 send and received issue

    Hi Support,
    I have install Exchange Server 2013 with server 2012 ( my domain not resisted but mail send & received in local for practice then live ) but few days back some changes in dns and ecp and mail stop sending and receiving. how to verify my exchange server
    2013 working fine. Please give the step check perpoes.     

    dear Pardeep, you said it was working fine then you did some DNS changes..
    i would suggest you best troubleshooting step is to go to exrca.com and perform the tests and from there we take it up.
    Secondly you can verify your config from the below link.
    http://www.techieshelp.com/exchange-2013-step-by-step-configuration/        
    in DNS you need to make sure you have atleast MX and A record done for your server having email services installed.
    for ECP... i would we would take this later lets check the mail sending and receiving first. use the above links
    MARK AS USEFUL/ANSWER IF IT DID
    Thanks
    Happiness Always
    Jatin

  • Exchange 2013 POP3 and IMAP connectivity issues 0x800CCC0F

    Hi all,
    there's an Exchange 2013 server running without problems during "regular" use, but when it comes to POP3 and/or IMAP (we really need that for some systems), everything is fine until there's a message with an attachment of about 100kb or more.
    We can poll messages with smaller attachments without problem, but bigger sizes won't work.
    So for testing I tried POP3 within Outlook Express, it gives Error 0x800CCC0F
    Telnet to TCP110 simply breaks up the connection when I try "retr"
    IMAP shows those messages as "to be deleted", but they are accesible within OWA.
    Test-PopConnectivity (also for IMAP) runs smoothly and successfully.
    Firewall is opened for all connections.
    Problem is and has always been there. The server is updated to the newest SP/updates.
    I tried both 110/143 and corresponding SSL - no difference.
    Pop3 and Imap logging shows no errors
    There's Trend Micro Messaging Security installed, but has been disabled for testing - no difference. (Issue has been there before installation of TM)
    So, any ideas how to fix this? I'd appreciate...
    Thanks in advance,
    Robert

    Hello,
    Take a network trace on both ends to see if there are any devices like firewalls drop the package.
    http://www.microsoft.com/en-us/download/details.aspx?id=4865
    Thanks,
    Simon Wu
    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 and SCOM 2012 R2

    Hi there, 
    Hopefully someone can assist me with this issue, if it is one... 
    I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
    76 users in total, roughly 80GB of Public Folders.
    I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected. 
    Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues. 
    Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well. 
    Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010. 
    A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect. 
    Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy. 
    Attempted to reran the probe for EWS and got the error below:
    Is there perhaps anyone that can assist me with these errors?
    Cheers

    FYI... IIS ARR is not supported for Exchange Server.
    Check in event log if you are getting anything related to the issue.
    About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
    Are those mailboxes still moving or in move request?
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    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

Maybe you are looking for