Web.QHMIT.com

SQL Server System Errors: 33000 - 33999

List of error messages between 33000 and 33999 in SQL Server 2017.

These error messages are all available by querying the sys.messages catalog view on the master database.

message_id severity is_event_logged text
33001160Cannot drop the option because the option is not specified on %S_MSG.
33002160Access to %ls %ls is blocked because the signature is not valid.
33003160DDL statement is not allowed.
33004160The password of login '%.*ls' is invalid. A new password should be set for this login without specifying the old password.
33005160Cannot find the certificate or asymmetric key from the file %.*ls. ErrorCode: 0x%x.
33006160WITH SIGNATURE option cannot be specified on database.
33007160Cannot encrypt symmetric key with itself.
33008160Cannot grant, deny, or revoke %.*ls permission on INFORMATION_SCHEMA or SYS %S_MSG.
33009160The database owner SID recorded in the master database differs from the database owner SID recorded in database '%.*ls'. You should correct this situation by resetting the owner of database '%.*ls' using the ALTER AUTHORIZATION statement.
33010160The MUST_CHANGE option cannot be specified together with the HASHED option.
33011160The %S_MSG private key cannot be dropped because one or more entities are encrypted by it.
33012100Cannot %S_MSG signature %S_MSG %S_MSG '%.*ls'. Signature already exists or cannot be added.
33013160A %S_MSG by %S_MSG '%.*s' does not exist.
33014160Cannot countersign '%.*s'. Only modules can be countersigned.
33015160The database principal is referenced by a %S_MSG in the database, and cannot be dropped.
33016160The user cannot be remapped to a login. Remapping can only be done for users that were mapped to Windows or SQL logins.
33017160Cannot remap a user of one type to a login of a different type. For example, a SQL user must be mapped to a SQL login; it cannot be remapped to a Windows login.
33018160Cannot remap user to login '%.*s', because the login is already mapped to a user in the database.
33019160Cannot create implicit user for the special login '%.*s'.
33020160A HASHED password cannot be set for a login that has CHECK_POLICY turned on.
33021161Failed to generate a user instance of SQL Server. Only local user accounts, interactive users accounts, service accounts, or batch accounts can generate a user instance. The connection will be closed.%.*ls
33022160Cannot obtain cryptographic provider properties. Provider error code: %d.
33023160The %S_MSG is too long. Maximum allowed length is %d bytes.
33024160Cryptographic provider %S_MSG '%ls' in dll is different from the guid recorded in system catalog for provider with id %d.
33025160Invalid cryptograpihic provider property: %S_MSG.
33026160Cryptographic provider with guid '%ls' already exists.
33027160Cannot load library '%.*ls'. See errorlog for more information.
33028160Cannot open session for %S_MSG '%.*ls'. Provider error code: %d. (%S_MSG)
33029160Cannot initialize cryptographic provider. Provider error code: %d. (%S_MSG)
33030160Cryptographic provider is not available.
33031160Cryptographic provider '%.*ls' is in disabled.
33032161SQL Crypto API version '%02d.%02d' implemented by provider is not supported. Supported version is '%02d.%02d'.
33033160Specified key type or option '%S_MSG' is not supported by the provider.
33034160Cannot specify algorithm for existing key.
33035160Cannot create key '%.*ls' in the provider. Provider error code: %d. (%S_MSG)
33036100Cannot drop the key with thumbprint '%.*ls' in the provider.
33037160Cannot export %S_MSG from the provider. Provider error code: %d. (%S_MSG)
33038160Operation is not supported by cryptographic provider key.
33039160Invalid algorithm '%.*ls'. Provider error code: %d. (%S_MSG)
33040160Cryptographic provider key cannot be encrypted by password or other key.
33041161Cannot create login token for existing authenticators. If dbo is a windows user make sure that its windows account information is accessible to SQL Server.
33042160Cannot add %S_MSG because it is already mapped to a login.
33043160Cannot add %S_MSG '%.*ls' because there is already %S_MSG specified for the login.
33044160Cannot drop %S_MSG because there is %S_MSG referencing this provider.
33045160Cannot drop %S_MSG because it is not mapped to this login.
33046160Server principal '%.*ls' has no credential associated with %S_MSG '%.*ls'.
33047160Fail to obtain or decrypt secret for %S_MSG '%.*ls'.
33048160Cannot use %S_MSG under non-primary security context.
33049160Key with %S_MSG '%.*ls' does not exist in the provider or access is denied. Provider error code: %d. (%S_MSG)
33050160Cannot create key '%.*ls' in the provider. Provider does not allow specifying key names.
33051160Invalid algorithm id: %d. Provider error code: %d. (%S_MSG)
33052160Cryptographic provider key cannot be a temporary key.
33053160Extensible Key Management is disabled or not supported on this edition of SQL Server. Use sp_configure 'EKM provider enabled' to enable it.
33054160Extensible key management is not supported in this edition of SQL Server.
33055160Exception happened when calling cryptographic provider '%.*ls' in the API '%.*ls'. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx.
33056160Cannnot impersonate login '%.*ls' to access %S_MSG '%.*ls'.
33057100Cryptographic provider is now disabled. However users who have an open cryptographic session with the provider can still use it. Restart the server to disable the provider for all users.
33058100Cryptographic provider is now dropped. However users who have an open cryptographic session with the provider can still use it. Restart the server to drop the provider for all users.
33059160An error occurred while trying to flush all running audit sessions. Some events may be lost.
33060160The format of supplied parameter sid is invalid. The sid might be incorrect or the sid might describe the wrong type of user.
33061160The specified RETENTION_DAYS value is greater than the maximum value allowed. The retenton days value must be less than %d days.
33062160Password validation failed. The password does not meet SQL Server password policy requirements because it is too short. The password must be at least %d characters.
33063160Password validation failed. The password does not meet SQL Server password policy requirements because it is too long. The password must be at most %d characters.
33064160Password validation failed. The password does not meet SQL Server password policy requirements because it is not complex enough. The password must be at least %d characters long and contain characters from three of the following four sets: Uppercase letters, Lowercase letters, Base 10 digits, and Symbols.
33066100An error occurred while configuring the password policy: NTSTATUS 0x%x, state %d. To skip configuring the password policy, use trace flag -T4634 during startup. This will cause SQL Server to run using a minimal password policy.
33069160CREATE CERTIFICATE statement cannot mix file and binary modes. Rewrite the statement using only the FILE or the BINARY keyword.
33070160The specified maximum size limit for the audit log file is less than the minimum value allowed. The maximum size limit must be at least 2 MB.
33071160This command requires %S_MSG to be disabled. Disable the %S_MSG and rerun this command.
33072160The audit log file path is invalid.
33073160Cannot find %S_MSG '%.*ls' or you do not have the required permissions.
33074160Cannot %S_MSG a %S_MSG %S_MSG from a user database. This operation must be performed in the master database.
33075160Granular auditing is not available in this edition of SQL Server. For more information about feature support in the editions of SQL Server, see SQL Server Books Online.
33076160The specified maximum size limit is greater than the maximum value allowed. The maximum size limit must be less than 16777215 TB.
33077160RESERVE_DISK_SPACE cannot be specified when setting MAXSIZE = UNLIMITED. Either reduce MAXSIZE or do not specify RESERVE_DISK_SPACE.
33078160The containment setting in the master database does not match the property of the database files. Use ALTER DATABASE to reset the containment property.
33079160Cannot bind a default or rule to the CLR type '%s' because an existing sparse column uses this data type. Modify the data type of the sparse column or remove the sparse designation of the column.
33080100Cryptographic provider library '%.*ls' loaded into memory. This is an informational message only. No user action is required.
33081100Failed to verify Authenticode signature on DLL '%.*ls'.
33082160Cannot find Cryptographic provider library with guid '%ls'.
33083160Cannot create %S_MSG for %S_MSG '%ls' because it is not supported by the extensible key management provider '%ls'.
33084160The OPEN SYMMETRIC KEY statement cannot reference a symmetric key created from an Extensible Key Management (EKM) provider. Symmetric keys created from an EKM provider are opened automatically for principals who can successfully authenticate with the cryptographic provider.
33085100One or more methods cannot be found in cryptographic provider library '%.*ls'.
33086100SQL Server Audit failed to record %ls action.
33087160%S_MSG property of the key returned by EKM provider doesn't match the expected value
33088160The algorithm: %.*ls is not supported for EKM operations by SQL Server
33089160Key validation failed since an attempt to get algorithm info for that key failed. Provider error code: %d. (%S_MSG)
33090100Attempting to load library '%.*ls' into memory. This is an informational message only. No user action is required.
33091100Warning: The certificate used for encrypting the database encryption key has not been backed up. You should immediately back up the certificate and the private key associated with the certificate. If the certificate ever becomes unavailable or if you must restore or attach the database on another server, you must have backups of both the certificate and the private key or you will not be able to open the database.
33092100Failed to verify the Authenticode signature of '%.*ls'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
33093160The Windows user or group '%s' is local or built-in. Use a Windows domain user or domain group.
33094100An error occurred during Service Master Key %S_MSG
33095100Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
33096100A generic failure occurred during Service Master Key encryption or decryption.
33097100Processing BrickId: %d with MasterDb.PrimaryPru.FragId %d
33098100Initializing SMK for brickId: %d
33099160You 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.
33101160Cannot 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.
33102160Cannot encrypt a system database. Database encryption operations cannot be performed for 'master', 'model', 'tempdb', 'msdb', or 'resource' databases.
33103160A database encryption key already exists for this database.
33104160A database encryption key does not exist for this database.
33105160Cannot 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.
33106160Cannot change database encryption state because no database encryption key is set.
33107160Cannot enable database encryption because it is already enabled.
33108160Cannot disable database encryption because it is already disabled.
33109160Cannot %S_MSG database encryption while an encryption, decryption, or key change scan is in progress.
33110160Cannot change database encryption key while an encryption, decryption, or key change scan is in progress.
33111160Cannot find server %S_MSG with thumbprint '%.*ls'.
33112100Beginning database encryption scan for database '%.*ls'.
33113100Database encryption scan for database '%.*ls' is complete.
33114100Database encryption scan for database '%.*ls' was aborted. Reissue ALTER DB to resume the scan.
33115160CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on the database. Try again later.
33116160CREATE/ALTER/DROP DATABASE ENCRYPTION KEY failed because a lock could not be placed on database '%.*ls'. Try again later.
33117160Transparent 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.
33118160Cannot enable or modify database encryption on a database that is read-only, has read-only files or is not recovered.
33119160Cannot modify filegroup read-only/read-write state while an encryption transition is in progress.
33120160In order to encrypt the database encryption key with an %S_MSG, please use an %S_MSG that resides on an extensible key management provider.
33121160The %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'.
33122160This 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.
33123160Cannot 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 after availability relationship has been disabled.
33124100Database encryption scan for database '%.*ls' cannot complete since one or more files are offline. Bring the files online to run the scan to completion.
33125100Can 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.
33126100Database encryption key is corrupted and cannot be read.
33127160The %S_MSG cannot be dropped because it is used by one or more databases to encrypt a Database Encryption Key.
33128160Encryption failed. Key uses deprecated algorithm '%.*ls' which is no longer supported at this db compatibility level. If you still need to use this key switch to a lower db compatibility level.
33129160Cannot use ALTER LOGIN with the ENABLE or DISABLE argument for a Windows group. GRANT or REVOKE the CONNECT SQL permission instead.
33130160Principal '%ls' could not be found or this principal type is not supported.
33131160Principal '%ls' was not unique.
33132160This principal type is not supported in Windows Azure SQL Database.
33133160Your subscription is not enabled for Integrated Authentication.
33134160Principal '%ls' could not be found at this time. Please try again later.
33135160Altering the name of a Windows principal is not supported through this form of execution. For more information about this, see SQL Server Books Online.
33136160The operation could not be completed at this time. Please try again later.
33137160The tenant '%.*ls' cannot be found.
33138160ALTER DATABASE on a federation member is not supported for Windows users or groups.
33139160This subscription does not support Integrated Authentication.
33140160The login '%.*ls' could not be created because a login is already associated with certificate '%.*ls'.
33141100The credential created might not be able to decrypt the database master key. Please ensure a database master key exists for this database and is encrypted by the same password used in the stored procedure.
33142160Updating the tenantId for Azure SQL Server was not successful.
33143160The account admin of the subscription does not belong to this tenant.
33144160Cannot change the schema of a temporary object.
33146100The database '%.*ls' is offline. The credential was created but SQL Server is unable to determine if the credential can decrypt the database master key.
33147201Federated Authentication Feature data used in login record to open a connection is structurally or semantically invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls.
33148160The user name for a windows login has to be identical to the login name.
33149161Dropping a credential '%.*ls' which could still be used by Managed Backup.
33150161Warning: Can not check whether the credential '%.*ls' is used by managed backup, because %ls. Please check whether the credential is used by managed backup.
33151160The user name for a user with password cannot be identical to the name of the server admin or the dbo of the database.
33152160Valid values of the database compatibility level are %d or %d.
33153160Valid values of the database compatibility level are %d, %d, or %d.
33154201Client sent an invalid token when server was expecting federated authentication token. And it was not a disconnect event.
33155201A disconnect event was raised when server is waiting for Federated Authentication token. This could be due to client close or server timeout expired.
33156201A Federated Authentication token was sent by the client when the server is not expecting it. So server will close the connection due to TDS non-conformance.
33157160Crypthographic providers are not supported on database credentials.
33158160Database credentials are not supported in master database.
33159160Principal '%ls' could not be created. Only connections established with Active Directory accounts can create other Active Directory users.
33160100Unable to verify Authenticode signatures due to error code %d. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
33161150Database master keys without password are not supported in this version of SQL Server.
33162160TYPE and SID options have to be used along with each other, in this version of SQL Server.
33163160The value specified for TYPE option is not supported in this version of SQL Server. Allowed values are E (EXTERNAL_USER) and X (EXTERNAL_GROUP)
33164160Cannot drop the credential '%.*ls' because it is used by an external data source.
33165160Cannot drop the external %ls '%.*ls' because it is used by an external table.
33166160dbManager permission check failed.
33167160This command is not supported for Azure AD users. Execute this command as a SQL Authenticated user.
33168160TYPE option cannot be used along with FOR/FROM LOGIN, CERTIFICATE, ASYMMETRIC KEY, EXTERNAL PROVIDER, WITHOUT LOGIN or WITH PASSWORD, in this version of SQL Server.
33169160User name cannot have backslash character, when using the TYPE option.
33170160SID option cannot be used along with FOR/FROM LOGIN, CERTIFICATE, ASYMMETRIC KEY, EXTERNAL PROVIDER, WITHOUT LOGIN or WITH PASSWORD, in this version of SQL Server.
33171160Only active directory users can impersonate other active directory users.
33172160Encrypting Secret for Database '%.*ls' and Credential '%.*ls' failed.
33173160Assigning value for output parameter @credentialSecret failed because the parameter size is less than the required size %u. Please provide a larger size.
33174160Cannot get credential '%.*ls' because it is not referenced by any external data source.
33175160Encryption operation failed. Key used for encryption has deprecated algorithm '%.*ls' which is no longer supported at this db compatibility level. If you still need to use this key switch to a lower db compatibility level.
33176160Signing operation failed. Key uses deprecated algorithm '%.*ls' which is no longer supported at this db compatibility level. If you still need to use this key switch to a lower db compatibility level.
33177160Hash operation failed. Hash Function uses deprecated algorithm '%.*ls' which is no longer supported at this db compatibility level. If you still need to use this hash algorithm switch to a lower db compatibility level.
33178160Encryption key length is over the currently supported maximum length of %d.
33179100Searching for '%.*ls' only searches "'%.*ls'" for SQL Server authentication logins.
33180100Searching for "'%.*ls'" only searches for Azure Active Directory users. To search for a SQL Server authentication login, add the server name at the end. For example [%.*ls@%.*ls].
33181160The new owner cannot be Azure Active Directory group.
33182160The command must be executed on the target database '%.*ls'.
33183160The Azure Key Vault client encountered an error with message '%s'.
33184160An error occurred while obtaining information for the Azure Key Vault client with message '%s'.
33201170An 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.
33202170SQL Server Audit could not write to file '%s'.
33203170SQL Server Audit could not write to the event log.
33204170SQL Server Audit could not write to the security log.
33205100Audit event: %s.
33206170SQL Server Audit failed to create the audit file '%s'. Make sure that the disk is not full and that the SQL Server service account has the required permissions to create and write to the file.
33207170SQL 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.
33208170SQL Server Audit failed to access the security log. Make sure that the SQL service account has the required permissions to access the security log.
33209100Audit '%.*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.
33210100SQL 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.
33211150A list of subentities, such as columns, cannot be specified for entity-level audits.
33212150There is an invalid column list after the object name in the AUDIT SPECIFICATION statement.
33213160All actions in an audit specification statement must be at the same scope.
33214170The operation cannot be performed because SQL Server Audit has not been started.
33215100One or more audits failed to start. Refer to previous errors in the error log to identify the cause, and correct the problems associated with each error.
33216100SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
33217100SQL Server Audit is starting the audits. This is an informational message. No user action is required.
33218100SQL Server Audit has started the audits. This is an informational message. No user action is required.
33219100The server was stopped because SQL Server Audit '%.*ls' is configured to shut down on failure. To troubleshoot this issue, use the -m flag (Single User Mode) to bypass Audit-generated shutdowns when the server is starting.
33220160Audit actions at the server scope can only be granted when the current database is master.
33221160You can only create audit actions on objects in the current database.
33222100Audit '%.*ls' failed to %S_MSG . For more information, see the SQL Server error log. You can also query sys.dm_os_ring_buffers where ring_buffer_type = 'RING_BUFFER_XE_LOG'.
33223160ALTER SERVER AUDIT requires the STATE option to be specified without using any other options.
33224160The specified pattern did not return any files or does not represent a valid file share. Verify the pattern parameter and rerun the command.
33225160The specified values for initial_file_name and audit_record_offset do not represent a valid location within the audit file set. Verify the file name and offset location, and then rerun the command.
33226100The fn_get_audit_file function is skipping records from '%.*ls' at offset %I64d.
33227160The specified value for QUEUE_DELAY is not valid. Specify either 0 or 1000 and higher.
33228160You cannot configure SQL Server Audit to shutdown the server because you do not have the permission to shut down the server. Contact your system administrator.
33229160Changes to an audit specification must be done while the audit specification is disabled.
33230160An audit specification for audit '%.*ls' already exists.
33231160You can only specify securable classes DATABASE, SCHEMA, or OBJECT in AUDIT SPECIFICATION statements.
33232160You may not add a role to Sysadmin.
33233160You can only create a user with a password in a contained database.
33234160The parameter %s cannot be provided for users that cannot authenticate in a database.
33235160The parameter %s cannot be provided for users that cannot authenticate in a database. Remove the WITHOUT LOGIN or PASSWORD clause.
33236160The default language parameter can only be provided for users in a contained database.
33237160Cannot use parameter %s for Windows users or groups.
33238160MAX_FILES and MAX_ROLLOVER_FILES options cannot be specified toghether.
33239160An error occurred while auditing this operation. Fix the error in the audit and then retry this operation.
33240160A failure occurred during initializing of an Audit. See the errorlog for details.
33241161Failed to configure user instance on startup. Error updating the idle timeout.
33242160When providing a sid, the user must be a user without login or a user with password.
33243161Failed to generate a user instance of SQL Server due to a failure in setting access control list on the user instance's process. The connection will be closed.%.*ls
33244170SQL Server Audit failed to create an audit file related to the audit '%s' in the directory '%s'. Make sure that the disk is not full and that the SQL Server service account has the required permissions to create and write to the file.
33245170SQL Server Audit failed to write to an audit file related to the audit '%s' in the directory '%s'. Make sure that the disk is not full and that the SQL Server service account has the required permissions to create and write to the file.
33246170SQL Server Audit failed to access the MDS file log. Make sure that the disk is not full and that the SQL Server service account has the required permissions to create and write to the file.
33247170SQL Server Audit could not write to the MDS local file (Error Code: %d).
33248160The specified value for QUEUE_DELAY is not valid for MDS log target. Specify value higher than 0.
33249160Cannot drop the credential '%.*ls' because it is being used.
33250160Failed to allocate memory for caching credential '%.*ls' which is used by a database file.
33251160A credential conflicting with '%.*ls' already exists in credential cache in memory. Use alter step to change the secret. Drop and re-create to change the credential name.
33252160This CREATE AUDIT request exceeds the maximum number of audits that can be created per database.
33253160Failed to modify the identity field of the credential '%.*ls' because the credential is used by an active database file.
33254160This operation cannot be performed in the master database.
33255160Audit specification '%.*ls' can only be bound to a %S_MSG audit.
33256160The audit store location or the audit store URL has been configured for this database audit.
33257160Cannot drop an audit store URL that is not configured for this database audit.
33258160Invalid value for procedure "%.*ls", parameter "%.*ls".
33259150Invalid security policy name '%.*ls'.
33260160The predicate was not added to the security policy '%.*ls' because there are no available predicate IDs. Drop and recreate the security policy.
33261160The security policy '%.*ls' does not contain a predicate on table '%.*ls'.
33262160A %S_MSG predicate for the same operation has already been defined on table '%.*ls' in the security policy '%.*ls'.
33263160Security predicates can only be added to user tables and schema bound views. '%.*ls' is not a user table or a schema bound view.
33264160The security policy '%.*ls' cannot be enabled with a predicate on table '%.*ls'. Table '%.*ls' is already referenced by the enabled security policy '%.*ls'.
33265160The security policy '%.*ls' cannot have a predicate on table '%.*ls' because this table is referenced by the indexed view '%.*ls'.
33266160The index on the view '%.*ls' cannot be created because the view is referencing table '%.*ls' that is referenced by a security policy.
33267160Security predicates cannot reference memory optimized tables. Table '%.*ls' is memory optimized.
33268160Cannot find the object "%.*ls" because it does not exist or you do not have permissions.
33269160Security predicates are not allowed on temporary objects. Object names that begin with '#' denote temporary objects.
33270160Cannot find the object "%.*ls" or this object is not an inline table-valued function.
33271160Cannot alter '%.*ls' because it is not a security policy.
33272160Unable to load the security predicate for table "%.*ls".
33273160Security predicates cannot be added on FileTables. '%.*ls' is a FileTable.
33274160The version was not created for the key '%.*ls' because there are no available version IDs. Drop and recreate the key.
33275160The encrypted value for this column encryption key cannot be dropped. Each column encryption key must have at least one encrypted value.
33277160Encryption scheme mismatch for columns/variables %.*ls. The encryption scheme for the columns/variables is %ls and the expression near line '%d' expects it to be %ls.
33278160Cannot assign the same encryption scheme to two expressions at line '%d'. The encryption scheme of the first expression is %ls and the encryption scheme of the second expression is %ls. Other columns/variables with the same encryption scheme as the first expression are: %.*ls. Other columns/variables with the same encryption scheme as the second expression are: %.*ls.
33279160Cannot remove the credential '%.*ls/%.*ls' because it is being used.
33280160Cannot create encrypted column '%.*ls' because type '%ls' is not supported for encryption.
33281160Column '%.*ls.%.*ls' has a different encryption scheme than referencing column '%.*ls.%.*ls' in foreign key '%.*ls'.
33282160Column '%.*ls.%.*ls' is encrypted using a randomized encryption type and is therefore not valid for use as a key column in a constraint, index, or statistics.
33283160'%S_MSG' clause is unsupported for encrypted columns.
33284160The encrypted column '%.*ls.%.*ls' cannot be used as a partition key column.
33285160Cannot set default constraint on encrypted column '%.*ls.%.*ls'. Default constraints are unsupported on encrypted columns.
33286160Cannot encrypt column '%.*ls', because it is of a user-defined type.
33287160Cannot drop column encryption key '%.*ls' because the key is referenced by column '%.*ls.%.*ls'.
33288160The encrypted value for the column encryption key cannot be added. There can be no more than two encrypted values for each column encryption key. Drop an exisiting encrypted value before adding the new one.
33289160Cannot create encrypted column '%.*ls', character strings that do not use a *_BIN2 collation cannot be encrypted.
33290160There is no column encryption key value associated with the column master key '%.*ls'.
33291160There is already a column encryption key value associated with the column master key '%.*ls'.
33292160The encryption algorithm '%.*ls' is not supported. Please specify a valid encryption algorithm.
33293160Cannot find the %S_MSG "%.*ls" because it does not exist or you do not have permissions.
33294160Some parameters or columns of the batch require to be encrypted, but the corresponding column encryption key cannot be found. Use sp_refresh_parameter_encryption to refresh the module parameters metadata.
33296160Cannot create table '%.*ls' since it references a column encryption key from a different database.
33297160Cannot create %S_MSG. The %S_MSG cannot be empty.
33298161Internal Query Processor Error: The encryption scheme of certain parameters was incorrectly analyzed. For more information, contact Customer Support Services.
33299160Encryption scheme mismatch for columns/variables %.*ls. The encryption scheme for the columns/variables is %ls and the expression near line '%d' expects it to be %ls (or weaker).
33301160The %ls that is specified for conversation priority '%.*ls' is not valid. The value must be between 1 and %d characters long.
33302160The %ls that is specified for conversation priority '%.*ls' is not valid. The value must be between 1 and 10.
33303160A conversation priority already exists in the database with either the name '%.*ls' or the properties %ls='%ls', %ls='%ls', and %ls='%.*ls'. Either use a unique name or a unique set of properties.
33304160The transmission queue row with conversation handle '%ls' and message sequence number %d references a missing multicast message body row with reference %d.
33305160The multicast message body row with reference %d should have reference count value of %d.
33306160The unreferenced message with reference %d has been deleted from the message body table.
33307160The message with reference %d has been updated to a reference count of %d in the message body table.
33308100The queue %d in database %d has activation enabled and contains unlocked messages but no RECEIVE has been executed for %u seconds.
33309100Cannot start cluster endpoint because the default %S_MSG endpoint configuration has not been loaded yet.
33310160Local cluster name can be set only once.
33311100The wait for connect request completion failed.
33312100The wait for querying proxy routes failed or was aborted.
33313160An out of memory condition has occurred in the Service Broker transport layer. A service broker connection is closed due to this condition.
33314160The supplied whitelist is invalid.
33315160The redirected endpointurl is Invalid
33316160Failed to reset encryption while performing redirection.
33317160The redirect response contains invalid redirect string
33318160The redirect request contains invalid string or redirect handler failed to handle the request
33319160The redirector returned lookup failure
33320160Tried to send redirect request but the redirect string is empty
33321160The other end does not support redirection
33322160The redirect message is corrupted
33323160The endpoint is closing because the connection was redirected
33324160Failed to parse the redirect info string
33325160Failed to construct new endpoint after redirection
33326160Forwarder disconnected during redirection
33327160Failed to parse the specified connection string
33328160Redirector lookup failed with error code: %x
33329160XdbHost encountered error code: %x during socket duplication
33330160XdbHost returned an error during socket duplication
33401160FILESTREAM database options cannot be set on system databases such as '%.*ls'.
33402160An invalid directory name '%.*ls' was specified. Use a valid operating system directory name.
33403160The case-sensitive or binary collation '%.*ls' cannot be used with the COLLATE_FILENAME option. Change the collation to a case-insensitive collation type.
33404160The database default collation '%.*ls' is case sensitive and cannot be used to create a FileTable. Specify a case insensitive collation with the COLLATE_FILENAME option.
33405160An error occurred during the %S_MSG %S_MSG operation on a FileTable object. (HRESULT = '0x%08x').
33406160An invalid filename, '%.*ls', caused a FileTable check constraint error. Use a valid operating system filename.
33407160An invalid path locator caused a FileTable check constraint error. The path locator cannot indicate a root row. Correct the path locator or use the default value.
33408160The operation caused a FileTable check constraint error. A directory entry cannot have a data stream associated with the row. Remove the blob data or clear the is_directory flag.
33409160The operation caused a FileTable check constraint error. A file entry cannot have a NULL value for the data stream associated with the row. Insert file data or use 0x to insert a zero length file.
33410160An invalid path locator caused a FileTable check constraint error. The parent of a row's path locator must be a directory, not a file. Correct the path locator to refer to a parent that is a directory.
33411160The option '%.*ls' is only valid when used on a FileTable. Remove the option from the statement.
33412160The option '%.*ls' is not valid when used with the '%.*ls' syntax. Remove the option from the statement.
33413160The option '%.*ls' can only be specified once in a statement. Remove the duplicate option from the statement.
33414160FileTable objects require the FILESTREAM database option DIRECTORY_NAME to be non-NULL. To create a FileTable in the database '%.*ls', set the DIRECTORY_NAME option to a non-NULL value using ALTER DATABASE. Or, to set the DIRECTORY_NAME option to NULL, in the database '%.*ls' disable or drop the existing FileTables.
33415160FILESTREAM DIRECTORY_NAME '%.*s' attempting to be set on database '%.*s' is not unique in this SQL Server instance. Provide a unique value for the database option FILESTREAM DIRECTORY_NAME to enable non-transacted access.
33416100When the FILESTREAM database option NON_TRANSACTED_ACCESS is set to FULL and the READ_COMMITTED_SNAPSHOT or the ALLOW_SNAPSHOT_ISOLATION options are on, T-SQL and transactional read access to FILESTREAM data in the context of a FILETABLE is blocked.
33417160An invalid path locator caused a FileTable check constraint error. The path locator has a level of %d, which is deeper than the limit of %d supported by FileTable. Reduce the depth of the directory hierarchy.
33418160FILETABLE_DIRECTORY '%.*s' attempting to be set on table '%.*s' is not unique in the database '%.*s'. Provide a unique value for the option FILETABLE_DIRECTORY to this operation.
33419160Function %ls is only valid on the varbinary(max) FILESTREAM column in a FileTable.
33420160Unable to process object '%.*s' because it is a three-part or four-part name. Specifying the server or database is not supported in the object identifer.
33421160The object name '%.*s' is not a valid FileTable object.
33422160The column '%.*s' cannot be added to table '%.*s' as it is a FileTable. Adding columns to the fixed schema of a FileTable object is not permitted.
33423160Invalid FileTable path name or format.
33424160Invalid computer host name in the FileTable path.
33425160Invalid share name in the FileTable path.
33426160INSERT, UPDATE, DELETE, or MERGE to FileTable '%.*ls' is not allowed inside a trigger on a FileTable.
33427160Function %ls is not allowed on the deleted table inside a trigger.
33428140User does not have permission to kill non-transacted FILESTREAM handles in database ID %d.
33429160The non-transacted FILESTREAM handle %d does not exist.
33430100Killed %d non-transactional FILESTREAM handles from database ID %d.
33431160An invalid path locator caused a FileTable check constraint error. The path locator has a length of %d, which is longer than the limit of %d allowed for depth %d. Reduce the length of the path locator.
33433100Unable to perform the Filetable lost update recovery for database id %d.
33434160The current state of the database '%.*s' is not compatible with the specified FILESTREAM non-transacted access level. The database may be read only, single user or set to emergency state.
33435160Cannot publish the FileTable '%ls' for replication. Replication is not supported for FileTable objects.
33436160Cannot enable Change Data Capture on the FileTable '%ls'. Change Data Capture is not supported for FileTable objects.
33437160Cannot publish the logbased view '%ls' for replication. Replication is not supported for logbased views that depend on FileTable objects.
33438160Cannot enable Change Tracking on the FileTable '%.*ls'. Change Tracking is not supported for FileTable objects.
33439160Cannot use IGNORE_CONSTRAINTS hint when inserting into FileTable '%.*ls', unless FILETABLE_NAMESPACE is disabled.
33440160When inserting into FileTable '%.*ls' using BCP or BULK INSERT, either CHECK_CONSTRAINTS option needs to be on, or FILETABLE_NAMESPACE needs to be disabled on the table.
33441160The FileTable '%.*s' cannot be partitioned. Partitioning is not supported on FileTable objects.
33442160The handle ID %d is opened against the server root share and cannot be killed. The lifetime of the handle is controlled by the client who originally opened it.
33443160The database '%.*s' cannot be enabled for both FILESTREAM non-transacted access and Database Mirroring.
33444160The database '%.*s' cannot be enabled for both FILESTREAM non-transacted access and HADR.
33445160The database '%.*s' is a readable secondary database in an availability group and cannot be enabled for FILESTREAM non-transacted access.
33446160The FILESTREAM database configuration cannot be changed for database '%.*s'. The database is either a mirror database in Database Mirroring, or is in a secondary replica of an Always On availability group. Connect to the server instance that hosts the primary database replica, and retry the operation.
33447160Cannot access file_stream column in FileTable '%.*ls', because FileTable doesn't support row versioning. Either set transaction level to something other than READ COMMITTED SNAPSHOT or SNAPSHOT, or use READCOMMITTEDLOCK table hint.
33448160Cannot disable clustered index '%.*ls' on FileTable '%.*ls' because the FILETABLE_NAMESPACE is enabled.
33449100FILESTREAM File I/O access is enabled, but no listener for the availability group is created. A FILESTREAM PathName will be unable to refer to a virtual network name (VNN) and, instead, will need to refer to a physical Windows Server Failover Clustering (WSFC) node. This might limit the usability of FILESTEAM File I/0 access after an availability group failover. Therefore, we recommend that you create a listener for each availability group. For information about how to create an availability group listener, see SQL Server Books Online.
33450100FILESTREAM File I/O access is enabled. One or more availability groups ('%ls') currently do not have a listener. A FILESTREAM PathName will be unable to refer to a virtual network name (VNN) and, instead, will need to refer to a physical Windows Server Failover Clustering (WSFC) node. This might limit the usability of FILESTEAM File I/0 access after an availability group failover. Therefore, we recommend that you create a listener for each availability group. For information about how to create an availability group listener, see SQL Server Books Online.
33501160Security predicates cannot be added on tables that contain filestream data. Column '%.*ls' on table '%.*ls' contains filestream data.
33502160The column '%.*ls' could not be added to table '%.*ls' because the column contains filestream data and the table is referenced by one or more security policies. Filestream columns are not allowed on tables that are referenced by security policies.
33503160BLOCK predicates can only be added to user tables. '%.*ls' is not a user table.
33504160The attempted operation failed because the target object '%.*ls' has a block predicate that conflicts with this operation. If the operation is performed on a view, the block predicate might be enforced on the underlying table. Modify the operation to target only the rows that are allowed by the block predicate.
33505160Partitioned view '%.*ls' is not updatable because table '%.*ls' has an enabled security policy that defines block predicates for this table.
33506160Only natively compiled inline table-valued functions can be used for security predicates on memory optimized tables. Table '%.*ls' is memory optimized, but function '%.*ls' is not natively compiled. Recreate the function using WITH NATIVE_COMPILATION.
33507160Function '%ls' cannot be used in the definition of BLOCK security predicates. Modify the BLOCK security predicates for this table or view to not use this function.
33508160Column '%.*ls' cannot be passed as a parameter for a BLOCK security predicate because the column definition contains an expression using a window function. Modify the BLOCK security predicates for this view to not use this column.
33509160Column '%.*ls' cannot be passed as a parameter for an AFTER UPDATE or AFTER INSERT BLOCK security predicate for this view because it refers to a base table that is not being modified in this statement. Modify the AFTER INSERT and AFTER UPDATE BLOCK security predicates for this view to not use this column.
33510160BLOCK security predicates cannot reference temporal history tables. Table '%.*ls' is a temporal history table.
33511160Table '%.*ls' is memory optimized. Only security policies with schema binding enabled may specify security predicates for memory optimized tables. Create a new security policy with schema binding enabled.
33512160Binding for the non-schema bound security predicate on object '%.*ls' failed with one or more errors, indicating the schema of the predicate function has changed. Update or drop the affected security predicates.
33513160Binding for the non-schema bound security predicate on object '%.*ls' failed, because the predicate function is not an inline table-valued function. Only inline table-valued functions can be used for security predicates.
33514160Incorrect parameter encryption metadata was received from the client. The error occurred during the invocation of the batch and therefore the client can refresh the parameter encryption metadata by calling sp_describe_parameter_encryption and retry.
33515160The parameter "%.*ls" does not have the same encryption information as the one it was created with. Use sp_refresh_parameter_encryption to refresh the parameter encryption information for the module.
33516160The object '%.*ls' is referenced by the security policy '%.*ls'. The currently installed edition of SQL Server does not support security policies. Either drop the security policy or upgrade the instance of SQL Server to a version that supports security policies.
33517160The column '%.*ls' of the object '%.*ls' is encrypted. The currently installed edition of SQL Server does not support encrypted columns. Either remove the encryption from the column or upgrade the instance of SQL Server to a version that supports encrypted columns.
33518160Valid values of the database compatibility level are %d, %d, %d, or %d.
33519160An external data source conflicting with '%.*ls' already exists in EDS cache in memory. Use alter step to change the location or credential. Drop and re-create to change the EDS name.
33520160Failed to allocate memory for caching external data source '%.*ls' which is used by a database file.
33521160Cannot drop the external data source '%.*ls' because it is being used.
33522160Cannot remove the external data source '%.*ls' because it is being used.
33523160Cryptographic failure due to insufficient memory.
33524100The fn_get_audit_file function is skipping records from '%.*ls'. You must be connected to database '%.*ls' to access its audit logs.
33525100The fn_get_audit_file function is skipping records from '%.*ls'. You must be connected to server '%.*ls' to access its audit logs.
33526100The fn_get_audit_file function is skipping records from '%.*ls', as it does not conform to the auditing blob naming convention.
33527160Error occured while initializing the security functions lookup table. This might be because the installation of SQL Server is corrupted and a required file is missing.