Insixdays Posted November 16, 2012 Report Share Posted November 16, 2012 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 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted November 19, 2012 Report Share Posted November 19, 2012 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. Quote Link to comment Share on other sites More sharing options...
Cygnis Posted November 26, 2012 Report Share Posted November 26, 2012 ...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 Quote Link to comment Share on other sites More sharing options...
ashleyandy Posted November 26, 2012 Report Share Posted November 26, 2012 I'm having the exact same issue and when I try to rebuild, I get the same error message -2259. Quote Link to comment Share on other sites More sharing options...
ashleyandy Posted November 26, 2012 Report Share Posted November 26, 2012 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. Quote Link to comment Share on other sites More sharing options...
MatthiasKoehler Posted November 28, 2012 Report Share Posted November 28, 2012 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! Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted November 28, 2012 Report Share Posted November 28, 2012 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. 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.