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
>
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, si
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 q
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 u
>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
