SQL Server Error Messages

General Error Message (Volume 3)

The below information can be seen from sys.messages table.

This helps to understand the error falls under which severity.

Msg_Id Severity Message

15001 16 Object ‘%ls’ does not exist or is not a valid object for this operation.
15002 16 The procedure ‘%s’ cannot be executed within a transaction. 15003 16 Only members of the %s role can execute this stored procedure.
15004 16 Name cannot be NULL.
15005 10 Statistics for all tables have been updated.
15006 16 ‘%s’ is not a valid name because it contains invalid characters.
15007 16 ‘%s’ is not a valid login or you do not have permission. 15008 16 User ‘%s’ does not exist in the current database.
15009 16 The object ‘%s’ does not exist in database ‘%s’ or is invalid for this operation.
15010 16 The database ‘%s’ does not exist. Supply a valid database name. To see available databases, use sys.databases.
15011 16 Database option ‘%s’ does not exist. Specify a valid database option.
15012 16 The device ‘%s’ does not exist. Use sys.backup_devices to show available devices.
15013 10 Table ‘%s’: No columns without statistics found.
15014 16 The role ‘%s’ does not exist in the current database. 15015 16 The server ‘%s’ does not exist. Use sp_helpserver to show available servers.
15016 16 The default ‘%s’ does not exist.
15017 16 The rule ‘%s’ does not exist.
15018 10 Table ‘%s’: Creating statistics for the following columns: 15019 16 The extended stored procedure ‘%s’ does not exist.
15020 10 Statistics have been created for the %d listed columns of the above tables.
15021 16 Invalid value given for parameter %s. Specify a valid parameter value.
15022 16 The specified user name is already aliased.
15023 16 User, group, or role ‘%s’ already exists in the current database.
15024 16 The group ‘%s’ already exists in the current database. 15025 16 The server principal ‘%s’ already exists.
15026 16 Logical device ‘%s’ already exists.
15028 16 The server ‘%s’ already exists.
15032 16 The database ‘%s’ already exists. Specify a unique database name.
15033 16 ‘%s’ is not a valid official language name.
15034 16 The application role password must not be NULL.
15036 16 The data type ‘%s’ does not exist or you do not have permission.
15040 16 User-defined error messages must have an ID greater than 50000.
15041 16 User-defined error messages must have a severity level between 1 and 25.
15042 10 The @with_log parameter is ignored for messages that are not us_english version.
15043 16 You must specify ‘REPLACE’ to overwrite an existing message. 15044 16 The type “%s” is an unknown backup device type. Use the type “disk” or “tape”.
15045 16 The logical name cannot be NULL.
15046 16 The physical name cannot be NULL.
15048 10 Valid values of the database compatibility level are %d, %d, %d, %d, or %d.
15049 11 Cannot unbind from ‘%s’. Use ALTER TABLE DROP CONSTRAINT. 15050 11 Cannot bind default ‘%s’. The default must be created using the CREATE DEFAULT statement.
15051 11 Cannot rename the table because it is published for replication.
15053 16 Objects exist which are not owned by the database owner. 15054 10 The current compatibility level is %d.
15056 10 The suspect flag on the database “%s” is already reset. 15057 16 List of %s name contains spaces, which are not allowed. 15058 16 List of %s has too few names.
15059 16 List of %s has too many names.
15060 16 List of %s names contains name(s) which have ‘%s’
non-alphabetic characters.
15061 16 The add device request was denied. A physical device named “%s” already exists. Only one backup device may refer to any physical device name.
15062 16 The guest user cannot be mapped to a login name.
15063 16 The login already has an account under a different user name.
15065 16 All user IDs have been assigned.
15066 16 A default-name mapping of a remote login from remote server ‘%s’ already exists.
15068 16 A remote user ‘%s’ already exists for remote server ‘%s’. 15069 16 One or more users are using the database. The requested operation cannot be completed.
15070 10 Object ‘%s’ was successfully marked for recompilation. 15071 16 Usage: sp_addmessage ,,
[, [,FALSE | TRUE [,REPLACE]]]
15072 16 Usage: sp_addremotelogin remoteserver [,loginname
[,remotename]]
15074 10 Warning: You must recover this database prior to access. 15076 16 Default, table, and user data types must be in the current database.
15077 16 Rule, table, and user data type must be in the current database.
15078 16 The table or view must be in the current database.
15079 10 Queries processed: %d.
15080 16 Cannot use parameter %s for a Windows login.
15081 16 Membership of the public role cannot be changed.
15083 16 Physical data type ‘%s’ does not accept a collation 15084 16 The column or user data type must be in the current database.
15085 16 Usage: sp_addtype name, ‘data type’ [,'NULL' | 'NOT NULL'] 15096 16 Could not find object ‘%ls’ or you do not have required permission or the object is not valid for adding extended property. 15097 16 The size associated with an extended property cannot be more than 7,500 bytes.
15098 16 The name change cannot be performed because the SID of the new name does not match the old SID of the principal.
15099 16 The MUST_CHANGE option cannot be used when CHECK_EXPIRATION is OFF.
15100 16 Usage: sp_bindefault defaultname, objectname [,
‘futureonly’]
15101 16 Cannot bind a default to a computed column or to a column of data type timestamp, varchar(max), nvarchar(max), varbinary(max), xml or sqlclr type.
15102 16 Cannot bind a default to an identity column.
15103 16 Cannot bind a default to a column created with or altered to have a default value.
15104 16 You do not own a table named ‘%s’ that has a column named ‘%s’.
15106 16 Usage: sp_bindrule rulename, objectname [, 'futureonly'] 15107 16 Cannot bind a rule to a computed column or to a column of data type text, ntext, image, timestamp, varchar(max), nvarchar(max), varbinary(max), xml or sqlclr type.
15108 16 sp_addtype cannot be used to define user-defined data types for varchar(max), nvarchar(max) or varbinary(max) data types. Use CREATE TYPE for this purpose.
15109 16 Cannot change the owner of the master, model, tempdb or distribution database.
15110 16 The proposed new database owner is already a user or aliased in the database.
15111 16 The proposed new database owner is already aliased in the database.
15112 11 The third parameter for table option ‘text in row’ is invalid. It should be ‘on’, ‘off’, ’0′, or a number from 24 through 7000. 15113 16 Too many failed login attempts. This account has been temporarily locked as a precaution against password guessing. A system administrator can unlock this login with the UNLOCK clause of ALTER LOGIN. 15114 16 Password validation failed. The password for the user is too recent to change.
15115 16 Password validation failed. The password cannot be used at this time.
15116 16 Password validation failed. The password does not meet Windows policy requirements because it is too short.
15117 16 Password validation failed. The password does not meet Windows policy requirements because it is too long.
15118 16 Password validation failed. The password does not meet Windows policy requirements because it is not complex enough. 15119 16 Password validation failed. The password does not meet the requirements of the password filter DLL.
15120 16 An unexpected error occurred during password validation. 15121 16 An error occurred during the execution of %ls. A call to ‘%ls’ failed with error code: ‘%d’.
15122 16 The CHECK_EXPIRATION option cannot be used when CHECK_POLICY is OFF.
15123 16 The configuration option ‘%s’ does not exist, or it may be an advanced option.
15124 16 The configuration option ‘%s’ is not unique.
15125 16 Trigger ‘%s’ is not a trigger for ‘%s’.
15127 16 Cannot set the default language to a language ID not defined in syslanguages.
15128 16 The CHECK_POLICY and CHECK_EXPIRATION options cannot be turned OFF when MUST_CHANGE is ON.
15129 16 ‘%d’ is not a valid value for configuration option ‘%s’. 15130 16 There already exists a ‘%s’ trigger for ‘%s’.
15131 16 Usage: sp_dbremove [,dropdev]
15133 16 INSTEAD OF trigger ‘%s’ cannot be associated with an order. 15134 16 No alias exists for the specified user.
15135 16 Object is invalid. Extended properties are not permitted on ‘%s’, or the object does not exist.
15136 16 The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot be dropped.
15137 16 An error occurred during the execution of
sp_xp_cmdshell_proxy_account. Possible reasons: the provided account was invalid or the ‘%.*ls’ credential could not be created. Error code: ‘%d’. 15138 16 The database principal owns a %S_MSG in the database, and cannot be dropped.
15141 16 The server principal owns an %S_MSG and cannot be dropped. 15143 16 ‘%s’ is not a valid option for the @updateusage parameter. Enter either ‘true’ or ‘false’.
15144 16 The role has members. It must be empty before it can be dropped.
15145 16 An implicit %S_MSG creation has failed. Reason: The %S_MSG may have been dropped or its name may already be in use.
15146 16 An encryption password must be provided to encrypt the private key of this %S_MSG.
15147 16 No decryption password should be provided because the private key of this %S_MSG is encrypted by a master key.
15148 16 The data type or table column ‘%s’ does not exist or you do not have permission.
15149 16 Principal doesn’t exist or doesn’t have sufficient
privileges.
15150 16 Cannot %S_MSG the %S_MSG ‘%.*ls’.
15151 16 Cannot %S_MSG the %S_MSG ‘%.*ls’, because it does not exist or you do not have permission.
15152 16 Cannot update user instances. Reason: %ls. Error code: 0x%x. 15153 16 The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the ‘%.*ls’ credential exists and contains valid information.
15154 16 The database principal owns an %S_MSG and cannot be dropped. 15155 16 The server principal owns a %S_MSG and cannot be dropped. 15156 16 The password that you specified is too long. The password should have no more than %d characters.
15157 16 Setuser failed because of one of the following reasons: the database principal ‘%.*ls’ does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.
15158 16 Cannot initialize security.
15159 16 Maximum impersonation nesting level exceeded (limit %d).. 15160 16 Cannot issue impersonation token from non-primary
impersonation context or for non-Windows user.
15161 16 Cannot set application role ‘%.*ls’ because it does not exist or the password is incorrect.
15162 16 Unexpected error while creating impersonation token. 15163 16 Invalid timeout value. Valid timeout is between 1 and 7200 sec.
15164 16 ‘%.*ls’ is not a valid login or cannot be issued
impersonation token.
15165 16 Could not find object ‘%ls’ or you do not have permission. 15166 10 Warning: User types created via sp_addtype are contained in dbo schema. The @owner parameter if specified is ignored.
15167 16 Cannot generate GUID.
15168 16 Cannot rename the view ‘%s’ and its columns and indexes because it is a system generated view that was created for optimization purposes.
15169 16 The server option “%ls” is not available in this edition of SQL Server.
15170 16 This login is the owner of %ld job(s). You must delete or reassign these jobs before the login can be dropped.
15171 16 Cannot use the parameter “%s” for a certificate or
asymmetric key login.
15172 16 FallBack certificate must be created or dropped in master database in single user mode.
15173 16 Login ‘%s’ has granted one or more permission(s). Revoke the permission(s) before dropping the login.
15174 16 Login ‘%s’ owns one or more database(s). Change the owner of the database(s) before dropping the login.
15175 16 Login ‘%s’ is aliased or mapped to a user in one or more database(s). Drop the user or alias before dropping the login. 15176 16 The only valid @parameter value is ‘WITH_LOG’.
15177 16 Usage: sp_dropmessage [, | 'ALL'] 15178 16 Cannot drop a message with an ID less than 50,000.
15179 16 The message number %u or specified language version does not exist.
15182 16 Cannot disable access to the guest user in master or tempdb. 15183 16 The database principal owns objects in the database and cannot be dropped.
15184 16 The database principal owns data types in the database and cannot be dropped.
15185 16 There is no remote user ‘%s’ mapped to local user ‘%s’ from the remote server ‘%s’.
15186 16 The server principal is set as the execution context of a trigger or event notification and cannot be dropped.
15187 10 The %S_MSG cannot be dropped because it is used by one or more %S_MSG(s).
15188 16 Cannot create an index that does not include all security columns.
15189 16 Cannot have more than one security column for a table. 15190 16 There are still remote logins or linked logins for the server ‘%s’.
15192 16 Cannot alter or drop the security column of a table. 15195 16 The MUST_CHANGE option is not supported by this version of Microsoft Windows.
15196 16 The current security context is non-revertible. The “Revert” statement failed.
15197 16 There is no text for object ‘%s’.
15198 16 The name supplied (%s) is not a user, role, or aliased login.
15199 16 The current security context cannot be reverted. Please switch to the original database where ‘%ls’ was called and try it again. 15200 16 There are no remote servers defined.
15201 16 There are no remote logins for the remote server ‘%s’. 15202 16 There are no remote logins defined.
15203 16 There are no remote logins for ‘%s’.
15204 16 There are no remote logins for ‘%s’ on remote server ‘%s’. 15205 16 There are no servers defined.
15206 16 Invalid Remote Server Option: ‘%s’.
15207 16 The trusted option in remote login mapping is no longer supported.
15208 16 The certificate, asymmetric key, or private key file does not exist or has invalid format.
15209 16 An error occurred during encryption.
15212 16 Invalid certificate subject. The certificate subject must have between 1 and %d characters.
15213 16 Warning: The certificate you created has an invalid validity period; its expiration date precedes its start date.
15214 16 Warning: The certificate you created is expired.
15215 16 Warning: The certificate you created is not yet valid; its start date is in the future.
15216 16 ‘%s’ is not a valid option for the @delfile parameter. 15217 16 Property cannot be updated or deleted. Property ‘%.*ls’ does not exist for ‘%.*ls’.
15218 16 Object ‘%s’ is not a table.
15219 16 Cannot change the owner of an indexed view.
15222 16 Remote login option ‘%s’ is not unique.
15223 11 Error: The input parameter ‘%s’ is not allowed to be null. 15224 11 Error: The value for the @newname parameter contains invalid characters or violates a basic restriction (%s).
15225 11 No item by the name of ‘%s’ could be found in the current database ‘%s’, given that @itemtype was input as ‘%s’.
15226 16 Cannot create user defined types from an XML datatype. 15227 16 The database ‘%s’ cannot be renamed.
15228 16 A member of the sysadmin role must set database ‘%s’ to single user mode with sp_dboption before it can be renamed.
15229 16 Usage: sp_db_vardecimal_storage_format [dbname [,'on' | 'off']]
15232 16 A certificate with name ‘%s’ already exists or this certificate already has been added to the database.
15233 16 Property cannot be added. Property ‘%.*ls’ already exists for ‘%.*ls’.
15234 16 Objects of this type have no space allocated.
15236 16 Column ‘%s’ has no default.
15237 16 User data type ‘%s’ has no default.
15238 16 Column ‘%s’ has no rule.
15239 16 User data type ‘%s’ has no rule.
15240 16 Cannot write into file ‘%s’. Verify that you have write permissions, that the file path is valid, and that the file does not already exist.
15241 16 Usage: sp_dboption [dbname [,optname [,'true' | 'false']]] 15242 16 Database option ‘%s’ is not unique.
15243 16 The option ‘%s’ cannot be changed for the master database. 15244 16 Only members of the sysadmin role or the database owner may set database options.
15246 16 Cannot dump the private key of certificate ‘%s’ because the private key cannot be found.
15247 16 User does not have permission to perform this action. 15248 11 Either the parameter @objname is ambiguous or the claimed @objtype (%s) is wrong.
15249 11 Error: Explicit @objtype ‘%s’ is unrecognized.
15250 16 The database name component of the object qualifier must be the name of the current database.
15251 16 Invalid ‘%s’ specified. It must be %s.
15252 16 The primary or foreign key table name must be given. 15253 11 Syntax error parsing SQL identifier ‘%s’.
15254 16 Users other than the database owner or guest exist in the database. Drop them before removing the database.
15255 11 ‘%s’ is not a valid value for @autofix. The only valid value is ‘auto’.
15256 16 Usage: sp_certify_removable [,'auto']
15257 16 The database that you are attempting to certify cannot be in use at the same time.
15258 16 The database must be owned by a member of the sysadmin role before it can be removed.
15259 16 The DEFAULT_SCHEMA clause cannot be used with a Windows group or with principals mapped to certificates or asymmetric keys. 15260 16 The format of the security descriptor string ‘%s’ is invalid.
15261 16 Usage: sp_create_removable
,,,,,,,,,
[,,,...,,]

15262 10 Invalid file size entered. All files must be at least 1 MB. 15263 16 A SID in the security descriptor string ‘%s’ could not be found in an account lookup operation.
15264 16 Could not create the ‘%s’ portion of the database.
15265 16 An unexpected error has occurred in the processing of the security descriptor string ‘%s’.
15266 16 Cannot make ‘%s’ database removable.
15267 16 A security descriptor with name ‘%s’ already exists. 15268 10 Authentication mode is %s.
15269 16 Logical data device ‘%s’ not created.
15271 16 Invalid @with_log parameter value. Valid values are ‘true’ or ‘false’.
15272 10 The %s ‘%.*s’ is not trusted to execute.
15273 10 The decryption key is incorrect.
15274 16 Access to the remote server is denied because the current security context is not trusted.
15276 16 Cannot provision master key passwords for system databases. 15277 16 The only valid @parameter_value values are ‘true’ or ‘false’.
15278 16 Login ‘%s’ is already mapped to user ‘%s’ in database ‘%s’. 15279 16 You must add the us_english version of this message before you can add the ‘%s’ version.
15280 16 All localized versions of this message must be dropped before the us_english version can be dropped.
15281 10 SQL Server blocked access to %S_MSG ‘%ls’ of component ‘%.*ls’ because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of ‘%.*ls’ by using sp_configure. For more information about enabling ‘%.*ls’, see “Surface Area Configuration” in SQL Server Books Online. 15282 10 A key with name ‘%.*ls’ or user defined unique identifier already exists or you do not have permissions to create it.
15283 16 The name ‘%s’ contains too many characters.
15284 16 The database principal has granted or denied permissions to objects in the database and cannot be dropped.
15285 16 The special word ‘%s’ cannot be used for a logical device name.
15286 16 Terminating this procedure. The @action ‘%s’ is
unrecognized. Try ‘REPORT’, ‘UPDATE_ONE’, or ‘AUTO_FIX’.
15287 16 Terminating this procedure. ‘%s’ is a forbidden value for the login name parameter in this procedure.
15288 10 Please specify one decryptor to decrypt a key.
15289 16 Terminating this procedure. Cannot have an open transaction when this is run.
15291 16 Terminating this procedure. The %s name ‘%s’ is absent or invalid.
15292 10 The row for user ‘%s’ will be fixed by updating its login link to a login already in existence.
15293 10 Barring a conflict, the row for user ‘%s’ will be fixed by updating its link to a new login.
15294 10 The number of orphaned users fixed by adding new logins and then updating users was %d.
15295 10 The number of orphaned users fixed by updating users was %d. 15296 16 General cryptographic failure.
15297 16 The certificate, asymmetric key, or private key data is invalid.
15299 16 The signature of the public key is invalid.
15300 11 No recognized letter is contained in the parameter value for General Permission Type (%s). Valid letters are in this set: %s . 15301 16 Collation ‘%s’ is supported for Unicode data types only and cannot be set at either the database or server level.
15302 11 Database_Name should not be used to qualify owner.object for the parameter into this procedure.
15303 11 The “user options” config value (%d) was rejected because it would set incompatible options.
15304 16 The severity level of the ‘%s’ version of this message must be the same as the severity level (%ld) of the us_english version. 15305 16 The @TriggerType parameter value must be ‘insert’, ‘update’, or ‘delete’.
15306 16 Cannot change the compatibility level of replicated or distributed databases.
15307 16 Could not change the merge publish option because the server is not set up for replication.
15308 16 You must set database ‘%s’ to single user mode with sp_dboption before fixing indexes on system tables.
15309 16 Cannot alter the trustworthy state of the model or tempdb databases.
15310 16 Failed to configure user instance on startup. Error updating SysServers table.
15311 16 The file named ‘%s’ does not exist.
15312 16 The file named ‘%s’ is a primary file and cannot be removed. 15313 10 The key is not encrypted using the specified decryptor. 15314 10 Either no algorithm has been specified or the bitlength and the algorithm specified for the key are not available in this installation of Windows.
15315 10 The key ‘%.*ls’ is not open. Please open the key before using it.
15316 10 Global temporary keys are not allowed. You can only use local temporary keys.
15317 10 The master key file does not exist or has invalid format. 15318 10 All fragments for database ‘%s’ on device ‘%s’ are now dedicated for log usage only.
15319 17 Error: DBCC DBREPAIR REMAP failed for database ‘%s’ (device ‘%s’).
15320 16 An error occurred while decrypting %S_MSG ‘%.*ls’ that was encrypted by the old master key. The FORCE option can be used to ignore this error and continue the operation, but data that cannot be decrypted by the old master key will become unavailable.
15321 16 There was some problem removing ‘%s’ from sysaltfiles. 15322 10 File ‘%s’ was removed from tempdb, and will take effect upon server restart.
15323 16 The selected index does not exist on table ‘%s’.
15324 16 The option %s cannot be changed for the ‘%s’ database. 15325 16 The current database does not contain a %s named ‘%ls’. 15326 10 No extended stored procedures exist.
15327 10 The database is now offline.
15328 10 The database is offline already.
15329 16 The current master key cannot be decrypted. If this is a database master key, you should attempt to open it in the session before performing this operation. The FORCE option can be used to ignore this error and continue the operation but the data encrypted by the old master key will be lost.
15330 11 There are no matching rows on which to report.
15331 11 The user ‘%s’ cannot take the action auto_fix due to duplicate SID.
15332 10 The private key is already set for this file. To change it you should drop and re-create the certificate.
15333 11 Error: The qualified @oldname references a database (%s) other than the current database.
15334 10 The %S_MSG has a private key that is protected by a user defined password. That password needs to be provided to enable the use of the private key.
15335 11 Error: The new name ‘%s’ is already in use as a %s name and would cause a duplicate that is not permitted.
15336 16 Object ‘%s’ cannot be renamed because the object
participates in enforced dependencies.
15337 10 Caution: sysdepends shows that other objects (views, procedures and so on) are referencing this object by its old name. These objects will become invalid, and should be dropped and re-created promptly. 15339 10 Creating ‘%s’.
15342 10 There is no private key provisioned for %S_MSG ‘%.*ls’. 15343 10 The username and/or password passed in is invalid or the current process does not have sufficient privileges.
15344 16 Ownership change for %S_MSG is not supported.
15345 16 An entity of type %S_MSG cannot be owned by a role, a group, or by principals mapped to certificates or asymmetric keys.
15346 16 Cannot change owner for an object that is owned by a parent object. Change the owner of the parent object instead.
15347 16 Cannot transfer an object that is owned by a parent object. 15348 16 Cannot transfer a schemabound object.
15349 16 Cannot transfer an MS Shipped object.
15350 16 An attempt to attach an auto-named database for file %.*ls failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
15351 10 The CLR procedure/function/UDT being signed refers to an assembly that is not signed either by a strong name or an assembly. 15352 10 The %S_MSG cannot be dropped because one or more entities are either signed or encrypted using it.
15353 16 An entity of type %S_MSG cannot be owned by a role, a group, an approle, or by principals mapped to certificates or asymmetric keys. 15354 10 Usage: sp_detach_db , [TRUE|FALSE], [TRUE|FALSE] 15356 16 The current application role has been dropped. The current security context contains no valid database user context.
15357 16 The current security context was set by “%ls”. It cannot be reverted by statement “%ls”.
15358 10 User-defined filegroups should be made read-only.
15359 16 Cannot add functional unit ‘%.*ls’ to component ‘%.*ls’. This unit has been already registered with the component.
15360 16 An error occurred while trying to load the xpstar dll to read the agent proxy account from LSA.
15361 16 An error occurred while trying to read the SQLAgent proxy account credentials from the LSA.
15362 16 An error occurred while trying to create the ‘%.*ls’ credential.
15364 16 Failed to generate a user instance of SQL Server. Only an integrated connection can generate a user instance. The connection will be closed.%.*ls
15365 16 Failed to generate a user instance of SQL Server. Only members of Builtin\Users can generate a user instance. The connection will be closed.%.*ls
15366 16 Failed to generate a user instance of SQL Server due to low memory. The connection will be closed.%.*ls
15367 16 Failed to generate a user instance of SQL Server due to a failure in generating a unique user instance name. The connection will be closed.%.*ls
15368 16 Failed to generate a user instance of SQL Server due to a failure in reading registry keys. The connection will be closed.%.*ls 15369 16 Failed to generate a user instance of SQL Server due to a failure in impersonating the client. The connection will be closed.%.*ls 15370 16 Failed to generate a user instance of SQL Server due to a failure in copying database files. The connection will be closed.%.*ls 15371 16 Failed to generate a user instance of SQL Server due to a failure in creating user instance event. The connection will be closed.%.*ls 15372 16 Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.%.*ls
15373 16 Failed to generate a user instance of SQL Server due to a failure in obtaining the user instance’s process information. The connection will be closed.%.*ls
15374 16 Failed to generate a user instance of SQL Server due to a failure in persisting the user instance information into system catalog. The connection will be closed.%.*ls
15375 16 Failed to generate a user instance of SQL Server due to a failure in making a connection to the user instance. The connection will be closed.%.*ls
15376 16 Failed to generate a user instance of SQL Server. Only the SQL Server Express version lets you generate a user instance. The connection will be closed.%.*ls
15377 16 Failed to configure user instance on startup. Error adding user to SysAdmin role.
15378 16 Failed to configure user instance on startup. Error configuring system database entries in MASTER DB.
15380 16 Failed to configure user instance on startup. Error configuring system database paths in MASTER DB.
15381 16 Failed to generate a user instance of SQL Server due to a failure in updating security descriptor on the process of the user instance. 15382 16 Failed to generate a user instance of SQL Server due to failure in retrieving the user’s local application data path. Please make sure the user has a local user profile on the computer. The connection will be closed.%.*ls
15383 16 Generating user instances in SQL Server is disabled. Use sp_configure ‘user instances enabled’ to generate user instances.%.*ls 15384 16 Failed to configure user instance on startup. Error updating Resource Manager ID.
15385 16 No database principal is defined for sid ‘%.*ls’.
15386 16 Another batch in the session is changing security context, new batch is not allowed to start.
15387 11 If the qualified object name specifies a database, that database must be the current database.
15388 11 There is no user table matching the input name ‘%s’ in the current database or you do not have permission to access the table. 15389 11 sp_indexoption is not supported for XML Index. Use ALTER INDEX instead.
15390 11 Input name ‘%s’ does not have a matching user table or indexed view in the current database.
15391 11 sp_indexoption is not supported for XML Index and the table has an XML index on it. Use ALTER INDEX instead to set the option for ALL the indexes.
15392 16 The specified option ‘%s’ is not supported by this edition of SQL Server and cannot be changed using sp_configure.
15393 16 An error occurred while decrypting the password for linked login ‘%.*ls’ that was encrypted by the old master key. The FORCE option can be used to ignore this error and continue the operation but the data encrypted by the old master key will be lost.
15394 16 Collation ‘%s’ is not supported by the operating system 15395 11 The qualified old name could not be found for item type ‘%s’.
15396 16 An asymmetric key with name ‘%s’ already exists or this asymmetric key already has been added to the database.
15397 16 The %S_MSG is not protected by a password. A decryption password cannot be used for this operation.
15398 11 Only objects in the master database owned by dbo can have the startup setting changed.
15399 11 Could not change startup option because this option is restricted to objects that have no parameters.
15401 11 Windows NT user or group ‘%s’ not found. Check the name again.
15402 11 ‘%s’ is not a fixed server role.
15403 16 The server principal “%.*ls” does not exist, does not have server access, or you do not have permission.
15404 16 Could not obtain information about Windows NT group/user ‘%ls’, error code %#lx.
15405 11 Cannot use the special principal ‘%s’.
15406 16 Cannot execute as the server principal because the principal “%.*ls” does not exist, this type of principal cannot be impersonated, or you do not have permission.
15407 11 ‘%s’ is not a valid Windows NT name. Give the complete name: .
15408 16 “%ls” cannot be called in this batch because a simultaneous batch has called it.
15409 11 ‘%s’ is not a role.
15410 11 User or role ‘%s’ does not exist in this database.
15411 11 Database principal or schema ‘%s’ does not exist in this database.
15412 11 ‘%s’ is not a known fixed role.
15413 11 Cannot make a role a member of itself.
15414 16 Cannot set compatibility level because database has a view or computed column that is indexed. These indexes require a SQL Server compatible database.
15415 11 User is a member of more than one group. sp_changegroup is set up for backward compatibility and expects membership in one group at most.
15416 16 Usage: sp_dbcmptlevel [dbname [, compatibilitylevel]] 15418 16 Only members of the sysadmin role or the database owner may set the database compatibility level.
15419 16 Supplied parameter sid should be binary(16).
15420 16 The group ‘%s’ does not exist in this database.
15421 16 The database principal owns a database role and cannot be dropped.
15422 16 Application roles can only be activated at the ad hoc level. 15425 16 No server principal is defined for sid ‘%.*ls’.
15426 16 You must specify a provider name with this set of
properties.
15427 16 You must specify a provider name for unknown product ‘%ls’. 15428 16 You cannot specify a provider or any properties for product ‘%ls’.
15429 16 ‘%ls’ is an invalid product name.
15431 16 You must specify the @rolename parameter.
15432 16 Stored procedure ‘%s’ can only be executed at the ad hoc level.
15433 16 Supplied parameter sid is in use.
15434 16 Could not drop login ‘%s’ as the user is currently logged in.
15435 10 Database successfully published.
15436 10 Database successfully enabled for subscriptions.
15437 10 Database successfully published using merge replication. 15438 10 Database is already online.
15439 10 Database is now online.
15440 10 Database is no longer published.
15441 10 Database is no longer enabled for subscriptions.
15442 10 Database is no longer enabled for merge publications. 15443 10 Checkpointing database that was changed.
15448 16 Encryption by the machine key cannot be added to the service master key because the service master key cannot be decrypted or does not exist.
15450 10 New language inserted.
15451 16 Dropping an encryption from the service master key failed. No encryption by the machine key exists.
15452 10 No alternate languages are available.
15453 10 us_english is always available, even though it is not in syslanguages.
15454 10 Language deleted.
15455 16 Adding an encryption to the service master key failed. An encryption by the machine key already exists.
15457 10 Configuration option ‘%ls’ changed from %ld to %ld. Run the RECONFIGURE statement to install.
15458 10 Database removed.
15459 10 In the current database, the specified object references the following:
15460 10 In the current database, the specified object is referenced by the following:
15461 10 Object does not reference any object, and no objects reference it.
15462 10 File ‘%s’ closed.
15463 10 Device dropped.
15464 16 Unsupported private key format or key length.
15465 16 The private key password is invalid.
15466 16 An error occurred during decryption.
15468 16 An error occurred during the generation of the %S_MSG. 15469 10 No constraints are defined on object ‘%ls’, or you do not have permissions.
15470 10 No foreign keys reference table ‘%ls’, or you do not have permissions on referencing tables.
15471 10 The text for object ‘%ls’ is encrypted.
15472 10 The object ‘%ls’ does not have any indexes, or you do not have permissions.
15474 16 Invalid private key. The private key does not match the public key of the %S_MSG.
15475 10 The database is renamed and in single user mode.
15476 10 A member of the sysadmin role must reset the database to multiuser mode with sp_dboption.
15477 10 Caution: Changing any part of an object name could break scripts and stored procedures.
15482 16 Cannot change the owner of a table that has an indexed view. 15490 10 The dependent aliases were also dropped.
15497 10 Could not add login using sp_addlogin (user = %s).
Terminating this procedure.
15499 10 The dependent aliases were mapped to the new database owner. 15500 10 The dependent aliases were dropped.
15502 10 Setting database owner to SA.
15503 10 Giving ownership of all objects to the database owner. 15504 10 Deleting users except guest and the database owner from sysusers.
15505 16 Cannot change owner of object ‘%ls’ or one of its child objects because the new owner ‘%ls’ already has an object with the same name.
15506 16 An error occurred while signing.
15507 16 A key required by this operation appears to be corrupted. 15508 16 An error occurred while generating a key required by this operation.
15509 16 The password cannot be dropped because another database may be using it.
15510 16 Cannot enable a login that has an empty password.
15511 10 Default bound to column.
15512 10 Default bound to data type.
15513 10 The new default has been bound to columns(s) of the specified user data type.
15514 10 Rule bound to table column.
15515 10 Rule bound to data type.
15516 10 The new rule has been bound to column(s) of the specified user data type.
15517 16 Cannot execute as the database principal because the principal “%.*ls” does not exist, this type of principal cannot be impersonated, or you do not have permission.
15518 16 Cannot execute as the Windows token. It is not valid, or you do not have permission.
15519 10 Default unbound from table column.
15520 10 Default unbound from data type.
15521 10 Columns of the specified user data type had their defaults unbound.
15522 10 Rule unbound from table column.
15523 10 Rule unbound from data type.
15524 10 Columns of the specified user data type had their rules unbound.
15525 10 sp_checknames is used to search for non 7-bit ASCII characters.
15526 10 in several important columns of system tables. The following 15527 10 columns are searched:
15528 10 In master:
15529 16 Cannot execute as the ticket. It is not valid, or you do not have permission.
15530 16 The %S_MSG with name “%.*ls” already exists.
15531 16 The security descriptor information is not valid.
15532 16 The security descriptor is invalid because it does not contain information about its owner or about its primary group. 15533 16 Invalid data type is supplied in the ‘%ls’ statement. 15534 16 Cookie generation failed in the ‘%ls’ statement.
15535 16 Cannot set a credential for principal ‘%.*ls’.
15536 10 In all databases:
15537 16 Login ‘%.*ls’ does not have access to server.
15538 16 Login ‘%.*ls’ does not have access to database.
15539 16 User ‘%s’ cannot be dropped, it can only be disabled. The user is already disabled in the current database.
15540 16 The identity string is too long. The identity string should contain no more than %d characters.
15541 16 Cannot drop the credential ‘%.*ls’ because it is used by a server principal.
15542 10 Cannot create a key without specifying an encryptor. 15556 10 Cannot decrypt or encrypt using the specified %S_MSG, either because it has no private key or because the password provided for the private key is incorrect.
15557 10 There is already a %S_MSG by %S_MSG ‘%.*ls’.
15558 10 Cannot drop %S_MSG by %S_MSG ‘%.*s’.
15559 10 Cannot drop %S_MSG ‘%.*ls’ because there is a %S_MSG mapped to it.
15560 10 Cannot add or drop a signature on ‘%.*ls’ because only modules can be signed.
15561 10 Signatures based on certificates or asymmetric keys are the only options supported in this version of the product.
15562 10 The module being executed is not trusted. Either the owner of the database of the module needs to be granted authenticate permission, or the module needs to be digitally signed.
15563 10 The %S_MSG has no private key set for it.
15574 10 This object does not have any statistics.
15575 10 This object does not have any statistics or indexes. 15576 16 You cannot set network name on server ‘%ls’ because it is not a linked SQL Server.
15577 10 Warning: A linked server that refers to the originating server is not a supported scenario. If you wish to use a four-part name to reference a local table, please use the actual server name rather than an alias.
15578 16 There is already a master key in the database. Please drop it before performing this statement.
15579 16 Adding an encryption to the symmetric key failed. An encryption by the same %S_MSG ‘%.*s’ may already exist.
15580 16 Cannot drop %S_MSG because %S_MSG ‘%.*s’ is encrypted by it. 15581 16 Please create a master key in the database or open the master key in the session before performing this operation.
15582 16 Cannot set aliases for certificate logins or asymmetric key logins.
15583 10 The module being signed is marked to execute as owner. If the owner changes the signature will not be valid.
15584 10 An error occurred while decrypting %S_MSG ‘%.*ls’ that was encrypted by the old master key. The error was ignored because the FORCE option was specified.
15585 10 The current master key cannot be decrypted. The error was ignored because the FORCE option was specified.
15586 16 Error in synchronizing system certificates between master and resource database.
15587 16 Cannot change owner of Assembly ‘%.*ls’ since dependent assembly ‘%.*ls’ is not owned by the new owner.
15588 10 The old and new master keys are identical. No data
re-encryption is required.
15589 16 Cannot revert the current security context because the cookie is invalid.
15590 16 Can only use the ‘No Revert’ or ‘Cookie’ options with the ‘Execute As’ statement at the adhoc level.
15591 16 The current security context cannot be reverted using this statement. A cookie may or may not be needed with ‘Revert’ statement depending on how the context was set with ‘Execute As’ statement. 15592 16 Cannot unset application role because none was set or the cookie is invalid.
15593 16 An error occurred while decrypting the password for linked login ‘%.*ls’ that was encrypted by the old master key. The error was ignored because the FORCE option was specified.
15594 16 The password is already provisioned for the database ‘%.*ls’ 15595 16 The password cannot be dropped because it is not provisioned for the database ‘%.*ls’
15596 10 Warning: use of a UNIQUE index, PRIMARY KEY constraint, or UNIQUE constraint on a table with row-level security can allow information disclosure.
15597 10 Warning: use of an IDENTITY column on a table with row-level security can allow information disclosure.
15598 10 Warning: use of an indexed view on a table with row-level security can allow information disclosure.
15599 10 Warning: use of a FOREIGN KEY constraint on a table with row-level security enabled can allow information disclosure, modification, or deletion not authorized at the row level.
15600 15 An invalid parameter or option was specified for procedure ‘%s’.
15601 16 Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text Search. The functionality to disable and enable full-text search for a database is deprecated. Please change your application.
15612 16 DBCC DBCONTROL error. Database was not made read-only. 15615 16 DBCC DBCONTROL error. Database was not made single user. 15622 10 No permission to access database ‘%s’.
15625 10 Option ‘%ls’ not recognized for ‘%ls’ parameter.
15626 10 You attempted to acquire a transactional application lock without an active transaction.
15627 10 sp_dboption command failed.
15635 16 Cannot execute ‘%ls’ because the database is in read-only access mode.
15645 16 Column ‘%ls’ does not exist.
15646 16 Column ‘%ls’ is not a computed column.
15647 10 No views with schema binding reference table ‘%ls’. 15650 10 Updating %s
15651 10 %d index(es)/statistic(s) have been updated, %d did not require update.
15652 10 %s has been updated…
15653 10 %s, update is not necessary…
15654 10 Table %s: cannot perform the operation on the table because its clustered index is disabled.
15656 16 Cannot create user defined types from XML data type. 15657 10 sp_db_vardecimal_storage_format statement failed.
16801 11 sp_dropwebtask requires at least one defined parameter @outputfile or @procname.
16802 11 sp_dropwebtask cannot find the specified task.
16803 11 sp_runwebtask requires at least one defined parameter @outputfile or @procname.
16804 11 SQL Web Assistant: Could not establish a local connection to SQL Server.
16805 11 SQL Web Assistant: Could not execute the SQL statement. 16806 11 SQL Web Assistant: Could not bind the parameter to the SQL statement.
16807 11 SQL Web Assistant: Could not obtain a bind token.
16808 11 SQL Web Assistant: Could not find the existing trigger. This could be due to encryption.
16809 11 SQL Web Assistant failed on the call to SQLGetData. 16810 11 SQL Web Assistant failed on the call to SQLFetch.
16811 11 SQL Web Assistant failed to bind a results column.
16812 11 SQL Web Assistant: The @query parameter must be specified. 16813 11 SQL Web Assistant: Parameters can be passed either by name or position.
16814 11 SQL Web Assistant: Invalid parameter.
16815 11 SQL Web Assistant: @procname is not valid.
16816 11 SQL Web Assistant: @outputfile is not valid.
16817 11 SQL Web Assistant: Could not read the given file.
16820 11 SQL Web Assistant failed because the state of the Web task in msdb..MSwebtasks is invalid.
16821 11 SQL Web Assistant: Could not open the output file.
16822 11 SQL Web Assistant: Could not open the template file. 16823 11 SQL Web Assistant: Could not allocate enough memory to satisfy this request.
16824 11 SQL Web Assistant: The template file specified in the Web task has a bad size.
16825 11 SQL Web Assistant: Could not read the template file. 16826 11 SQL Web Assistant: Could not find the specified marker for data insertion in the template file.
16827 11 SQL Web Assistant: Could not write to the output file. 16828 11 SQL Web Assistant: @tabborder must be tinyint.
16829 11 SQL Web Assistant: @singlerow must be 0 or 1. Cannot specify this parameter with @nrowsperpage.
16830 11 SQL Web Assistant: The @blobfmt parameter specification is invalid.
16831 11 SQL Web Assistant: The output file name is mandatory for every column specified in the @blobfmt parameter.
16832 11 SQL Web Assistant: Procedure called with too many
parameters.
16833 11 SQL Web Assistant: @nrowsperpage must be a positive number and it cannot be used with @singlerow.
16834 11 SQL Web Assistant: Read/write operation on text, ntext, or image column failed.
16838 11 SQL Web Assistant: Could not find the table in the HTML file.
16839 11 SQL Web Assistant: Could not find the matching end table tag in the HTML file.
16841 11 SQL Web Assistant: The @datachg parameter cannot be specified with the given @whentype value.
16842 11 SQL Web Assistant: Could not find and drop the necessary trigger for updating the Web page.
16843 11 SQL Web Assistant: Could not add the necessary trigger for the @datachg parameter. There could be an existing trigger on the table with missing or encrypted text.
16844 11 SQL Web Assistant: Incorrect syntax for the @datachg parameter.
16845 11 SQL Web Assistant: @datachg must be specified for the given @whentype option.
16846 11 SQL Web Assistant: @unittype and/or @numunits must be specified for the given @whentype option.
16847 11 SQL Web Assistant: @fixedfont must be 0 or 1.
16848 11 SQL Web Assistant: @bold must be 0 or 1.
16849 11 SQL Web Assistant: @italic must be 0 or 1.
16850 11 SQL Web Assistant: @colheaders must be 0 or 1.
16851 11 SQL Web Assistant: @lastupdated must be 0 or 1.
16852 11 SQL Web Assistant: @HTMLheader must be in the range 1 to 6. 16853 11 SQL Web Assistant: @username is not valid.
16854 11 SQL Web Assistant: @dbname is not valid.
16855 11 SQL Web Assistant: @whentype must be in the range 1 to 9. 16856 11 SQL Web Assistant: @unittype must be in the range 1 to 4. 16857 11 SQL Web Assistant: @targetdate is invalid. It must be a valid date after 1900-01-01.
16858 11 SQL Web Assistant: The @targettime parameter must be between 0 and 240000.
16859 11 SQL Web Assistant: @dayflags must be 1, 2, 4, 8, 16, 32, or 64.
16860 11 SQL Web Assistant: @numunits must be greater than 0. 16861 11 SQL Web Assistant: @targetdate must be specified for the given @whentype option.
16862 11 SQL Web Assistant: @dayflags must be specified for the given @whentype option.
16863 11 SQL Web Assistant: URL specification is invalid.
16864 11 SQL Web Assistant: @blobfmt is invalid. The file must include the full path to the output_file location.
16865 11 SQL Web Assistant: URL hyperlink text column must not be of the image data type.
16866 11 SQL Web Assistant: Could not obtain the number of columns in @query.
16867 11 SQL Web Assistant: URL hyperlink text column is missing in @query.
16868 11 SQL Web Assistant failed on the call to SQLColAttribute. 16869 11 SQL Web Assistant: Columns of data type image cannot have a template.
16870 11 SQL Web Assistant: Internal error. Could not read @ parameters.
16871 11 SQL Web Assistant: Invalid @charset. Execute
sp_enumcodepages for a list of character sets.
16873 11 SQL Web Assistant: Invalid @codepage. Execute
sp_enumcodepages for a list of code pages.
16874 11 SQL Web Assistant: Internal error. Cannot translate to the specified code page.
16875 11 SQL Web Assistant: Translation to the desired code page is unavailable on this system.
16876 11 SQL Web Assistant: Internal error. Could not obtain COM interface ID.
16877 11 SQL Web Assistant: Internal error. Could not obtain COM language ID.
16878 11 SQL Web Assistant: Internal error. Could not initialize COM library.
16879 11 SQL Web Assistant: Internal error. Could not translate from Unicode to the specified code page.
16880 11 SQL Web Assistant: Internal error. Could not create translation object. Make sure that the file MLang.dll is in your system directory.
16881 16 SQL Web Assistant: This version is not supported on Win32s of Windows 3.1.
16882 16 SQL Web Assistant: Web task not found. Verify the name of the task for possible errors.
16883 16 SQL Web Assistant: Could not list Web task parameters. xp_readwebtask requires @procname.
16884 16 SQL Web Assistant: Procedure name is required to convert Web tasks.
16885 16 SQL Web Assistant: Could not upgrade the Web task to 7.0. The Web task will remain in 6.5 format and will need to be re-created. 16886 16 SQL Web Assistant: Could not update Web tasks system table. The Web task remains in 6.5 format.
16887 16 SQL Web Assistant: @procname parameter is missing. The parameter is required to upgrade a Web task to 7.0.
16888 16 SQL Web Assistant: Source code page is not supported on the system. Ensure @charset and @codepage language files are installed on your system.
16889 16 SQL Web Assistant: Could not send Web task row to the client.
16890 16 SQL Web Assistant: ODS error occurred. Could not send Web task parameters.
16901 16 %hs: This feature has not been implemented yet.
16902 16 %ls: The value of the parameter %ls is invalid.
16903 16 The “%ls” procedure was called with an incorrect number of parameters.
16904 16 sp_cursor: optype: You can only specify ABSOLUTE in conjunction with DELETE or UPDATE.
16905 16 The cursor is already open.
16906 17 Temporary storage used by the cursor to store large object variable values referred by the cursor query is not usable any more. 16907 16 %hs is not allowed in cursor statements.
16909 16 %ls: The cursor identifier value provided (%x) is not valid. 16910 16 The cursor %.*ls is currently used by another statement. 16911 16 %hs: The fetch type %hs cannot be used with forward only cursors.
16914 16 The “%ls” procedure was called with too many parameters. 16915 16 A cursor with the name ‘%.*ls’ already exists.
16916 16 A cursor with the name ‘%.*ls’ does not exist.
16917 16 Cursor is not open.
16922 16 Cursor Fetch: Implicit conversion from data type %s to %s is not allowed.
16924 16 Cursorfetch: The number of variables declared in the INTO list must match that of selected columns.
16925 16 The fetch type %hs cannot be used with dynamic cursors. 16926 16 sp_cursoroption: The column ID (%d) does not correspond to a text, ntext, or image column.
16927 16 Cannot fetch into text, ntext, and image variables. 16928 16 sp_cursor: Exec statement is not allowed as source for cursor insert.
16929 16 The cursor is READ ONLY.
16930 16 The requested row is not in the fetch buffer.
16931 16 There are no rows in the current fetch buffer.
16932 16 The cursor has a FOR UPDATE list and the requested column to be updated is not in this list.
16933 16 The cursor does not include the table being modified or the table is not updatable through the cursor.
16934 10 Optimistic concurrency check failed. The row was modified outside of this cursor.
16935 16 No parameter values were specified for the sp_cursor-%hs statement.
16936 16 sp_cursor: One or more values parameters were invalid. 16937 16 A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor.
16938 16 sp_cursoropen/sp_cursorprepare: The statement parameter can only be a batch or a stored procedure with a single select, without FOR BROWSE, COMPUTE BY, or variable assignments.
16941 16 Cursor updates are not allowed on tables opened with the NOLOCK option.
16942 16 Could not generate asynchronous keyset. The cursor has been deallocated.
16943 16 Could not complete cursor operation because the table schema changed after the cursor was declared.
16945 16 The cursor was not declared.
16946 16 Could not open the cursor because one or more of its tables have gone out of scope.
16947 16 No rows were updated or deleted.
16948 16 The variable ‘%.*ls’ is not a cursor variable, but it is used in a place where a cursor variable is expected.
16949 16 The variable ‘%.*ls’ is a cursor variable, but it is used in a place where a cursor variable is not valid.
16950 10 The variable ‘%.*ls’ does not currently have a cursor allocated to it.
16951 16 The variable ‘%.*ls’ cannot be used as a parameter because a CURSOR OUTPUT parameter must not have a cursor allocated to it before execution of the procedure.
16952 16 A cursor variable cannot be used as a parameter to a remote procedure call.
16953 10 Remote tables are not updatable. Updatable keyset-driven cursors on remote tables require a transaction with the REPEATABLE_READ or SERIALIZABLE isolation level spanning the cursor.
16954 16 Executing SQL directly; no cursor.
16955 16 Could not create an acceptable cursor.
16956 10 The created cursor is not of the requested type.
16957 16 FOR UPDATE cannot be specified on a READ ONLY cursor. 16958 16 Could not complete cursor operation because the set options have changed since the cursor was declared.
16959 16 Unique table computation failed.
16960 16 You have reached the maximum number of cursors allowed. 16961 10 One or more FOR UPDATE columns have been adjusted to the first instance of their table in the query.
16962 16 The target object type is not updatable through a cursor. 16963 16 You cannot specify scroll locking on a cursor that contains a remote table.
16964 16 For the optimistic cursor, timestamp columns are required if the update or delete targets are remote.
16965 16 Cursor scroll locks were invalidated due to a transaction defect. Reissue the UPDATE or DELETE statement after a cursor fetch. 16966 16 %ls: Specified concurrency control option %d (%ls) is incompatible with static or fast forward only cursors. Only read-only is compatible with static or fast forward only cursors.
16992 16 The cursor operation is required to wait for cursor asynchronous population to complete. However, at this point the transaction cannot be yielded to let the asynchronous population to continue. 16996 16 %ls cannot take output parameters.
16998 16 The asynchronous cursor worktable population thread spawn failed.
16999 20 Internal Cursor Error: The cursor is in an invalid state. 17000 10 Usage: sp_autostats [, {ON|OFF} [,
] ]
17001 16 Failure to send an event notification instance of type ‘%s’ on conversation handle ‘%s’. Error Code = ‘%s’.
17002 16 Failed to post QUEUE_ACTIVATION event. Error code: ’0x%s’. 17003 16 Closed event notification conversation endpoint with handle ‘%s’, due to the following error: ‘%.*ls’.
17004 16 Event notification conversation on dialog handle ‘%s’ closed without an error.
17005 16 Event notification ‘%ls’ in database ‘%ls’ dropped due to send time service broker errors. Check to ensure the conversation handle, service broker contract, and service specified in the event notification are active.
17049 16 Unable to cycle error log file from ‘%ls’ to ‘%ls’ due to OS error ‘%s’. A process outside of SQL Server may be preventing SQL Server from reading the files. As a result, errorlog entries may be lost and it may not be possible to view some SQL Server errorlogs. Make sure no other processes have locked the file with write-only access.”
17051 16 SQL Server evaluation period has expired.
17053 16 %ls: Operating system error %ls encountered.
17054 16 The current event was not reported to the Windows Events log. Operating system error = %s. You may need to clear the Windows Events log if it is full.
17056 10 The evaluation period for your edition of SQL Server expires in %d day(s).
17057 16 Security context for operating system objects could not be created. SQL Server cannot be started. Look for corresponding entries in the event viewer to help diagnose the root cause.
17058 16 initerrlog: Could not open error log file ‘%s’. Operating system error = %s.
17060 10 %s
17061 10 Error: %d Severity: %d State: %d %s
17063 16 Error: %d Severity: %d State: %d %s
17065 16 SQL Server Assertion: File: <%s>, line = %d Failed Assertion = ‘%s’ %s. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
17066 16 SQL Server Assertion: File: <%s>, line=%d Failed Assertion = ‘%s’. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
17067 16 SQL Server Assertion: File: <%s>, line = %d %s. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. 17068 10 PrintStack Request
17069 10 %s
17070 16 Clustered instances are not supported on this edition of SQL Server.
17101 10 (c) 2005 Microsoft Corporation.
17102 16 Failed to initialize Distributed COM (CoInitializeEx returned %lx). Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel.
17103 10 All rights reserved.
17104 10 Server process ID is %ld.
17105 10 Could not open master database in system task thread context. Terminating server.
17106 10 Common Criteria compliance mode is enabled. This is an informational message only; no user action is required.
17108 10 Password policy update was successful.
17109 10 FallBack certificate was successfully created.
17110 10 Registry startup parameters:
17111 10 Logging SQL Server messages in file ‘%s’.
17112 16 An invalid startup option %c was supplied, either from the registry or the command prompt. Correct or remove the option. 17113 16 Error %ls occurred while opening file ‘%ls’ to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
17114 16 Error %ls occurred while opening file ‘%ls’ to obtain configuration information at startup time. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
17115 10 Command Line Startup Parameters:
17116 16 Failed to initialize distributed COM; DCOM is not installed. Heterogeneous queries and remote procedure calls are disabled. Check the DCOM configuration using Component Services in Control Panel. 17119 10 The number of concurrent user connections was reduced to %ld, because it exceeded the allowable limit for this edition of SQL Server. To avoid this message in the future, use sp_configure to permanently adjust the number of user connections within the licensed limit.
17120 16 SQL Server could not spawn %s thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
17121 10 SQL Server is started with trace flag %d, this may cause user to see some error messages masked using ‘%ls’.
17124 10 SQL Server has been configured for lightweight pooling. This is an informational message; no user action is required.
17125 10 Using dynamic lock allocation. Initial allocation of %I64u Lock blocks and %I64u Lock Owner blocks per node. This is an informational message only. No user action is required.
17126 10 SQL Server is now ready for client connections. This is an informational message; no user action is required.
17127 16 initdata: No memory for kernel buffer hash table.
17128 16 initdata: No memory for kernel buffers.
17129 10 initconfig: Warning: affinity mask specified is not valid. Defaulting to no affinity. Use sp_configure ‘affinity mask’ or ‘affinity64 mask’ to configure the system to be compatible with the CPU mask on the system. You can also configure the system based on the number of licensed CPUs.
17130 16 Not enough memory for the configured number of locks. Attempting to start with a smaller lock hash table, which may impact performance. Contact the database administrator to configure more memory for this instance of the Database Engine.
17131 16 Server startup failed due to insufficient memory for descriptor hash tables. Reduce non-essential memory load or increase system memory.
17132 16 Server startup failed due to insufficient memory for descriptor. Reduce non-essential memory load or increase system memory. 17133 16 Launch of startup procedure ‘%s’ failed.
17135 10 Launched startup procedure ‘%s’.
17136 10 Clearing tempdb database.
17137 10 Starting up database ‘%s’.
17138 16 Unable to allocate enough memory to start ‘%ls’. Reduce non-essential memory load or increase system memory.
17140 16 Could not dispatch SQL Server by Service Control Manager. Operating system error = %s.
17141 16 Could not register Service Control Handler. Operating system error = %s.
17142 16 SQL Server service has been paused. No new connections will be allowed. To resume the service, use SQL Computer Manager or the Services application in Control Panel.
17143 16 %s: Could not set Service Control Status. Operating system error = %s.
17144 10 SQL Server is not allowing new connections because the Service Control Manager requested a pause. To resume the service, use SQL Computer Manager or the Services application in Control Panel. 17145 10 Service Control Handler received an invalid control code = %d.
17146 10 SQL Server is allowing new connections in response to ‘continue’ request from Service Control Manager. This is an informational message only. No user action is required.
17147 10 SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required. 17148 10 SQL Server is terminating in response to a ‘stop’ request from Service Control Manager. This is an informational message only. No user action is required.
17149 10 Using the static lock allocation specified in the locks configuration option. Allocated %I64u Lock blocks and %I64u Lock Owner blocks per node. This is an informational message only. No user action is required.
17150 10 Lock partitioning is enabled. This is an informational message only. No user action is required.
17152 10 Multinode configuration: node %ld: CPU mask: 0x%0*I64x Active CPU mask: 0x%0*I64x. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
17153 10 Processor affinity turned on: processor mask 0x%0*I64x. Threads will execute on CPUs per affinity mask/affinity64 mask config option. This is an informational message; no user action is required. 17155 10 I/O affinity turned on, processor mask 0x%0*I64x. Disk I/Os will execute on CPUs per affinity I/O mask/affinity64 mask config option. This is an informational message only; no user action is required. 17156 16 initeventlog: Could not initiate the EventLog Service for the key ‘%s’.
17158 10 The server resumed execution after being idle %d seconds. This is an informational message only. No user action is required. 17159 10 The server is idle. This is an informational message only. No user action is required.
17161 10 SQL Server could not use the NO_BUFFERING option during I/O, because the master file sector size, %d, is incorrect. Move the master file to a drive with a correct sector size.
17162 10 SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
17163 10 SQL Server is starting at high priority base (=13). This is an informational message only. No user action is required.
17164 10 Detected %d CPUs. This is an informational message; no user action is required.
17166 10 Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
17167 10 Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action is required.
17169 10 Unable to locate kernel HTTP driver Httpapi.dll in path. SQL Server native HTTP support is not available. Error: 0x%lx Your operating system may not support the kernel HTTP driver.
17170 10 SQL Server native HTTP support is not available. Could not find function entry point ‘%hs’ in %hs. Error 0x%lx. Native HTTP access to SQL Server requires a later version of the operating system. 17171 10 SQL Server native HTTP support failed and will not be available. ‘%hs()’ failed. Error 0x%lx.
17172 16 SNIInitialize() failed with error 0x%lx.
17174 10 Unable to initialize SQL Server native HTTP support due to insufficient resources. HTTP access to SQL Server will not be available. Error 0x%lx. This error typically indicates insufficient memory. Reduce non-essential memory load or increase system memory.
17175 10 The registry settings for SNI protocol configuration are incorrect. The server cannot accept connection requests. Error: 0x%lx. Status: 0x%lx.
17176 10 This instance of SQL Server last reported using a process ID of %s at %s (local) %s (UTC). This is an informational message only; no user action is required.
17177 10 This instance of SQL Server has been using a process ID of %s since %s (local) %s (UTC). This is an informational message only; no user action is required.
17178 10 Address Windowing Extensions is enabled. This is an informational message only; no user action is required.
17179 10 Could not use Address Windowing Extensions because the ‘lock pages in memory’ privilege was not granted.
17180 10 Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.
17181 16 SNIInitializeListener() failed with error 0x%lx.
17182 16 TDSSNIClient initialization failed with error 0x%lx, status code 0x%lx.
17183 10 Attempting to cycle error log. This is an informational message only; no user action is required.
17184 10 The error log has been reinitialized. See the previous log for older entries.
17185 16 Unable to update password policy.
17186 16 Failed to enqueue %s task. There may be insufficient memory. 17187 16 SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again. %.*ls
17188 16 SQL Server cannot accept new connections, because it is shutting down. The connection has been closed.%.*ls
17189 16 SQL Server failed with error code 0x%x to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems.%.*ls 17190 16 FallBack certificate initialization failed with error code: %d.
17191 16 Cannot accept a new connection because the session has been terminated. This error occurs when a new batch execution is attempted on a session that is logging out, or when a severe error is encountered upon connection. Check the error log to see if this session was terminated by a KILL command or because of severe errors.%.*ls
17192 10 Dedicated admin connection support was not started because of error 0x%lx, status code: 0x%lx. This error typically indicates a socket-based error, such as a port already in use.
17193 10 SQL Server native SOAP support is ready for client
connections. This is an informational message only. No user action is required.
17194 16 The Server was unable to load the SSL provider needed to login. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configured the server. See Books Online for information on this error message: 0x%lx.%.*ls 17195 16 The server was unable to complete its initialization sequence because the available network libraries do not support the required level of encryption. The server process has stopped. Before restarting the server, verify that SSL certificates have been installed. See Books Online topic “Configuring Client Protocols and Network Libraries”.
17196 16 Preparing for eventual growth to %d GB with Hot Add Memory. 17197 16 Login failed due to timeout; the connection has been closed. This error may indicate heavy server load. Reduce the load on the server and retry login.%.*ls
17198 16 Connection failed because the endpoint could not be found. This may result if an endpoint is dropped while a connection attempt is in progress. Attempt to connect to a different endpoint on the server.%.*ls 17199 10 Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
17200 16 Changing the remote access settings for the Dedicated Admin Connection failed with error 0x%lx, status code 0x%lx.
17201 10 Dedicated admin connection support was established for listening locally on port %d.
17202 10 Dedicated admin connection support was established for listening remotely on port %d.
17203 16 SQL Server cannot start on this machine. The processor(s) (CPU) model does not support all instructions needed for SQL Server to run. Refer to the System Requirements section in BOL for further information. 17204 16 %ls: Could not open file %ls for file number %d. OS error: %ls.
17207 16 %ls: Operating system error %ls occurred while creating or opening file ‘%ls’. Diagnose and correct the operating system error, and retry the operation.
17208 16 %s: File ‘%s’ has an incorrect size. It is listed as %d MB, but should be %d MB. Diagnose and correct disk failures, and restore the database from backup.
17253 10 SQL Server cannot use the NO_BUFFERING option during I/O on this file, because the sector size for file ‘%s’, %d, is invalid. Move the file to a disk with a valid sector size.
17300 16 SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure to check the maximum number of sessions allowed. Use sys.sessions to check the current number of sessions, including user processes.
17303 16 The session with SPID %d was found to be invalid during termination, possibly because of corruption in the session structure. Contact Product Support Services.
17308 16 %s: Process %d generated an access violation. SQL Server is terminating this process.
17310 20 A user request from the session with SPID %d generated a fatal exception. SQL Server is terminating this session. Contact Product Support Services with the dump produced in the log directory. 17311 16 SQL Server is terminating because of fatal exception %lx. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).
17312 16 SQL Server is terminating a system or background task %s due to errors in starting up the task (setup state %d).
17313 10 Unable to locate driver ntdll.dll in path. SQL Server native HTTP support is not available. Error: 0x%lx Your operating system may not support this driver.
17401 10 Server resumed execution after being idle %d seconds: user activity awakened the server. This is an informational message only. No user action is required.
17403 10 Server resumed execution after being idle %d seconds. Reason: timer event.
17404 10 The server resumed execution after being idle for %d seconds.
17405 24 An image corruption/hotpatch detected while reporting exceptional situation. This may be a sign of a hardware problem. Check SQLDUMPER_ERRORLOG.log for details.
17406 10 Server resumed execution after being idle %d seconds. Reason: resource pressure.
17550 10 DBCC TRACEON %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
17551 10 DBCC TRACEOFF %d, server process ID (SPID) %d. This is an informational message only; no user action is required.
17557 16 DBCC DBRECOVER failed for database ID %d. Restore the database from a backup.
17558 10 Bypassing recovery for database ID %d. This is an
informational message only. No user action is required.
17560 10 DBCC DBREPAIR: ‘%ls’ index restored for ‘%ls.%ls’.
17561 10 %ls index restored for %ls.%ls.
17572 16 DBCC cannot free DLL ‘%ls’. SQL Server requires this DLL in order to function properly.
17573 10 CHECKDB for database ‘%ls’ finished without errors on %ls (local time). This is an informational message only; no user action is required.
17656 10 Warning ******************
17657 10 Attempting to change default collation to %s.
17658 10 SQL Server started in single-user mode. This an
informational message only. No user action is required.
17659 10 Warning: System table ID %d has been updated directly in database ID %d and cache coherence may not have been maintained. SQL Server should be restarted.
17660 10 Starting without recovery. This is an informational message only. No user action is required.
17661 10 Recovering all databases, but not clearing tempdb. This is an informational message only. No user action is required.
17663 10 Server name is ‘%s’. This is an informational message only. No user action is required.
17664 10 The NETBIOS name of the local node that is running the server is ‘%ls’. This is an informational message only. No user action is required.
17674 10 Login: %.*ls %.*ls, server process ID (SPID): %d, kernel process ID (KPID): %d.
17676 10 SQL Server shutdown due to Ctrl-C or Ctrl-Break signal. This is an informational message only. No user action is required. 17681 10 Loading default collation %s for this instance of SQL Server.
17750 16 Could not load the DLL %ls, or one of the DLLs it
references. Reason: %ls.
17751 16 Could not find the function %ls in the library %ls. Reason: %ls.
17752 16 SQL Server has insufficient memory to run the extended stored procedure ‘%ls’. Release server memory resources by closing connections or ending transactions.
17753 16 %.*ls can only be executed in the master database.
17802 20 The Tabular Data Stream (TDS) version 0x%x of the client library used to open the connection is unsupported or unknown. The connection has been closed. %.*ls
17803 20 There was a memory allocation failure during connection establishment. Reduce nonessential memory load, or increase system memory. The connection has been closed.%.*ls
17805 20 The value in the usertype field of the login record is invalid. The value 0×01, which was used by Sybase clients, is no longer supported by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server.%.*ls
17806 20 SSPI handshake failed with error code 0x%x while
establishing a connection with integrated security; the connection has been closed.%.*ls
17807 20 Event ‘%ld’, which was received from the client, is not recognized by SQL Server. Contact the vendor of the client library that is being used to connect to SQL Server, and have the vendor fix the event number in the tabular data stream that is sent.
17809 20 Could not connect because the maximum number of ‘%ld’ user connections has already been reached. The system administrator can use sp_configure to increase the maximum value. The connection has been closed.%.*ls
17810 20 Could not connect because the maximum number of ‘%ld’ dedicated administrator connections already exists. Before a new connection can be made, the existing dedicated administrator connection must be dropped, either by logging off or ending the process.%.*ls
17812 10 Dedicated administrator connection has been disconnected. This is an informational message only. No user action is required. 17813 20 The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.%.*ls 17825 18 Could not close network endpoint, or could not shut down network library. The cause is an internal error in a network library. Review the error log: the entry listed after this error contains the error code from the network library.
17826 18 Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
17827 20 There was a failure while attempting to encrypt a password. The connection has been closed.%.*ls
17828 20 The prelogin packet used to open the connection is
structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
17829 20 A network error occurred while establishing a connection; the connection has been closed.%.*ls
17830 20 Network error code 0x%x occurred while establishing a connection; the connection has been closed. This may have been caused by client or server login timeout expiration. Time spent during login: total %d ms, enqueued %d ms, network writes %d ms, network reads %d ms, establishing SSL %d ms, negotiating SSPI %d ms, validating login %d ms.%.*ls 17832 20 The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.%.*ls
17835 20 Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library.%.*ls
17836 20 Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library.%.*ls
17881 16 ‘%ls’ is an unsupported Open Data Services API.
17883 10 Process %ld:%ld:%ld (0x%lx) Worker 0x%p appears to be non-yielding on Scheduler %ld. Thread creation time: %I64d. Approx Thread CPU Used: kernel %I64d ms, user %I64d ms. Process Utilization %d%%. System Idle %d%%. Interval: %I64d ms.
17884 10 New queries assigned to process on Node %d have not been picked up by a worker thread in the last %d seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the “max worker threads” configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: %d%%. System Idle: %d%%.
17885 16 An unexpected query string was passed to a Web Service Description Language (WSDL) generation procedure.
17886 20 The server will drop the connection, because the client driver has sent multiple requests while the session is in single-user mode. This error occurs when a client sends a request to reset the connection while there are batches still running in the session, or when the client sends a request while the session is resetting a connection. Please contact the client driver vendor.
17887 10 IO Completion Listener (0x%lx) Worker 0x%p appears to be non-yielding on Node %ld. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.
17888 10 All schedulers on Node %d appear deadlocked due to a large number of worker threads waiting on %ls. Process Utilization %d%%. 17889 16 A new connection was rejected because the maximum number of connections on session ID %d has been reached. Close an existing connection on this session and retry.%.*ls
17890 10 A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: %d seconds. Working set (KB): %I64d, committed (KB): %I64d, memory utilization: %d%%.
17891 10 Resource Monitor (0x%lx) Worker 0x%p appears to be
non-yielding on Node %ld. Memory freed: %I64d KB. Approx CPU Used: kernel %I64d ms, user %I64d ms, Interval: %I64d.
17892 20 Logon failed for login ‘%.*ls’ due to trigger
execution.%.*ls
17893 20 Failed to get client host address while preparing to execute LOGON triggers.
17894 10 CPU time stamp frequency has changed from %I64d to %I64d ticks per millisecond. No action has been taken.
17895 10 CPU time stamp frequency has changed from %I64d to %I64d ticks per millisecond. The new frequency will be used.
17896 10 The time stamp counter of CPU on scheduler id %d is not synchronized with other CPUs.
18002 20 Exception happened when running extended stored procedure ‘%.*ls’ in the library ‘%.*ls’. SQL Server is terminating process %d. Exception type: %ls; Exception code: 0x%lx.
18052 16 Error: %d, Severity: %d, State: %d.
18053 16 Error: %d, Severity: %d, State: %d. (Params:%ls). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
18054 16 Error %d, severity %d, state %d was raised, but no message with that error number was found in sys.messages. If error is larger than 50000, make sure the user-defined message is added using sp_addmessage. 18055 20 Exception %d, %d occurred when the server tried to reset connection %d. Because the server cannot recover from the failure to reset the connection, the connection has been dropped. Please contact Microsoft technical support.
18056 20 The client was unable to reuse a session with SPID %d, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.

18057 16 Error: Failed to set up execution context.
18058 17 Failed to load format string for error %d, language id %d. Operating system error: %s. Check that sqlevn70.rll is installed in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\Resources\1033, where 1033 is the language ID of US English, or the appropriate folder for the locale in use. Also check memory usage.
18059 16 The connection has been dropped because the principal that opened it subsequently assumed a new security context, and then tried to reset the connection under its impersonated security context. This scenario is not supported. See “Impersonation Overview” in Books Online. 18060 16 Failed to format string for error %d, language id %d. This may be caused by low memory in server, or error happening while formatting the message.
18061 20 The client was unable to join a session with SPID %d. This error may have been caused by an earlier operation failing or a change in permissions since the session was established. Check the error logs for failed operations immediately before this error message.
18100 10 Process ID %d was killed by hostname %.*ls, host process ID %d.
18113 10 SQL Server shutdown after verifying system indexes. 18124 10 The default collation was successfully changed.
18204 16 %s: Backup device ‘%s’ failed to %s. Operating system error %s.
18210 16 %s: %s failure on backup device ‘%s’. Operating system error %s.
18225 10 Tape ‘%s’ (family ID %d, sequence %d, media_set_guid %s) is mounted on tape drive ‘%s’. This is an informational message only. No user action required
18226 10 Tape mount is being requested on drive ‘%s’. Expected volume has (Family ID %d, sequence %d).
18227 10 Unnamed tape (family ID %d, sequence %d, media_set_guid %s) is mounted on tape drive ‘%s’. This is an informational message only. No user action required.
18228 10 Tape mount request on drive ‘%s’ is cancelled. This is an informational message only. No user action is required.
18257 10 %s: Device or media does not support %s. To access this feature, use a different device or media.
18264 10 Database backed up. Database: %s, creation date(time): %s(%s), pages dumped: %d, first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
18265 10 Log was backed up. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
18266 10 Database file was backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %d, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
18267 10 Database was restored: Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). Informational message. No user action required. 18268 10 Log was restored. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required. 18269 10 Database file was restored. Database: %s, creation
date(time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.
18270 10 Database differential changes were backed up. Database: %s, creation date(time): %s(%s), pages dumped: %d, first LSN: %s, last LSN: %s, full backup LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required. 18271 10 Database changes were restored. Database: %s, creation date(time): %s(%s), first LSN: %s, last LSN: %s, number of dump devices: %d, device information: (%s). This is an informational message. No user action is required.
18272 16 During restore restart, an I/O error occurred on checkpoint file ‘%s’ (operating system error %s). The statement is proceeding but cannot be restarted. Ensure that a valid storage location exists for the checkpoint file.
18273 16 Could not clear ‘%s’ bitmap in database ‘%s’ because of error %d. As a result, the differential or bulk-logged bitmap overstates the amount of change that will occur with the next differential or log backup. This discrepancy might slow down later differential or log backup operations and cause the backup sets to be larger than necessary. Typically, the cause of this error is insufficient resources. Investigate the failure and resolve the cause. If the error occurred on a data backup, consider taking a data backup to create a new base for future differential backups. 18274 10 Tape ‘%s’ was dismounted from drive ‘%s’. This is an informational message. No user action is required.
18275 10 Unnamed tape was dismounted from drive ‘%s’. This is an informational message. No user action is required.
18276 10 Database file differential changes were backed up. Database: %s, creation date(time): %s(%s), file list: (%s), pages dumped: %d, number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
18277 10 Database file changes were restored. Database: %s, creation date(time): %s(%s), file list: (%s), number of dump devices: %d, device information: (%s). This is an informational message only. No user action is required.
18400 16 The background checkpoint thread has encountered an unrecoverable error. The checkpoint process is terminating so that the thread can clean up its resources. This is an informational message only. No user action is required.
18450 14 Login failed for login “%.*ls”. The login is not defined as a valid login of a trusted SQL Server connection.%.*ls
18451 14 Login failed for user ‘%.*ls’. Only administrators may connect at this time.%.*ls
18452 14 Login failed for user ‘%.*ls’. The user is not associated with a trusted SQL Server connection.%.*ls
18453 10 Login succeeded for user ‘%.*ls’. Connection: trusted.%.*ls 18454 10 Login succeeded for user ‘%.*ls’. Connection:
non-trusted.%.*ls
18455 10 Login succeeded for user ‘%.*ls’.%.*ls
18456 14 Login failed for user ‘%.*ls’.%.*ls
18457 14 Login failed for user ‘%.*ls’. The user name contains a mapping character or is longer than 30 characters.%.*ls
18458 14 Login failed. The number of simultaneous users already equals the %d registered licenses for this server. To increase the maximum number of simultaneous users, obtain additional licenses and then register them through the Licensing item in Control Panel.%.*ls
18459 14 Login failed. The workstation licensing limit for SQL Server access has already been reached.%.*ls
18460 14 Login failed. The number of simultaneous users has already reached the limit of %d licenses for this ‘%ls’ server. Additional licenses should be obtained and installed or you should upgrade to a full version.%.*ls
18461 14 Login failed for user ‘%.*ls’. Reason: Server is in single user mode. Only one administrator can connect at this time.%.*ls 18462 14 The login failed for user “%.*ls”. The password change failed. The password for the user is too recent to change. %.*ls 18463 14 The login failed for user “%.*ls”. The password change failed. The password cannot be used at this time. %.*ls
18464 14 Login failed for user ‘%.*ls’. Reason: Password change failed. The password does not meet Windows policy requirements because it is too short.%.*ls
18465 14 Login failed for user ‘%.*ls’. Reason: Password change failed. The password does not meet Windows policy requirements because it is too long.%.*ls
18466 14 Login failed for user ‘%.*ls’. Reason: Password change failed. The password does not meet Windows policy requirements because it is not complex enough.%.*ls
18467 14 The login failed for user “%.*ls”. The password change failed. The password does not meet the requirements of the password filter DLL. %.*ls
18468 14 The login failed for user “%.*ls”. The password change failed. An unexpected error occurred during password validation. %.*ls 18469 10 [CLIENT: %.*hs]
18470 14 Login failed for user ‘%.*ls’. Reason: The account is disabled.%.*ls
18471 14 The login failed for user “%.*ls”. The password change failed. The user does not have permission to change the password. %.*ls 18482 16 Could not connect to server ‘%.*ls’ because ‘%.*ls’ is not defined as a remote server. Verify that you have specified the correct server name. %.*ls.
18483 16 Could not connect to server ‘%.*ls’ because ‘%.*ls’ is not defined as a remote login at the server. Verify that you have specified the correct login name. %.*ls.
18485 16 Could not connect to server ‘%.*ls’ because it is not configured to accept remote logins. Use the remote access configuration option to allow remote logins.%.*ls
18486 14 Login failed for user ‘%.*ls’ because the account is currently locked out. The system administrator can unlock it. %.*ls 18487 14 Login failed for SQL Server login ‘%.*ls’. The password for this login has expired.%.*ls
18488 14 Login failed for user ‘%.*ls’. Reason: The password of the account must be changed.%.*ls
18489 10 The dedicated administrator connection is in use by “%.*ls” on “%.*ls”.%.*ls
18491 16 SQL Server could not start because of an invalid serial number. The serial number information retrieved at startup appears invalid. To proceed, reinstall SQL Server.
18492 16 SQL Server cannot start because the license agreement for this ‘%ls’ version of SQL Server is invalid. The server is exiting. To proceed, reinstall SQL Server with a valid license.
18493 16 The user instance login flag is not supported on this version of SQL Server. The connection will be closed.%.*ls
18494 16 The user instance login flag is not allowed when connecting to a user instance of SQL Server. The connection will be closed.%.*ls 18495 16 The user instance login flag cannot be used along with an attach database file name. The connection will be closed.%.*ls 18750 16 %ls: The parameter ‘%ls’ is not valid.
18751 16 %ls procedure was called with the wrong number of
parameters.
18752 16 Only one Log Reader Agent or log-related procedure
(sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you executed a log-related procedure, drop the connection over which the procedure was executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure.
18755 16 Could not allocate memory for replication. Verify that SQL Server has sufficient memory for all operations.
18756 16 Could not retrieve replication information for table %d. Verify that the table has a primary key, and then rerun the Log Reader Agent.
18757 16 Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication. 18760 16 Invalid %ls statement for article %d. Verify that the stored procedures that propagate changes to Subscribers use the appropriate call syntax, and then rerun the Log Reader Agent. Use sp_helparticle and sp_changearticle to view and change the call syntax.
18761 16 Commit record at {%08lx:%08lx:%04lx} has already been distributed.
18762 16 Invalid begin LSN {%08lx:%08lx:%04lx} for commit record {%08lx:%08lx:%04lx}. Check DBTABLE.
18763 16 Commit record {%08lx:%08lx:%04lx} reports oldest active LSN as (0:0:0).
18764 16 Execution of filter stored procedure %d failed. See the SQL Server errorlog for more information.
18765 16 The “%s” log sequence number (LSN) that was specified for the replication log scan is invalid.
18766 16 The replbeginlsn field in the DBTABLE is invalid.
18767 16 The specified begin LSN {%08lx:%08lx:%04lx} for replication log scan occurs before replbeginlsn {%08lx:%08lx:%04lx}.
18768 16 The specified LSN {%08lx:%08lx:%04lx} for repldone log scan occurs before the current start of replication in the log
{%08lx:%08lx:%04lx}.
18769 16 The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not a replicated commit record.
18770 16 The specified LSN {%08lx:%08lx:%04lx} for repldone log scan is not present in the transaction log.
18771 16 Invalid storage type %d specified writing variant of type %d.
18772 16 Invalid server data type (%d) specified in repl type lookup. 18773 16 Could not locate text information records for the column “%.*ls”, ID %d during command construction.
18774 16 The stored procedure %s must be executed within a
transaction.
18775 16 The Log Reader Agent encountered an unexpected log record of type %u encountered while processing DML operation.
18776 16 An error occurred while waiting on the article cache access event.
18777 16 %s: Error initializing MSMQ components
18778 16 %s: Error opening Microsoft Message Queue %s
18780 16 You have specified a value for the @dts_package_password parameter. You must also specify a value for the @dts_package_name parameter.
18781 16 The value specified for the @backupdevicetype parameter is not valid. The value must be ‘logical’, ‘disk’, or ‘tape’.
18782 16 Could not locate backup header information for database ‘%s’ in the specified backup device. Specify a backup device that contains a backup of the Publisher database.
18783 16 The subscription setup script path has been truncated, because the snapshot folder directory path is too long. Reconfigure the Distributor to use a shorter path for this Publisher, and then retry the operation.
18784 16 The alternate snapshot folder path generated by replication has been truncated. Reconfigure the publication to use a shorter alternate snapshot folder path, and then retry the operation.
18786 16 The specified publication does not allow subscriptions to be initialized from a backup. To allow initialization from a backup, use sp_changepublication: set ‘allow_initialize_from_backup’ to ‘true’. 18787 16 Snapshot publications cannot use the option to initialize a subscription from a backup. This option is only supported for transactional publications.
18790 16 Cannot enable the option to initialize a subscription from a backup. This is not supported for non-SQL Server Publishers; it is only supported for transactional publications from SQL Server Publishers. 18795 16 The valid new types of a log based indexed view article are ‘indexed view logbased’, ‘indexed view logbased manualfilter’, ‘indexed view logbased manualview’, and ‘indexed view logbased manualboth’ only. 18796 16 The valid new types of a log based table article are ‘logbased’, ‘logbased manualfilter’, ‘logbased manualview’, and ‘logbased manualboth’ only.
18799 16 Only users who are members of the following roles can perform this operation: sysadmin fixed server role; dbowner or dbcreator fixed database role in the current database.
18801 16 Unable to allocate memory for replication schema version node.
18802 16 Cannot insert a new schema change into the systranschemas system table. HRESULT = ’0x%x’. If the problem persists, contact Customer Support Services.
18803 16 The topic %.*ls is not a supported help topic. To see the list of supported topics, execute the stored procedure sp_replhelp N’helptopics’.
18804 16 Peer-to-peer replication has been enabled, and the Log Reader Agent was unable to find an Extended-Originator-Record (EOR) for a transaction that did not originate at this server. Contact Customer Support Services.
18805 16 The Log Reader Agent failed to construct a replicated command from log sequence number (LSN) {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services.
18806 16 Cannot initialize the replication resource. Ensure that SQL Server has sufficient memory. If the problem persists, restart SQL Server. 18807 16 Cannot find an object ID for the replication system table ‘%s’. Verify that the system table exists and is accessible by querying it directly. If it does exist, stop and restart the Log Reader Agent; if it does not exist, drop and reconfigure replication.
18808 16 Article information is not valid. Stop the Log Reader Agent, execute the stored procedure sp_replflush, and then restart the Log Reader Agent.
18809 16 END_UPDATE log record {%08lx:%08lx:%04lx} encountered without matching BEGIN_UPDATE.
18810 16 Cannot restart the scan on table ‘%s’. HRESULT = ’0x%x’. Stop and restart the Log Reader Agent. If the problem persists, contact Customer Support Services.
18811 16 Invalid %s log record.
18812 16 Can not lock the database object in article cache.
18815 16 Expecting %I64d bytes of data, but only %I64d were found in the transaction log. For more information, contact Customer Support Services.
18817 16 Text information block not valid. Contact Customer Support Services.
18818 16 Failed to scan to log sequence number (LSN)
{%08lx:%08lx:%04lx}. Contact Customer Support Services.
18819 16 Failed to lock the current log record at log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services. 18821 16 The rowset does not contain any column with offset %d. Back up the publication database and contact Customer Support Services. 18823 16 Invalid value %d for %s.
18826 16 Failed to delete rows from the systranschemas table. HRESULT = ’0x%x’. The rows will be deleted the next time replication executes the stored procedure sp_replcmds.
18827 16 The Log Reader Agent scanned to the end of the log before processing all transactions in the hash table. %d transactions in the hash table, %d transactions processed, end of log LSN {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services. 18828 16 Invalid filter procedure definition.
18829 16 Failed to scan to the delete log record of an update base on log sequence number (LSN) {%08lx:%08lx:%04lx}. Contact Customer Support Services.
18830 16 A bounded update was logged within the range of another bounded update within the same transaction. First BEGIN_UPDATE {%08lx:%08lx:%04lx}, current BEGIN_UPDATE {%08lx:%08lx:%04lx}. Contact Customer Support Services.
18832 16 The Log Reader Agent scanned to the end of the log while processing a bounded update. BEGIN_UPDATE LSN {%08lx:%08lx:%04lx}, END_UPDATE LSN {%08lx:%08lx:%04lx}, current LSN {%08lx:%08lx:%04lx}. Back up the publication database and contact Customer Support Services. 18834 16 An unexpected Text Information Begin (TIB) log record was encountered while processing the TIB for offset %ld. Last TIB processed: (textInfoFlags 0x%x, coloffset %ld, newSize %I64d, oldSize %I64d). Contact Customer Support Services.
18835 16 Encountered an unexpected Text Information End (TIE) log record. Last Text Information Begin (TIB) processed: (textInfoFlags 0x%x, coloffset %ld, newSize %I64d, oldSize %I64d), text collection state %d. Contact product support.
18836 16 %s, ti: {RowsetId %I64d, {TextTimeStamp %I64d, {RowId {PageId %ld, FileId %u}, SlotId %d}}, coloffset %ld, textInfoFlags 0x%x, textSize %I64d, offset %I64d, oldSize %I64d, newSize %I64d}. 18837 16 Cannot find rowset ID %I64d in the current schema. Stop and restart the Log Reader Agent. If the problem persists, reinitialize all subscriptions to the publication.
18838 16 The Log Reader Agent encountered a NULL command that is not valid. Restart the agent if it has stopped. If the problem persists, reinitialize all subscriptions to the publication.
18840 16 Cannot locate database information in the article cache. Stop and restart SQL Server and the Log Reader Agent. If the problem persists, back up the publication database, and then contact Customer Support Services.
18842 16 Failed to retrieve the oldest active log sequence number (LSN) from a commit record. Stop and restart SQL Server and the Log Reader Agent. If the problem persists, reinitialize all subscriptions to the publication.
18843 16 Failed to allocate or reallocate buffer for replication command, old size %d, new size %d.
18844 16 Invalid compensation range: begin {%08lx:%08lx:%04lx}, end {%08lx:%08lx:%04lx}. Reinitialize all subscriptions to the publication. 18845 16 Cannot retrieve the rowset ID from log records generated from a text pointer based operation. Reinitialize all subscriptions to the publication.
18846 16 Possible inconsistent state in the distribution database: dist_backup_lsn {%08lx:%08lx:%04lx}, dist_last_lsn {%08lx:%08lx:%04lx}. Execute “sp_repldone NULL, NULL, 0, 0, 1″, and then execute sp_replflush. Reinitialize all subscriptions to the publication.
18847 16 Cannot retrieve the peer-to-peer database information. Contact Customer Support Services.
18849 16 Failed to evaluate the filter procedure or computed column. Cannot find the column offset information for column ID %d, rowsetId %I64d. Stop and restart the Log Reader Agent. If the problem persists, back up the publication database and then contact Customer Support Services. 18850 16 Encountered an unexpected %s log record. Last FileStreamInfo node processed: {%d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, %d, %ld, %I64d, %I64d, %I64d, %I64d, {%08lx:%08lx:%04lx}, %d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, {%08lx:%08lx:%04lx}}. If the problem persists, contact Customer Support Services.
18851 16 Failed to %s the replication context for TxF: {%d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, %d, %ld, %I64d, %I64d, %I64d, %I64d, {%08lx:%08lx:%04lx}, %d, {{%I64d, %I64d}, %I64d, %I64d, %d, %d}, {%08lx:%08lx:%04lx}}. If the problem persists, contact product support. 18852 16 Failed to read the TXF_REPLICATION_RECORD_WRITE structure. Last error returned ‘%ld’. If the problem persists, contact Customer Support Services.
18853 10 Replication is skipping schema version logging because the systranschemas table is not present in database ‘%d’. This is an informational message only. No user action is required.
18854 16 One or more subscriptions have been marked inactive. Drop and re-create all subscriptions for this node that are failing with this error.
18855 11 Can not rename the database name because it is published or it is a distribution database used by replication.
18856 16 Agent ‘%s’ is retrying after an error. %d retries attempted. See agent job history in the Jobs folder for more details.
18857 16 The subscription to this publication is not active yet. No user action is required.
19030 10 SQL Trace ID %d was started by login “%s”.
19031 10 SQL Trace stopped. Trace ID = ‘%d’. Login Name = ‘%s’. 19032 10 SQL Trace was stopped due to server shutdown. Trace ID = ‘%d’. This is an informational message only; no user action is required. 19033 10 Server started with ‘-f’ option. Auditing will not be started. This is an informational message only; no user action is required. 19034 21 Cannot start C2 audit trace. SQL Server is shutting down. Error = %ls
19035 16 OLE task allocator failed to initialize. Heterogeneous queries, distributed queries, and remote procedure calls are unavailable. Confirm that DCOM is properly installed and configured.
19036 10 The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the OLEDB provider.
19051 16 Unknown error occurred in the trace.
19052 16 The active trace must be stopped before modification. 19053 16 The trace event ID is not valid.
19054 16 The trace column ID is not valid.
19055 16 Filters with the same event column ID must be grouped together.
19056 16 The comparison operator in the filter is not valid. 19057 16 The boolean operator in the filter is not valid.
19058 16 The trace status is not valid.
19059 16 Could not find the requested trace.
19060 16 The trace option is not valid.
19061 16 Cannot remove SPID trace column.
19062 16 Could not create a trace file.
19063 16 Not enough memory was available for trace.
19064 16 The requested trace stop time has been already passed. 19065 16 The parameter is not valid.
19066 16 Cannot modify a restricted trace.
19067 16 Cannot create a new trace because the trace file path is found in the existing traces.
19068 16 The trace file path is not valid or not supported.
19069 16 The trace file name is not valid because it contains a rollover file number (NNN in C:\file_NNN) while the trace rollover option is enabled.
19070 16 The default trace cannot be stopped or modified. Use SP_CONFIGURE to turn it off.
19071 16 Stopping the trace because the current trace file is full and the rollover option is not specified.
19096 16 Fail to delete an old trace file ‘%ls’. Error = ‘%ls’. 19097 10 Windows error occurred while running %s. Error = %s. 19098 16 An error occurred starting the default trace. Cause: %ls Use sp_configure to turn off and then turn on the ‘default trace enabled’ advanced server configuration option.
19099 16 Trace ID ‘%d’ was stopped because of an error. Cause: %ls. Restart the trace after correcting the problem.

About these ads

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: