Jump to content
Sign in to follow this  
Yoann

Retrospect not launching scheduled scripts

Recommended Posts

Interesting. IME, opening & closing Retrospect has never solved the problem, nor does restarting the service, or, for that matter, restarting the computer. Those were all obvious things I tried before I learned about the service reinstall procedure.

 

The only workaround that's ever worked for me is reinstalling the service via the Retrospect Preferences dialog box. Opening Retrospect will start waiting backups running in the foreground if the Launcher is corrupted. But once Retrospect is closed, no further scheduled backups run until the Launcher is reinstalled.

Share this post


Link to post
Share on other sites

It seems, then, that we have different problems exhibiting the same symptoms.

 

Opening Retrospect also starts waiting backups, but after closing it again, scheduled backups start running on schedule as before.

 

Are you running 6.0 Multiserver as well?

Share this post


Link to post
Share on other sites

Currently 7.0 Small Business.

 

I've run every Retrospect version number since 5.5 in Express, Pro, Single-Server and Small Business flavors on Win 2K Pro, Win XP Pro, Win 2K Server and SBS 2003...and all with the same problem and workaround.

Share this post


Link to post
Share on other sites

Odd. I'm not sure how, or if, our problems are related. Same behavior, but definitely not the same workaround. Still, sounds like the Launcher service is buggy in some way...

 

Then again, I don't believe Dantz releases patches to fix bugs in its software; they seem to just release a next version. So, if they do pinpoint a bug, I'm not sure it'll help my current situation in any way.

Share this post


Link to post
Share on other sites

Hi

 

If we can pinpoint a bug we will definitely do something about it. Very often bugs can be fixed in driver updates so we release them that way.

 

Jeff V - it sounds like you have always had this problem. It really sounds like there is something unique about your setups that causes the launcher service to fail. Can you think of any special steps you always take when setting up your machines?

 

I've got about 10 different test machines and they all work and always have.

 

Thanks

Nate

Share this post


Link to post
Share on other sites

Not sure what to say, just reporting the behavior I've observed on several occasions... For now, I guess I'll just have to kick the Launcher Service every so often to get it to work.

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  

×