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.


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

     Cumulative Update 2 for SQL Server 2016 SP1    

     Cumulative Update 4 for SQL Server 2016

     Cumulative update 3 for SQL Server 2014 SP2 

     Cumulative Update 10 for SQL Server 2014 SP1

     Cumulative Update 6 for SQL Server 2012 Service Pack 3 

About cumulative updates for SQL Server

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

    Latest cumulative update for SQL Server 2016

    Latest cumulative update for SQL Server 2014 SP1/SP2

    Latest cumulative update for SQL Server 2012 


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


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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!