pjwidener Posted April 2, 2008 Report Share Posted April 2, 2008 (edited) I'm having this same problem. I've received an "execution terminated unexpectedly, possibly due to a power failure or system crash" error the last 3 days. It's an engine error...will the 7.5.14.102 driver update and hotfix take care of this problem? I haven't received this error until I updated to 7.5.13.100. Any help would be appreciated. Edited April 2, 2008 by Guest Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 2, 2008 Report Share Posted April 2, 2008 I have split your post into a new topic. 1) What is your Retrospect application version. You only provide the driver version. 2) What is the exact error reported in the operations log or in the crash dialog box? The error you describe is generic and will happen ANY time Retrospect fails to close correctly. 3) What is Retrospect doing when the failure happens? 4) What operating system version? 5) What type of backup device? Please be specific. The more details you provide, the easier someone can answer your question. Quote Link to comment Share on other sites More sharing options...
pjwidener Posted April 2, 2008 Author Report Share Posted April 2, 2008 Sorry for the lack of detail. Here is the requested information. Application version = 7.5.512 Driver Update and Hot Fix, version = 7.5.14.102 I have attached the exact error that I'm receiving When the failure happens, it's either running a scheduled execution...and today, when I ran a manual execution. Operating system = Windows Server 2003 R2, SE, SP2 Backup device = Tape Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 2, 2008 Report Share Posted April 2, 2008 Please see this troubleshooting guide http://kb.dantz.com/article.asp?article=6306&p=2 Does it happen with one backup set or multiple backup sets? Could be a corrupt catalog file or damaged preferences. Quote Link to comment Share on other sites More sharing options...
pjwidener Posted April 2, 2008 Author Report Share Posted April 2, 2008 As of today, it's just this specific backup set. I guess I could try to run a repair on the catalog file. Quote Link to comment Share on other sites More sharing options...
pjwidener Posted April 2, 2008 Author Report Share Posted April 2, 2008 When the execution hits a certain source, the backup script will hang on "Preparing to execute..." for quite some time, and then pop up the previously attached error. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 2, 2008 Report Share Posted April 2, 2008 Does the problem always happen on the same source and not others? If this is a client, try to forget the client from the client database and then add the client again. If this happens to just one backup set, then try a 2nd backup set or do a catalog rebuild. Quote Link to comment Share on other sites More sharing options...
pjwidener Posted April 2, 2008 Author Report Share Posted April 2, 2008 It was directly involved with a particular source. I forgot that client and then re-added it; moving it to the start of the execution list and it resulted in the same assertion failure at "elem.cpp-986" Would a re-installation of the client take care of this? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 2, 2008 Report Share Posted April 2, 2008 If it really just happens with this client, then it won't hurt to reinstall it. Not sure if it will really help. In rare cases, a client may send bad data over the network causing a crash. I suspect the client's snapshot is hosed in the catalog and a catalog rebuild is needed. Quote Link to comment Share on other sites More sharing options...
pjwidener Posted April 3, 2008 Author Report Share Posted April 3, 2008 Once I re-installed the backup client on the server, I noticed that the source in question was running client version 7.0.107. So...once I re-installed the client version 7.5.116, and re-added the client to the script, the execution ran smoothly. Just wanted to give an update, and thanks for the help. Quote Link to comment Share on other sites More sharing options...
ekeller Posted May 16, 2008 Report Share Posted May 16, 2008 I have also been recieving thsi error. This is on a new server installation, new scripts, new backup clients. Ernie Keller GFPS Great Falls, MT Quote Link to comment Share on other sites More sharing options...
Mayoff Posted May 16, 2008 Report Share Posted May 16, 2008 Ernest, you have not provided us with any info we can use to help you. What version of Retrospect are you using? What is Retrospect doing when the error happens? How do you reproduce the error? What is your storage device? What type of backup set? What operating systems? What troubleshooting have you tried so far? Quote Link to comment Share on other sites More sharing options...
ekeller Posted May 16, 2008 Report Share Posted May 16, 2008 I am using Retrospect 7.5 with all of the latest updates and fixes. I am using a server with Server 2003 SP2, with 2 GB Memory and 3 TB internal hard drives. The server was set up and Retrospect 7.5 was installed on 5/12/08 and updated. I am using automated scripts which were just written on 5/14/08. These scripts are similar to those which were written for Retrospect 7.0 but they were not copied. Ernie Keller GFPS Great Falls, MT 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.