Filter
Top Products
Server Error Messages 5600 - 5699
972
Server Error Messages 5600 - 5699
5211 26 Failure concurrent with dump in database %d: caller does not possess flushlist lock.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5212 26 Failure concurrent with dump in database %d: no DFL pieces on not-full list.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5213 26 Failure concurrent with dump in database %d: caller improperly holds flushlist lock.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5214 20 During DUMP DATABASE for database %d, flushlist closure not complete at end of
synchronisation.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
dbcc diagnostics can be run.
5215 26 DUMP DATABASE for database %d failed: could not find dflinfohead to deallocate.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5216 26 DUMP DATABASE for database %d failed: trailing piece in not-full list proved not-
empty.
Explanation: An internal locking/synchronization rule was broken. Report the error to
your System Administrator. Shut down and restart Adaptive Server.
5217 20 DFL Manager failed to sleep.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Report the error to your System Administrator.
Number Severity Text and Explanation
Number Severity Text and Explanation
5600 20 Adaptive Server internal error: Did not expect to find distributed transaction participant
descriptor for local participant.
Explanation: Adaptive Server encountered an internal error affecting the current
process. Reconnect to Adaptive Server. Report the error to your System Administrator so
DBCC diagnostics can be run.