FIX: TDE encrypted Databases go in suspect state during the recovery phase when you restart SQL Server

Symptoms

Assume that you have a Transparent Data Encryption (TDE) encrypted database on an instance of Microsoft SQL Server. When you restart the instance of SQL Server, you may receive a lock time-out error that resembles the following:
Starting up database <DatabaseName>.
Error: 1222, Severity: 16, State: 55.
Lock request time out period exceeded.
Error: 9016, Severity: 21, State: 7.
An error occurred while processing the log for database <DatabaseName>. The log block could not be decrypted.
Then, the database will go in a suspect state.You can get the database back online by using Emergency Mode. You won't encounter corruption.

Resolution

This problem was fixed in the following cumulative update for SQL Server:


    Cumulative Update 4 for SQL Server 2016

About cumulative updates for SQL Server
About cumulative updates for SQL Server

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

Learn about the terminology  that Microsoft uses to describe software updates.
Properties

Article ID: 3197631 - Last Review: Jan 17, 2017 - Revision: 3

Feedback