Internal mail delayed between two on-premise 2013 servers...

Hello all -

We have two Exchange 2013 the present the first holds all of the mail stores and the second has zero mailboxes defined.

1.  Every now an then we see internal mail being routed to the server-B with no mailboxes and held before it is routed to the server-A that contains all user mailboxes.  The delay is only happening for internal mail recipients.  Externally things are flowing fine.

2.  Is there any way to force Server-A to be the primary server and Server-B to be the secondary?  Seems odd that the second server is even process connection requests as the autodiscover entry all point to Server-A.


Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
Exchange has no concept of "primary" and "secondary".
All servers are equal, and all servers in the same AD site can process the email. That can mean you will see email going through another server to be delivered to a user on the same server as the sender. That is to be expected.

Primary reasons for email not being delivered in a timely manner include AV software on the server being incorrectly configured. The queue viewer can also give more information.

zookeepa1Author Commented:
Thanks SImon -

Given the issue is not happening right now -  Is there a way to dig into Exchange 2013 log files or Powershell to understand why the mail server held onto an email for 12 minutes before sending it through to the users mail box?  I have the mail header but that only highlights the mail flow.  Is there a unique mail identification that I can use to step through each server process to better understand when and where the delay kicked in.

If so, what identification tag am I looking for? Which internal systems should I check?  Which commands can I run within Powershell - if any?

Tim EdwardsIT Team Lead - Unified Communications & CollaborationCommented:
I ran into something similiar in my 2010 environment and it ended up being a space issue on C:, my IIS logs were eating space and took the drive under 5 GB which started to slowly show delays on internal.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Simon Butler (Sembee)ConsultantCommented:
Message tracking can give you some information, but to hold on to the emails is unusual. If it is Exchange doing it then something is usually logged in the event viewer.
However most of the time it is external influences - AV software being the most common.

Lack of disk space as indicated above can also have an impact on email processing, but that usually causes the email to stop unless the space fluctuates wildly - and that would be a indication of something wrong or you are right on the threshold for back pressure to kick in.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.