Error: 33120, Severity: 16, In order to encrypt the database encryption key with an %S_MSG, please use an %S_MSG that resides on an extensible key management provider.
Error: 33121, Severity: 16, The %S_MSG ‘%ls’ does not have a login associated with it. Create a login and credential for this key to automatically access the extensible key management provider ‘%ls’.
Error: 33122, Severity: 16, This command requires a database encryption scan on database ‘%.*ls’. However, the database has changes from previous encryption scans that are pending log backup. Take a log backup and retry the command.
Error: 33123, Severity: 16, Cannot drop or alter the database encryption key since it is currently in use on a mirror or secondary availability replica. Retry the command after all the previous reencryption scans have propagated to the mirror or secondary availability replicas or af
Error: 33124, Severity: 10, Database encryption scan for database ‘%.*ls’ cannot complete since one or more files are offline. Bring the files online to run the scan to completion.
Error: 33125, Severity: 10, Can not create login token because there are too many secondary principals. The maximum number of allowed secondary principals allowed is %lu. To fix this, remove the login from a server role.
Error: 33126, Severity: 10, Database encryption key is corrupted and cannot be read.
Error: 33127, Severity: 16, The %S_MSG cannot be dropped because it is used by one or more databases to encrypt a Database Encryption Key.
Error: 33128, Severity: 16, Encryption failed. Key uses deprecated algorithm ‘%.*ls’ which is no longer supported.
Error: 33129, Severity: 16, Cannot use ALTER LOGIN with the ENABLE or DISABLE argument for a Windows group. GRANT or REVOKE the CONNECT SQL permission instead.
Error: 33201, Severity: 17, An error occurred in reading from the audit file or file-pattern: ‘%s’. The SQL service account may not have Read permission on the files, or the pattern may be returning one or more corrupt files.
Error: 33202, Severity: 17, SQL Server Audit could not write to file ‘%s’.
Error: 33203, Severity: 17, SQL Server Audit could not write to the event log.
Error: 33204, Severity: 17, SQL Server Audit could not write to the security log.
Error: 33205, Severity: 10, Audit event: %s.
Error: 33206, Severity: 17, SQL Server Audit failed to create the audit file ‘%s’. Make sure that the disk is not full and that the SQL service account has the required permissions to create and write to the file.
Error: 33207, Severity: 17, SQL Server Audit failed to access the event log. Make sure that the SQL service account has the required permissions to the access the event log.
Error: 33208, Severity: 17, SQL Server Audit failed to access the security log. Make sure that the SQL service account has the required permissions to access the security log.
Error: 33209, Severity: 10, Audit ‘%.*ls’ has been changed to ON_FAILURE=CONTINUE because the server was started by using the -m flag. because the server was started with the -m flag.
Error: 33210, Severity: 10, SQL Server Audit failed to start, and the server is being shut down. To troubleshoot this issue, use the -m flag (Single User Mode) to bypass Audit-generated shutdowns when the server is starting.
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.
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.