SQL Server Errors or Failures Error: 3703 to Error: 3733

SQLServerF1

 

Error: 3703, Severity: 16, Cannot detach the %S_MSG ‘%.*ls’ because it is currently in use.,
Error: 3705, Severity: 16, Cannot use DRP %ls with ‘%.*ls’ because ‘%.*ls’ is a %S_MSG. Use %ls.,
Error: 3706, Severity: 16, Cannot %S_MSG a database snapshot.,
Error: 3707, Severity: 16, Cannot detach a suspect or recovery pending database. It must be repaired or dropped.,
Error: 3708, Severity: 16, Cannot %S_MSG the %S_MSG ‘%.*ls’ because it is a system %S_MSG.,
Error: 3709, Severity: 16, Cannot %S_MSG the database while the database snapshot “%.*ls” refers to it. Drp that database first.,

Error: 3710, Severity: 16, Cannot detach an opened database when the server is in minimally configured mode.,
Error: 3716, Severity: 16, The %S_MSG ‘%.*ls’ cannot be dropped because it is bound to one or more %S_MSG.,
Error: 3717, Severity: 16, Cannot drp a default constraint by DRP DEFAULT statement. Use ALTR TABLE to drp a constraint default.,
Error: 3721, Severity: 16, Type ‘%.*ls’ cannot be renamed because it is being referenced by object ‘%.*ls’.,
Error: 3723, Severity: 16, An explicit DRP INDEX is not allowed on index ‘%.*ls’. It is being used for %ls constraint enforcement.,
Error: 3724, Severity: 16, Cannot %S_MSG the %S_MSG ‘%.*ls’ because it is being used for replication.,
Error: 3725, Severity: 16, The constraint ‘%.*ls’ is being referenced by table ‘%.*ls’, foreign key constraint ‘%.*ls’.,

Error: 3726, Severity: 16, Could not drp object ‘%.*ls’ because it is referenced by a FOREIGN KEY constraint.,
Error: 3727, Severity: 10, Could not drp constraint. See previous errors.,
Error: 3728, Severity: 16, ‘%.*ls’ is not a constraint.,
Error: 3729, Severity: 16, Cannot %ls ‘%.*ls’ because it is being referenced by object ‘%.*ls’.,
Error: 3730, Severity: 16, Cannot drp the default constraint ‘%.*ls’ while it is being used by a foreign key as SET DEFAULT referential action.,
Error: 3732, Severity: 16, Cannot drp type ‘%.*ls’ because it is being referenced by object ‘%.*ls’. There may be other objects that reference this type.,
Error: 3733, Severity: 16, Constraint ‘%.*ls’ does not belong to table ‘%.*ls’.,

This is applicable on below versions of SQL Server

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

Hope this was helpful.

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

 

SQL Server Errors or Failures Error: 247 to Error: 267

SQLServerF1

You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 247 to Error: 267

Error: 247, severity: 16,
An anchor member was found in the recursive part of recursive query “%.*ls”

Error: 248, severity: 16,
The conversion of the %ls value ‘%.*ls’ overflowed an int column

Error: 249, severity: 16,
The type “%ls” is not comparable. It cannot be used in the %ls Clause

Error: 251, severity: 16,
Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded

Error: 252, severity: 16,
Recursive common table expression ‘%.*ls’ does not contain a top-level UNION ALL operator

Error: 253, severity: 16,
Recursive member of a common table expression ‘%.*ls’ has multiple recursive references

Error: 254, severity: 16,
Prefixed columns are not allowed in the column list of a PIVOT operator

Error: 255, severity: 16,
Pseudocolumns are not allowed in the column list of a PIVOT operator

Error: 256, severity: 16,
The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary

Error: 257, severity: 16,
Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query

Error: 258, severity: 15,
Cannot call methods on %ls

Error: 259, severity: 16,
Ad hoc updates to system catalogs are not allowed

Error: 260, severity: 16,
Disallowed implicit conversion from data type %ls to data type %ls, table ‘%.*ls’, column ‘%.*ls’. Use the CONVERT function to run this query

Error: 261, severity: 16,
‘%.*ls’ is not a recognized function

Error: 262, severity: 16,
%ls permission denied in database ‘%.*ls’

Error: 263, severity: 16,
Must specify table to select from

Error: 264, severity: 16,
The column name ‘%.*ls’ is specified more than once in the SET clause or column list of an INSERT.
A column cannot be assigned more than one value in the same clause. Modify the clause to make sure that a column is updated only once. If this statement up.

Error: 265, severity: 16,
The column name “%.*ls” specified in the %ls operator conflicts with the existing column name in the %ls argument

Error: 266, severity: 16,
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %ld, current count = %ld

Error: 267, severity: 16,
Object ‘%.*ls’ cannot be found

This is applicable on below versions of SQL Server

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

Hope this was helpful.

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

 

SQL Server Errors or Failures Error: 226 to Error: 246

SQLServerF1

You may receive various errors in SQL Server while working. Below are some of the SQL Server Errors from Error: 226 to Error: 246

Error: 226, severity: 16,
%ls statement not allowed within multi-statement transaction.

Error: 227, severity: 15,
“%.*ls” is not a valid function, property, or field.

Error: 228, severity: 15,
Method ‘%.*ls’ of type ‘%.*ls’ in assembly ‘%.*ls’ does not return any value.

Error: 229, severity: 14,
The %ls permission was denied on the object ‘%.*ls’, database ‘%.*ls’, schema ‘%.*ls’.

Error: 230, severity: 14,
The %ls permission was denied on the column ‘%.*ls’ of the object ‘%.*ls’, database ‘%.*ls’, schema ‘%.*ls’.

Error: 231, severity: 11,
No such default. ID = %ld, database ID = %d.

Error: 232, severity: 16,
Arithmetic overflow error for type %ls, value = %f.

Error: 233, severity: 16,
The column ‘%.*ls’ in table ‘%.*ls’ cannot be null.

Error: 234, severity: 16,
There is insufficient result space to convert a money value to %ls.

Error: 235, severity: 16,
Cannot convert a char value to money. The char value has incorrect syntax.

Error: 236, severity: 16,
The conversion from char data type to money resulted in a money overflow error.

Error: 237, severity: 16,
There is insufficient result space to convert a money value to %ls.

Error: 239, severity: 16,
Duplicate common table expression name ‘%.*ls’ was specified.

Error: 240, severity: 16,
Types don’t match between the anchor and the recursive part in column “%.*ls” of recursive query “%.*ls”.

Error: 241, severity: 16,
Conversion failed when converting date and/or time from character string.

Error: 242, severity: 16,
The conversion of a %ls data type to a %ls data type resulted in an out-of-range value.

Error: 243, severity: 16,
Type %.*ls is not a defined system type.

Error: 244, severity: 16,
The conversion of the %ls value ‘%.*ls’ overflowed an %hs column. Use a larger integer column.

Error: 245, severity: 16,
Conversion failed when converting the %ls value ‘%.*ls’ to data type %ls.

Error: 246, severity: 16,
No anchor member was specified for recursive query “%.*ls”.

This is applicable on below versions of SQL Server

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

Hope this was helpful.

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

 

SQL Server Errors or Failures Error: 185 to Error: 205

SQLServerF1

Below are some of the SQL Server Errors from Error: 185 to Error: 205

Error: 185, Severity: 15,
Data stream is invalid for WRITETEXT statement in bulk form.

Error: 186, Severity: 15,
Data stream missing from WRITETEXT statement.

Error: 187, Severity: 15,
The valid range for MAX_QUEUE_READERS is 0 to 32767.

Error: 188, Severity: 16,
Cannot specify a log file in a CREATE DATABASE statement without also specifying at least one data file.

Error: 189, Severity: 15,
The %ls function requires %d to %d arguments.

Error: 190, Severity: 15,
An invalid date or time was specified in the statement.

Error: 191, Severity: 15,
Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.

Error: 192, Severity: 15,
The scale must be less than or equal to the precision.

Error: 193, Severity: 16,
The object or column name starting with ‘%.*ls’ is too long. The maximum length is %d characters.

Error: 194, Severity: 15,
A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable.

Error: 195, Severity: 15,
‘%.*ls’ is not a recognized %S_MSG.

Error: 196, Severity: 15,
SELECT INTO must be the first query in a statement containing a UNION, INTERSECT or EXCEPT operator.

Error: 197, Severity: 15,
EXECUTE cannot be used as a source when inserting into a table variable.

Error: 198, Severity: 15,
Browse mode is invalid for statements containing a UNION, INTERSECT or EXCEPT operator.

Error: 199, Severity: 15,
An INSERT statement cannot contain a SELECT statement that assigns values to a variable.

Error: 201, Severity: 15,
Procedure or function ‘%.*ls’ expects parameter ‘%.*ls’, which was not supplied.

Error: 202, Severity: 16,
Invalid type ‘%s’ for WAIT FOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAIT FOR DELAY supports the INT and SMALLINT data types.

Error: 203, Severity: 16,
The name ‘%.*ls’ is not a valid identifier.

Error: 204, Severity: 16,
Normalization error in node %ls.

Error: 205, Severity: 20,
All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists.

This is applicable on below versions of SQL Server

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

Hope this was helpful.

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

 

SQL Server Errors or Failures Error: 164 to Error: 184

SQLServerF1

Below are some of the SQL Server Errors, Error: 164 through Error: 184.

Error: 164, Severity: 15,
Each GROUP BY expression must contain at least one column that is not an outer reference

Error: 165, Severity: 16,
Privilege %ls may not be granted or revoked

Error: 166, Severity: 15,
‘%ls’ does not allow specifying the database name as a prefix to the object name

Error: 167, Severity: 15,
Cannot create %S_MSG on a temporary object

Error: 168, Severity: 15,
The floating point value ‘%.*ls’ is out of the range of computer representation (%d bytes)

Error: 169, Severity: 15,
A column has been specified more than once in the order by list. Columns in the order by list must be unique

Error: 171, Severity: 15,
Browse mode cannot be used with INSERT, SELECT INTO, or UPDATE statements

Error: 172, Severity: 15,
Cannot use HOLDLOCK in browse mode

Error: 173, Severity: 15,
The definition for column ‘%.*ls’ must include a data type

Error: 174, Severity: 15,
The %.*ls function requires %d argument(s)

Error: 175, Severity: 15,
An aggregate may not appear in a computed column expression or check constraint

Error: 176, Severity: 15,
The FOR BROWSE clause is no longer supported in views

Error: 177, Severity: 15,
The IDENTITY function can only be used when the SELECT statement has an INTO clause

Error: 178, Severity: 15,
A RETURN statement with a return value cannot be used in this context

Error: 179, Severity: 15,
Cannot use the OUTPUT option when passing a constant to a stored procedure

Error: 180, Severity: 15,
There are too many parameters in this %ls statement. The maximum number is %d

Error: 181, Severity: 15,
Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement

Error: 182, Severity: 15,
Table and column names must be supplied for the READTEXT or WRITETEXT utility

Error: 183, Severity: 15,
The scale (%d) for column ‘%.*ls’ must be within the range %d to %d

Error: 184, Severity: 16,
DEFAULT cannot be specified more than once for filegroups of the same content type

This is applicable on below versions of SQL Server

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

Hope this was helpful.

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

 

SQL Server Errors Error or Failures 121 to Error 140

SQLServerF1

Below are some of the SQL Server Errors

Error: 121, Severity: 15,
The 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.

Error: 122, Severity: 15,
The %ls option is allowed only with %ls syntax.

Error: 123, Severity: 15,
Batch/procedure exceeds maximum length of %d characters.

Error: 124, Severity: 15,
CREATE PROCEDURE contains no statements.

Error: 125, Severity: 15,
Case expressions may only be nested to level %d.

Error: 126, Severity: 15,
Invalid pseudocolumn “%.*ls”.

Error: 127, Severity: 15,
A TOP N or FETCH rowcount value may not be negative.

Error: 128, Severity: 15,
The name “%.*s” is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted.

Error: 129, Severity: 15,
Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100.

Error: 130, Severity: 16,
Cannot perform an aggregate function on an expression containing an aggregate or a subquery.

Error: 131, Severity: 15,
The size (%d) given to the %S_MSG ‘%.*ls’ exceeds the maximum allowed for any data type (%d).

Error: 132, Severity: 15,
The label ‘%.*ls’ has already been declared. Label names must be unique within a query batch or stored procedure.

Error: 133, Severity: 15,
A GOTO statement references the label ‘%.*ls’ but the label has not been declared.

Error: 134, Severity: 15,
The variable name ‘%.*ls’ has already been declared. Variable names must be unique within a query batch or stored procedure.

Error: 135, Severity: 15,
Cannot use a BREAK statement outside the scope of a WHILE statement.

Error: 136, Severity: 15,
Cannot use a CONTINUE statement outside the scope of a WHILE statement.

Error: 137, Severity: 15,
Must declare the scalar variable “%.*ls”.

Error: 138, Severity: 15,
Correlation clause in a subquery not permitted.

Error: 139, Severity: 15,
Cannot assign a default value to a local variable.

Error: 140, Severity: 15,
Can only use IF UPDATE within a CREATE TRIGGER statement.

This is applicable on below versions of SQL Server

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

Hope this was helpful.

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

 

SQL Server Setup or Installation Failure While Trying to Start SQL Server Services

New installation of Microsoft SQL Server 2012 standalone Express Edition instance Failed with error “Could not find the Database Engine startup handle” “Error Code 0x851A0019”. Below is the error snippet from Setup Summary log file.

Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.

Setup failed at the very end while it was trying to bring the SQL Server services online.
Upon checking the SQL Server Errorlog, found below errors

Error: 5178, Severity: 16, State: 1.
Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 1048576. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.

Above error message points towards some issue with the DISK or SAN drive, so check with the storage admin. There are issues resolved by updating the Firmware and drivers of the Hardware provider. Also, there are few known issues at Operating System level, so apply all latest fixes for the Operating System. Additionally make sure disk is formatted with NTFS file format, but not as FAT32. Make sure that the disk/folders are not read-only, mapped, or compressed drives.

Windows 7 and Windows Server 2008 R2
– Install Service Pack 1 (SP1), or install the update that is described in the following article in the Microsoft Knowledge Base:
982018 An update that improves the compatibility of Windows 7 and Windows Server 2008 R2 with Advanced Format Disks is available
– Make sure that the drivers and firmware for your storage controller and other hardware components are updated. Also, make sure that the drives and firmware support large-sector drives.

Windows Vista and Windows Server 2008
– Install the hotfix that is described in the following article in the Microsoft Knowledge Base:
2553708 A hotfix rollup that improves Windows Vista and Windows Server 2008 compatibility with Advanced Format disks
– Make sure that the drivers and firmware for your storage controller and other hardware components are updated. Also, make sure that the drivers and firmware support large-sector drives.

References:
http://support.microsoft.com/kb/2510009
http://support2.microsoft.com/kb/926930

If you could not find the SQL Server Errorlog as mentioned above, then try the below general steps to see if that is helpful in resolving the issue or making some progress.

– Make sure to uninstall the failed SQL Server instance completely using add remove programs.

– Make sure you remove all file sand folders related to SQL Server from all the drives.

– Run the setup.exe by selecting “run as administrator”

– During installation when you are selecting SQL Server service accounts from account selection page, instead of using default service accounts, use domain account ot Local system account.

This is applicable on below versions of SQL Server

SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

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