Can’t Email Essentials Health Report Since Daylight Savings Time

Mark Berry November 3, 2014

In the U.S., daylight savings time started on November 2 at 2:00am. Which means that at 2:00am, it was suddenly 1:00am. At that moment, Essentials lost its ability to send email.

I maintain multiple Server 2012 R2 Essentials machines. Each one emails its health report at 6am. On all three, on the Health Report tab, at 11/2 1:00am, I see the message:

Status:  Cannot send email.
Error:  The Windows Server

Essentials Management service is not running.

That message repeats on November 2 and 3 at 6am, i.e. at the times when the reports should have been sent.

When I right-click on a report and choose Email the Health Report, it shows “Emailing report…” but never finishes. If I stop and restart the dashboard, it is back to “Cannot send email.”

Essentials Health Report 1

Reviewing my email history, I see that I did receive the 1:00am emails, even though the dashboard says “Cannot send email.” However I did not receive the subsequent 6am emails.

Workaround:  Restart the Service

The Windows Server Essentials Management service is running and I doubt that it stopped. I decided to try restarting the Windows Server Essentials Management service. After that, when I sent a Health Report email from the dashboard, it went out immediately.

Essentials Health Report 2


It seems there are a couple bugs here:

  • The Essentials sever tries to send an unscheduled health report at the beginning of Daylight Savings Time.
  • The Essentials sever cannot send email after the change to Daylight Savings Time.

Fortunately the workaround is simple:  restart the Windows Server Essentials Management service.

Update November 8, 2016

As several have reported in the comments below, this issue continues two years later. In the US, on November 6, 2:00am became 1:00am. Essentials tried and failed to email a Health Report at 1:00am, and has failed at 6:00am every day since then. The reason given is still, “The Windows Server Essentials Management service is not running,” even though it is. After restarting the Windows Server Essentials Management service just now, I was able to manually email this morning’s report.

Essentials Health Report 3


  1. Amadeos   |  November 14, 2014 at 8:19 pm

    Thanks so much, I had the same issue and wasn’t sure what was happening. I thought it was my SMTP settings and restarted the SMTP server many times. Finally restarting the Windows Server Essentials Management service fixed. it.

  2. Papastef   |  October 27, 2015 at 6:05 pm

    Worked fine, thanks!

  3. Steve Pitts   |  October 31, 2016 at 12:41 pm


    Thanks for posting this. Rather sad that two years later the bugs still exists, but at least your entry gave me some clue as to where to look for a solution. Without you sharing your experience I would have wasted a lot more time trying to figure out what was going on. Chapeau!

    Cheers, Steve

  4. Chris Lilley   |  November 04, 2016 at 6:09 am

    Thanks Mark. We noticed this issue on a couple of our Essentials servers that this week and never made the connection that Daylight saving hours occurred last weekend. Great info share, thanks again.

  5. Bluechips   |  November 08, 2016 at 7:34 am

    Thanks Mark. I noticed this issue on one of my Essentials servers this week and never made the connection about Daylight saving having anything to do with this. Great share, thanks again!

  6. Server Essentials 2012 & 2016 Can’t Email Health Reports | techspeeder   |  November 08, 2016 at 3:56 pm

    […] did a little digging and I found that apparently there is a bug in the Server Essentials software and when Daylight […]

Leave a Reply