Can’t Email Essentials Health Report Since Daylight Savings Time

In the U.S., daylight savings time ended 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. (See notes below re. 2016 Essentials as well.) 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

Bugs

It seems there are a couple bugs here:

  • The Essentials sever tries to send an unscheduled health report at the end of Daylight Savings Time.
  • The Essentials sever cannot send email after the end of 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

Update November 3, 2019 – Affects Some But Not All 2016 Essentials

So this is interesting. Two Essentials 2016 installations were failing to send email and needed the Essentials Management Service restarted. These two machines use an unauthenticated SMTP server running on the same LAN for email relaying.

A third Essentials 2016 installation, only a couple weeks old, did send the email without a service restart. This server sends directly through smtp.gmail.com.

I’m curious if anyone else sees this pattern? Local SMTP vs. remote, authenticated SMTP?

Update November 2, 2020 – All Machines Affected Again

This year, one 2012 R2 Essentials and three 2016 Essentials machines all failed to send reports after Daylight Savings Time ended on November 1. The SMTP server didn’t matter. Restarting the Windows Server Essentials Management service got the emails working again.

19 thoughts on “Can’t Email Essentials Health Report Since Daylight Savings Time

  1. Amadeos

    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. Steve Pitts

    Mark,

    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

  3. Chris Lilley

    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.

  4. Bluechips

    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!

  5. Pingback: Server Essentials 2012 & 2016 Can’t Email Health Reports | techspeeder

  6. Mark Berry Post author

    Les, thanks for the reminder. Guess I should just put this in the calendar. One positive note: my new Server 2016 with the Essentials role did _not_ stop sending health reports. However, 2012R2 Essentials machines still break at the time change.

  7. Les Connor

    No, thank *you* for the reminder, Mark!. I’d completely forgotten about this, until today. I only have one 2016 with essentials role, and it was affected (as were all older versions). I don’t know why yours wasn’t ;-). Unless it lives in Saskatchewan, that is ;-).

    These servers balk at 25 hour days ;-).

  8. Sean Donohue

    Hmm..I will have to look. Our server started failing over the weekend, I will head this up more in the AM.

  9. Les Connor

    Nov 2019!. Restart the service.

    Just checking in ;-).

  10. Martin Baxter

    Just been very grateful for this bit of knowledge.
    All our client servers have failed, 2012 Essentials, 2016 Essentials and also any standard servers running the Essentials experience.
    Wh has this not been addressed by Microsoft in the last 5 years?

  11. Martin Baxter

    This will work from the command prompt (run as administrator) for the task:-

    net stop ServiceProviderRegistry && net start ServiceProviderRegistry && net start WseNtfSvc && net start WseMgmtSvc && net start WseMediaSvc && net start WseHealthSvc

  12. Andrew Solmssen

    First time this has been an issue for me in several years of WSE. I had two machines affected of about 6 I manage – 1 WSE 2012R2, one my own WSE 2016 VM. They both had the spurious attempt to send logs at 1AM day of DST change, and then were unable to send. I rebooted mine and also cleared the C:\ProgramData\Microsoft\Windows Server\Data\settingsproviderdata\HEALTHREPORT directory per another post by Susan Bradley. On the WSE 2012R2 machine I just restarted the email and management services. I had to reconfigure email reports after that, but both machines are now sending reports correctly.

  13. Les Connor

    November 2020 – WSE 2016, no health reports!. Restart service :-).

    As much as the IT landscape changes (esp. MS), some things stay the same :-).

Leave a Reply

Your email address will not be published. Required fields are marked *

Notify me of followup comments via e-mail. You can also subscribe without commenting.

This site uses Akismet to reduce spam. Learn how your comment data is processed.