Jump to content
Sign in to follow this  
atravesde

Retrospect crash - help

Recommended Posts

i am having this error

please any idea what to do

everything was going good about 4 months

until yesterday, when this error display

thank you very much

 

Edited by Guest

Share this post


Link to post
Share on other sites

This error is sometimes caused by corrupt preferences. I would just try a restart of the computer first. If that doesn't help, then you may need to try restoring and using an older config75.dat file.

Share this post


Link to post
Share on other sites

i already did that, i use the config.bak

and the same problem,

 

then i reinstall the application (same build, in the modify option)

and it works about just 1 day. Now the error

comes again.

We dont know what to do, cause when i try to access an option, the assertion failure comes

then the retrospect quits.

 

the other option is to replace the spanish version (latest 387) with the 508 but there is only english version.

 

what else can i try?

 

thank you

 

Maynor

 

 

 

 

Share this post


Link to post
Share on other sites

The .bak file could have also contained corruption since it is a backup copy of the newest .dat file. You should be starting with totally new preferences to see if the problem continues.

 

If you want to try an old config, you need to restore it from a week or two prior to the crashes.

Share this post


Link to post
Share on other sites

i understand that.

But the problem is that the error occur in a customer server.

 

just to confirm.

what happend if i restore and old config dat or bak file, where since the modification date the customer add 100 clients, make 20 schedule scripts, and 10 proactive backups. create 30 containers client, define 100 subvolumes.

the answer is

do i have to repeat and define all these setings

to be at the actual retrospect Settings state?

 

thank you again

 

Maynor

 

 

 

 

 

 

Share this post


Link to post
Share on other sites

If you restore a config file that was created before you made all the script and client changes, then you will need to re-do those things.

 

Removing the config is a test. if it doesn't work, then you revert to the old config.

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  

×