Jump to content
bljohns

What causes "Assertion check at "elem16.c-687"???

Recommended Posts

I'm happy to provide the before/after copies of the Retrospect Preferences directory and all my system configuration details to someone at Dantz.

 

 

That's gonna be a challenge, as Dantz Development Inc. no longer exists!

 

Dantz is now EMC Insignia.

Edited by Guest

Share this post


Link to post
Share on other sites

The dreaded assertion check at "elem16.c-687" error is back again, after a 20 month absence. Maybe a clue or just a coincidence: an XP SP2 windozer on my network was updated to .Net 3.0, patched, and got a new, active share on the network yesterday. Maybe it's just a coincidence, but the assertion check failure occurred this morning, while trying to back the another XP on the same network. Maybe the updated computer thinks it needs to horn in on the discussion between the mac server and the other XP client. Those backups had been running every other night - no problem.

 

Share this post


Link to post
Share on other sites

Problem is back. Backups fail when Retrospect tries to talk to the XP client. Even going to the "Configure" tab causes the error message to happen.

 

I forget the XP client and added it back, I'm able to back things up without errors.

 

Maybe since there's a workaround, this is low priority for being fixed?

Share this post


Link to post
Share on other sites

FYI: I get this same error from time to time on the same Windows user backing up to a MacMini Intel. I delete the user and add her back to the set and she'll run for a while before this crops up again.

 

So same work around as the post above me.

Share this post


Link to post
Share on other sites

I have the exact same problem. Started just a few days ago with a previously normally functioning Windows XP Backup Client.

 

Another completely bizarre "occurrence" I've never seen before during backing up. Sure keeps life interesting, this program. ;)

 

Going to Configure > Clients and opening the client and doing Configure causes it to happen 100% of the time.

 

Thanks to this thread, I have the workaround (forgetting the client, adding it back in). Seems to be working again.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×