asdffdsa's community posts

thanks for the effort, but, i cannot spend more time on this at work.

as i posted a few times, i already have a workaround to this nightmare on 10 machines in multiple locations.

the lesson i learned is this.
just as with backups, need multiple backup tools backing up to multiple locations.
so too, with remote access software, install multiple remote access software.
never depend on a single tool for any need.

i will continue to depend on remote.utilities as my main tool, but i will also install another free edition of remote access software.

please close this topic.

Conrad Sallian wrote:
I believe this is when you manually started it, correct?

no.

after the windows 11 upgrade, the host will not start on it own.
i already sent you the windows event viewer showing that RU.Host will not start after the upgrade.
this has happened on 10 machines in multiple locations.

here is the screenshot from the host machine.
clearly, RU.Host service is not running.

Conrad Sallian wrote:
Locate, zip, and send the most recent log for the day (e.g., rut_log_2024-11.html).

done

thanks, this has occurred on 10 machines, in multiple locations.

Conrad Sallian wrote:
1. On one of the machines experiencing Host issues, uninstall the Host completely.
2. Open the Command Prompt and run this command:
netstat -ano | findstr :5650

C:\Windows\System32>netstat -ano | findstr :5650

C:\Windows\System32>

Conrad Sallian wrote:
If you restart the Host computer after that, will the Host service start on its own?

no. that is the most confusing issue.

the only way is to do the following.
1. click start menu
2. type "start host", run as administrator
after that, the icon will appear in the system tray, the service is started, the host is online again.

David Silvera wrote:
since upgrading to a new version of RU and new version of Windows 11 can be a headache, like what you are experiencing.

thanks, but that is not correct time sequence.
1. several weeks ago, i upgraded RU hosts, that worked no problem
2. this week, started remotely upgrading windows 11

David Silvera wrote:
On the other hand, if the previous version of RU works fine, you could use the previous stable version of 7.2.2.0.

thanks, but no need for that.  once i manually start the RU.Host, it seems to work fine.
1. using RU.Viewer, remote into host
2. install that other remote control software, that does not this RU host issue/bug.
3. upgrade windows 11
4. reboot
5. now, RU.Host is offline.
6. remote into the host using that other remote control software
7. click start menu, type "start host", run as administrator.
8. now, RU.Host is working again.

here are two screenshots of the event viewer.

today, lost control of another three machines. in total, 10 machines.

this is from windows registry, two events
event #1

Log Name:      System
Source:        Service Control Manager
Date:          11/27/2024 10:56:49 AM
Event ID:      7009
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      PPLREIDENV
Description:
A timeout was reached (45000 milliseconds) while waiting for the Remote Utilities - Host service to connect.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7009</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-27T15:56:49.1301633Z" />
    <EventRecordID>98</EventRecordID>
    <Correlation />
    <Execution ProcessID="400" ThreadID="3488" />
    <Channel>System</Channel>
    <Computer>PPLREIDENV</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">45000</Data>
    <Data Name="param2">Remote Utilities - Host</Data>
    <Binary>52004D0061006E0053006500720076006900630065000000</Bi­nary>
  </EventData>
</Event>

event #2

Log Name:      System
Source:        Service Control Manager
Date:          11/27/2024 10:56:49 AM
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      PPLREIDENV
Description:
The Remote Utilities - Host service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2024-11-27T15:56:49.1301633Z" />
    <EventRecordID>99</EventRecordID>
    <Correlation />
    <Execution ProcessID="400" ThreadID="3488" />
    <Channel>System</Channel>
    <Computer>PPLREIDENV</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Remote Utilities - Host</Data>
    <Data Name="param2">%%1053</Data>
    <Binary>52004D0061006E0053006500720076006900630065000000</Bi­nary>
  </EventData>
</Event>

........

Conrad Sallian wrote:
One more question. Have you checked the integrity of the Host files in the C:\Program Files(x86)\Remote Utilities - Host installation directory. The files rutserv.exe and rfusclient.exe shoulld be there.

thanks, that is not the issue, i think i already explained that.

Conrad Sallian wrote:
Please note that when the Host fails to start, the most common reasons are:
1. Security software (this accounts for 99% of cases).
2. Specific settings on the machine that prevent the Host service from starting, such as certain security policies.

thanks, that was already mentioned, and i replied, that is not the issue.

since i know this is going to happen again.
you are welcome to remote into such a machine and take a look for yourself.

now, this time, both hosts are running old version 7.2.2.0
6th time this has happened.
7th time this has happened.