Jump to content
Sign in to follow this  
algilson

Windows 2003 SP2

Recommended Posts

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:

retro_crash.jpg

 

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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). cool.gif

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×