|
|
|
When using transaction logs that were encrypted with advanced encryption, a transaction log reader (such as the internal server thread that processes Full-Text Index, deferred key, and record update callback log entries) might fail to read the transaction logs. In this situation, a message such as the following was logged to CTSTATUS.FCS and the internal thread entered a paused state:
DeferredIndexer: Failed to read next change from transaction log: 76
The error code may vary; for example, error 75 was also observed in this situation. The logic has been modified to prevent this error from occurring.
