reggoboy Posted October 29, 2008 Report Share Posted October 29, 2008 I must say that I was thrilled to see the issue of the clients going silently offline finally being addressed, some years after the issue was raised. Better late then never. But as usual, updating Retrospect has been nothing but a headache. I pushed the update to a client successfully, but promptly lost connectivity to it. Trying to reconnect gave the name/login conflict error. So I was forced to "forget" the client, forcing me down the path of having to reconfigure my entire backup scripts. Regardless, I was willing to do that. But the client shows "not logged in", and "Log in..." presents "Can't log in, error 524 (invalid activator code)". Searching forums for 524 returns nothing. Any guidance would be most appreciated as my backup strategy is now completely down. Thanks! Dave Quote Link to comment Share on other sites More sharing options...
Mayoff Posted October 29, 2008 Report Share Posted October 29, 2008 (edited) Is this happening on more then one client or just one client? Some users reported this problem with the prior release of the 6.2 application and 6.2 client. We have tried unsuccessfully to reproduce this problem. What happens if you uninstall (using the client installer) and reinstall the client on this computer? Does this client have more then one network connection running (wireless and wired)? Edited October 29, 2008 by Guest Quote Link to comment Share on other sites More sharing options...
twickland Posted October 29, 2008 Report Share Posted October 29, 2008 Dave, you don't say what version of the Retrospect app you're using. Quote Link to comment Share on other sites More sharing options...
jswingchun Posted October 29, 2008 Report Share Posted October 29, 2008 I had the same problem. I was running Retrospect server 6.1.126 with the 6.2.234 client and got the exact same error. I updated my RS to 6.1.230 and all is good again. Quote Link to comment Share on other sites More sharing options...
rhwalker Posted October 29, 2008 Report Share Posted October 29, 2008 Robin, I saw this on all four of the PPC iMacs and one eMac that I updated yesterday by the rcu. The symptom was, while on "Configure > Client", that connection was lost to the client immediately upon doing the update. However, if I then hit the "Cancel" button while connection was lost, and then re-selected the client, the correct version was shown and I was able to connect to the client. Russ Quote Link to comment Share on other sites More sharing options...
Mayoff Posted October 29, 2008 Report Share Posted October 29, 2008 Russ, after this initial failure, has it continued working? Quote Link to comment Share on other sites More sharing options...
rhwalker Posted October 29, 2008 Report Share Posted October 29, 2008 Russ, after this initial failure, has it continued working? Yes, works fine now, that's why I just treated it as a transient communication loss during the installation process, and didn't bother to report it. FYI, I have never before had a loss of communication with any clients on our network, whether on install or during backup, except during the one rcu install, years back, when there was a retropds log issue. Russ Quote Link to comment Share on other sites More sharing options...
reggoboy Posted October 30, 2008 Author Report Share Posted October 30, 2008 Is this happening on more then one client or just one client? It was BOTH. What happens if you uninstall (using the client installer) and reinstall the client on this computer? I believe I tried that and it did not help the situation. Does this client have more then one network connection running (wireless and wired)? No: one client was WiFi only and the other was Ethernet only. However, I have some updated information. My server was running 6.1.138. I didn't realize there was a newer version out. Client 1: "Test..." confirms the push to 6.2.234 succeeded, but I cannot "Add by Address..." because it asks me for an Activator Code (I don't know what that is; I have a License Code). Client 2: 6.2.234 installed locally successfully with Status: "Waiting for first access", but get "Can't log in, error 524 (invalid activator code)" when trying to "Log in..." from the server. Then I upgraded the server to 6.1.230 Now, using "Log in..." from the server to Client 2 did NOT give any errors. Also, "Add by Address..." from the server to Client 1 connected just fine after entering the correct password. So all the problems appear to be fixed. I'm now in the process of re-Subvoluming to rebuild my scripts, etc. Thanks to all of you for your attention to this matter and for the tip about upgrading the server. If I have any more problems, you'll be sure to hear from me ;-) Dave p.s. Go Phils! Scary: I remember 25 years ago when we won, too... Quote Link to comment Share on other sites More sharing options...
mwbronson Posted October 30, 2008 Report Share Posted October 30, 2008 I had the same problem when I updated the client and after I updated the application backing up the client worked fine. Mac OS 10.5.5 with all the updates. Quote Link to comment Share on other sites More sharing options...
lstone19 Posted October 30, 2008 Report Share Posted October 30, 2008 My server was running 6.1.138. I didn't realize there was a newer version out. I had the same issue. The e-mail announcing the new client said no server update was required. Well, true only if you had previously updated the server when the 6.1.230 update came out (I don't even remember seeing anything about it). So I'd say an advisory that 6.1.230 is required on the server first. So did the client update from 6.1.130 (just one fortunately), could no longer reach it, had to fall back, client login problem, forget client, redo all scripts, bleh... Then found this topic. Got the server update, updated fine, then clients updated fine except for the client being unreachable for a few seconds after the update. That's probably not unexpected - it needs to restart. Just cancel, wait a few seconds, and try to reconnect. Nightly backups all ran fine last night so it looks like it's good. Quote Link to comment Share on other sites More sharing options...
RavenPlenty Posted November 10, 2008 Report Share Posted November 10, 2008 (edited) I am having similar troubles. I am running Retrospect 6.1.230 on the host computer, and have 5 client computers running Client 6.2.234. After I updated the first client to 6.2.234, I discovered the issue where it would not activate after restart. Advice was to uninstall and reinstall the Client. I did that 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? ...And the other 4 clients simply don't appear at all in the Retrospect Network control panel. Help? Edited November 10, 2008 by Guest Quote Link to comment Share on other sites More sharing options...
RavenPlenty Posted November 12, 2008 Report Share Posted November 12, 2008 The answer to my problems is available here: http://forums.dantz.com/showtopic.php?tid/28561/ 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.