banterer Posted April 13, 2004 Report Share Posted April 13, 2004 Hello, I keep on getting the same error message on one particular W2k machine. I have Retrosopect 5.1.175. The message is this: Internal consistency check failed: Assertion check at "elem16.c-687" I have searched their online database and found nothing. Are these forums the only form of free tech support available for the "purchased" product? I assume that these forums are not here for support of downloaded demos. Jorge Link to comment Share on other sites More sharing options...
natew Posted April 15, 2004 Report Share Posted April 15, 2004 Hi The forums are freely available to anyone. Have you tried forgetting and re-adding this client machine? At what point in the backup does the error occur? Can you backup subvolumes from the client at all? Nate Link to comment Share on other sites More sharing options...
optotronic Posted May 11, 2004 Report Share Posted May 11, 2004 I also encountered this error message when accessing a particular Windows 2000 client while using Retrospect Workgroup 6.0.193. Forgetting and re-adding the client fixed the problem. Bill Link to comment Share on other sites More sharing options...
banterer Posted May 23, 2004 Author Report Share Posted May 23, 2004 Thanks Bill, I tried that and it is now at least scanning the files so I think that did it since it refused to even start looking at anything before declaring its intent to quit!! Thanks again, Jorge Link to comment Share on other sites More sharing options...
optotronic Posted June 1, 2004 Report Share Posted June 1, 2004 This problem recurred several times on various clients. Forgetting and re-adding the client fixed it each time, until the next time the problem arose. I believe the Retrospect (server) preferences were being corrupted by the bug that causes two copies of Retrospect to launch in some cases. To clarify, there is a bug that causes two copies of Retrospect to launch sometimes. I think the corruption occurs when two copies of Retrospect are running. Presumably the code to write the preferences is not designed for multiple access. I worked around this bug by disabling the option to auto launch Retrospect when a script needs to be run. Instead I leave Retrospect running at all times. This is not ideal, but not having the backups is worse. Bill Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.