EVault - After Uninstalling EVault Cloud Disaster Recovery, MSEXCHANGEDIAGNOSTICS Service Fails to Start

Follow

Summary

This Knowledge base article provides information about the MSEXCHANGEDIAGNOSTICS service failing to start after uninstalling EVault Cloud Disaster Recovery.


More Information

Note: EVault recommends that before attempting to uninstall EVault Cloud Disaster Recovery that you uninstall the EVault Cloud Disaster Recovery IIS Plug-in using the EVault Cloud Disaster Recovery Manager to prevent the occurrence of MSEXCHANGEDIAGNOSTICS service failing to start.

Symptom

After uninstalling EVault Cloud Disaster Recovery and rebooting the server, MSEXCHANGEDIAGNOSTOCS service fails to start.

Cause

EVault Cloud Disaster Recovery is unable to reset some services to automatic due to permission limitations.

Resolution

If the EVault Cloud Disaster Recovery IIS Plug-in was not uninstalled using the EVault Cloud Disaster Recovery Manager prior to uninstalling EVault Cloud Disaster Recovery, perform the following steps:

  1. Run the following commands in a command prompt (or copy - paste them in a .BAT file, and run it).

    Note: Ensure the commands are correctly spelled.

    sc create FixServiceStartup binPath= "cmd /K sc config schedule start= auto"
    sc start FixServiceStartup
    sc delete FixServiceStartup

    Note: When running the sc start FixServiceStartup command, the command will run for approximately 30 seconds and display the following expected output:

    [SC] StartService FAILED 1053: The service did not respond to the start or control request in a timely fashion.
  2. Start the Service Control Manager and confirm that the Startup Type for the Task Scheduler service is set to Automatic .
  3. Reboot the server.


Applies To

EVault Cloud Disaster Recovery for Exchange with
Microsoft Exchange 2013 on Windows Server 2008 R2 and Windows Server 2012


Related Information

CDR-REFID-2602

KBID-2603

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.