SQL Server Errors or Failures from Error: 33099 to Error: 33119

SQLServerF1

Error: 33099, Severity: 16, You cannot add server-scoped catalog views, system stored procedures, or extended stored procedures to a database audit specification in a user database. Instead add them to a database audit specification in the master database.

Error: 33101, Severity: 16, Cannot use %S_MSG ‘%.*ls’, because its private key is not present or it is not protected by the database master key. SQL Server requires the ability to automatically access the private key of the %S_MSG used for this operation.
Error: 33102, Severity: 16, Cannot encrypt a system database. Database encryption operations cannot be performed for ‘master’, ‘model’, ‘tempdb’, ‘msdb’, or ‘resource’ databases.
Error: 33103, Severity: 16, A database encryption key already exists for this database.
Error: 33104, Severity: 16, A database encryption key does not exist for this database.
Error: 33105, Severity: 16, Cannot drop the database encryption key because it is currently in use. Database encryption needs to be turned off to be able to drop the database encryption key.

Error: 33106, Severity: 16, Cannot change database encryption state because no database encryption key is set.
Error: 33107, Severity: 16, Cannot enable database encryption because it is already enabled.
Error: 33108, Severity: 16, Cannot disable database encryption because it is already disabled.
Error: 33109, Severity: 16, Cannot disable database encryption while an encryption, decryption, or key change scan is in progress.
Error: 33110, Severity: 16, Cannot change database encryption key while an encryption, decryption, or key change scan is in progress.
Error: 33111, Severity: 16, Cannot find server %S_MSG with thumbprint ‘%.*ls’.
Error: 33112, Severity: 10, Beginning database encryption scan for database ‘%.*ls’.
Error: 33113, Severity: 10, Database encryption scan for database ‘%.*ls’ is complete.
Error: 33114, Severity: 10, Database encryption scan for database ‘%.*ls’ was aborted. Reissue ALTER DB to resume the scan.
Error: 33115, Severity: 16, CREATE/ALTER/DROPP DATABASE ENCRYPTION KEY failed because a lock could not be placed on the database. Try again later.
Error: 33116, Severity: 16, CREATE/ALTER/DROPP DATABASE ENCRYPTION KEY failed because a lock could not be placed on database ‘%.*ls’. Try again later.

Error: 33117, Severity: 16, Transparent Data Encryption is not available in the edition of this SQL Server instance. See books online for more details on feature support in different SQL Server editions.
Error: 33118, Severity: 16, Cannot enable or modify database encryption on a database that is read-only, has read-only files or is not recovered.
Error: 33119, Severity: 16, Cannot modify filegroup read-only/read-write state while an encryption transition is in progress.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *