algilson Posted April 2, 2007 Report Share Posted April 2, 2007 Over the weekend we installed Windows 2003 Service Pack 2 on our Retrospect Server host. + $[15]Retrospect$[16] version 7.5.370 Launched at 4/2/2007 7:23 AM + Driver Update and Hot Fix, version 7.5.10.104 Exit at 4/2/2007 7:24 AM Now every time I launch Retrospect it appears to render the screen as if it's loading, and the freezes. See: If I delete the config75.dat and .bak files, and launch Retrospect it will start properly. I then enter my access codes, and arrive at the proper Activity Monitor screen. If I quit Retrospect and relaunch, it freezes on launch again. Help? - Al Quote Link to comment Share on other sites More sharing options...
algilson Posted April 2, 2007 Author Report Share Posted April 2, 2007 Update: sorry, I should have added that I run Retrospect through a terminal session. I just realized that if I run Retrospect from the local machine, not through RDP, it runs fine. Not ideal, but it runs. - Al Quote Link to comment Share on other sites More sharing options...
mauricev Posted June 27, 2007 Report Share Posted June 27, 2007 That implies there is a bug in Retrospect that is tripped by something specific in the configuration, though I didn't know it was affecting only through RDP, though. I'm using RDP on the Mac. Quote Link to comment Share on other sites More sharing options...
misleb Posted June 27, 2007 Report Share Posted June 27, 2007 Try editing your connection profile and tell it to connect to the console of the server instead of a regular TS session. Add this line to your profile with a text editor: connect to console:i:1 Quote Link to comment Share on other sites More sharing options...
AmyJ Posted June 28, 2007 Report Share Posted June 28, 2007 The Service Pack upgrade is changing the permissions on our configuration folder to “Everyone: Full Control” Resolution: Change permissions on C:\Documents and Settings\All Users\Application Data\Retrospect: 1. Remove Everyone 2. Add Administrators: Full Control 3. Add SYSTEM: Full Control This should allow access Retrospect via Remote Desktop again. To be clear, this is a Microsoft bug. A service pack upgrade should not change the permissions on our folder. Amy Quote Link to comment Share on other sites More sharing options...
mauricev Posted June 28, 2007 Report Share Posted June 28, 2007 I'm not sure what's going on. SP2 may be altering permissions on or in the Retrospect folder, but I don't see how it could trigger such odd behavior. On my end, resetting the permissions on this directory and what's in it didn't make any difference. OTOH, setting RDC to login to the console allows Retrospect to work (and apparently regardless of the permissions). 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.