reowen Posted June 30, 2008 Report Posted June 30, 2008 When I install 6.2.229 on my 10.4.11 MacBook Pro it will not run with "The Client was installed without root permission". (Note that the installer *did* authenticate and I *did* install from an admin account). Based on one tip I found online I did enable the root account (with great reluctance; it is insane that one would have to open one's computer up like that), but have not tried the installation from that account. I guess I should try that next. I tried to unintall 6.2.229 and install 6.1.130 instead, but it fails in the same way. So at the moment I have no operable client.
rapope Posted June 30, 2008 Report Posted June 30, 2008 Odd that you are having issues with admin permissions as well. I am unable to install the 230 program itself. It would seem logical that it isn't just the both of us having these issues. Good luck with your issue, Rocky
Mayoff Posted June 30, 2008 Report Posted June 30, 2008 You should never need to enable to root account to install the Retrospect Client software. If the 6.1.130 client has the same problem, then you are not seeing an issue with the new client software. You appear to be having some type of system permissions issue.
rapope Posted June 30, 2008 Report Posted June 30, 2008 It seems odd that two users are having permissions issues... I ran a "repair disk permissions" for my issue and it has no effect. Thanks, Rocky
Mayoff Posted June 30, 2008 Report Posted June 30, 2008 Rocky. The creator of this thread reported a problem installing 2 different versions of the client software, not a problem with installing the application that you reported. So this would be a totally different issue. What happens when you try to install the prior version?
CallMeDave Posted July 1, 2008 Report Posted July 1, 2008 As I replied on RetroTALK this morning, there used to be an issue if the "Install OS X Client" VISE installer application was launched directly from a file shared remote volume. If the installer was copied locally, or if the installer was still on the disk image (which could happily live on a shared volume) there would be no issue. - How, exactly, did you perform the install that failed? Dave
Mayoff Posted July 1, 2008 Report Posted July 1, 2008 Clearly something didn't work correctly during the install. We ran a very long beta program and didn't see a single report of this until after the final release. We would like to reproduce the problem and fix it, so any configuration specific details you can offer will be helpful. You can try to fix this problem by resetting the permissions: 1) Run /Applicatons/Utilities/Terminal.app 2) From Terminal, change directory into Retrospect Client's bundle cd /Applications/Retrospect\ Client.app/Contents/Resources 3) From Terminal, change permissions on retroclient chmod u+s retroclient 4) From Terminal, change ownership of pitond. You will be prompted for admin password. sudo chown root:admin retroclient
rapope Posted July 1, 2008 Report Posted July 1, 2008 Hi, I ran the installer from a local volume. In my case, the installer somehow thought my admin account was a regular user account. A reboot "cured" the problem.
Mayoff Posted July 14, 2008 Report Posted July 14, 2008 An updated version of the Retrospect Client .rcu files was posted to our website on Friday. This update should prevent future client updates from having problems.
cwwade3 Posted July 16, 2008 Report Posted July 16, 2008 You indicate that there is an updated rcu file for the client installer on the Retrospect web site, but I can't find it. The only item listed was posted on 6/30, not last Friday. Is this just a problem with the date listed on the web site?
Mayoff Posted July 17, 2008 Report Posted July 17, 2008 Yes, the dates have not been updated but the software has been.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.