steveaustin Posted October 13, 2008 Report Share Posted October 13, 2008 Hi, I've been experiencing the dreaded assertion failure error on a reasonably frequent basis recently, twice in the last 48 hours. The exact error is "Assertion failure at type.cpp-2609" It's occurring during our automated overnight backups, standard Disk to Disk backup followed by a Normal backup to tape. Nothing unusual, data being pulled off a few servers running Retrospect Client. The error claims to write details to a file called "assert_log.utx", but I can never find this file - is this not in fact occurring? Has anyone run across this before? Any ideas what might be causing it, or what I can do to fix this? Currently it's seriously affecting our ability to provide a reliable backup service for our users; not very good considering this is supposed to be a professional backup solution! Quote Link to comment Share on other sites More sharing options...
steveaustin Posted November 7, 2008 Author Report Share Posted November 7, 2008 Apologies, I misread the error - it's 'tyce.cpp', not 'type.cpp'. Anyone have any ideas? It's still crashing 4/5 times a month at random intervals. It also crashes on occasion with error 'elem.cpp-1000'. TIA for any assistance! Quote Link to comment Share on other sites More sharing options...
Mayoff Posted November 7, 2008 Report Share Posted November 7, 2008 You may have corrupt preferences. Try to rename the Retrospect folder inside documents and settings\all users\application data. Quote Link to comment Share on other sites More sharing options...
steveaustin Posted November 10, 2008 Author Report Share Posted November 10, 2008 I'll give this a go, but given that the error occurrence is sporadic I won't know for sure if this is successful for a while. Is there any information on what can cause corrupt preferences or how I can prevent this happening again? Quote Link to comment Share on other sites More sharing options...
steveaustin Posted January 19, 2009 Author Report Share Posted January 19, 2009 After further investigation on this it turns out that Retrospect is sporadically crashing when SQL server 2000 is running its transaction log backups. Every crash timestamp over the last 6 months is within a second or two of SQL server initiating a TLog backup. 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.