RE: Retrospect 4.3 (Mac) Assertion Check?
Here's my 2c... I was running Retro 4.2 on an 8100 without problem. After I upgraded to Retro 4.3, I started getting asserts pretty frequently, complaining that the catalog was out of synch, IIRC. I replaced the RAM in the 8100 and the problem went away. Brad. -Original Message- From: Mark [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 07, 2001 5:48 PM To: Irena Solomon Cc: retro-talk Subject: Re: Retrospect 4.3 (Mac) Assertion Check? On Wed, 7 Feb 2001, Irena Solomon wrote: This particular assert we are currently tracking and believe it to be ASIP Memory Management-related. Most users who have seen this error report that after restarting the assert does not reproduce. Thanks for the quick reply, Irena. In our case, simply restarting the Retrospect application seemed to cure the problem - at least for now. In the instances where it was reproducible, we've found that disabling third-party server administration tools have been effective in addressing it. Such tools as Timbuktu? This is an OS 8.6/ASIP 6.2.2 7250 server that has run successive versions of Retrospect 4.x (and TB2 4.x and 5.x) for at least two years, and this is the very first time for this little problem to occur. However, it *seems* to be specific to Retro 4.3, and we may try a regression to Retro 4.2 if the behavior persists. Keep your fingers crossed g. Thanks again, MI -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Search: http://www.mail-archive.com/retro-talk%40latchkey.com/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050. -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Search: http://www.mail-archive.com/retro-talk%40latchkey.com/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Retrospect 4.3 (Mac) Assertion Check?
Retrospect Experts: I am copying Dantz on this, but a search of the Retrospect error list on their Web site does not mention this one: Trouble in Retrospect: Internal consistency check failed: Assertion check at "elem16.c-438" [Quit] This is with version 4.3, and a relaunch of the program has begun the scripted backup that had been aborted at Midnight due to the above issue. Does this sound familiar to anyone here? Regards, Mark E. Ingram [EMAIL PROTECTED] (also [EMAIL PROTECTED]) -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Search: http://www.mail-archive.com/retro-talk%40latchkey.com/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Re: Retrospect 4.3 (Mac) Assertion Check?
Internal consistency check failed: Assertion check at "elem16.c-438" [Quit] This is with version 4.3, and a relaunch of the program has begun the scripted backup that had been aborted at Midnight due to the above issue. Does this sound familiar to anyone here? Hi Mark, I got an assertion check on a restore a couple weeks ago. Basically, the technotes told me to call tech support. :-) For me, I quit Retrospect, restarted, and tried the restore again. Worked just fine. However, my assertion check was a different "elem" number than yours. Dantz Tech Support has documentation on what these mean and what the cures are. I'd say a call to them is in good order. Pam -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Search: http://www.mail-archive.com/retro-talk%40latchkey.com/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Re: Retrospect 4.3 (Mac) Assertion Check?
Hi Mark, Retrospect does internal consistency checks to ensure internal operations are fine. Typically this is an indication that an internal file in use by Retrospect has been corrupted. This particular assert we are currently tracking and believe it to be ASIP Memory Management-related. Most users who have seen this error report that after restarting the assert does not reproduce. In the instances where it was reproducible, we've found that disabling third-party server administration tools have been effective in addressing it. You're right, the error code is not on the "Common Error Codes" section, but it is in the Knowledgebase. If you have questions, of course, please give us a call. Regards, Irena Solomon Dantz Technical Support 925.253.3050 Try our Searchable Knowledgebase at: http://partners.dantz.com:591/faq/ Subject: Retrospect 4.3 (Mac) Assertion Check? Retrospect Experts: I am copying Dantz on this, but a search of the Retrospect error list on their Web site does not mention this one: Trouble in Retrospect: Internal consistency check failed: Assertion check at "elem16.c-438" [Quit] This is with version 4.3, and a relaunch of the program has begun the scripted backup that had been aborted at Midnight due to the above issue. Does this sound familiar to anyone here? Regards, Mark E. Ingram [EMAIL PROTECTED] (also [EMAIL PROTECTED]) -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Search: http://www.mail-archive.com/retro-talk%40latchkey.com/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
Re: Retrospect 4.3 (Mac) Assertion Check?
On Wed, 7 Feb 2001, Pam Lefkowitz wrote: I got an assertion check on a restore a couple weeks ago. Basically, the technotes told me to call tech support. :-) Thanks, Pam. I did hear back privately from Dantz, and they are keeping an eye on the situation to see if it reoccurs. For me, I quit Retrospect, restarted, and tried the restore again. Worked just fine. Same here - but for a scripted backup. However, my assertion check was a different "elem" number than yours. Actually, after the initial message was dismissed, a series of maybe three or four more of these boxes - each with a different "elem" number - did appear in sequence. Thanks again, MI -- -- To subscribe:[EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives:http://list.working-dogs.com/lists/retro-talk/ Search: http://www.mail-archive.com/retro-talk%40latchkey.com/ For urgent issues, please contact Dantz technical support directly at [EMAIL PROTECTED] or 925.253.3050.
