RavenPlenty Posted November 12, 2008 Report Share Posted November 12, 2008 The back story: I am running Retrospect 6.1.230 on the host computer, and have 5 client computers running Client 6.2.234. After updating from 6.1.130 to 6.2.234, I discovered the issue where it would not activate after restarting. Advice was to uninstall and reinstall the Client. I did that on one client and it worked fine. Satisfied with the apparent solution, I've done the same (uninstall/reinstall) on the remaining 4 client computers and now my problem is this: Only one computer is visible on the Retrospect Network, and I can't connect to it – "An additional client licence code is required in the Licence Manager." What happened? ...And the other 4 clients simply don't appear at all in the Retrospect Network control panel. Help? Quote Link to comment Share on other sites More sharing options...
rhwalker Posted November 12, 2008 Report Share Posted November 12, 2008 Perhaps you need to forget the clients in Retrospect and add them again. That would reset the license issues. One thing you might want to do is to restore your Retrospect preferences from a backup, because, when you forget the clients and re-add them, that will remove them from your scripts. If you don't have too many scripts, you could just add the clients back. Russ Quote Link to comment Share on other sites More sharing options...
RavenPlenty Posted November 12, 2008 Author Report Share Posted November 12, 2008 Just figured this out, apparently as you were responding. Yes, sure enough I had to delete all the clients first. Then everybody showed up on the network and I was able to re-add them as clients again. And yes they were removed from the scripts so I had to add them back into the scripts as well. Man oh man, Retrospect is just baffling sometimes. It's not just me, right? Thanks for your help though. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted November 12, 2008 Report Share Posted November 12, 2008 Man oh man, Retrospect is just baffling sometimes. It's not just me, right? No, it's not just you. We've been using Retrospect since 1992 at our firm, and updates go through spells when they cause fits. Amy Jensen (former Retrospect QA) is greatly missed. I've learned to test thoroughly on a testbed machine before updating all the production computers in the office. You might want to offer to be a beta tester to help ensure that releases go smoothly on configurations like yours. I am hopeful that the Retrospect X release, rumored for later this year, will be less fragile because it will be built on a modern code base. Regards, Russ Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.