SQL Server Error : 2 Details

SQL Server Error: 2 Severity: 0 Event Logged or not: No Description: An 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) Severity 0 Description: Informational messages that return status information or report errors that are not severe. The Database Engine does not raise system errors with severities of 0 through 9.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by … Read the rest

SQL Server Error : 103 Details

SQL Server Error: 103 Severity: 15 Event Logged or not: No Description: The %S_MSG that starts with ‘%.*ls’ is too long. Maximum length is %d. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

SQL Server Error 103

SQL

SQL Server Error : 102 Details

SQL Server Error: 102 Severity: 15 Event Logged or not: No Description: Incorrect syntax near ‘%.*ls’. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

Solution for Resolving the Error

SQL Server Error Code and solution summary

SQL … Read the rest

SQL Server Error : 101 Details

SQL Server Error: 101 Severity: 15 Event Logged or not: No Description: Query not allowed in Wait for. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

Solution for Resolving the Error

SQL Server Error Code and solution

SQL Server Error : 104 Details

SQL Server Error: 104 Severity: 15 Event Logged or not: No Description: ORDER BY items must appear in the select list if the statement contains a UNION, INTERSECT or EXCEPT operator. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go… Read the rest

SQL Server Error : 33027 Details

SQL Server Error: 33027 Severity: 0 Event Logged or not: No Description: Failed to load cryptographic provider ‘%.*ls’ due to an invalid Authenticode signature or invalid file path. Check previous messages for other failures. Severity 0 Description: Informational messages that return status information or report errors that are not severe. The Database Engine does not raise system errors with severities of 0 through 9.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location … Read the rest

SQL Server Error : 127 Details

SQL Server Error: 127 Severity: 15 Event Logged or not: No Description: A TOP N value may not be negative. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

Solution for Resolving the Error

SQL Server Error Code and

SQL Server Error : 125 Details

SQL Server Error: 125 Severity: 15 Event Logged or not: No Description: Case expressions may only be nested to level %d. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

7. Sort order for search results:- N’asc’ = ascending, N’desc’ … Read the rest