question

MiF avatar image
0 Votes"
MiF asked ZhengqiLou-MSFT commented

Microsoft Exchange Health Manager (MSExchangeHM) not start properly

Hi everyone,
I have recently the following problem: MSExchangeHM Service does not start properly and continuously change the state between "Starting" and "Stopping". There are 4 error messages with event ID 1011 from source "MSExchangeHM" appear in the event viewer, approximately every 15 minutes (local language ist German):


 Protokollname: Application
 Quelle:        MSExchangeHM
 Datum:         23.06.2021 10:16:33
 Ereignis-ID:   1011
 Aufgabenkategorie:Worker
 Ebene:         Fehler
 Schlüsselwörter:Klassisch
 Benutzer:      Nicht zutreffend
 Computer:      SERVER-05.xxxxxx.local
 Beschreibung:
 Microsoft Exchange Health Manager worker process (17424) received restart request and will be stopped. Restart reason: Unknown. 
    
 Error message: 
    
 System.Diagnostics.Eventing.Reader.EventLogException: Ende der Datei (EOF) erreicht
    bei System.Diagnostics.Eventing.Reader.EventLogException.Throw(Int32 errorCode)
    bei System.Diagnostics.Eventing.Reader.NativeWrapper.EvtSubscribe(EventLogHandle session, SafeWaitHandle signalEvent, String path, String query, EventLogHandle bookmark, IntPtr context, IntPtr callback, Int32 flags)
    bei System.Diagnostics.Eventing.Reader.EventLogWatcher.StartSubscribing()
    bei Microsoft.Office.Datacenter.ActiveMonitoring.CrimsonWatcher`1.Start(Boolean isSyncMode)
    bei Microsoft.Office.Datacenter.ActiveMonitoring.LocalDataAccess.InitializeProbeResultNotification()
    bei Microsoft.Office.Datacenter.ActiveMonitoring.LocalDataAccess.Initialize(IEnumerable`1 discoveryWorkItems, Boolean reinitializeTables)
    bei Microsoft.Exchange.ActiveMonitoring.MonitoringWorker.Activate()
    bei Microsoft.Exchange.ActiveMonitoring.MonitoringWorker.Run(String[] args). BuildVersion:15.02.0858.012
 Ereignis-XML:
 <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
   <System>
     <Provider Name="MSExchangeHM" />
     <EventID Qualifiers="49156">1011</EventID>
     <Level>2</Level>
     <Task>2</Task>
     <Keywords>0x80000000000000</Keywords>
     <TimeCreated SystemTime="2021-06-23T08:16:33.417161100Z" />
     <EventRecordID>2051951</EventRecordID>
     <Channel>Application</Channel>
     <Computer>SERVER-05.xxxxxxx.local</Computer>
     <Security />
   </System>
   <EventData>
     <Data>17424</Data>
     <Data>System.Diagnostics.Eventing.Reader.EventLogException: Ende der Datei (EOF) erreicht
    bei System.Diagnostics.Eventing.Reader.EventLogException.Throw(Int32 errorCode)
    bei System.Diagnostics.Eventing.Reader.NativeWrapper.EvtSubscribe(EventLogHandle session, SafeWaitHandle signalEvent, String path, String query, EventLogHandle bookmark, IntPtr context, IntPtr callback, Int32 flags)
    bei System.Diagnostics.Eventing.Reader.EventLogWatcher.StartSubscribing()
    bei Microsoft.Office.Datacenter.ActiveMonitoring.CrimsonWatcher`1.Start(Boolean isSyncMode)
    bei Microsoft.Office.Datacenter.ActiveMonitoring.LocalDataAccess.InitializeProbeResultNotification()
    bei Microsoft.Office.Datacenter.ActiveMonitoring.LocalDataAccess.Initialize(IEnumerable`1 discoveryWorkItems, Boolean reinitializeTables)
    bei Microsoft.Exchange.ActiveMonitoring.MonitoringWorker.Activate()
    bei Microsoft.Exchange.ActiveMonitoring.MonitoringWorker.Run(String[] args)</Data>
     <Data>15.02.0858.012</Data>
   </EventData>
 </Event>


The number in brackets after worker process changes from message to message, but the content remains the same.

Unfortunately I couldn't find nothing to the problem (-:

Does anyone have any idea how it could be fixed?

It is a virtual (Hyper-V) Exchange Server 2019 Enterprise with the current build (15.2.858.12), running on Windows Server 2019 Standard.


Thank you in advance!
Michael.

office-exchange-server-administration
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MiF avatar image
1 Vote"
MiF answered ZhengqiLou-MSFT commented

Hi @ZhengqiLou-MSFT,

sorry for late reply, was busy with other things (-;

I have tried your suggestion: by cmdlet with "RecoverServer" says Exchange Server there is always fine and is nothing to fix... |-:

But I solved the problem in a different way. Just restore the VHDX with System Partition (mailbox database is on separate partition) from backup taken before the power failure on fiber optic switch and connect to Exchange Server instead of the current one.
This way I have my server back in good health and without losing any data (-:


Thanks you (@ZhengqiLou-MSFT and @AndyDavid ) for your replies and participation!
Michael

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @MiF,

That's OK, glad to know you issue has been resolved now. Thank you for providing how you fixed this issue, now you could mark your own answer as Accepted Answer, so others who have the same issue could get help from your post:)

Cheers,
Lou

0 Votes 0 ·
ZhengqiLou-MSFT avatar image
0 Votes"
ZhengqiLou-MSFT answered ZhengqiLou-MSFT edited

Hi @MiF

Are the other services working as usual? Please check if the Microsoft Exchange Active Directory services is started.

Sorry I didn't find anything helpful on the error logs. But I think you could run prepare AD domain again.
Prepare all domains in the Active Directory forest

 E:\Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareAllDomains

And then run the repair cmdlet:

 E:\Setup.exe /IAcceptExchangeServerLicenseTerms /Mode:RecoverServer

Hope that helps.

Best regards,
Lou


If the response 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.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @MiF

Do the suggestions above help? If the issue has been resolved, please click “Accept as answer” to mark helpful reply as an answer, this will make answer searching in the forum easier and be beneficial to other community members as well.

Regards,
Lou


If the response 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.


0 Votes 0 ·
MiF avatar image
0 Votes"
MiF answered AndyDavid commented

Yes, Exchange Server - just one.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Ok, if you can't move to another server, consider opening a ticket with Microsoft support It could be that some corruption took place during the outage

0 Votes 0 ·
MiF avatar image
0 Votes"
MiF answered AndyDavid commented

I've already tried to recreate. I couldn't do that with powershell because the service (MSExchangeHM) wasn't running, so I removed the objects from AD manually.

Now the health mailboxes cannot be restored because... the service cannot start normally and still not running )-:

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Do you have just one server?

0 Votes 0 ·
AndyDavid avatar image
0 Votes"
AndyDavid answered

Try recreating the health mailboxes

You can delete them all with powershell:
Get-Mailbox -Monitoring | Remove-Mailbox

Make sure you also read this and give the necessary permissions so the AD objects are removed:
https://docs.microsoft.com/en-us/exchange/troubleshoot/administration/remove-mailboxdatabase-cannot-remove-health-mailboxes

Otherwise, remove the AD objects manually

Then restart the Microsoft Exchange Health Manager, MSExchangeHM service on each 2019 server to recreate them.

ALso see:
https://social.technet.microsoft.com/wiki/contents/articles/40090.exchange-2013-recreating-health-mailboxes.aspx



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MiF avatar image
0 Votes"
MiF answered

Nothing installed or updated. But it started after power supply failure on fiber optic switch. I've already run the chkdsk on Exchnage Server, no success...
Latest CU was installed a couple days ago, with hope it will help.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndyDavid avatar image
0 Votes"
AndyDavid answered AndyDavid edited

Any idea what changed? When did it start? Anything installed or updated on the server?

Since you are at the latest CU, I would consider:

  1. Building a new server and moving mailboxes to it.

  2. Opening a ticket with Microsoft Support. They should be able to get traces and tell you what is causing this.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.