Share via


Exchange 2016 Event ID 8019 RemoteDelivery

Question

Tuesday, August 29, 2017 8:44 AM

Hi Guys,

we have this strange warning in the Event Logs:

Creating extra connection for idle queue: 3 with queue type: SmtpDeliveryToMailbox and next hop domain: edb_internal. Current number of connections is: 1

Creating extra connection for idle queue: 2854 with queue type: DnsConnectorDelivery and next hop domain: hotmail.com. Current number of connections is: 1

In some days we have only 1 or 2 events but sometimes they are more than 10. I'm wondering if there is any problem with the server because of the warning with SmtpDeliveryToMailbox . The other one with DnsConnectorDelivery I believe it could be ignored because it is for additional DNS connection (or at least this is what I understand from it)

We are with Exchange 2016 CU6 running on Windows Server 2012 R2. I've search online but didn't find anything useful. Thank you very much in advance.

All replies (10)

Tuesday, August 29, 2017 11:37 AM

Hi

Have you read this article: https://social.technet.microsoft.com/Forums/en-US/6769be10-0778-4de8-b06f-0fcf279fd105/creating-extra-connection-for-idle-queue-event-id-8019-source-msexchangetransport?forum=Exch4016MFSM


Wednesday, August 30, 2017 10:37 AM

Hi Kondio,

Don't worry about that, it may be due to huge of messages are being delivered to the same destination mailbox database at the particular period, and the server can not process all messages at the same time due to performance issues, resulting in some unprocessed messages being temporarily stored in the queue. We can ignore this warning safely.

Moreover, you can also refer to the following article to understand these delivery types in details:

Queue properties

Delivery Type in Queue Viewer

DeliveryType in the Exchange Management Shell

Description

NextHopCategory

NextHopDomain

SMTP Delivery to Mailbox

SmtpDeliveryToMailbox

The queue holds messages for delivery to Exchange 2016 or Exchange 2013 mailbox recipients. The destination mailbox database is in one of the following locations:

  • The local Exchange 2016 Mailbox server or Exchange 2013 Mailbox server.
  • An Exchange 2016 Mailbox server in the same Exchange 2016 DAG.
  • An Exchange 2013 Mailbox server in the same Exchange 2013 DAG.
  • An Exchange 2016 Mailbox server or an Exchange 2013 Mailbox server in the same Active Directory site in non-DAG environments.

Internal

This value is the name of the destination mailbox database. For example, Mailbox Database 0471695037.

DnsConnectorDelivery

DnsConnectorDelivery

The queue holds messages for delivery to recipients in an SMTP domain. The Send connector that services the domain has the local transport server configured as source server, and the Send connector is configured to use DNS routing.

External

This value is the destination address space that's configured on the Send connector. For example, contoso.com.

Hope this helps,

Best Regards,

Niko Cheng
TechNet Community Support

Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Wednesday, August 30, 2017 11:56 AM

Hi Joerg,

yes, I've checked but actually there is no a solution. 

Information like "If everything is working than don't worry" usually are causing problems after this.


Wednesday, August 30, 2017 11:59 AM

Hi Niko,

thank you for your answer. Is there any way to find the cause of the problem? I mean if there is a problem with delivering for example - long time to sync the clients, delay or similar problems I would like to solve them. I'm not very good in analyzing the performance and most of the users would say only "ah, it is just slow" but I'm trying to have as "clean" as possible running system.


Friday, September 1, 2017 3:12 AM

Hi Kondio,

In fact, Exchange has a system resource monitoring feature called Back Pressure could detect when vital system resources, such as hard drive space and memory, are over-utilized, and takes action to prevent the server from becoming completely overwhelmed and unavailable. We can check if there are any event log entries that are generated by specific back pressure events in Exchange server regularly, and that will help us analyze most of performance issues.

Understanding back pressure

Hope this helps,

Best Regards,

Niko Cheng
TechNet Community Support

Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Friday, September 1, 2017 11:04 AM

Hi Niko,

thank you for your answer. I'll try to check it during the weekend and turn back to you.


Tuesday, September 5, 2017 1:59 AM

Hi Kondio,

I'm just writing to check how's everything going? If you have any questions or needed further help on this issue, please feel free to post back. If the issue has been resolved, please mark the helpful replies as answers, this will make answer searching in the forum easier and be beneficial to other community members as well.

 

Thanks for your understanding.

Best Regards,

 

Niko Cheng
TechNet Community Support

Please remember to mark the replies as answers.
If you have feedback for TechNet Subscriber Support, contact [email protected].


Thursday, September 7, 2017 9:07 AM

Hi Nico,

sorry I had some problems with the other servers. I will update the issue next week.


Tuesday, September 12, 2017 12:15 PM

Hi Nico,

here are the results. From what I see looks like everything is ok.

Resource            : PrivateBytes
CurrentResourceUse  : Low
PreviousResourceUse : Low
PressureTransitions : [PressureTransitions: MediumToHigh=75 HighToMedium=73 LowToMedium=72 MediumToLow=71]
Pressure            : 3

Resource            : SystemMemory
CurrentResourceUse  : Low
PreviousResourceUse : Low
PressureTransitions : [PressureTransitions: MediumToHigh=94 HighToMedium=89 LowToMedium=88 MediumToLow=84]
Pressure            : 84

Resource            : UsedVersionBuckets[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue\mail.que]
CurrentResourceUse  : Low
PreviousResourceUse : Low
PressureTransitions : [PressureTransitions: MediumToHigh=1500 HighToMedium=1000 LowToMedium=999 MediumToLow=800]
Pressure            : 2

Resource            : JetSessions[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue\mail.que]
CurrentResourceUse  : Low
PreviousResourceUse : Low
PressureTransitions : [PressureTransitions: MediumToHigh=1800 HighToMedium=1700 LowToMedium=1600 MediumToLow=1500]
Pressure            : 13

Resource            : CheckpointDepth[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue\mail.que]
CurrentResourceUse  : Low
PreviousResourceUse : Low
PressureTransitions : [PressureTransitions: MediumToHigh=300 HighToMedium=280 LowToMedium=250 MediumToLow=230]
Pressure            : 0

Resource            : DatabaseUsedSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue]
CurrentResourceUse  : Low
PreviousResourceUse : Low
PressureTransitions : [PressureTransitions: MediumToHigh=99 HighToMedium=97 LowToMedium=96 MediumToLow=94]
Pressure            : 76

Resource            : UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue]
CurrentResourceUse  : Low
PreviousResourceUse : Low
PressureTransitions : [PressureTransitions: MediumToHigh=99 HighToMedium=94 LowToMedium=90 MediumToLow=88]
Pressure            : 79

Resource            : UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data]
CurrentResourceUse  : Low
PreviousResourceUse : Low
PressureTransitions : [PressureTransitions: MediumToHigh=99 HighToMedium=94 LowToMedium=90 MediumToLow=88]
Pressure            : 79


Friday, September 29, 2017 1:16 PM

Hi Niko,

I've posted the results. Do you think that there is something not properly set?