Windows patches and TopView
Windows patches affect TopView operation. To ensure TopView runs successfully after a Windows patch, we recommend the following during the patching process:
- Shut down TopView Engine services before Windows patches
- Apply the Windows patch
- After the server has started back up, check to ensure all TopView Engine services are running in both:
- The Windows services dialog, and
- In the TopView Admin Tools application. It is possible for the TopView process to be running as a service but unable to start due to issues connecting to the data server. If the TopView process is running but does not appear able to connect, please:
- Restart the service. This is usually enough to
correct any post-patch issues.
- Check the application logs in the TopView Admin Tools application, looking for logged errors, to expose any issues that need correcting.
Sometimes, Windows will start the TopView Engine services and leave them in a bad state after a patch. This is why we recommend double-checking
and restarting the service if there are issues.
If reboots after Windows
patches regularly start TopView in a bad state, we recommend setting the TopView
service to use “Delayed Startup”.
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 ...Does TopView run on 64-bit Windows?
Yes! TopView 6.4 and later will run on Windows 64-bit operating systems.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 ...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 ...