0

Our small network (1 server, ~10 workstations) runs Exchange Server 2010 on Windows 2008 R2 Standard; it has worked fine for years, but recently we cannot send or receive mail, though no error is apparent in Outlook; mail just ceases to arrive or be delivered. (External senders get a failed delivery notification after some hours.)

Disk space and memory look okay (store.exe uses ~90% of RAM but I gather this is normal and it will release RAM as needed); I see nothing of relevance in the Application event logs. Exchange Best Practices Analyzer shows no critical issues.

The Troubleshooting Assistant's Connectivity Test indicates that "the SMTP service and SMTP instance(s) on server MAT1 are started but the port did not respond". Further investigation shows that the Windows service "Microsoft Exchange Transport" is hanging (and due to the hang, cannot be stopped through the UI, only by taskkill). Rebooting the server fixes the issue briefly, but the service always hangs again a few hours later. How can I diagnose this hung service?

  • Have you recently installed any .NET Framework updates? – SturdyErde Jul 19 '18 at 15:22
  • Yes, on 14 July there was an automatic installation of ".NET Framework 4.7.2 for Windows Server 2008 R2 for x64" (KB4054530): are you aware of any conflict with Exchange? – equin0x80 Jul 20 '18 at 7:35
  • That update is almost certainly your problem. Exchange Server is not compatible with .NET Framework 4.7.2 yet. – SturdyErde Jul 21 '18 at 10:50
1

Maybe a windows update issue, refer to the following blog: Issue with July Updates for Windows on an Exchange Server

  • Based on that article, I rolled back and hid the updates KB4338823 and KB4338818. It seems to have fixed the issue. – equin0x80 Jul 23 '18 at 13:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.