Failover service failed to launch

Failover service failed to launch

If using TopView failover you see failover events in the Watchdog Engine but the TopView failover service does not start, your watchdog TopView service likely does not have permissions to launch other Windows services.

See the Microsoft KB for how to grant that permission: Grant users rights to manage services - Windows Server | Microsoft Learn.

    • Related Articles

    • Allow a Windows user to start/stop a service

      Background On newer Windows OS’s, the current user may not be allowed to install/start/stop services. This may prevent the user from installing/starting/stopping TopView Engine Services. The solution has been to run the Configurator “as ...

    • Launch TopView automatically at computer start up

      TopView can be set to automatically launch at Windows start up by configuring a Windows Service to run a TopView Engine. TopView Configurator provides tooling to easily set this up. In the TopView Configurator, open the configuration you want ...

    • Win10 1909 update disabled Remote Registry Service

      We seen some upgrades of Windows 10 to feature update 1909 experiencing issues. The Remote Registry Service was disabled after update. Once the service was re-enabled and started, TopView could see monitored performance counters again - this is a ...

    • Windows Services Error: The service did not respond to the start or control request in a timely fashion

      This error occurs whenever a windows service fails to start, or takes too long to start. It is normally reported to the user via a message box after attempting to start the service, and is also recorded in the Event Logs. This error has been more ...

    • SyncThing recommendations

      Our TopView failover guide recommends synchronizing various files and folders between the primary and redundant systems when using TopView in a failover configuration. One syncing solution we recommend is Syncthing, an open-source solution that can ...