Exchange Server 2013 SP1 - Internal Email Flow slowness

Hi Fellows,
I have a brand new implementation of Exchange Server 2013 SP1 with three mailbox servers and 3 CAS servers.
I am facing a considerable slow transportation of email internally. although there are just 3 mailboxes on the infrastructure at the moment.
When a user sends email to himself or other two accounts, delivery takes from 15 seconds to 35 seconds to be delivered.
Experience is same even if the email is sent from OWA, ActiveSync or Outlook.
Header analysis shows the message exchange between mailbox servers is taking time. any clue?
Decreasing Tarpit interval on Mailbox server receive connectors will be helpful?
Network communication, Storage performance, Server performance are all as good as we love to.
Thanks.
J.A

Hello,
When a user send message to a internal user in a AD site, the connector will not be used. I recommend you use message tracking to check the issue occur on server side or transport process. Please use queue viewer to check if there is mail traffic.
Cara Chen
TechNet Community Support

Similar Messages

  • Strange Exchange name when connecting with Outlook 2013 to Exchange server 2013 SP1

    I've setup a test environment with Windows Server standard 2012 R2 and Exchange Server 2013 SP1...
    In- and outbound SMTP works fine, as well as connecting with OWA and Mac Outlook client...
    Oddly though when setting up an Outlook 2013 connection....it recognizes the email address correctly, but later on can't connect and shows a dialog to enter the server and email account manually....though the profiled fields show something like:
    Exchange Server: [email protected]
    Mailbox: =SMTP:[email protected]
    When I fill in the right fields....it won't connect and falls back to the values above...
    Something wrong in the Exchange setup?

    Hmm...found aguide here:
    http://enterpriseit.co/microsoft-exchange/2013/ssl-certificate-request/
    Though it doesn't mention anything that with the self-signed certs it won't allow Outlook 2013 to connect...
    So from my point of view Outlook 2013 should be able to connect anyway...as during the connect process you can install the self-signed cert.....so must be something else then...

  • What is the order for upgrading exchange server 2013 SP1 servers to CU7?

    Hi All 
    I am planning to upgrade my exchange server 2013 SP1CU4 to CU7 . As per my understanding , we always proceed with the CAS servers and then the Mailbox Servers during up-gradation.
    But I am confused now , since I have seen articles stating , that the Mailbox servers has to be upgraded first and then the CAS servers in exchange 2013. 
    What will be the correct order . My environment consists of 2 Mailbox servers in DAG and 2 CAS servers (Exchange server 2013 SP1)
    Thanks in Advance .
    Joyso Senior Messaging Admin

    Hi Joyso,
    The Microsoft recommendation regarding the order in which the Exchange 2013 server roles should be installed or Upgraded is Mailbox and then CAS.
    It makes sense as the CAS Role is a stateless server and all major components are held by the Mailbox Role.
    Until a 2013 mailbox server comes online, the CAS server is pretty much useless. Hence, the recommended installation order in 2013 is the reverse of 2010 – Mailbox role first & then CAS
    Note: If your DAG have more nodes, you need first upgrade all non-PAM nodes and then upgrade PAM node.
    Some References:
    The recommendation from the Product Group is to install Exchange 2013 Preview Mailbox Role first, and then the
    CAS role.
    If you're separating your server roles, we recommend installing the Mailbox server role first.
    Upgrade your Exchange 2013 server roles in the required order. First, upgrade Mailbox servers
    and then upgrade Client Access servers. -Upgrade DAG Mailbox servers
    Exchange 2013 Server Roles Installation Order – Mailbox First:
    Regards,
    Satyajit
    Please “Vote As Helpful”
    if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Messaging tracking logs filename format changed in Exchange Server 2013 sp1

    Hi,
    I have noticed that the file name format is changed for exchange server 2013 sp1.
    Now it will have hh attached to it like
    MSGTRKMSyyyymmddhh-n.log;
    MSGTRKMDyyyymmddhh-n.log:
    MSGTRKyyyymmddhh-n.log.
    So the "hh" will goes from 00 to 23 for single day.
    So Lets say at 24 april 2014 first fill is created @7.30 AM, so the first file name will be
    MSGTRK2014042400-1.log. Now exchange server will create new file every hour by incrementing hh part of file name. Now the last file i.e
    MSGTRK2014042423-1.log will be created on 25 April 2014 at 6.30 AM.
    I am not able to understand why exchange server is creating the file with old date on next day ( with 24 April on file name time stamp on 25 April).
    And also how it will be decided to create the first file @ 7.30 AM.
    Can anyone explain to me about this ? Why it is happening like this?
    Thanks
    Sandeep Gupta

    Hi Sandeep,
    This could related to the time difference. What’s the time zone of your server? In my lab, many files in the last day were created in the next day. For example, files in 20140410
    were created on 20140411.
    Also, as you mentioned, the file name format is as:
    MSGTRKMSyyyymmddhh-n.log;
    MSGTRKMDyyyymmddhh-n.log:
    MSGTRKyyyymmddhh-n.log.
    However as I know, the format is like
    MSGTRKyyyymmdd-m.log, it will not have “hh”(you mean hours) in the behind and the file is not created every hour but create a new file when the old is full. So please capture some screenshots of the message tracking files
    and the date/time information of the file to verify.
    Title: Message Tracking
    Link:
    http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx
    Regards, Eric Zou

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

  • Upgrade Exchange Server 2013 SP1

    Hello,
    I have two Exchange 2013 SP1 servers with DAG configured. I want to upgrade them with CU8. Kindly advise how to do or is there any step by step document available for upgrading the DAG member server.
    Thanks in advance.

    yes you need to upgrade one at a time and putting them in maintenance mode
    this article has step by step info
    http://vanhybrid.com/2013/11/28/script-putting-exchange-server-2013-into-maintenance-mode/
    Where Technology Meets Talent

  • Outlook 2013 not connect with Exchange server 2013 in internal network

    Hello All,
    I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
    but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
    I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network. 
    Can you please suggest as soon as possible.
    Thanks,
    Parvez

    Hi,
    Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
    Thus, let’s try the following resolutions:
    1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
    2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
    3. Check if the above host name is in your certificate.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Exchange Server 2013 SP1 - Readiness Check Failing - Detected Non-existent Exchange 2007 Servers

    For development purposes, I needed to install Exchange Server 2013 in our environment.  Our current environment includes a couple Domain Controllers, a Sharepoint Server, and a SQL Server.  So, it's got a very simple topology.  The one thing
    our environment does NOT have are current Exchange servers.
    During the "Prerequisite Analysis" phase of the install it complained that two servers, that I can find nowhere in our active directory domain, are running Exchange 2007.  Obviously, this presents some unique problems.  Perhaps as a test
    many years ago, someone installed Exchange 2007 to "play" with, but we've never run Exchange for any length of time.  
    So, this is quite the conundrum, given the above does anyone have any suggestions as to a potential solution?  Ideally, I'd like to be able to "lift the covers" and cleanup the references to the non-existent servers somehow, but ANY suggestions
    for fixes are MUCH appreciated.
    Cheers,
    Nate

    Here is the thing I would do (Only if I am not going to have any exchange 2007 ever in the environment).
    On any of windows server 2008 download
    Exchange 2010 SP3
    Extract the file and run the below command:
    Setup.com /ps
    This will make Exchange 2013 install. Also Deleting Exchange Administrator Group wouldn't help as Setup will look for the information about schema into AD.
    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.

  • Mail flow completely broken after upgrading Exchange Server 2013 CU3 (Build 775.38) to Exchange Server 2013 SP1 (Build 847.32)

    internal mail flow completely broken.
    external mail flow completely broken.
    i upgraded exchange server as follows:
    1. setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
    2. setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
    3. upgraded the exchange server with GUI installer
    also considered this: http://support.microsoft.com/kb/2938053/en-us
    receive connectors :
    Transport Service couldn't start, then i disabled hub transports, and it starts, but no mail flow on port 25. according to this:
    http://social.technet.microsoft.com/wiki/contents/articles/24056.what-the-crash.aspx
    i didn't have any success to fix mail flow, any solution?

    Hi Alireza
    The above tech-net http://social.technet.microsoft.com/wiki/contents/articles/24056.what-the-crash.aspx
    will be applicable only if we get these events in the app log 1019,1018,1036,4999
    You can check the transport service is running in which service account - Local or network 
    It should be running in network account by default.
    You can run get-transportagent and check if there are any transport agents installed 
    If you find them then disable all the transport agents that you have installed on the Exchange servers by running disable-transportagents
    Disable the antivirus if you have any installed.
    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 SP1 - Optimize for Single Server Use

    Hello,
    i've set up Exchange 2013 SP1 with at last CU6 - get exchangeserver says:
    AdminDisplayVersion             : Version 15.0 (Build 995.29)
    ExchangeVersion                 : 0.1 (8.0.535.0)              - - - funny number ;-) (is this an early version???)
    Yes, the annoying 16028 in the application log are running every five minutes, but thats not the main question.
    Which services are needed in a SINGLE-SERVER Environment, without DAG and unified messaging?
    Can the Self-Checking, Health- and Self-Probing be put down?
    These services are started automatic:
       Microsoft Exchange Active Directory Topology
       Microsoft Exchange Anti-spam Update
       Microsoft Exchange DAG Management
       Microsoft Exchange Diagnostics
       Microsoft Exchange EdgeSync
       Microsoft Exchange Frontend Transport
       Microsoft Exchange Health Manager
       Microsoft Exchange Mailbox Assistants
       Microsoft Exchange Mailbox Replication
       Microsoft Exchange Mailbox Transport Delivery
       Microsoft Exchange Mailbox Transport Submission
       Microsoft Exchange Migration Workflow
       Microsoft Exchange Replication
       Microsoft Exchange RPC Client Access
       Microsoft Exchange Search
       Microsoft Exchange Search Host Controller
       Microsoft Exchange Service Host
       Microsoft Exchange Throttling
       Microsoft Exchange Transport
       Microsoft Exchange Transport Log Search
       Microsoft Exchange Unified Messaging
       Microsoft Exchange Unified Messaging Call Router
       Microsoft Exchange-Informationsspeicher
       Microsoft Filtering Management Service
       Microsoft Online Services Sign-in Assistant
    And with C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue\mail.que about 512 MBytes size (which may may be a designed default size)...
    Have set up about 6 users mailboxes, 3 public folder in a mailbox for public folders. Only for testing purposes sent some (small) mails, no external mails received (only testing receive with 'popcon' for mail delivery to the internal boxes).
    The server (2012 R2) is running only in the internal network (yes, with internet connection for updates).
    No virus scanners, not third party receive or send connectors, only the 5 default (3 Frontend, 2 Hub) receive Connectors and one Send Connector to our mail provider set up and no user activity (only sometimes from me for testing).
    It seems like it's doing only with itself, logging file sizes of above 11 GB (in 4 weeks), with huge amounts of probing, health checking, internal testing, internal updating etc.
    Can this logging be set up to a lower level, can services be deactivated (for single server configuration),
    the logging volume should be in a useful relation to the mail use of the server, a message for every self test, internal health check etc. in the log-files normally isn't useful, only when problems occur there is a need...
    Thanks in advance
    Andreas

    Between Exchange protocol-based log files, PerfMon .blg files used by Managed Availability, IIS logs, etc., the total footprint can add up quickly and these logs are not purged automatically.  You can take a look at this site below and use the powershell
    script to clean it up.
    http://www.c7solutions.com/2013/04/removing-old-exchange-2013-log-files-html

  • Exchange Server 2013 not receiving emails

    I have a new Exchange 2013 mail server installation (no migration - completely new domain and everything).  For some reason the server is not accepting mail from the Internet.  My router is indicating it is forwarding SMTP packets to the Exchange
    server's IP address, but nothing shows up in the message queues or users mailboxes.  The event viewer is giving me no clues.  No errors.  This is a simple installation - one Server 2012 DC and the Exchange server.  One Exchange server in
    a domain environment.  The receive connector looks correct.  It is using port 25 and I indicated to use the IP address of the Exchange server network card.  Any ideas as to how to configure the receive connector?  Thanks!

    Greylisted  is an anti spam check done on exchange. However to me this would meanone of two things.
    1: The inbound email domain is listed not your exchange server. Your Exchange server seems to be set up to only allow inbound mail from specific domains perhaps instead of * (All).
    2: More likely i think is that your domain is not set up in Exchange.
    In order to test the product you probably want to create your own domain, and that is easily done in the Exchange Admin Center by clicking the Mail Flow item
    and then Accepted Domains in the tab area and finally the Add… icon, <o:p></o:p>
    Type in the information and click Save,
    the new domain will show up on the List View.<o:p></o:p>
    For reference you can check if your domain is blacklisted here: http://mxtoolbox.com/blacklists.aspx but i am sure this is not your issue.
    Martin

  • Windows Server 2012 R2 with Exchange Server 2013 SP1 Completely fresh install giving errors signing into EAC

    Hi,
    I am struggling with a completely clean installation of Server 2012 R2 and Exchange 2013 SP1.  I followed these steps:
    Installed Server OS
    Windows Updates
    Added Active Directory Role (This is a single standalone server that would have been SBS until it was dropped)
    Added DHCP & DNS
    Added Certificate Services
    Added Windows Server Update Services (WID Database & WSUS Services)
    Windows Updates
    Added Media Foundation
    Added File Server Resource Manager and Work Folders
    Added Windows Server Backup
    Windows Updates
    Checked all running without errors in Server Manager and performed a full bare bones backup.
    Ran Setup.exe from Exchange 2013 SP1 disc.
    Installed Pre-requisites and then rebooted
    Windows Updates
    Ran Setup.exe from Exchange 2013 SP1 disc.
    Installation completed without errors
    Rebooted
    Checked all running without errors in Server Manager.
    I Launch Exchange Administrative Center and get "problem with website's server certificate error" (normal on machine with self-assigned certificates).  Click Continue to Website and get:
    Windows Security dialog box:
    iexplore - "The server localhost is asking for your username and password.  The server reports that it is from Digest"
    however no username and password combination will work:  have tried [Administrator]; [Domain\Administrator] even created a user to no avail.
    I believe the issue is somewhere in the IIS configuration because I also get the same error when trying to log into the server website from either the server or another machine on the network.
    I have tried the complete installation three times now:  (full disclosure not all of the same features/roles each time).  On the first attempt I got this error immediately and on try number 2 was able to get into the EAC and created the mailboxes
    but then it started giving the same error.  The above steps are try number 3.
    Any ideas?
    Thanks in advance.
    Andy Halford
    P.S. A Follow up which might be significant:  The Default Web Site is not running and will not start (it was previously running before the Exchange installation) and when I try I get the message that Another Website may be using the same port however none
    of the others (Exchange Back End or WSUS Administration) are using ports 80 or 443 and I still get the error when they are both stopped.

    Could you post the list of sites:
    appcmd list site
    The ones listening on port 80:
    appcmd list site /bindings:http/*:80:
    And on port 443:
    appcmd list site /bindings:https/*:443:
    Step by Step Screencasts and Video Tutorials

  • Exchange server 2010 exchange server 2013 sp1 2 servers one domain

    Scenario : Existing Server - Small Business Server 2011 with exchange 2010 \ Additional server on domain server 2012 r2 with exchange 2013 sp1 \ exchange 2013 sp1 installed on the second server but the exchange toolbox snap in fails, EAC login credentials
    will not log on, and the shell tries to log onto the exchange 2013 with access denied error but then logs into the existing 2010 exchange server. Any suggestions on how to get these two installs of exchange to play nicely? reasoning is to eventually migrate
    everything over to the new exchange.

    Hi,
    Based on my experience, here are some troubleshooting:
    1. Check if all your Exchange 2013 services are working properly.
    2. Check if the login account is a member of Exchange management group. You can try another admin account.
    3. Check your event log and find if there is any error.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange Server 2013 SP1 CU5 - The Microsoft Exchange Replication service VSS Writer encountered an exception

    We have 2 server DAG with a witness all servers are Server 2012 R2.  Both members of the DAG are Exchange 2013 SP1 CU5.
    We haven't seen this until recently, but during a VSS enabled storage snapshot the following errors occur.  All of which are related to MSExchangeRepl and the Exchange VSS Writer.
    Event IDs 2140, 2026, 2028, 2030.
    The errors start with the 2140 seen here:
    The Microsoft Exchange Replication service VSS Writer encountered an exception in function Microsoft::Exchange::Cluster::ReplicaVssWriter::CReplicaVssWriterInterop::PrepareSnapshot. HResult -2147467259. Exception Microsoft.Mapi.MapiExceptionDatabaseError: MapiExceptionDatabaseError:
    Unable execute Prepare on snapshot. (hr=0x80004005, ec=1108)
    Diagnostic context:
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 56264   StoreEc: 0x1388    
        Lid: 46280   StoreEc: 0x454     
        Lid: 1750    ---- Remote Context End ----
        Lid: 59216  
        Lid: 34640   StoreEc: 0x454     
        Lid: 52264  
        Lid: 46120   StoreEc: 0x454     
       at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
       at Microsoft.Mapi.ExRpcAdmin.ProcessSnapshotOperation(Guid mdbGuid, SnapshotOperationCode operationCode, UInt32 flags)
       at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass1c.<SnapshotPrepare>b__1b()
       at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
       at Microsoft.Exchange.Data.HA.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
       at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
       at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.SnapshotPrepare(Guid dbGuid, UInt32 flags)
       at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.PrepareSnapshot().

    Hi Julez K,
    According to your description, you could try upgrading to CU6.
    In addition, you could review the Exchange Application (App) Event log and the Exchange System (Sys) Event log for errors , and some related resolutions for your reference.
    http://www.symantec.com/business/support/index?page=content&id=TECH209938
    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.
    Hope it can be helpful.
    Best regards,
    Eric

  • Exchange Server 2013 SP1 Install on Windows Server 2012 R2

    I am trying to install Exchange 2013 SP1 onto a Windows Server 2012 R2. I get an error message that the operating system is not supported. I have installed all the prerequisite.

    Does that mean that you can't install Exchange 2013 Sp1 with a Remote Desktop Role together included with Server 2012 R2?
    Or is it possible to restore the Remote Desktop Role afterwards?
    You can't install any build of Exchange 2013 on any server that has the RDS Role installed. So in other words, this is not a "limitation" with Exchange 2013 SP1 and Windows Server 2012 R2.
    Additional Reading, check out: Exchange OWA/Activesync conflicting with RD Gateway
    role
    Martina Miskovic

Maybe you are looking for