willfurby Posted June 4, 2008 Report Share Posted June 4, 2008 (edited) Windows SBS 2003 SP1 Retrospect SBS Premium v7.5.508 Drivers Update and Hotfix v7.5.14.102 We are receiving Assert errors on a random basis, but they are happening frequently. There is a proactive script that runs, but the error happens at night when the "Nightly" backup script runs. The "nightly" backup script only backs up the internal server drives. The backup drives are also internal. I though about attaching the assert log here, but it is pretty big. I can copy just the latest error portion if needed. Any help would be appreciated. If you need any more information, please do not hesitate to ask. Thanks. Edited June 4, 2008 by Guest Quote Link to comment Share on other sites More sharing options...
Mayoff Posted June 4, 2008 Report Share Posted June 4, 2008 Does the assert happen when you use a different backup set? If not, then you probably have corrupt catalog file for the failing backup set. Quote Link to comment Share on other sites More sharing options...
willfurby Posted June 4, 2008 Author Report Share Posted June 4, 2008 I have already re-created the backup set for these drives; and I have created a new backup set. Neither of these options appear to fix the problem. It will run without error for a couple of nights and then error out. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted June 4, 2008 Report Share Posted June 4, 2008 What is the actual assert error code reported? Does it matter which internal drive is being copied when it fails? Quote Link to comment Share on other sites More sharing options...
willfurby Posted June 4, 2008 Author Report Share Posted June 4, 2008 I did not write down the assert code, and it is not listed in the assert log. Here is the what the first portion of the log is: OS: Windows Server 2003 version 5.2 (build 3790), Service Pack 1, (32 bit) Application: C:\Program Files\Retrospect\Retrospect 7.5\Retrospect.exe, version 7.5.508 Driver Update and Hot Fix version 7.5.14.102 Exception occurred on 6/1/2008 at 1:50:00 AM Exception code: c0000005 ACCESS_VIOLATION Fault address: 64307638 0001:00006638 (null) I am not sure which drive it is currently backing up when the errors happen. Is there a way to find out? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted June 5, 2008 Report Share Posted June 5, 2008 ACCESS_VIOLATION is the error. It is a generic crash. It could be cause source specific or even corrupt preferences. Try to watch the backup to see what it copying when it crashes. Quote Link to comment Share on other sites More sharing options...
MRIS Posted June 5, 2008 Report Share Posted June 5, 2008 It could even be hardware related, such as bad RAM. Quote Link to comment Share on other sites More sharing options...
willfurby Posted June 10, 2008 Author Report Share Posted June 10, 2008 I just received another assert error. This time it was attempting to backup a client. Here is the beginning of the error log: OS: Windows Server 2003 version 5.2 (build 3790), Service Pack 1, (32 bit) Application: C:\Program Files\Retrospect\Retrospect 7.5\Retrospect.exe, version 7.5.508 Driver Update and Hot Fix version 7.5.14.102 Exception occurred on 6/5/2008 at 9:43:06 AM Error info: Assertion failure at "elem.cpp-1000" Exception code: e0000000 ASSERTION Fault address: 77e55e02 0001:00014e02 (null) Quote Link to comment Share on other sites More sharing options...
Mayoff Posted June 11, 2008 Report Share Posted June 11, 2008 This error could be caused by a corrupt config75.dat file. I would try to rename the Retrospect folder in documents and settings\all users\application data and try Retrospect again. Quote Link to comment Share on other sites More sharing options...
willfurby Posted June 11, 2008 Author Report Share Posted June 11, 2008 I have renamed and recreated the configxx.dat file before; but, I have never renamed the Retrospect folder. Will it be recreated or should I rename the old folder and create a new one with nothing in it? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted June 11, 2008 Report Share Posted June 11, 2008 A new folder will be created during your next launch. This might help with the Chunk checksum error you also reported. Quote Link to comment Share on other sites More sharing options...
willfurby Posted June 11, 2008 Author Report Share Posted June 11, 2008 Awesome! I will give that a try. We do nightly backups so I will update this topic tomorrow after I review the logs. Thanks. 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.