Jump to content
Sign in to follow this  
chriskampen

assertion failure

Recommended Posts

Hi

 

This error can by a couple of things

 

corruption in the databases

http://support.microsoft.com/?id=318429

 

Or by having public stores that are unmounted.

 

Do any of these apply to your situation? If not try creating a clean set of Retrospect preference files. You can do this by renaming your old files c:\documents and settings\all users\application data\retrospect\config65.dat and config65.bak

 

Thanks

Nate

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
Sign in to follow this  

×