locked
Something went wrong and we haven't been able to send your message yet RRS feed

  • Question

  • Hi everyone,

    I have just installed and configured the Exchange server. For few emails it was working well, but suddenly it started to save all send email on draft saying this error "Something went wrong and we haven't been able to send your message yet".

    I am using Windows Server 2016 as DC, and Windows Server 2016 as base OS for Exchange 2016 CU4. Request for your help on this.


    Cheers,
    Aerrow

    Visit: pdhewaju.com.np

    Please remember to mark the replies as answers.

    Saturday, March 25, 2017 5:30 PM

Answers

All replies

  • Hi Aerrow,

    First, please run the following command on your exchange server to check if all services are running:

    Get-ServiceHealth

    Then, check your Dns lookup settings in EAC via the following steps:

    Open EAC-- Click Servers -- Double Click Exchange server name -- Check DNS lookups settings 

    Finally, check if there is any related event log in Exchange server.

    Moreover, I recommend you can try to reboot the server and check if any 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 tnmff@microsoft.com.

    Monday, March 27, 2017 8:37 AM
  • Almost forget another thing, if there is any Anti-Virus software had been installed, it'd recommend to disable it temporally to check again.

    Best Regards,


    Niko Cheng
    TechNet Community Support


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

    Monday, March 27, 2017 8:42 AM
  • Hi Niko,

    Did all those.. checked the DNS... it is okay.. But I couldn't find cmdlet 'Get-Servicehealth' but found 'Get-ServerHealth'

    can you specify me exactly what should I look on this?

    Thank you.


    Cheers,
    Aerrow

    Visit: pdhewaju.com.np

    Please remember to mark the replies as answers.

    Monday, March 27, 2017 9:21 AM
  • Hi Aerrow,

    Sorry for mistake, it's "Test-ServiceHealth", not get-servicehealth.


    Niko Cheng
    TechNet Community Support


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

    Monday, March 27, 2017 9:27 AM
  • Hi Niko,

    here is the result which i get using this cmdlet.


    Cheers,
    Aerrow

    Visit: pdhewaju.com.np

    Please remember to mark the replies as answers.

    Monday, March 27, 2017 11:09 AM
  • Hi Niko,

    thank you for your help... Just found the issue... the issue was with the DNS... don't know why even though the NSLOOKUP and DCDIAG test for DNS is passed it is showing such error. I just made add of my IP and HOSTNAME of DC and Exchange server on Exchange Server HOST FILE and now it is working good. Made detail report and posted on my blog.

    http://pdhewaju.com.np/2017/04/02/solvedsomething-went-wrong-havent-able-send-message-yet/


    Cheers,
    Aerrow

    Visit: pdhewaju.com.np

    Please remember to mark the replies as answers.

    • Marked as answer by AerrowMVP Sunday, April 2, 2017 2:46 PM
    Sunday, April 2, 2017 2:36 PM
  • Hi Aerrow,

    Glad you solved the issue and thanks for your sharing!

    Best Regards,


    Niko Cheng
    TechNet Community Support


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

    Monday, April 3, 2017 1:28 AM