One of our users received an assertion error message, on Windows 2008 server running SA 5.5.05 build # 2817. There is no transaction log defined and the event viewer displayed the error message below:
*** ERROR *** Assertion failed: 52101 Error during checkpoint when operating without transaction log
In order to restart the service they replaced the database with the last night's backup
Any suggestions on how to check the source of the issues?
UPDATE: dbvalid didn't indicate any issues.
It does need to be remember that versions 5.5 and 6.0 went "End of Support" 12 years ago. And in this case version 5.5 was never tested with any of the currently shipping operating systems so there may be an issue there.
For assertions you should first refer to the technical whitepaper:
"I've got an assertion! What should I do?"
In your customer's case if the continue to have or are repeateding having the assertion even after restoring the backup then the problem may also exist in the backup. As such you may need to rebuild the backup or resort to a database salvage.
Adding a transaction log should change the nature of the assertion and may prove to be more diagnostic but if this is due to corruption in the file then you may have no choice but to salvage the file some other way.
Do contact technical support if you make no progress with the information provided in the link (above).
answered 26 Sep '12, 16:56
Nick Elson S...