Exchange Server 2013 POP3 Service on CAS cannot after Upgrade to SP1

Exchange Server 2013 POP3 Service on CAS cannot after Upgrade to SP1
When I manual start MSExchangepop3 Service on CAS It show "The Microsoft Exchange POP3 Service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
In event log show POP3 EventID 1018 , 1019 , 1036
It said like this blinding already use (0.0.0.0)
The point is "IF I SET BINDING FOR 995 , MSEXCHANGE POP3 Service will automatic stop"
Does anyone face this issue please?
Thank you

You could check what (if anything) else is running on that port.
From a command prompt, type netstat -ano | find 995
This will give you the Process Identifier (PID) for the process that is running on port 995. Then you can open Task Manager, add PID as an additional column, and find out what that process is.
Hope that helps.

Similar Messages

  • Exchange Server 2013 Database not showing in ECP after removal of Exchange Server 2010

    I recently complete the migration of my Exchange 2010 server to Exchange 2013. I then proceeded to uninstall the 2010 server using setup.com /m:uninstall. At the end of the process I received an error that it did not complete the uninstall.
    I checked the server and Exchanged 2010 was removed. When I checked ECP on 2013 it still showed the old 2010 server listed. I used ADSI edit and manually removed the old sever.
    Now when I log into 2013 ECP I only see the one serve but when I go into databases, none are listed. I check under the server itself and it shows the database that it is using but it is not listed under the database tab.
    If I do a search under the database tab I can find it and adds it to the list. I can then open and view details.
    My issue is, after I log out and then back in, I have to run the search to find the database again. In ideas on how to have it show up in the list like it did  before I removed the 2010 Exchange server?
    Thank you,

    Hi,
    From your description, I recommend you verify the following things for troubleshooting:
    1. Please make sure that AD replication is completely by checking the user object's homeMDB attribute. This value should contain the DN value of the Exchange Server 2013 mailbox database.
    2. Wait 30 minutes for the cache on the Exchange Server 2013 Client Access Server to clear or restart the MSExchangeOWAAppPool on the Exchange Server 2013 Client Access Server.
    For more information, here is a kb for your reference.
    Exchange 2013 Redirects to Exchange 2010 for OWA and ECP
    http://support.microsoft.com/kb/2931385
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange server 2013 upgrade

    Hi Guys,
    My current version is "Microsoft Exchange Server 2013 RTM" and I would like to upgrade it to CU1. But I could
    see that this is a major upgrade and it would cause some AD permission changes and schema update. I  also have an RD server and also a SharePoint server connected to the same AD. So, I'm a bit hesitant to do the upgrade an I fear that the permission changes
    would cause access problems to the users in RD server and SharePoint server.
    Could someone shed some light on this? Also, would there be any issues with this CU1 update? Could someone share the steps to perform this upgrade? The Mailserver and ClientAccess roles are configured on the same machine.

    Hi Nash Burns,
    According to the Exchange Team Blog (http://blogs.technet.com/b/exchange/archive/2013/04/02/released-exchange-server-2013-rtm-cumulative-update-1.aspx),
    CU1 grants Exchange Servers to make changes on msExchActiveSyncDevices class on
    inetOrgPerson objects.
    Another change in CU1 is about Monitoring Mailboxes.
    Before CU1, Monitoring Mailbox are created in default "<domain root>/Users" container. With CU1, Monitoring Mailboxes will be created in the "Exchange System Objects/Monitoring Mailboxes" container.
    In my organization, CU1 update didn't change any permissions on my RDS servers.
    One question : why don't you apply directely SP1?

  • Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?

    Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?
    We recently upgraded from Exchange 2010 to Exchange 2013.
    The links that used OWA Web parts have completely stopped working and generate the " :( something went wrong contact your help desk" screen for domain Authenticated users other than myself. The links accessed content of a Shared Account of which
    I am an owner and can set the necessary permissions using the Outlook 2013 client.
    Using the example from the link provided below we were able to provide calendar access to all authenticated users in our area. The link for calendar still works for me but for noone else. Additionally, all navigation menus are missing when I use this link.
    <server>/owa/<SMTP address>/?cmd=contents&module=calendar&view=weekly name
    Another crafted link provided web access to our group's task list. This has completely stopped working for anyone including myself. However, when I use "open another mailbox" I am able to navigate to the needed pages.
    <server name>/owa/<SMTP address>/?cmd=contents&module=tasks
    These links were crafted using advice provided from this provided link.
    technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx
    Is it still possible to use Outlook Web App Web Parts in Exchange Server 2013 - OWA?
    Or
    Is this a misconfiguration of some sort?
    My IT support has given up and closed out the ticket stating that maybe Microsoft will fix this someday...

    Hello,
    At present, there is no official article to verify whether we can use Outlook Web App Web Parts in Exchange Server 2013. In exchange online, the Outlook Web App Parts is supported.
    Cara Chen
    TechNet Community Support
    Hi, you said this feature is supported in Exchange Online (I understand you're referring to Office 365). Can you please point me to some documentation as I was trying to use it with my E3 account and it doesn't seem to work?
    What I'm trying to acomplish is something similar to our old URL (Exchange 2010) in Office 365:
    https://ourserver.mydomain.com/owa/[email protected]/?cmd=contents&module=calendar&view=monthly
    The best I can do in Office 365 is this:
    https://outlook.com/owa/mydomain.com/[email protected]/#path=/calendar
    But it's clearly not the same and Office 365 ignores all the information I add to the URL. I would greatly appreciate something in the line of the document referred by 'MarquetteENG' (technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx)
    Thanks.
    Paulo.
    Paulo Dias - IT Pro Evangelist

  • Cannot connect to an Exchange account in Outlook 2013 using "Microsoft Exchange Server or Compatible Service"

    Dear All,
    I cannot connect to my Exchange account in Outlook 2013 using "Microsoft Exchange Server or Compatible Service".
    First I would like to present my network environment, I have 4 physical servers;
    The first one is holding the Domain Controller 1, IP@: 192.168.1.10
    The second server is holding the additional Domain Controller which it is DC2, IP@: 192.168.1.11
    The third server is holding the Exchange 2013 Mailbox, IP@: 192.168.1.15
    And the last server is holding the Exchange 2013 CAS-HT, IP@: 192.168.1.16
    I am doing the steps below:
    1-Creating a new profile in outlook and start configuring the exchange account by entering the IP address of the Exchange-CAS Server, 192.168.1.16
    2-entering the account name: [email protected]
    3-Go to "More Settings" > "Connection" > "Connect to Microsoft Exchange using HTTP" > and entering the "Exchange Proxy Settings"
    4-type the exchange CAS Server URL, https://192.168.1.16
    5-Check the "Connect using SSL Only"
    6-Authentication Settings: "NTLM Authentication", and pressing Apply
    7-When I press the "Check Name" button, a message occurred> "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action".
    8-I go back to the "Exchange Proxy Settings" and I Uncheck the "Connect using SSL Only" and pressing Apply
    9-i press the "Check Name" Button, a small window occurred to enter a Username and Password, so I enter the Administrator username and the administrator password and pressing "OK", but nothing is changed, I tried to enter my
    username and password in the small window and I still got the same result.
    I cannot verify the account name and I cannot complete the process.
    I appreciate you kind assistance.

    Hi,
    To narrow down the cause, I’d like to recommend the following troubleshooting:
    1. Try to login the test account through OWA.
    2. Check the Autodiscover settings: get-clientaccessserver |fl autodiscoverserviceinternaluri
    3. Check the result of directly accessing the following URL:
    https://autodiscover.domain.com/autodiscover/autodiscover.xml
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • CANNOT ACCES EXCHANGE ADMIN CENTER (ECP) ON EXCHANGE SERVER 2013. GOT HTTP 500 INTERNAL SERVER ERROR

    HI, I just installed Exchange server 2013 Standar SP1 on a windows server 2012.  I have 3 servers one is a Domain Controller, the other one has the MBX role, and the last one the CAS role,  first i installed the MBX and after the CAS role, i passed
    prerequisite check without any issue.  However when I tried access Exchange Admin Centre (ECP) at https:\\servername\ecp
    I got HTTP 500 Internal Server Error saying  "This website cannot display the page.  Most likely causes: 1. The website is under maintenance. 2. The website has a programming error."   I tried access ECP at https://localhost/ecp and
    I got the same problem.  Under either cases I was able to see the logon page of  ECP and I was able to enter my credential (e.g. domain\user name, password).  However I got HTTP 500 Internal Server Error at the next page.
    I appreciate your help, on my case.

    Hi,
    The link that Jatin points to should be this.
    https://social.technet.microsoft.com/Forums/en-US/2f64d305-e9e2-4f48-a5b4-4f72d7bca801/exchange-2013-owaecp-http-500-internal-server-error?forum=exchangesvrclients
    Please view the Application Pool to check whether the version of .NET Framework is 4.0 and try the following command.
    %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i.
    If this does not help then please check if there is any warnings or errors in Event Log and take your time to post them for my further troubleshooting.
    Thanks.

  • Cannot install Exchange server 2013

    hey,
    I'm trying to install exchange server 2013 on windows server 2012 and I getting this error :
    One or more servers in the existing organization are running Exchange 2000 Server or Exchange Server 2003. Installation can't proceed until all Exchange 2000 or Exchange 2003 servers are removed.
    Warning:
    Cannot find the Recipient Update Service responsible for domain 'DC=Nesstr,DC=com'. New and existing users may not be properly Exchange-enabled.
    Now, I think before I got here there was exchange server 2003 in virtual machine but I cant find the vm, probably someone has deleted the vm without uninstall the exchange properly and maybe this is the problem.
    anyone suggestion what to do next ?
    best Regards,
    Idan keshet

    Hi Idan,
    We need to do these steps to connect to Configuration:
    1. Open ADSI Edit.
    2. Right-click ADSI Edit, select Connect to… .
    3. In Connection Point, Select a well known Naming Context > Configuration.
    4. Click OK.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Exchange server 2013 - cannot send / receive external emails - we can access owa -we can send/receive internal emails

    Exchange server 2013 in Windows server 2012 VM
    It was working fine then start the issue.
    Firewall is managed externally and the last report said:
    "I checked the firewall logs, which shows traffic being allowed through port 25 from 10.10.10.10 to 4.28.237.225: Log Number 116 Last Activity 2014-08-28 23:48:33 Status [accept] Src 10.10.10.10 Dst 4.28.237.225 Service SMTP Policy ID 1 Src Port 64081
    Dst Port 25 While I showed one log, there were multiple log entries showing the same: traffic being accepted through port 25 from 10.10.10.10 to 4.28.237.225.
    Can you verify that the mail server is set up so as to allow port 25? "
    Today I was able to telnet the server from home: successfully 
    220 DTALL-EXCSRV002.DTC.dualtemp.com Microsoft ESMTP MAIL Service ready at Sat, 30 Aug 2014 16:31:16 -0400 ehlo 250-DTALL-EXCSRV002.DTC.dualtemp.com Hello [70.44.124.141] 250-SIZE 37748736 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-X-ANONYMOUSTLS
    250-AUTH NTLM 250-X-EXPS GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250 XRDST
    Also the receive - send connectors seems ok
    Mx record point to Microsoft protection:
    dualtemp-com.mail.protection.outlook.com.
    Again, OWA is able to access and send/receive emails internal but never external even no bounceback  just it never arrive.
    Help me please. This is my first admin chaos...

    Hi,
    Is there any update with your issue?
    If the CAS and Mailbox servers are collocated on the same server, the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. If you install the CAS and Mailbox on the same server, please make sure that port 2525 is open.
    For more information about Exchange 2013 mail flow, here is a blog for your reference.
    Exchange 2013 Mail Flow Demystified…Hopefully
    http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
    Hope this can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • 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

  • Cannot Access EAC/ECP on exchange server 2013 after installation

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

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

  • Exchange server 2013 services need to restart automatically at certain period of time how do i schedule

    Hi All,
    Need to restart exchange server 2013 services automatically at a certain period of time is there a script to schedule to automate can you please help me step by step process.
    Thanks & Regards, Santosh Chowdary Vasireddy System Administrator Prolifcs DHFLVC Silicon Towers, 5th Floor, Survey #14, Kondapur, Hyderabad – 500 032. Work +91 40 3999 1999 Ex.1656 l Cell +91 9849277255 l [email protected] A Global
    Provider of IBM, Microsoft and Testing Solutions Award Winner for Technical Excellence, BPM, SOA, Portal and Governance

    You can create a PS1 file and run it in a scheduled task.
    The PS1 files will need to have this.
    Restart-Service MSExchangeTransport
    Restart-Service MSexchangeIS
    etc...
    How to add a Scheduled task is given in this link.
    http://www.mikepfeiffer.net/2010/02/creating-scheduled-tasks-for-exchange-2010-powershell-scripts/

  • Deploying 2x Exchange Server 2013 CAS server email traffic high availability during patching & reboot

    Hi people,
    What is the best way to utilize VMware technology to host 2x the Exchange Server 2013 CAS role VM in my production VM to ensure that the email traffic is not halted during server patching ?
    Previously in Exchange Server 2007 I am using Windows NLB (IGMP Multicast) on my ESXi 4.1, now with ESXi 5.1 and 2013 I wonder if there is any better way to make sure that the server failover does not disrupt the mail flow between the Smarthost and the CAS server role.
    Thanks

    Hey AlbertWT,
    Can you clarify exactly what you mean when you say "server patching?"  Do you mean patching at the ESXi host level or something within the guest?
    As you probably know Exchange 2013 CAS no longer needs NLB or even a hardware load balancer.  Due to changes in the architecture, even simple DNS round robin is "enough" to load balance the CAS role.  NLB has its own set of headaches which you are probably all too familiar with so getting rid of that can help remove a lot of complexity from the situation.
    If you can clarify what you mean by "server patching" and "server failover" in your post I think that would be helpful for me to give you a more definitive answer.
    Matt
    http://www.thelowercasew.com

  • Exchange server 2013 CAS server high availability

    Hi
    I have exchange server 2010 sp3(2 MB, 2Hub/Cas) servers.
    Planning to migrate to exchange server 2013.( 2 cas servers and 2 mbx servers).
    I dont want to go all traffic single so i am keeping the role separate..
    In exchange 2010 i achieved hub/CAS high availability through NLB.
    In exchange 2013 how to acheive this...
    Please share your suggestions with document if possible...

    Here ya go:
    http://technet.microsoft.com/en-us/library/jj898588(v=exchg.150).aspx
    Load balancing
    and
    http://technet.microsoft.com/en-us/office/dn756394
    Even though it says 2010, it applies to 2013 vendors as well.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • 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

  • Exchange Server 2013 REST EWS service

    Exchange Server 2013 introduces REST EWS service which enables us to retrieve user's photo either from exchange or AD server.
    Does it provides this functionality only? Does REST EWS service provide APIs to pull data or items from inbox, calendar, journal and Notes etc?
    If yes, then it is not documented on MSDN site.
    Can you please confirm if REST EWS service provides all the API which SOAP based EWS service provides? Or does it provide only limited functionality?

    To follow up on this conversation, there are many REST APIs now available in Exchange Online.
    http://msdn.microsoft.com/en-us/office/office365/api/api-catalog
    Michael | Microsoft Exchange Developer Content
    The
    Exchange Development Forum Guide has useful information for using the Exchange Development Forum.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Maybe you are looking for