Hub Version 14 queue

Posted on 2014-04-09
Last Modified: 2014-04-24
In my environment, I am using exchange 2010, and suddenly some users (60) are started to complain that they are experiencing intermittent slow response from outlook, and as an investigation I found that  Hub version 14 queue is getting higher in one of the DAG member server, can you please advice.
Question by:ipsec600
  • 4

Author Comment

ID: 39989704
it seems now all users are affected and emails are becoming too slow for delivery and HUB version 14 queue is getting higher gradually, need advise how can i troubleshoot this issue.

Author Comment

ID: 39990713
I have increased Memory in  all exchange dag member servers and restarted all DAG member servers as well, and found everything was started to work properly, but after couple of hours HUB version 14 queue is becoming higher and exchange started to consume all memory. Can you advise what needs to investigate please.
LVL 15

Expert Comment

ID: 39992685
A special Send connector named the intra-organization Send connector exists on every Hub Transport server. This connector is implicitly created, invisible, and requires no management. The intra-organization Send connector is used to relay messages to the following destinations:

To other Hub Transport servers in the Exchange organization, including Exchange 2007 Hub Transport servers

To Exchange Server 2003 servers in the Exchange organization

To Edge Transport servers in the Exchange organization

By default, protocol logging for the intra-organization Send connector is disabled. You can enable or disable protocol logging for the intra-organization Send connector by using the IntraOrgConnectorProtocolLoggingLevel parameter on the Set-TransportServer cmdlet. If you enable protocol logging for the intra-organization Send connector, logging occurs in the Send connector protocol logs configured on the Hub Transport server.

Accepted Solution

ipsec600 earned 0 total points
ID: 40010741
Thanks  jrhelgeson for your post, I opened a support case with Microsoft to assist me on the investigation, quite surprisingly, Microsoft took long time to investigate, and finally through Netmon trace it figured out that HUB server was not able to send data to EDGE server and eventually did not receive packet acknowledgement, and network team investigated and found that there was a faulty module in the network switch and after replacing the faulty module issue because resolved.

Author Closing Comment

ID: 40019506
Microsoft support identified the root cause and resolved the issue.

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Utilizing an array to gracefully append to a list of EmailAddresses
How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question