Restart Microsoft Exchange Service Host service every some minutes

Question

Restart Microsoft Exchange Service Host service every some minutes

Михаил Андросов 481

Hi!

We using Microsoft Exchange Server 2016 CU22. The Microsoft Exchange Service Host service is constantly rebooting on one of the servers.

In event Log I see

Source: Service Control Manager

ID: 7031

The Microsoft Exchange Service Host service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.

How can I understand the reason for the reboots and fix the situation?

0 comments

Answer accepted by question author

Hin-V 16,830 Microsoft External Staff Moderator

Hi @Михаил Андросов

Thank you for posting your question in Microsoft Q&A.

As my research, the Event ID 7031 you're seeing is just a symptom, it tells you that the Service Control Manager gave up on the service after it crashed. The actual error that details the cause will almost always be in the Application event log, not the System log where you found the 7031 event.

Could you try to found the root cause: Open Event Viewer.

Navigate to Windows Logs > Application.

Look for Error events that occurred at the exact same time as the 7031 event in the System log.

Click on that error event and check it Event ID

I have found this article and hope it helpExchange Service Host service fails after installing March 2022 security update (KB5013118)In the meantime, you could try to:

Update to a Later Security Update

The issue is resolved in the May 2022 Security Update (KB5014261) and all subsequent monthly SUs for Exchange 2016. Since CU22 is your base, try to apply the latest available SU.

Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

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.

Accept answer 1 answer

Hin-V 16,830 Reputation points Microsoft External Staff Moderator

2025-09-19T07:16:06.0833333+00:00

Hi @Михаил Андросов
I hope you are doing well.

Have you had a chance to check the replies provided?

Any update would be appreciated.

If you want any further support, let me know in the comment section. I truly hope you can find the definitive solution to your concern.
Михаил Андросов 481 Reputation points

2025-09-19T07:51:48.15+00:00

It's unclear why. But the reboots of the service stopped. Without my intervention.
Hin-V 16,830 Reputation points Microsoft External Staff Moderator

2025-09-19T14:37:13.64+00:00

Hi @Михаил Андросов

Thank you for your responding.

I'm really glad to hear that your issue resolved itself.

From my perspective, here are some of the most common reasons why this type of issue may "self-resolve":

Due to a temporary connection loss: The service might have temporarily lost connection to another critical component it depends on, for example, Active Directory or another server in the cluster. When the connection was restored, the service stabilized.

Due to a corrupted email or item: This is a leading cause. There was a corrupted email or calendar appointment in the system. The service would crash every time it tried to process it. The issue stopped because the faulty item was deleted, either by a user or automatically by the system.

Due to system resource overload: Another program (like backup software, an antivirus scan, or a heavy Windows task) temporarily consumed too much RAM or CPU. This left the Exchange service with insufficient resources to run, causing it to crash. When that other task finished, the service returned to normal operation.

Due to a conflict with an Exchange maintenance task: Exchange automatically runs maintenance tasks in the background. It's possible that one of these tasks encountered an error, causing the issue. When that task completed (or was cancelled), the problem also disappeared.

If the issue returns, you could consider checking the Application Event Log, as I mentioned earlier.

If you have any additional concern, feel free to comment below. I be more than happy to assist.

Warm thanks and have a nice day.
Hin-V 16,830 Reputation points Microsoft External Staff Moderator

2025-09-22T06:42:57.5366667+00:00

Hi @Михаил Андросов

I hope the information I shared earlier was at least somewhat helpful in addressing your issue. In case you require further assistance regarding this topic, feel free to reach out.. I’d be happy to explore the issue more deeply with you so we can work together toward a better solution.

If you found the answer helpful, we kindly invite you to mark it as the accepted answer. Once marked, it will automatically be pinned to the top. Since many other users also search for information in this community, your valuable contribution will help them easily find the right channel and useful insights more quickly.

Thank you very much, and I wish you a great day.

1 additional answer

Your answer

Hin-V 16,830 Reputation points Microsoft External Staff Moderator

2025-09-19T07:16:06.0833333+00:00

Hi @Михаил Андросов
I hope you are doing well.

Have you had a chance to check the replies provided?

Any update would be appreciated.

If you want any further support, let me know in the comment section. I truly hope you can find the definitive solution to your concern.
Михаил Андросов 481 Reputation points

2025-09-19T07:51:48.15+00:00

It's unclear why. But the reboots of the service stopped. Without my intervention.
Hin-V 16,830 Reputation points Microsoft External Staff Moderator

2025-09-19T14:37:13.64+00:00

Hi @Михаил Андросов

Thank you for your responding.

I'm really glad to hear that your issue resolved itself.

From my perspective, here are some of the most common reasons why this type of issue may "self-resolve":

Due to a temporary connection loss: The service might have temporarily lost connection to another critical component it depends on, for example, Active Directory or another server in the cluster. When the connection was restored, the service stabilized.

Due to a corrupted email or item: This is a leading cause. There was a corrupted email or calendar appointment in the system. The service would crash every time it tried to process it. The issue stopped because the faulty item was deleted, either by a user or automatically by the system.

Due to system resource overload: Another program (like backup software, an antivirus scan, or a heavy Windows task) temporarily consumed too much RAM or CPU. This left the Exchange service with insufficient resources to run, causing it to crash. When that other task finished, the service returned to normal operation.

Due to a conflict with an Exchange maintenance task: Exchange automatically runs maintenance tasks in the background. It's possible that one of these tasks encountered an error, causing the issue. When that task completed (or was cancelled), the problem also disappeared.

If the issue returns, you could consider checking the Application Event Log, as I mentioned earlier.

If you have any additional concern, feel free to comment below. I be more than happy to assist.

Warm thanks and have a nice day.
Hin-V 16,830 Reputation points Microsoft External Staff Moderator

2025-09-22T06:42:57.5366667+00:00

Hi @Михаил Андросов

I hope the information I shared earlier was at least somewhat helpful in addressing your issue. In case you require further assistance regarding this topic, feel free to reach out.. I’d be happy to explore the issue more deeply with you so we can work together toward a better solution.

If you found the answer helpful, we kindly invite you to mark it as the accepted answer. Once marked, it will automatically be pinned to the top. Since many other users also search for information in this community, your valuable contribution will help them easily find the right channel and useful insights more quickly.

Thank you very much, and I wish you a great day.

Answer 1

Sergey Leonov 1

In my case, the cause of this error was a stopped and disabled service the - IIS Admin Service (IISAdmin).

0 comments