Community
Just an Update Info
Links used in this discussion
- https://www.remoteutilities.com/support/forums/forum1/2268-host-sometimes-fails-to-start-after-boot-up
- https://www.remoteutilities.com/support/kb/host-service-won-t-start/#How_to_export_Windows_System_Events_log_Windows_10_
- https://www.remoteutilities.com/support/docs/host-log/
- http://mcadsl.com/pub_files/RUMonitor.msi
- http://mcadsl.com/pub_files/RUMonitorSource.zip
- https://www.remoteutilities.com/support/docs/installing-and-uninstalling/#Uninstall_Host
- https://www.remoteutilities.com/support/forums/messages/forum1/message10215/1977-is-it-just-me
- https://www.remoteutilities.com/test/set_config.zip
We have a small number of machines that run customer choice software - Norton, TrendMicro and some with just plain Windows Defender.
I have created exceptions in Emsisoft and Webroot previously as a precaution, I did not see any change. With the other systems, I have not created any exceptions.
I have now updated all the servers [8] on a single site to the new 7.2.10 host and disabled the RUM. I have also enabled the local logging on these machines. I have not yet updated the self hosted server version. Does that need to be done in order to test the new version effectively?
Matthew
Yes, please keep it disabled. Let's test one solution now. Please, unzip and run this script on the Host computer as administrator. You should get the following settings as a result (it's in the Remote Utilties - Host sevice properties):I have now updated all the servers [8] on a single site to the new 7.2.10 host and disabled the RUM.
Note: the script will work only if the Host is installed in the default folder, i.e. Program Files (x86). Also note that there's the parameter -restart added. In a nutshell, this modifies the Host restart process slightly by running a code (which has already been there since previous versions) by killing all running instances of rutserv before attempting the restart. We assume that this could have been the bottleneck and the reason why the Host couldn't restart properly even when you used the settings as on the screenshot.
Download set_config.zip
You can test this for a while on several Hosts - I also encourage anyone else to join the testing. If this resolves the problem we will include the fix in the very next update.
Answering your question about RU Server - it's not necessary, but it will do no harm if you upgrade the server, just in case.
Thanks.
UPD: Updated the script to also accomodate 32-bit versions of Windows.
I have just run the script on one of these machines (while logged on remotely) and rebooted it after doing windows updates. The machine has rebooted (I can ping it) but the host has not restarted. I shall be there on site tomorrow, so can check if the service properties are still changed according to the script. It may be that the script should have been run while the host service was not running.
It looks as though it is setting the service to run rutserv.exe -restart on the first and second failure, and nothing on subsequent failures.
I had previously set these to 'Restart the Service' upon failure, with no effect.
Matthew
Hi Matthew,Matthew Cooper wrote:
Hi Conrad, am I correct in my interpretation that this script simply changes the parameters on the Recover tab for the RManService [Remote Utilities - Host]?
It looks as though it is setting the service to run rutserv.exe -restart on the first and second failure, and nothing on subsequent failures.
I had previously set these to 'Restart the Service' upon failure, with no effect.
Matthew
Yes, it is. But the point is that it now sets this -restart flag which triggers the code in the program that properly performs the restart. Of course, the script is just helper to set these settings, and we are only testing now. I recommend that you test this configuration for a while and see.
Hello Shane,Shane Farmer wrote:
For me it starts after machine start and it will then stop working after 5 to 10 minutes. I can restart the service, same issue. It's one three machines. All of them have this issue. Since moving to one of the 7.x versions. I will send logs next week as I just quite trying to use it after a year of no fixes.
The reason for stopping the service may well be of an external nature, it cannot just stop by itself. You should carefully check if there's no software (especially security software) that interferes with the host operation.
Hello Peter,Peter Gray wrote:
I have not noticed the problem with host service stopping, but I have several old slow machines where the host service does not reliably start on switch on or on reboot. With some of these, I dare not do a reboot unless I am on site, so able to restart the host manually.
I have just run the script on one of these machines (while logged on remotely) and rebooted it after doing windows updates. The machine has rebooted (I can ping it) but the host has not restarted. I shall be there on site tomorrow, so can check if the service properties are still changed according to the script. It may be that the script should have been run while the host service was not running.
What is the operating system on those machines?
All my older machines are Windows 7, except one remaining working XP. Not all of them have the startup issue. The one I tested yesterday is W7I have just run the script on one of these machines (while logged on remotely) and rebooted it after doing windows updates. The machine has rebooted (I can ping it) but the host has not restarted. I shall be there on site tomorrow, so can check if the service properties are still changed according to the script. It may be that the script should have been run while the host service was not running.
Hello Peter,
What is the operating system on those machines?
When I checked it this morning, the host service properties were still as modified bythe script, so running the script while the service was running was OK.
While looking at the host servicce properties I changes the Startup Type from Automatic to Automatic (Delayed Start), and then rebooted the machine. This time the host service *did* start on re-boot. So far I have only tried this once, on the one machine. I plan to do the same change on the other slow machines.
* Website time zone: America/New_York (UTC -4)