cgtyoder Posted February 25, 2010 Report Share Posted February 25, 2010 Running Retrospect 7.7.208.0 Single Server on Windows Server 2008 Std x64 SP2. Been having some problems lately - one of them is that when I attempt to quit Retrospect, it hangs and will not quit. End Task from Task Manager does the trick. However, when I attempt to restart Retrospect, I get a Retrospect Monitor window saying, "Cannot connect to Retrospect." I have to use Task Manager as well to kill this. I end up having to restart the server to get things working again. What is happening here? Quote Link to comment Share on other sites More sharing options...
cgtyoder Posted February 25, 2010 Author Report Share Posted February 25, 2010 It gets worse now - after restarting this time, I am still getting the Retrospect Monitor window saying, "Cannot connect to Retrospect." Any suggestions? Do I need to reinstall R? Quote Link to comment Share on other sites More sharing options...
railes Posted February 26, 2010 Report Share Posted February 26, 2010 How about replacing the Config77.dat file in C:\Documents and Settings\All Users\Application Data\Retrospect with a backup? You may be able to use Config77.bak but that might be corrupt also. The other day, Retrospect was crashing every time I went into change a script. Wasn't polite - it seized up the whole server, forcing a hard restart 3x. I finally replaced Config77.dat from a backup 2 days prior and that fixed it. Quote Link to comment Share on other sites More sharing options...
cgtyoder Posted March 1, 2010 Author Report Share Posted March 1, 2010 Rich, you are The Man. That did it. (I did have to reboot, then stop the Retrospect Helper Service first before I could change the Config77.dat file.) Thanks for the assistance. 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.