Comments on: Exchange Server 2013: Using Test-ServiceHealth to Verify Required Services are Running https://practical365.com/exchange-2013-test-service-health/ Practical Office 365 News, Tips, and Tutorials Fri, 20 Oct 2023 14:53:22 +0000 hourly 1 https://wordpress.org/?v=6.6.1 By: Tim https://practical365.com/exchange-2013-test-service-health/#comment-278096 Fri, 20 Oct 2023 14:53:22 +0000 https://www.practical365.com/?p=6688#comment-278096 Worked great on Exchange 2016

]]>
By: salih https://practical365.com/exchange-2013-test-service-health/#comment-232601 Sun, 13 Dec 2020 08:29:08 +0000 https://www.practical365.com/?p=6688#comment-232601 hi,
this week I get same error from report.I chechek it win RM service that it running.
when I check other exc. services , ı notice that Microsoft Exchange EdgeSync is not runing.
I started it and then test-servicehealth cmd .I see that everything is OK.

]]>
By: clifford https://practical365.com/exchange-2013-test-service-health/#comment-229611 Thu, 21 May 2020 09:17:15 +0000 https://www.practical365.com/?p=6688#comment-229611 HI I am running exchange 2016

I ran the script and get Mailbox server role services fail

and
Mailbox server roles services fail

]]>
By: Francho https://practical365.com/exchange-2013-test-service-health/#comment-229297 Mon, 20 Apr 2020 22:31:35 +0000 https://www.practical365.com/?p=6688#comment-229297 Hi, I can’t find the Test-ServiceHealth command

There is a list of modules content and how to import it.

Thank you

]]>
By: Terry https://practical365.com/exchange-2013-test-service-health/#comment-193423 Mon, 04 Mar 2019 03:11:33 +0000 https://www.practical365.com/?p=6688#comment-193423 You forgot adding the point that the command Test-ServiceHealth should be ran within Exchange Management shell.

]]>
By: Marcin https://practical365.com/exchange-2013-test-service-health/#comment-166823 Wed, 24 Oct 2018 10:35:27 +0000 https://www.practical365.com/?p=6688#comment-166823 Hi Paul,

Unified Message Service fails on one of the exchange servers. I am not able to invoke MSExchangeUM service. It fails with “Failed to start Service “Microsfot Exchange Unified Messaging. OpenError (System.ServiceProcess.ServiceController:ServiceController)”

I rebooted the server to no avail. Do you have any suggestions?

Thank you,
Marcin

]]>
By: <div class="apbct-real-user-wrapper"> <div class="apbct-real-user-author-name">Paul Cunningham</div> <div class="apbct-real-user-badge" onmouseover=" let popup = document.getElementById('apbct_trp_comment_id_159001'); popup.style.display = 'inline-flex'; "> <div class="apbct-real-user-popup" id="apbct_trp_comment_id_159001"> <div class="apbct-real-user-title"> <p class="apbct-real-user-popup-header">The Real Person!</p> <p class="apbct-real-user-popup-text">Author <b>Paul Cunningham</b> acts as a real person and passed all tests against spambots. Anti-Spam by CleanTalk.</p> </div> </div> </div> </div> https://practical365.com/exchange-2013-test-service-health/#comment-159001 Wed, 30 May 2018 00:05:09 +0000 https://www.practical365.com/?p=6688#comment-159001 In reply to Gibra.

Either start the service, or you’ll need to customize your script to ignore that result when the MSExchangeEdgeSync service is stopped.

]]>
By: Gibra https://practical365.com/exchange-2013-test-service-health/#comment-158990 Tue, 29 May 2018 10:39:54 +0000 https://www.practical365.com/?p=6688#comment-158990 Hi how can I disable EDGE service status test?
I’m not using EGDE role and script is giving error output for HUB transport role because “MSExchangeEdgeSync” is stopped.

thanx in advance.

]]>
By: Benoit https://practical365.com/exchange-2013-test-service-health/#comment-99425 Fri, 16 Jun 2017 14:23:12 +0000 https://www.practical365.com/?p=6688#comment-99425 In reply to Paul Cunningham.

Thanks for your answer but how to check if searches or queries running ?

]]>
By: Paul Cunningham https://practical365.com/exchange-2013-test-service-health/#comment-99178 Fri, 16 Jun 2017 00:54:04 +0000 https://www.practical365.com/?p=6688#comment-99178 In reply to Benoit.

Make sure you’re updated to the latest CU for Exchange 2013. Make sure nobody is running big searches or scripts that query the transport logs.

]]>