Jump to content
Insixdays

Retrospect 8 upgrade from 7.7 error message Assertion failure at "grx.cpp-1089"

Recommended Posts

Just upgraded from 7.7 to 8.0. The server does not see any of the 7.7 clients so I can update them and grooming jobs run and then I get the Assertion failure at "grx.cpp-1089"

The server is Windows 2008 R2. This is also a case with Retrospect #00013353

Share this post


Link to post
Share on other sites

This error always happens if you have a catalog file that is corrupted due to a prior failed grooming operation. I suggest doing a catalog rebuild for the set you were using at the time of the crash.

Share this post


Link to post
Share on other sites

...grooming jobs run and then I get the Assertion failure at "grx.cpp-1089"

 

I received this error the first time I tried grooming after upgrading to Retrospect 8. So I rebuilt my catalog, tried grooming again, and got the same error! Any other suggestions?

 

I never encountered this on version 7.7, which I have used successfully for over 2 years...

 

Edit: Additionally, I cannot even view the properties of the affected Backup Set once this error has occurred. When I try to, I get an error message -2259 (incomplete grooming detected). Looks like I'll be rebuilding it a second time :(

Share this post


Link to post
Share on other sites

i deleted the backup set altogether and recreated and it corrected the issue. however, thats not feasible for most. im wondering whats going to happen the next time anything needs to be groomed.

Share this post


Link to post
Share on other sites

I also have problems with this error after Update vom 7.7 to 8.0. My difficulty was, that Retrospect start automaticly with grooming after a start, so I didn't had the chance to stop this job and retrospect crashes everytime after a few seconds.

 

At first, I decided to reinstall the software, but then I tried to use the old config77.bak. And really, this works better, because the grooming-job didn't start any more. So I also rebuild now the catalogue. Hope this will work.

 

Please Retrospect Team, catch this exception an make the Programm to continue in a better way. This crash wasn't good. Thanks!

Share this post


Link to post
Share on other sites

Please Retrospect Team, catch this exception an make the Programm to continue in a better way. This crash wasn't good. Thanks!

This is just a user-to-user discussion. Please contact Retrospect Support directly.

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

×