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

Assume that you have a Transparent Data Encryption (TDE) encrypted database on an instance of Microsoft SQL Server 2012. 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 update for SQL Server:

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:

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.

Article ID: 3197631 - Last Review: 12/28/2016 18:03:00 - Revision: 3.0

Microsoft SQL Server 2012 Service Pack 3, Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Enterprise Core, Microsoft SQL Server 2014 Express, Microsoft SQL Server 2014 Standard

  • kbqfe kbfix kbexpertiseadvanced kbsurveynew KB3197631