none
Test-Mailflow -> Error

    Question

  • Hi there,

    at my customers Exchange Environment (2 Nodes Exchange Server 2013 Cumulative Update 18 (CU18)) the Powershell CMD "Test-Mailflow" doesnt work anymore.

    If you run it in the shell, it needs a couple of minutes until it shows:

    TestMailflowResult: *ERROR*

    Actually, it is a german installation so: TestMailflowResult: *FEHLER*

    We asked Microsoft-Support what could be the problem but since we have no real errors or impact, they cant support it. We allready recreated the arbitration mailboxes -> no luck.

    Maybe somebody has a good idea?

    Thanks

    Jan

    Monday, November 27, 2017 11:02 AM

All replies

  • Hi,

    Anything in the logs? What happen if you remote connect to the Exchange servers via "New-PSSession", is it the same outcome?

    Tuesday, November 28, 2017 12:26 AM
  • Hi,

    Thanks for contacting our forum.

    It’s recommended to check the Application log to see if any events related and post out in detail if exist.

    We can also use the Test-ExchangeServerHealth.ps1 script to test your Exchange server health state.

    https://gallery.technet.microsoft.com/office/Generate-Health-Report-for-19f5fe5f

    It’s recommended to restart the transport service or servers in down time and check the results.

    Hope it helps.


    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Tuesday, November 28, 2017 2:05 AM
    Moderator
  • Hi there,

    thanks for your reply. The customer uses the Script to generete reports. Everything is fine in the reports, except the Point Mailflow. The script uses the CMD Test-MailFlow, thats why we care about this, so get a clean report ;)

    The Applicationlog ist without Entries when we run the CMD and we did already restart the Service and Servers, no luck.

    Thanks

    Jan

    Monday, December 11, 2017 9:58 AM
  • Since everything are fine, and no error messages in detail, it's recommended to change the language to English and check the results to verify that if this issue caused by German language.

    Thanks.


    Regards,

    Jason Chao


    Please remember to mark the replies as answers if they helped.
    If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, December 15, 2017 2:07 AM
    Moderator