Mike Greene's community posts

Yes it was both in place upgrade from the very latest v6 (6.12b) I  and also uninstall and re-install of v7.  The error persisted, even when running the portable viewer.

Pulling the address xml files from backup would reproduce the error.  If I deleted the separate address books and the connections xml the program would not produce the error.

Allowing plain vanilla config and connection xml files would allow the program to run, I applied my new v7 lic key and manually created all of my entries.  no issues since doing that, but burned up a bunch of time dealing with this so probably won't test v7 much more this week, unless I absolutely need to use RU to access my remote  hosts.

At the risk of beating this dead horse, I'd have to agree the upgrade prompt caught me twice (actually 3 times!) today I figured I'd go ahead and upgrade, ugh, problems... which I posted earlier regarding address books.  I ended up grepping the XML files and recreating all my entries, hopefully I won't encounter any more issues or ones that require quite the effort that was.

Uninstalling v7 and re-installing v6 on previous "click to update" whoops... wasn't a big deal for me but your download page doesn't provide a link to v6, you would have to come here to get that info. Thankfully I keep older installers for several programs (RU is one of them)

I do like this program but there are oddities that are frustrating and expose some programming issues within the UI and core software, having been on both sides of this coin (programmer and user) I am very familiar with the difficulties with anticipating the infinite number of variables you have to deal with.

I tend to deal with the problem directly and only post here to bring to light issues I've encountered, I don't really expect solutions to the issues because I've already been down that road enough times to know the drill (uninstall/reinstall, turn off FW, use run only agent, etc etc)

Upgraded my Pro version of viewer to V7 today.  Now getting an unending cycle of errors (have to terminate process, sometimes have to reboot workstation).

Issue seems to stem from address books.  If I do not copy over my address book groups and create a new entry from scratch no issue, copy one of the .xml files and the error/crash occurs.

"send report" doesn't work, copy button works but I can just as easily grab the log file from the event log folder.

Here is the important bits from the event log (computer and user name removed)

operating system   : Windows 10 x64 build 19042
system language    : English
system up time     : 27 minutes 29 seconds
program up time    : 9 seconds
processors         : 8x Intel® Core™ i7-7700 CPU @ 3.60GHz
physical memory    : 10629/16247 MB (free/total)
free disk space    : (C:) 56.46 GB
display mode       : 1680x1050, 32 bit
process id         : $3ef4
allocated memory   : 139.73 MB
largest free block : 836.15 MB
executable         : rutview.exe
exec. date/time    : 2021-05-06 04:47
version            : 7.0.2.0
callstack crc      : $b2f2281c, $e0699f5c, $e0699f5c
exception number   : 4
exception class    : EInvalidOperation
exception message  : Control 'dxDockPanelGroups' has no parent window. Path: fmMain .dxDockPanelGroups.

thread $2478:
005fc73b +8b rutview.exe  Vcl.Controls    3360  +1 InvalidControlOperation
006055bd +79 rutview.exe  Vcl.Controls    9720 +13 TWinControl.CreateWnd
00605b42 +16 rutview.exe  Vcl.Controls    9901  +3 TWinControl.CreateHandle
01672201 +05 rutview.exe  dxDockControl   9723  +1 TdxCustomDockControl.CreateHandle
00609fe0 +1c rutview.exe  Vcl.Controls   12541  +4 TWinControl.HandleNeeded
00609fd7 +13 rutview.exe  Vcl.Controls   12540  +3 TWinControl.HandleNeeded
00609fed +05 rutview.exe  Vcl.Controls   12547  +1 TWinControl.GetHandle
0065d757 +03 rutview.exe  Vcl.ComCtrls   10108  +0 TTreeNodes.GetHandle
0065dbad +05 rutview.exe  Vcl.ComCtrls   10344  +1 TTreeNodes.GetFirstNode
018285ca +12 rutview.exe  MainForm        3330  +3 TfmMain.TimerUpdateTreeIconsTimer
006a750f +0f rutview.exe  Vcl.ExtCtrls    3193  +1 TTimer.Timer
006a73ef +2b rutview.exe  Vcl.ExtCtrls    3151  +4 TTimer.WndProc
005070e4 +14 rutview.exe  System.Classes 18175  +8 StdWndProc
767439ab +0b user32.dll                            DispatchMessageW
0073afa7 +f3 rutview.exe  Vcl.Forms      11028 +23 TApplication.ProcessMessage
0073afea +0a rutview.exe  Vcl.Forms      11058  +1 TApplication.HandleMessage
0073b321 +c9 rutview.exe  Vcl.Forms      11196 +26 TApplication.Run
018687b8 +78 rutview.exe  rutview          236 +16 initialization
7628fa27 +17 KERNEL32.DLL                          BaseThreadInitThunk

cpu registers:
>> will be calculated soon

stack dump:
>> will be calculated soon

disassembling:
>> will be calculated soon
11-05-2021__18:20:48__193 Closing.

That option already exists:

https://www.remoteutilities.com/solutions/self-hosted-server.php

The most challenging aspect of this is creating the correct port forwarding or nat rules for your brand of router/firewall.

Ya, seeing everything down again.

This has motivated me to get my on-prem RU-ID server going. (always looking for the silver lining...)

Hosts now show as online/available  (west coast)

Happening here too, West coast, all machine are showing offline/unknown and not able to connect no matter how many times I try.

Prior to the Dec 20 rutview.exe file I completely uninstalled and deleted the /app*/roaming/* folders for RU and reinstalled.

I did not uninstall/reinstall the app when using the Dec 20 .exe, I just copied over the file (keeping a copy of the July 2 .exe file elsewhere)

Answers:

1) Yes, same Win10Pro 1909 machine, connecting to the Win10Pro host is also working fine now
2) Not that specific update number, I had two updates today. (image attached)
3) Both scan mode and unicode tested, both worked fine.

Pretty odd huh?  I really wished it didn't just start working without some sort of concrete reason, but I'm glad it's working because it was a major pain to use the onscreen keyboard.

Well this is interesting, I downloaded the portable viewer, created two separate directories and extracted the contents of the zip file in each, copied over the Dec 20 build to one of them.

Applied my license, and created one entry in the address book on each version.

Tested both, and both work without issue.

I'm at a total loss as to why everything is working on both versions of viewer but I'll gladly accept it, even though it bugs me that we really don't have a reason why it would suddenly stop and then start working again.