Exchange 2016 keep hung up

Question

Hi,

We have an Exchange 2016 server on premise (on Hyper-V) that keep hung up once a week or so. Users can't send or receive emails when that happened; we can still ping the server ip address, but we can't connect via the Hyper-V Manager, RDS, or Teamviewer although it's shown running on the Hyper-V Manager. We have to restart the Exchange server from Hyper-V in order for users to be able to send and receive mails again.

Is there anywhere in a log or event log that we can take a look to see what the problem would be?

Your comments or advices will be greatly appreciated.

Tee

Answer 1

One of the things I find with VM's is that allowing the host to manage the memory and CPU used on the Exchange Server VM causes major issues so

• first thing I would do is dedicate memory and CPU to that VM.
• This is even more important if you are running a bunch of VM's on the host
• I would also suggest checking to logs on the VM host as well as the VM itself to see if it logged any errors or critical events about the host or the Exchange VM

Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 --> 2007 --> 2010 --> 2013 --> 2016 --> 2019 --> Exchange Online with Lucid8's DigiScope

Answer 2

Hi @Tee356

I agree with the suggestions above, we could check the application log for both VM and your Exchange server. In addition, the official document introduces about Exchange Server virtualization, we can mainly refer to the part Exchange memory requirements and recommendations:

Exchange (like many server applications with optimizations for performance that involve caching of data in memory) is susceptible to poor system performance and an unacceptable client experience if it doesn't have full control over the memory allocated to the physical or virtual machine on which it's running. As a result, using dynamic memory or memory overcommit features for Exchange isn't supported.

Keep us updated if any news comes up.

---

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.
 

Answer 3

Thank you guys, I will try your suggestions.

Answer 4

Hi all,

There are so many errors and warnings in the event log, and most of those I don't know what that were. I will need to do some more error lookups.

Anyway, I have seen the CPU and Memory usages were high in the upper 90's and sometime reached 100. I have increased more memory and CPU to the Exchange server and it seems to be stable since. I checked the event log afterward and didn't see any more warning or error.

Thanks everyone again for all your help.

Tee