Mysql fatal error the error returned was

mysql fatal error the error returned was

dev.mysql.com › doc › mysql-errors › server-error-reference. Occurs for failure to create or copy a file needed for some operation. Possible causes: Permissions problem for source file; destination file already exists. The error returned by rows.Close() is the only exception to the general rule that it's best to capture and check for errors in all database operations. If rows.

Mysql fatal error the error returned was - All above

Database engine errors

-2Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2).-1An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (Microsoft SQL Server, Error: -1).2An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)2120NoWarning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator.53An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider).10115NoQuery not allowed in Wait for.10215NoIncorrect syntax near '%.*ls'.10315NoThe %S_MSG that starts with '%.*ls' is too long. Maximum length is %d.10415NoORDER BY items must appear in the select list if the statement contains a UNION, INTERSECT or EXCEPT operator.10515NoUnclosed quotation mark after the character string '%.*ls'.10616NoToo many table names in the query. The maximum allowable is %d.10715NoThe column prefix '%.*ls' does not match with a table name or alias name used in the query.10815NoThe ORDER BY position number %ld is out of range of the number of items in the select list.10915NoThere are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.11015NoThere are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.11115No'%ls' must be the first statement in a query batch.11215NoVariables are not allowed in the %ls statement.11315NoMissing end comment mark '*/'.11415NoBrowse mode is invalid for a statement that assigns values to a variable.11515NoThe FOR UPDATE clause is invalid for statements containing set operators.11615NoOnly one expression can be specified in the select list when the subquery is not introduced with EXISTS.11715NoThe %S_MSG name '%.*ls' contains more than the maximum number of prefixes. The maximum is %d.11915NoMust pass parameter number %d and subsequent parameters as '@name = value'. After the form '@name = value' has been used, all subsequent parameters must be passed in the form '@name = value'.12015NoThe select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT columns.12115NoThe select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match the number of INSERT columns.12215NoThe %ls option is allowed only with %ls syntax.12315NoBatch/procedure exceeds maximum length of %d characters.12415NoCREATE PROCEDURE contains no statements.12515NoCase expressions may only be nested to level %d.12615NoInvalid pseudocolumn "%.*ls".12715NoA TOP N value may not be negative.12815NoThe name "%.*s" is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted.12915NoFillfactor %d is not a valid percentage; fillfactor must be between 1 and 100.13016NoCannot perform an aggregate function on an expression containing an aggregate or a subquery.13115NoThe size (%d) given to the %S_MSG '%.*ls' exceeds the maximum allowed for any data type (%d).13215NoThe label '%.*ls' has already been declared. Label names must be unique within a query batch or stored procedure.13315NoA GOTO statement references the label '%.*ls' but the label has not been declared.13415NoThe variable name '%.*ls' has already been declared. Variable names must be unique within a query batch or stored procedure.13515NoCannot use a BREAK statement outside the scope of a WHILE statement.13615NoCannot use a CONTINUE statement outside the scope of a WHILE statement.13715NoMust declare the scalar variable "%.*ls".13815NoCorrelation clause in a subquery not permitted.13915NoCannot assign a default value to a local variable.14015NoCan only use IF UPDATE within a CREATE TRIGGER statement.14115NoA SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations.14215NoIncorrect syntax for definition of the '%ls' constraint.14315NoA COMPUTE BY item was not found in the order by list. All expressions in the compute by list must also be present in the order by list.14415NoCannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause.14515NoORDER BY items must appear in the select list if SELECT DISTINCT is specified.14615NoCould not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded.14715NoAn aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, and the column being aggregated is an outer reference.14815NoIncorrect time syntax in time string '%.*ls' used with WAITFOR.14915NoTime value '%.*ls' used with WAITFOR is not a valid value. Check date/time syntax.15015NoBoth terms of an outer join must contain columns.15115No'%.*ls' is an invalid money value.15215NoThe same large data placement option "%.*ls" has been specified twice.15315NoInvalid usage of the option %.*ls in the %ls statement.15415No%S_MSG is not allowed in %S_MSG.15515No'%.*ls' is not a recognized %ls option.15615NoIncorrect syntax near the keyword '%.*ls'.15715NoAn aggregate may not appear in the set list of an UPDATE statement.15815NoAn aggregate may not appear in the OUTPUT clause.15915NoMust specify the table name and index name for the DROP INDEX statement.16015NoRule does not contain a variable.16115NoRule contains more than one variable.16215NoInvalid expression in the TOP clause.16315NoThe compute by list does not match the order by list.16415NoEach GROUP BY expression must contain at least one column that is not an outer reference.16516NoPrivilege %ls may not be granted or revoked.16615No'%ls' does not allow specifying the database name as a prefix to the object name.16715NoCannot create %S_MSG on a temporary object.16815NoThe floating point value '%.*ls' is out of the range of computer representation (%d bytes).16915NoA column has been specified more than once in the order by list. Columns in the order by list must be unique.17115NoBrowse mode cannot be used with INSERT, SELECT INTO, or UPDATE statements.17215NoCannot use HOLDLOCK in browse mode.17315NoThe definition for column '%.*ls' must include a data type.17415NoThe %.*ls function requires %d argument(s).17515NoAn aggregate may not appear in a computed column expression or check constraint.17615NoThe FOR BROWSE clause is no longer supported in views. Set the database compatibility level to 80 or lower for this statement to be allowed.17715NoThe IDENTITY function can only be used when the SELECT statement has an INTO clause.17815NoA RETURN statement with a return value cannot be used in this context.17915NoCannot use the OUTPUT option when passing a constant to a stored procedure.18015NoThere are too many parameters in this %ls statement. The maximum number is %d.18115NoCannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement.18215NoTable and column names must be supplied for the READTEXT or WRITETEXT utility.18315NoThe scale (%d) for column '%.*ls' must be within the range %d to %d.18416NoDEFAULT cannot be specified more than once for filegroups of the same content type.18515NoData stream is invalid for WRITETEXT statement in bulk form.18615NoData stream missing from WRITETEXT statement.18716NoThe valid range for MAX_QUEUE_READERS is 0 to 32767.18815NoCannot specify a log file in a CREATE DATABASE statement without also specifying at least one data file.18915NoThe %ls function requires %d to %d arguments.19015NoAn invalid date or time was specified in the statement.19115NoSome part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.19216NoThe scale must be less than or equal to the precision.19315NoThe object or column name starting with '%.*ls' is too long. The maximum length is %d characters.19415NoA SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable.19515No'%.*ls' is not a recognized %S_MSG.19615NoSELECT INTO must be the first query in a statement containing a UNION, INTERSECT or EXCEPT operator.19715NoEXECUTE cannot be used as a source when inserting into a table variable.19815NoBrowse mode is invalid for statements containing a UNION, INTERSECT or EXCEPT operator.19915NoAn INSERT statement cannot contain a SELECT statement that assigns values to a variable.20116NoProcedure or function '%.*ls' expects parameter '%.*ls', which was not supplied.20216NoInvalid type '%s' for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data types.20316NoThe name '%.*ls' is not a valid identifier.20420YesNormalization error in node %ls.20516NoAll queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists.20616NoOperand type clash: %ls is incompatible with %ls20716NoInvalid column name '%.*ls'.20816NoInvalid object name '%.*ls'.20916NoAmbiguous column name '%.*ls'.21016NoConversion failed when converting datetime from binary/varbinary string.21123YesPossible schema corruption. Run DBCC CHECKCATALOG.21216NoExpression result length exceeds the maximum. %d max, %d found.21316NoColumn name or number of supplied values does not match table definition.21416NoProcedure expects parameter '%ls' of type '%ls'.21516NoParameters supplied for object '%.*ls' which is not a function. If the parameters are intended as a table hint, a WITH keyword is required.21616NoParameters were not supplied for the function '%.*ls'.21716NoMaximum stored procedure, function, trigger, or view nesting level exceeded (limit %d).21816NoCould not find the type '%.*ls'. Either it does not exist or you do not have the necessary permission.21916NoThe type '%.*ls' already exists, or you do not have permission to create it.22016NoArithmetic overflow error for data type %ls, value = %ld.22110NoFIPS Warning: Implicit conversion from %ls to %ls.22216NoThe base type "%.*ls" is not a valid base type for the alias data type.22311NoObject ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default.22411NoObject ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default.22516NoThe parameters supplied for the %ls "%.*ls" are not valid.22616No%ls statement not allowed within multi-statement transaction.22715No%.*ls is not a valid function, property, or field.22815NoMethod '%.*ls' of type '%.*ls' in assembly '%.*ls' does not return any value.22914NoThe %ls permission was denied on the object '%.*ls', database '%.*ls', schema '%.*ls'.23014NoThe %ls permission was denied on the column '%.*ls' of the object '%.*ls", database '%.*ls', schema '%.*ls'.23111NoNo such default. ID = %ld, database ID = %d.23216NoArithmetic overflow error for type %ls, value = %f.23316NoThe column '%.*ls' in table '%.*ls' cannot be null.233A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)23416NoThere is insufficient result space to convert a money value to %ls.23516NoCannot convert a char value to money. The char value has incorrect syntax.23616NoThe conversion from char data type to money resulted in a money overflow error.23716NoThere is insufficient result space to convert a money value to %ls.23916NoDuplicate common table expression name '%.*ls' was specified.24016NoTypes don't match between the anchor and the recursive part in column "%.*ls" of recursive query "%.*ls".24116NoConversion failed when converting date and/or time from character string.24216NoThe conversion of a %ls data type to a %ls data type resulted in an out-of-range value.24316NoType %.*ls is not a defined system type.24416NoThe conversion of the %ls value '%.*ls' overflowed an %hs column. Use a larger integer column.24516NoConversion failed when converting the %ls value '%.*ls' to data type %ls.24616NoNo anchor member was specified for recursive query "%.*ls".24716NoAn anchor member was found in the recursive part of recursive query "%.*ls".24816NoThe conversion of the %ls value '%.*ls' overflowed an int column.24916NoThe type "%ls" is not comparable. It cannot be used in the %ls clause.25116NoCould not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded.25216NoRecursive common table expression '%.*ls' does not contain a top-level UNION ALL operator.25316NoRecursive member of a common table expression '%.*ls' has multiple recursive references.25416NoPrefixed columns are not allowed in the column list of a PIVOT operator.25516NoPseudocolumns are not allowed in the column list of a PIVOT operator.25616NoThe data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary.25716NoImplicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query.25815NoCannot call methods on %ls.25916NoAd hoc updates to system catalogs are not allowed.26016NoDisallowed implicit conversion from data type %ls to data type %ls, table '%.*ls', column '%.*ls'. Use the CONVERT function to run this query.26116No'%.*ls' is not a recognized function.26216No%ls permission denied in database '%.*ls'.26316NoMust specify table to select from.26416NoThe column name '%.*ls' is specified more than once in the SET clause. A column cannot be assigned more than one value in the same SET clause. Modify the SET clause to make sure that a column is updated only once. If the SET clause updates columns of a view, then the column name '%.*ls' may appear twice in the view definition.26516NoThe column name "%.*ls" specified in the %ls operator conflicts with the existing column name in the %ls argument.26616NoTransaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %ld, current count = %ld.26716NoObject '%.*ls' cannot be found.26816NoCannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option.27016NoObject '%.*ls' cannot be modified.27116NoThe column "%.*ls" cannot be modified because it is either a computed column or is the result of a UNION operator.27216NoCannot update a timestamp column.27316NoCannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column.27516NoPrefixes are not allowed in value or pivot columns of an UNPIVOT operator.27616NoPseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator.27716NoThe column "%.*ls" is specified multiple times in the column list of the UNPIVOT operator.27816NoThe text, ntext, and image data types cannot be used in a GROUP BY clause.27916NoThe text, ntext, and image data types are invalid in this subquery or aggregate expression.28016NoOnly base table columns are allowed in the TEXTPTR function.28116No%d is not a valid style number when converting from %ls to a character string.28210NoThe '%.*ls' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead.28316NoREADTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger.28416NoRules cannot be bound to text, ntext, or image data types.28516NoThe READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions.28616NoThe logical tables INSERTED and DELETED cannot be updated.28716NoThe %ls statement is not allowed within a trigger.28816NoThe PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only.29016NoInvalid EXECUTE statement using object "%ls", method "%ls".29116NoCAST or CONVERT: invalid attributes specified for type '%.*ls'29216NoThere is insufficient result space to convert a smallmoney value to %ls.29316NoCannot convert char value to smallmoney. The char value has incorrect syntax.29416NoThe conversion from char data type to smallmoney data type resulted in a smallmoney overflow error.29516NoConversion failed when converting character string to smalldatetime data type.29716NoThe user does not have permission to perform this action.30014No%ls permission was denied on object '%.*ls', database '%.*ls'.30116NoQuery contains an outer-join request that is not permitted.30216NoThe newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type 'uniqueidentifier' in a CREATE TABLE or ALTER TABLE statement. It cannot be combined with other operators to form a complex scalar expression.30316NoThe table '%.*ls' is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause.30416No'%d' is out of range for index option '%.*ls'. See sp_configure option '%ls' for valid values.30516NoThe XML data type cannot be compared or sorted, except when using the IS NULL operator.30616NoThe text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator.30716NoIndex ID %d on table '%.*ls' (specified in the FROM clause) does not exist.30816NoIndex '%.*ls' on table '%.*ls' (specified in the FROM clause) does not exist.30916NoCannot use index "%.*ls" on table "%.*ls" in a hint. XML indexes are not allowed in hints.31015NoThe value %d specified for the MAXRECURSION option exceeds the allowed maximum of %d.31116NoCannot use text, ntext, or image columns in the 'inserted' and 'deleted' tables.31216NoCannot reference text, ntext, or image columns in a filter stored procedure.31316NoAn insufficient number of arguments were supplied for the procedure or function %.*ls.31416NoCannot use GROUP BY ALL with the special tables INSERTED or DELETED.31516NoIndex "%.*ls" on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online.31616NoThe index ID %d on table "%.*ls" (specified in the FROM clause) is disabled or resides in a filegroup which is not online.31716NoTable-valued function '%.*ls' cannot have a column alias.31816NoThe table (and its columns) returned by a table-valued method need to be aliased.31916NoIncorrect syntax near the keyword 'with'. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.32016NoThe compile-time variable value for '%.*ls' in the OPTIMIZE FOR clause must be a literal.32115No%.*ls is not a recognized table hints option. If it is intended as a parameter to a table-valued function or to the CHANGETABLE function, ensure that your database compatibility mode is set to 90.32215NoThe variable "%.*ls" is specified in the OPTIMIZE FOR clause, but is not used in the query.32316NoThe 'COMPUTE' clause is not allowed in a statement containing an INTERSECT or EXCEPT operator.32415NoThe 'ALL' version of the %.*ls operator is not supported.32515NoIncorrect syntax near '%.*ls'. You may need to set the compatibility level of the current database to a higher value to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE.32616NoMulti-part identifier '%.*ls' is ambiguous. Both columns '%.*ls' and '%.*ls' exist.32716NoFunction call '%.*ls' is ambiguous: both a user-defined function and a method call with this name exist.32816NoA cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from one of the base tables.32916NoEach GROUP BY expression must contain at least one column reference.33015NoThe target '%.*ls' of the OUTPUT INTO clause cannot be a view or common table expression.33115NoThe target table '%.*ls' of the OUTPUT INTO clause cannot have any enabled triggers.33215NoThe target table '%.*ls' of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. Found reference constraint '%ls'.33315NoThe target table '%.*ls' of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found check constraint or rule '%ls'.33415NoThe target table '%.*ls' of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause.33516NoFunction call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name '%.*ls' without parameters instead.33615NoIncorrect syntax near '%.*ls'. If this is intended to be a common table expression, you need to explicitly terminate the previous statement with a semi-colon.33710NoWarning: the floating point value '%.*ls' is too small. It will be interpreted as 0.33816NoREADEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views, remote tables, and inserted or deleted tables inside triggers.33916NoDEFAULT or NULL are not allowed as explicit identity values.34016NoCannot create the trigger "%.*ls" on view "%.*ls". AFTER triggers cannot be created on views.34116NoReplication filter procedures may not contain columns of large object, large value, XML or CLR type.34216NoColumn "%.*ls" is not allowed in this context, and the user-defined function or aggregate "%.*ls" could not be found.34315NoUnknown object type '%.*ls' used in a CREATE, DROP, or ALTER statement.34416NoRemote function reference '%.*ls' is not allowed, and the column name '%.*ls' could not be found or is ambiguous.34516NoFunction '%.*ls' is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform this access. A function is assumed by default to perform data access if it is not schemabound.34615NoThe parameter "%.*ls" cannot be declared READONLY since it is not a table-valued parameter.34716NoThe table-valued parameter "%.*ls" cannot be declared as an OUTPUT parameter.34816NoThe table variable "%.*ls" cannot be passed to a stored procedure with the OUTPUT option.34916NoThe procedure "%.*ls" has no parameter named "%.*ls".35016NoThe column "%.*ls" does not have a valid data type. A column cannot be of a user-defined table type.35116NoColumn, parameter, or variable %.*ls. : Cannot find data type %.*ls.35215NoThe table-valued parameter "%.*ls" must be declared with the READONLY option.35316NoFunction '%.*ls' is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. This is because the function performs user or system data access, or is assumed to perform this access. By default, a function is assumed to perform data access if it is not schema-bound.35415NoThe target '%.*ls' of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.35515NoThe target table '%.*ls' of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.35615NoThe target table '%.*ls' of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found reference constraint '%ls'.35715NoThe target table '%.*ls' of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found rule '%ls'.35815NoThe target table '%.*ls' of the MERGE statement cannot have any enabled rules. Found rule '%ls'.35915NoThe target '%.*ls' of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT clause is also used.36015NoThe target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that contains the sparse column. Rewrite the statement to include either the sparse column or the column set, but not both.36116NoThe number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %d. This total number includes identity, timestamp, and columns that have default values. To correct this error, change the query to target a sparse column set instead of single sparse columns.40116NoUnimplemented statement or expression %ls.40216NoThe data types %s and %s are incompatible in the %s operator.40316NoInvalid operator for data type. Operator equals %ls, type equals %ls.40416NoThe column reference "inserted.%.*ls" is not allowed because it refers to a base table that is not being modified in this statement.40516NoA remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement.40616No%ls cannot be used in the PIVOT operator because it is not invariant to NULLs.40716NoInternal error. The string routine in file %hs, line %d failed with HRESULT 0x%x.40816NoA constant expression was encountered in the ORDER BY list, position %i.41116NoCOMPUTE clause #%d, aggregate expression #%d is not in the select list.41216NoThe column "%.*ls" is not updatable because it is derived or constant.41316NoCorrelated parameters or sub-queries are not supported by the inline function "%.*ls".41416NoUPDATE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF UPDATE trigger.41516NoDELETE is not allowed because the statement updates view "%.*ls" which participates in a join and has an INSTEAD OF DELETE trigger.41616NoThe service queue "%.*ls" cannot be directly updated.41716NoTOP is not allowed in an UPDATE or DELETE statement against a partitioned view.41816NoObjects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object '%.*ls'.42116NoThe %ls data type cannot be selected as DISTINCT because it is not comparable.42216NoCommon table expression defined but not used.42316NoXml data type methods are not supported in check constraints. Create a scalar user-defined function to wrap the method invocation. The error occurred at table "%.*ls".42416NoXml data type methods are not supported in computed column definitions of table variables and return tables of table-valued functions. The error occurred at column "%.*ls", table "%.*ls", in the %ls statement.42516NoData type %ls of receiving variable is not equal to the data type %ls of column '%.*ls'.42616NoThe length %d of the receiving variable is less than the length %d of the column '%.*ls'.42720YesCould not load the definition for constraint ID %d in database ID %d. Run DBCC CHECKCATALOG to verify the integrity of the database.42816NoInsert bulk cannot be used in a multi-statement batch.43216NoXml data type methods are not supported in check constraints anymore. Please drop the constraint or create a scalar user-defined function to wrap the method invocation. The error occurred at table "%.*ls".43416NoFunction '%ls' is not allowed in the OUTPUT clause.43516NoXml data type methods are not supported in computed column definitions. Create a scalar user-defined function to wrap the method invocation. The error occurred at column "%.*ls", table "%.*ls", in the %ls statement.43816NoXml data type methods are not allowed in rules. The error occurred at table "%.*ls".44016NoInternal query compilation error. The stack overflow could not be handled.44116NoCannot use the '%ls' function on a remote data source.44216NoThe NEST argument must be a column reference. Expressions are not allowed.44316NoInvalid use of a side-effecting operator '%s' within a function.44416NoSelect statements included within a function cannot return data to a client.44516NoCOLLATE clause cannot be used on expressions containing a COLLATE clause.44616NoCannot resolve collation conflict for %ls operation.44716NoExpression type %ls is invalid for COLLATE clause.44816NoInvalid collation '%.*ls'.44916NoCollation conflict caused by collate clauses with different collation '%.*ls' and '%.*ls'.45016NoCode page translations are not supported for the text data type. From: %d To: %d.45116NoCannot resolve collation conflict for column %d in %ls statement.45216NoCOLLATE clause cannot be used on user-defined data types.45316NoCollation '%.*ls' is supported on Unicode data types only and cannot be set at the database or server level.45416NoThe UNNEST argument must be a nested table column.45516NoThe last statement included within a function must be a return statement.45616NoImplicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict.45716NoImplicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict.45816NoCannot create the SELECT INTO target table "%.*ls" because the xml column "%.*ls" is typed with a schema collection "%.*ls" from database "%.*ls". Xml columns cannot refer to schemata across databases.45916NoCollation '%.*ls' is supported on Unicode data types only and cannot be applied to char, varchar or text data types.46016NoDISTINCT operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.46116NoTOP operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.46216NoOuter join is not allowed in the recursive part of a recursive common table expression '%.*ls'.46316NoFunctions with parameters are not allowed in the recursive part of a recursive common table expression '%.*ls'.46416NoFunctions with side effects are not allowed in the recursive part of a recursive common table expression '%.*ls'.46516NoRecursive references are not allowed in subqueries.46616NoUNION operator is not allowed in the recursive part of a recursive common table expression '%.*ls'.46716NoGROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression '%.*ls'.46816NoCannot resolve the collation conflict between "%.*ls" and "%.*ls" in the %ls operation.46916NoAn explicit column list must be specified for target table '%.*ls' when table hint KEEPIDENTITY is used and the table contains an identity column.47016NoThe synonym "%.*ls" referenced synonym "%.*ls". Synonym chaining is not allowed.47116NoOnly one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB, can be specified.47216NoEither a format file or one of the three options SINGLE_BLOB, SINGLE_CLOB, or SINGLE_NCLOB must be specified.47316NoThe incorrect value "%.*ls" is supplied in the PIVOT operator.47416NoUnable to load the computed column definitions for table "%.*ls".47516NoInvalid SAMPLE clause. Only table names in the FROM clause of SELECT, UPDATE, and DELETE queries may be sampled.47616NoInvalid PERCENT tablesample size "%f" for table "%.*ls". The PERCENT tablesample size must be between 0 and 100.47716NoInvalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table "%.*ls". The value or seed must be an integer.47816NoThe TABLESAMPLE clause cannot be used in a view definition or inline table function definition.47916NoInvalid ROWS value or REPEATABLE seed "%I64d" in the TABLESAMPLE clause for table "%.*ls". The value or seed must be greater than 0.48016NoThe TABLESAMPLE clause cannot be used with the table function "%.*ls".48116NoThe TABLESAMPLE clause cannot be used with the linked server table "%.*ls".48216NoNon-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause.48316NoThe OUTPUT clause cannot be used in an INSERT...EXEC statement.48416NoCannot declare more than %d local variables.48516NoViews and inline functions cannot return xml columns that are typed with a schema collection registered in a database other than current. Column "%.*ls" is typed with the schema collection "%.*ls", which is registered in database "%.*ls".48616No%.*ls does not allow specifying a schema name as a prefix to the assembly name.48716NoAn invalid option was specified for the statement "%.*ls".48816No%s columns must be comparable. The type of column "%.*ls" is "%s", which is not comparable.48916NoThe OUTPUT clause cannot be specified because the target view "%.*ls" is a partitioned view.49016NoThe resync functionality is temporarily disabled.49116NoA correlation name must be specified for the bulk rowset in the from clause.49216NoDuplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name "%.*ls" is a duplicate.49316NoThe column '%.*ls' that was returned from the nodes() method cannot be used directly. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks.49416NoThe TABLESAMPLE clause can only be used with local tables.49516NoThe return table column "%.*ls" is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata.49616NoThe parameter "%.*ls" is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata.49716NoVariables are not allowed in the TABLESAMPLE or REPEATABLE clauses.49816NoInvalid value in the TABLESAMPLE or the REPEATABLE clause.49916NoInvalid parameter for the getchecksum function.50016NoTrying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s).50516NoThe current user account was invoked with SETUSER or SP_SETAPPROLE. Changing databases is not allowed.50616NoThe invalid escape character "%.*ls" was specified in a %ls predicate.50716NoInvalid argument for SET ROWCOUNT. Must be a non-null non-negative integer.50911NoUser name '%.*ls' not found.51016NoCannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint.51116NoCannot create a row of size %d which is greater than the allowable maximum row size of %d.51216NoSubquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.51316NoA column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in database '%.*ls', table '%.*ls', column '%.*ls'.51516NoCannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails.51716NoAdding a value to a '%ls' column caused an overflow.51816NoCannot convert data type %ls to %ls.52216NoThe WAITFOR thread was evicted.52316NoA trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active.52416NoA trigger returned a resultset and the server option 'disallow results from triggers' is true.52516NoThe column that was returned from the nodes() method cannot be converted to the data type %ls. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks.52616No%ls of XML types constrained by different XML schema collections and/or DOCUMENT/CONTENT option is not allowed. Use the CONVERT function to run this query.52716NoImplicit conversion between XML types constrained by different XML schema collections is not allowed. Use the CONVERT function to run this query.52916NoExplicit conversion from data type %ls to %ls is not allowed.53016NoThe statement terminated. The maximum recursion %d has been exhausted before statement completion.53110NoCannot set NOCOUNT to OFF inside the trigger execution because the server option "disallow_results_from_triggers" is true or we are inside LOGON trigger execution.53216NoThe timestamp (changed to %S_TS) shows that the row has been updated by another user.53310NoCannot set XACT ABORT to OFF inside the trigger execution unless the database compatibility is 90.53416No'%.*ls' failed because it is not supported in the edition of this SQL Server instance '%.*ls'. See books online for more details on feature support in different SQL Server editions.53516NoThe datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use datediff with a less precise datepart.53616NoInvalid length parameter passed to the %ls function.53716NoInvalid length parameter passed to the LEFT or SUBSTRING function.53916NoSchema changed after the target table was created. Rerun the Select Into query.54016YesThere is insufficient system memory to run RAISERROR.54116NoThere is not enough stack to execute the statement54216NoAn invalid datetime value was encountered. Value exceeds the year 9999.54316NoCreation of a return table failed for the table valued function '%.*ls'.54416NoCannot insert explicit value for identity column in table '%.*ls' when IDENTITY_INSERT is set to OFF.54516NoExplicit value must be specified for identity column in table '%.*ls' either when IDENTITY_INSERT is set to ON or when a replication user is inserting into a NOT FOR REPLICATION identity column.54716NoThe %ls statement conflicted with the %ls constraint "%.*ls". The conflict occurred in database "%.*ls", table "%.*ls"%ls%.*ls%ls.54816NoThe insert failed. It conflicted with an identity range check constraint in database '%.*ls', replicated table '%.*ls'%ls%.*ls%ls. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent.54916NoThe collation '%.*ls' of receiving variable is not equal to the collation '%.*ls' of column '%.*ls'.55016NoThe attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and one or more rows resulting from the operation did not qualify under the CHECK OPTION constraint.55216NoCryptoAPI function '%ls' failed. Error 0x%x: %ls55516NoUser-defined functions are not yet enabled.55616NoINSERT EXEC failed because the stored procedure altered the schema of the target table.55716NoOnly functions and some extended stored procedures can be executed from within a function.55816NoRemote function calls are not allowed within a function.56116NoFailed to access file '%.*ls'56216NoFailed to access file '%.*ls'. Files can be accessed only through shares56314NoThe transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated.56416NoAttempted to create a record with a fixed length of '%d'. Maximum allowable fixed length is '%d'.56518NoA stack overflow occurred in the server while compiling the query. Please simplify the query.56621YesAn error occurred while writing an audit trace. SQL Server is shutting down. Check and correct error conditions such as insufficient disk space, and then restart SQL Server. If the problem persists, disable auditing by starting the server at the command prompt with the "-f" switch, and using SP_CONFIGURE.56716NoFile '%.*ls' either does not exist or is not a recognizable trace file. Or there was an error opening the file.56816NoEncountered an error or an unexpected end of trace file '%.*ls'.56916NoThe handle that was passed to %ls was invalid.57015NoINSTEAD OF triggers do not support direct recursion. The trigger execution failed.57116NoThe specified attribute value for %ls is invalid.57216NoInvalid regular expression "%.*ls" near the offset %d.57316NoEvaluation of the regular expression is too complex: '%.*ls'.57416No%ls statement cannot be used inside a user transaction.57516NoA LOGON trigger returned a resultset. Modify the LOGON trigger to not return resultsets.57616NoCannot create a row that has sparse data of size %d which is greater than the allowable maximum sparse data size of %d.57716NoThe value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647.57816NoInsert Exec not allowed in WAITFOR queries.57916NoCannot execute WAITFOR query with snapshot isolation level.58216NoOffset is greater than the length of the column to be updated in write.58316NoNegative offset or length in write.58416NoSelect Into not allowed in WAITFOR queries.58516NoChanging database context is not allowed when populating the resource database.58716NoAn invalid delayed CLR type fetch token is provided.58816NoMultiple tasks within the session are using the same delayed CLR type fetch token at the same time.58916NoThis statement has attempted to access data whose access is restricted by the assembly.59016NoRPC was aborted without execution.59116No%ls: The formal parameter "%ls" was defined as OUTPUT, but the actual parameter was not declared as OUTPUT.59216NoCannot find %S_MSG ID %d in database ID %d.59310Nofn_trace_gettable: XML conversion of trace data for event 165 failed.59410Nofn_trace_gettable: XML conversion of trace data is not supported in fiber mode.59516NoBulk Insert with another outstanding result set should be run with XACT_ABORT on.59616NoCannot continue the execution because the session is in the kill state.59716NoThe execution of in-proc data access is being terminated due to errors in the User Datagram Protocol (UDP).59816NoAn error occurred while executing CREATE/ALTER DB. Please look at the previous error for more information.59916No%.*ls: The length of the result exceeds the length limit (2GB) of the target large type.60112NoCould not continue scan with NOLOCK due to data movement.60221YesCould not find an entry for table or index with partition ID %I64d in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.60321YesCould not find an entry for table or index with object ID %d (partition ID %I64d) in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB.60521YesAttempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d.60621YesMetadata inconsistency. Filegroup id %ld specified for table '%.*ls' does not exist. Run DBCC CHECKDB or CHECKCATALOG.60816YesNo catalog entry found for partition ID %I64d in database %d. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.60916NoB+ tree is not empty when waking up on RowsetBulk.61016YesInvalid header value from a page. Run DBCC CHECKDB to check for a data corruption.61116NoCannot insert or update a row because total variable column size, including overhead, is %d bytes more than the limit.61321NoCould not find an entry for worktable rowset with partition ID %I64d in database %d.61521YesCould not find database ID %d, name '%.*ls'. The database may be offline. Wait a few minutes and try again.61720YesDescriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it. A work table is missing an entry. Rerun the query. If a cursor is involved, close and reopen the cursor.62216NoThe filegroup "%.*ls" has no files assigned to it. Tables, indexes, text columns, ntext columns, and image columns cannot be populated on this filegroup until a file is added.62716NoCannot use SAVE TRANSACTION within a distributed transaction.62816NoCannot issue SAVE TRANSACTION when there is no active transaction.65016NoYou can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels.65116NoCannot use the %ls granularity hint on the table "%.*ls" because locking at the specified granularity is inhibited.65216NoThe index "%.*ls" for table "%.*ls" (RowsetId %I64d) resides on a read-only filegroup ("%.*ls"), which cannot be modified.66616NoThe maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %I64d. Dropping and re-creating the index may resolve this; otherwise, use another clustering key.66716NoThe index "%.*ls" for table "%.*ls" (RowsetId %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is offline, is being restored, or is defunct.66922NoThe row object is inconsistent. Please rerun the query.67016NoLarge object (LOB) data for table "%.*ls" resides on an offline filegroup ("%.*ls") that cannot be accessed.67116NoLarge object (LOB) data for table "%.*ls" resides on a read-only filegroup ("%.*ls"), which cannot be modified.67210NoFailed to queue cleanup packets for orphaned rowsets in database "%.*ls". Some disk space may be wasted. Cleanup will be attempted again on database restart.67410YesException occurred in destructor of RowsetNewSS 0x%p. This error may indicate a problem related to releasing pre-allocated disk blocks used during bulk-insert operations. Restart the server to resolve this problem.67510YesWorktable with partition ID %I64d was dropped successfully after repeated attempts.67610YesError occurred while attempting to drop worktable with partition ID %I64d.67710YesUnable to drop worktable with partition ID %I64d after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required.67810YesActive rowset for partition ID %I64d found at the end of the batch. This error may indicate incorrect exception handling. Use the current activity window in SQL Server Management Studio or the Transact-SQL KILL statement to terminate the server process identifier (SPID) responsible for generating the error.67916NoOne of the partitions of index '%.*ls' for table '%.*ls'(partition ID %I64d) resides on a filegroup ("%.*ls") that cannot be accessed because it is offline, restoring, or defunct. This may limit the query result.68010YesError [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d.68116NoAttempting to set a non-NULL-able column's value to NULL.68216NoInternal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption.68322NoAn internal error occurred while trying to convert between variable-length and fixed-length decimal formats. Run DBCC CHECKDB to check for any database corruption.68422NoAn internal error occurred while attempting to convert between compressed and uncompressed storage formats. Run DBCC CHECKDB to check for any corruption.68522NoAn internal error occurred while attempting to retrieve a backpointer for a heap forwarded record.70119YesThere is insufficient system memory in resource pool '%ls' to run this query.70810YesServer is running low on virtual address space or machine is running low on virtual memory. Reserved memory used %d times since startup. Cancel query and re-run, decrease server load, or cancel other applications.80120YesA buffer was encountered with an unexpected status of 0x%x.80217NoThere is insufficient memory available in the buffer pool.80310Yessimulated failure (DEBUG only)80510Yesrestore pending80610Yesaudit failure (a page read from disk failed to pass basic integrity checks)80710Yes(no disk or the wrong disk is in the drive)80810Yesinsufficient bytes transferred82120YesCould not unhash buffer at 0x%p with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE. Contact Technical Support.82221YesCould not start I/O operation for request %S_BLKIOPTR. Contact Technical Support.82324YesThe operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file '%ls'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.82424YesSQL Server detected a logical consistency-based I/O error: %ls. It occurred during a %S_MSG of page %S_PGID in database ID %d at offset %#016I64x in file '%ls'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.82510YesA read of the file '%ls' at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and system event log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.82610Yesincorrect pageid (expected %d:%d; actual %d:%d)82921YesDatabase ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore.83010Nostale page (a page read returned a log sequence number (LSN) (%u:%u:%u) that is older than the last one that was written (%u:%u:%u))83120NoUnable to deallocate a kept page.83224YesA page that should have been constant has changed (expected checksum: %08x, actual checksum: %08x, database %d, file '%ls', page %S_PGID). This usually indicates a memory failure or other hardware or OS corruption.83310NoSQL Server has encountered %d occurrence(s) of I/O requests taking longer than %d seconds to complete on file '%ls' in database '%ls' (%d). The OS file handle is 0x%p. The offset of the latest long I/O is: %#016I64x84410NoTime out occurred while waiting for buffer latch -- type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit id: %I64d%ls, task 0x%p : %d, waittime %d, flags 0x%I64x, owning task 0x%p. Continuing to wait.84517NoTime-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d.84610NoA time-out occurred while waiting for buffer latch -- type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit Id: %I64d%ls, task 0x%p : %d, waittime %d, flags 0x%I64x, owning task 0x%p. Not continuing to wait.84710YesTimeout occurred while waiting for latch: class '%ls', id %p, type %d, Task 0x%p : %d, waittime %d, flags 0x%I64x, owning task 0x%p. Continuing to wait.84810YesUsing large pages for buffer pool.84910YesUsing locked pages for buffer pool.85010Yes%I64u MB of large page memory allocated.85110Nothe page is in an OFFLINE file which cannot be read85410YesMachine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption.85510YesUncorrectable hardware memory corruption detected. Your system may become unstable. Check the Windows event log for more details.85610YesSQL Server has detected hardware memory corruption in database '%ls', file ID: %u, page ID; %u, memory address: 0x%I64x and has successfully recovered the page.90216NoTo change the %ls, the database must be in state in which a checkpoint can be executed.90416NoDatabase %ld cannot be autostarted during server shutdown or startup.90521YesDatabase '%.*ls' cannot be started in this edition of SQL Server because it contains a partition function '%.*ls'. Only Enterprise edition of SQL Server supports partitioning.90716NoThe database "%ls" has inconsistent database or file metadata.90810YesFilegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available.90921YesDatabase '%.*ls' cannot be started in this edition of SQL Server because part or all of object '%.*ls' is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterprise Edition.91010NoDatabase '%.*ls' is upgrading script '%.*ls' from level %d to level %d.91116NoDatabase '%.*ls' does not exist. Make sure that the name is entered correctly.91216NoScript level upgrade for database '%.*ls' failed because upgrade step '%.*ls' encountered error %d, state %d, severity %d. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.91322YesCould not find database ID %d. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred.91421NoScript level upgrade for database '%.*ls' failed because upgrade step '%.*ls' was aborted before completion. If the abort happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.91521NoUnable to obtain the current script level for database '%.*ls'. If the error happened during startup of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that script upgrade may run to completion.91614NoThe server principal "%.*ls" is not able to access the database "%.*ls" under the current security context.91721NoAn upgrade script batch failed to execute for database '%.*ls' due to compilation error. Check the previous error message for the line which caused compilation to fail.91821NoFailed to load the engine script metadata from script DLL '%.*ls'. The error code reported by Windows was %d. This is a serious error condition, which usually indicates a corrupt or incomplete installation. Repairing the SQL Server instance may help resolve this error.91910NoUser '%.*ls' is changing database script level entry %d to a value of %d.92020NoOnly members of the sysadmin role can modify the database script level.92114NoDatabase '%.*ls' has not been recovered yet. Wait and try again.92214NoDatabase '%.*ls' is being recovered. Waiting until recovery is finished.92314NoDatabase '%.*ls' is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it.92414NoDatabase '%.*ls' is already open and can only have one user at a time.92519YesMaximum number of databases used for each query has been exceeded. The maximum allowed is %d.92614NoDatabase '%.*ls' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.92714NoDatabase '%.*ls' cannot be opened. It is in the middle of a restore.92820YesDuring upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause.92920YesUnable to close a database that is not currently open. The application should reconnect and try again. If this action does not correct the problem, contact your primary support provider.93021YesAttempting to reference recovery unit %d in database '%ls' which does not exist. Contact Technical Support.93121YesAttempting to reference database fragment %d in database '%ls' which does not exist. Contact Technical Support.93221YesSQL Server cannot load database '%.*ls' because change tracking is enabled. The currently installed edition of SQL Server does not support change tracking. Either disable change tracking in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports change tracking.93321YesDatabase '%.*ls' cannot be started because some of the database functionality is not available in the current edition of SQL Server.93421YesSQL Server cannot load database '%.*ls' because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change Data Capture. Either disable Change Data Capture in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports Change Data Capture.93521YesThe script level for '%.*ls' in database '%.*ls' cannot be downgraded from %d to %d, which is supported by this server. This usually implies that a future database was attached and the downgrade path is not supported by the current installation. Install a newer version of SQL Server and re-try opening the database.94214NoDatabase '%.*ls' cannot be opened because it is offline.94314NoDatabase '%.*ls' cannot be opened because its version (%d) is later than the current server version (%d).94410NoConverting database '%.*ls' from version %d to the current version %d.94516NoDatabase '%.*ls' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.94614NoCannot open database '%.*ls' version %d. Upgrade the database to the latest version.94716YesError while closing database '%.*ls'. Check for previous additional errors and retry the operation.94820YesThe database '%.*ls' cannot be opened because it is version %d. This server supports version %d and earlier. A downgrade path is not supported.94916Notempdb is skipped. You cannot run a query that requires tempdb95020YesDatabase '%.*ls' cannot be upgraded because its non-release version (%d) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database.95110NoDatabase '%.*ls' running the upgrade step from version %d to version %d.95216NoDatabase '%.*ls' is in transition. Try the statement later.95414NoThe database "%.*ls" cannot be opened. It is acting as a mirror database.95514NoDatabase %.*ls is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened. Check the partner and witness connections if configured.95614NoDatabase %.*ls is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again later.95717NoDatabase '%.*ls' is enabled for Database Mirroring, The name of the database may not be changed.95810YesThe resource database build version is %.*ls. This is an informational message only. No user action is required.95920YesThe resource database version is %d and this server supports version %d. Restore the correct version or reinstall SQL Server.96010NoWarning: User "sys" (principal_id = %d) in database "%.*ls" has been renamed to "%.*ls". "sys" is a reserved user or schema name in this version of SQL Server.96110NoWarning: Index "%.*ls" (index_id = %d) on object ID %d in database "%.*ls" was renamed to "%.*ls" because its name is a duplicate of another index on the same object.96210NoWarning: Primary key or Unique constraint "%.*ls" (object_id = %d) in database "%.*ls" was renamed to "%.*ls" because its index was renamed.96310NoWarning: Database "%.*ls" was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER DATABASE to bring the database online. The database will come online in restricted_user state.96410NoWarning: System user '%.*ls' was found missing from database '%.*ls' and has been restored. This user is required for SQL Server operation.96510NoWarning: A column nullability inconsistency was detected in the metadata of index "%.*ls" (index_id = %d) on object ID %d in database "%.*ls". The index may be corrupt. Run DBCC CHECKTABLE to verify consistency.96610NoWarning: Assembly "%.*ls" in database "%.*ls" has been renamed to "%.*ls" because the name of the assembly conflicts with a system assembly in this version of SQL Server.96710NoWarning: The index "%.*ls" on "%.*ls"."%.*ls" is disabled because the XML data bound to it may contain negative values for xs:date and xs:dateTime which are not longer supported.96810NoWarning: The XML facet on type "%.*ls" in schema collection "%.*ls" is updated from "%.*ls" to "%.*ls" because Sql Server does not support negative years inside values of type xs:date or xs:dateTime.96910NoWarning: The default or fixed value on XML element or attribute "%.*ls" in schema collection "%.*ls" is updated from "%.*ls" to "%.*ls" because Sql Server does not support negative years inside values of type xs:date or xs:dateTime.97010NoWarning: The XML instances in the XML column "%.*ls.%.*ls.%.*ls" may contain negative simple type values of type xs:date or xs:dateTime. It will be impossible to run XQuery or build a primary XML index on these XML instances.97110NoThe resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at '%.*ls' instead of the currently attached resource database at '%.*ls'.97217NoCould not use database '%d' during procedure execution.97310YesDatabase %ls was started . However, FILESTREAM is not compatible with the READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION options. Either remove the FILESTREAM files and the FILESTREAM filegroups, or set READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION to OFF.97410NoAttaching the resource database in the same directory as sqlservr.exe at '%.*ls' failed as the database files do not exist.97510YesSystem objects could not be updated in database '%.*ls' because it is read-only.97614NoThe target database, '%.*ls', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other d97710NoWarning: Could not find associated index for the constraint '%.*ls' on object_id '%d' in database '%.*ls'.97814NoThe target database ('%.*ls') is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online.97914NoThe target database ('%.*ls') is in an availability group and currently does not allow read only connections. For more information about application intent, see SQL Server Books Online.98021YesSQL Server cannot load database '%.*ls' because it contains a columnstore index. The currently installed edition of SQL Server does not support columnstore indexes. Either disable the columnstore index in the database by using a supported edition of SQL Se98110NoDatabase manager will be using %d target database version.98214NoUnable to access the '%.*ls' database because no online secondary replicas are enabled for read-only access. Check the availability group configuration to verify that at least one secondary replica is configured for read-only access. Wait for an enabled re98314NoUnable to access availability database '%.*ls' because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation98421YesFailed to perform a versioned copy of sqlscriptdowngrade.dll from Binn to Binn\Cache folder. VerInstallFile API failed with error code %d.98510YesSuccessfully installed the file '%ls' into folder '%ls'.98610NoCouldn't get a clean bootpage for database '%.*ls' after %d tries. This is an informational message only. No user action is required.98723YesA duplicate key insert was hit when updating system objects in database '%.*ls'.98814NoUnable to access database '%.*ls' because it lacks a quorum of nodes for high availability. Try the operation again later.98916NoFailed to take the host database with ID %d offline when one or more of its partition databases is marked as suspect.99016NoTaking the host database with ID %d offline because one or more of its partition databases is marked as suspect.99116NoFailed to take the host database '%.*ls' offline when one or more of its partition databases is marked as suspect.99216NoFailed to get the shared lock on database '%.*ls'.99310NoRedo for database '%.*ls' applied version upgrade step from %d to %d.99410NoWarning: Index "%.*ls" on "%.*ls"."%.*ls" is disabled because it contains a computed column.99510NoWarning: Index "%.*ls" on "%.*ls"."%.*ls" is disabled. It cannot be upgraded as it resides on a read-only filegroup.99610NoWarning: Index "%.*ls" on "%.*ls"."%.*ls" is disabled. This columnstore index cannot be upgraded, likely because it exceeds the row size limit of '%d' bytes.

“MySQL server has gone away” error – Solution(s)

The MySQL server has gone away error, means that MySQL server (mysqld) timed out and closed the connection. By default, MySQL will close connections after eight hours (28800 seconds) if nothing happens. However, in some cases, your web host, DBA, or app developer may have decreased this timeout setting, discussed below.

MySQL server has gone away, can be a frustrating error to solve. This is partly because to solve this error; sometimes the solution involves multiple layers, application, or service config changes. This article includes solutions I’ve seen for this MySQL server general error. If you’ve found a solution not listed or linked to on this page, please send me a note or leave a comment.

MySQL server has gone away

 

MySQL server has gone away error log examples.

Keep in mind that this error can be logged in a few ways, as listed below. In addition, at times, the error is only an indication of a deeper underlying issue. Meaning the error could be due to a problem or bug in your connecting application or remote service. In which case, you need to check ALL related error logs with the same timestamp to determine whether another issue may be to blame. Application Performance Monitoring solutions and PHP Stack tracetools can be of help. With this in mind, here are error log examples of the MySQL server has gone away error:

General error: 2006 MySQL server has gone awayError Code: 2013. Lost connection to MySQL server during queryWarning: Error while sending QUERY packetPDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away

 

MySQL wait_timeout

The reason for MySQL server has gone away error is often because MySQL’s wait_timeout was exceeded. MySQL wait_timeout is the number of seconds the server waits for activity on a non-interactive connection before closing it. You should make sure the wait_timeout is not set too low. The default for MySQL wait_timeout is 28800 seconds. Often, it gets lowered arbitrarily. That said, the lower you can set wait_timeout without affecting database connections, can be a good sign of MySQL database efficiency. Also, check the variables: net_read_timeoutnet_write_timeout and interactive_timeout. Adjust or add the following lines in my.cnf to meet your requirements:

wait_timeout=90 net_read_timeout=90 net_write_timeout=90 interactive_timeout=300 connect_timeout=90

 

MySQL connect timeout in PHP config

Have a look at your php.ini config file. You’ll find MySQL configuration options. Make sure the mysql.connect_timeout setting isn’t set lower than MySQL wait_timeout, discussed above. The PHP option mysql.connect_timeout is not only used for connect timeout. It’s also when waiting for the first response from the MySQL server. Try increasing mysql.connect_timeout to match or exceed your MySQL wait_timeout and make sure that mysql.allow_persistent is on (default = enabled).

mysql.connect_timeout=90 mysql.allow_persistent=1

IMPORTANT: Read first about PHP Persistent Database Connections to understand the benefits and caveats.

Also, adjust PHP’s default_socket_timeout. For example, a PHP script could be running a slow query. Creating a wait that utilizes the default_socket_timeout. Eventually, it quits with the “MySQL server has gone away” error. Before you send hate mail, please read here first. Here’s an excerpt:

“PHP, by default, sets a read timeout of 60s for streams. This is set via , default_socket_timeout. This default applies to all streams that set no other timeout value. mysqlnd does not set any other value and therefore connections of long running queries can be disconnected after default_socket_timeout seconds resulting in an error message .”

default_socket_timeout=90

To be throughout, also adjust max_execution_time and max_input_time still in php.ini, if necessary. If PHP’s execution time is longer than max_execution_time, then MySQL server might disconnect.

max_execution_time = 90 max_input_time = 90

 

MySQL max_allowed_packet

max_allowed_packet is the maximum size of one packet. The default size of 4MB helps the MySQL server catch large (possibly incorrect) packets. As of MySQL 8, the default has been increased to 16MB. If mysqld receives a packet that is too large, it assumes that something is wrong and closes the connection. To fix this, you should increase the max_allowed_packet in my.cnf, then restart MySQL. The max for this setting is 1GB. For example:

max_allowed_packet = 512M

 

MySQL innodb_log_file_size

You may need to increase the innodb_log_file_size MySQL variable in your my.cnf configuration. MySQL’s innodb_log_file_size should be 25% of innodb_buffer_pool_size (if possible, no less than 20%). Remember that the larger this value, the longer it will take to recover from a database crash. (Source: Phpmyadmin Advisor)

This means for example: if your buffer pool size is set to innodb_buffer_pool_size=16G and your innodb_log_files_in_group setting is still set to the recommended default of 2 files (innodb_log_files_in_group=2), then your innodb_log_file_size should be set to 2G. This will create two (2) log files at 2GB each, which equals 25% of innodb_buffer_pool_size=16G.

WARNING: You must stop MySQL server in order to change innodb_log_file_size or innodb_log_files_in_group. If you don’t, you risk catastrophe! (Read: MySQL Log Redo instructions.)

 

Other causes of MySQL server has gone away

Remote MySQL connections

Remember earlier I mentioned that the error, at times, is only an indication of a deeper underlying issue. For example, remote MySQL connections to 3rd party services. Using a 3rd party payment processing plugin for osCommerce, Magento, etc.

MySQL database charset and collation

Changing default database charset to latin1 and default collation to latin1_general_ci seemed to have solved MySQL server has gone away for some.

Exceeding MySQL max_connections setting

Max_connections set the maximum permitted number of simultaneous client connections. Be careful with this setting!! Exhaustion of memory and other resources can occur when set too large and scheduling overhead also increases. As a guide, set max_connections to approximately double the previous number of maximum simultaneous client connections. E.g., if after a month of uptime, the maximum simultaneous client connections were 114, then set to max_connections=250. Before you go crazy with this setting, please read: How MySQL Handles Client Connections.

Still unresolved? See MySQL’s help page.

Oracle has put together a nice self-help page for MySQL server has gone away errors. On that page, they also suggest that you make sure MySQL didn’t stop/restart during the query. Excerpt:

“You can check whether the MySQL server died and restarted by executing mysqladmin version and examining the server’s uptime. If the client connection was broken because mysqld crashed and restarted, you should concentrate on finding the reason for the crash.”

# mysqladmin version mysqladmin Ver 9.1 Distrib 10.1.40-MariaDB, for Linux on x86_64 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Server version 10.1.40-MariaDB Protocol version 10 Connection Localhost via UNIX socket UNIX socket /var/lib/mysql/mysql.sock Uptime: 20 days 11 hours 49 min 40 sec Threads: 5 Questions: 1030744326 Slow queries: 3343 Opens: 3585 Flush tables: 1 Open tables: 2564 Queries per second avg: 582.150# mysqladmin status Uptime: 1770590 Threads: 4 Questions: 1030752268 Slow queries: 3343 Opens: 3585 Flush tables: 1 Open tables: 2564 Queries per second avg: 582.151

I hope this helps!


Related articles:

 

Published: June 7th, 2019

Mysql FATAL error when running ALTER TABLE

I´m still in shock with what happened to me yesterday. I have a mysql database running in production. Yesterday trying to fix a performance issue in our software, I figured out that we were missing a a foreign key in a table. I run this alter table (IN PRODUCTION) using workbench:

Surprisingly, I got a connection lost error, and to my surprise the whole table discounts has been dropped. Lucky I got a backup, but now I´m pretty scared.

I´m trying to re create the table:

, but I´m getting Error Code: 1005. Can't create table 'yanpyprod.boats_discounts' (errno: 150). I have read other posts such us MySQL: Can't create table (errno: 150) but just for testing, even if I try to create next table without any foreign keys, I´m getting the error.

UPDATE: To answer @Eden comment, I have exactly the same database replicated in development and I can create the table without problems.

UPDATE 2: For debugging purposes, I run.

In development, all three queries worked perfectly. In production, I got: Error Code: 1051. Unknown table 'boats_discounts' when tried to drop the table. - Error Code: 1005. Can't create table 'yanpyprod.boats_discounts' (errno: 150) when tried to create it.

UPDATE 3:

I have run next query to find out if there is any foreign key referencing table discounts. I can confirm that there isn´t any foreign key to discounts.id

UPDATE 4: After running this that I read here: Error Code: 1005. Can't create table '...' (errno: 150) I can see this interesting information error. It´s totally related, but still doesn´t make sense to me. I mean,

LATEST FOREIGN KEY ERROR

200226 16:21:14 Error in foreign key constraint of table schema/discounts: there is no index in the table which would contain the columns as the first columns, or the data types in the table do not match the ones in the referenced table or one of the ON ... SET NULL columns is declared NOT NULL. Constraint: , CONSTRAINT "discounts_ibfk_1" FOREIGN KEY ("discount_type_id") REFERENCES "discount_types" ("id")

This is the discount_types DDL:

But, using this query that I found here: List of Constraints from MySQL Database I cannot find the 'discounts_ibfk_1' foreign key constraint:

UPDATE 5: I´m desperate. I´m running all queries in MySQL workbench. When I try to run the same query:

directly in mysql console, I get a different error:

It´s pretty clear that the table doesn´t exist, because I´m trying to create it. So, I think something got corrupted. However, no idea how to fix it.

Please also see this example. Note that I have just created table discounts2 exactly as discounts, then created the indexes and foreign keys and then tried to rename discounts2 to discounts. Please see the result:

Again, I would say the database is corrupted, but I don´t know how to fix this.

Last updated: August 10th, 2021

Value +-----------------+-------+

Changing the max_connections parameter (Temporarily)

To change the value of the system variable max_connections, the –max_connections option can be used. To change this variable temporarily while the server is running, enter the following SQL statement:

$ mysql –u root –p mysql> SET GLOBAL max_connections = 512;
Note: It’s not necessary to have a client which is currently connected to the server disconnect to run this SQL statement as root. The server permits one connection more than the value of the max_connections. One connection is reserved for the root user or any other accounts that has SUPER privilege.

When the MySQL server daemon (mysqld) is restarted the above value will set back to the default value of 151. To make changes permanent use the below method.

Changing the max_connections parameter (Permanently)

A better method to change max_connections parameter would be to add this option to the options file (my.cnf or my.ini, depending on your system) so that it takes effect next time the server is restarted. Assuming you are using /etc/my.cnf file, add the below line to it.

# vi /etc/my.cnf max_connections = 512

Now restart the mysqld daemon for the changes to take effect.

For CentOS/RHEL 6:

For CentOS/RHEL 7:

# systemctl restart mysqld

What is the Maximum Value for max_connections on Linux?

The upper limit for how large you can configure max_connections is largely determined by the operating system in addition to the limit of 100,000 that MySQL sets. Linux has a limit called max open files, this is defined “per login” and says the maximum number of files a process can open. The default is 1024 (which you can see using ulimit -n).