Transport Queue fail

Lucas Vorms 251 Reputation points
2021-02-18T11:38:14.533+00:00

Dear all,

Every day we are receiving a report about the heath of our two exchange server.

Yesterday I installed the Windows server 2016 cumulative update and the security update of the cu18

2x OS : Windows server 2016
2x Exchange version : 2016

We are using the "Test-ExchangeServerHealth" from here :
https://github.com/cunninghamp/Test-ExchangeServerHealth.ps1/blob/master/Test-ExchangeServerHealth.ps1

And today today we can see in the report that there is an issue with the transport queue
69439-screenshot-2021-02-18-122727.jpg

Each time I re run the report the number of failure increase.

here is what I've already tried :
69544-test-heath.jpg

69545-get-queue01.jpg

69533-inkedget-queue02-li.jpg

Appreciate any help and advises.

regards,

Lucas

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,598 questions
0 comments No comments
{count} votes

Accepted answer
  1. Lucas Vorms 251 Reputation points
    2021-02-19T15:39:49.857+00:00

    Dear all,

    We fixed the issue.

    In fact the problem was located in the second exchange server.
    The disk was full and we had to expend it.

    Then all the queue started to decrease automatically

    Regards,


3 additional answers

Sort by: Most helpful
  1. Andy David - MVP 147.5K Reputation points MVP
    2021-02-18T12:48:13.77+00:00

    Don't look at just the submission queue, look at them all

    get-queue -server <server>
    
    0 comments No comments

  2. Lucas Vorms 251 Reputation points
    2021-02-18T13:00:40.217+00:00

    Thank you for your reply

    here is the output

    69572-screenshot-2021-02-18-135935.jpg

    Regards,


  3. Yuki Sun-MSFT 41,046 Reputation points Microsoft Vendor
    2021-02-19T06:39:21.383+00:00

    Hi @Lucas Vorms ,

    As suggested by Andy, from the output of the Get-Queue command, it seems that the issue is related to the backlog in the delivery queue to journal db. If the message count in the queue doesn't tend to decrease, I'd recommend giving it a go by restarting the Transport Service and see how it goes.
    In case the issue persists, you can have a look at the Queue Viewer to see if there's any error message for the messages stuck in the queue. It's also suggested to check the Event Viewer for potentially relevant event logs.


    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.