Doug, like the app, was wondering why i get this on some of the systems. Could not find file \\servername\c$\RRx\rrxTemp.log. The folder gets created but am getting this on screen of the tool. I seems to be hit and miss between servers and workstations.
Could not find file \\servername\c$\RRx\rrxTemp.log
(13 posts) (4 voices)-
doug
Key MasterPosted 10 months ago # -
doug
Key Masterlittlemac - can you provide me with more information? What action are you performing when you get that message? Does anything else happen? When the rrxTemp.log file does not get created, it likely means that the WSUS script is not getting executed on the remote machine. This could be a permissions issue, or more likely I'm thinking it has something to do with PsExec. Make sure PsExec is in your system path or in the same directory as RemoteRebootX.exe. Also make sure to manually execute PsExec one time so that you can accept the license agreement. Let me know if this works. If not, please provide me with the exact steps that you are taking to get this error.
Thanks,
DougPosted 10 months ago # -
hadadink
MemberDoug, I am seeing this issue also. I've added two hosts for testing. I've copied psexec.exe to my \Windows dir and executed it once to accept the EULA. So, when I right click on one of the hosts and choose "WSUS - search, download, install + reboot if required", this is whey I get that error. I've noticed that when choosing any other "WSUS" action, things seem to work fine.
Thanks,
AlanPosted 9 months ago # -
doug
Key MasterAlan - am I understanding correctly that you're able to use "WSUS - install downloaded updates + reboot if required" without getting any errors, but that you DO get the error when using "WSUS - search, download, install + reboot if required" ?? I must say I'm a bit baffled by this one and something doesn't sound quite right. Please confirm that I'm understanding correctly. It seems to me that if one works, so should the other, but to have one work but not the other is weird. However I also need to have more precise error checking (will be implementing that going forward), so sometimes some of the errors are a bit misleading. In this case though, I'm not quite sure. Let me know if I'm understanding correctly.
Thanks,
DougPosted 9 months ago # -
grsavage
MemberI'm having the same issue on 1 out of 80 servers.
Selecting "search, download, install" OR "install downloaded updates" results in "Could not find file \\servername\c$\RRx\rrxTemp.log".
If I go to the remote server and manually create rrxTemp.log file, the next attempt at "search, download, install" OR "install downloaded updates" results in "Could not find WSUS Search Download Install Updates.exe. Make sure that it exists in the directory as RemoteRebootX.exe". (I do not have such a file; my download didn't include it) After getting this message, the rrxTemp.log on the remote machine no longer exists, and the next "install" attempt results in the first message mentioned (could not find WSUS...).
On this machine I CAN:
-Get Last Boot Time
-Start/Stop PingingI CAN'T:
-Install dwonloaded updates
-search, download, install updates
-view logI am currently unable to try any option that include "reboot" because I can't risk taking the machine down at the moment.
Other than this blip, I love the program; Don't know why Microsoft couldn't have included this stuff.
Posted 9 months ago # -
doug
Key Mastergrsavage - are you using "integrated security" ?? Try manually entering the credentials instead of integrated security. Let me know if that changes anything. It sounds like there's some weird authentication issue that's preventing RemoteRebootX do it's thing. Admittedly, me error checking is not perfect in this app right now, and the errors you are getting are not exactly accurate, which just means it's harder to figure out the exact cause of the problem. At some point I plan to make the error handling more robust but for now this is what we've got. Let me know if you have any luck specifying credentials instead of using integrated security.
-Doug
Posted 8 months ago # -
louis
MemberI get the same error, i have tried every single update style, even played with the credentials every time i get the could not find file, if i create the log file manualy i then get a error PsExec error: 2.
I would love to get this tool going i have 150 servers located everywhere this would make my year.Posted 6 months ago # -
doug
Key MasterLouis, can you watch the remote system in C:\RRx when you execute the WSUS action? Does a WSUS.Install.Downloaded.Updates.exe file get copied to that directory or not? Let me know.
Thanks,
DougPosted 6 months ago #
Reply
You must log in to post.