Home » SQL Server Errors

SQL Server Errors

sql server DBA 999

SQL Server- Unable to connect to SQL Server Error 26

Error Description:

SQL server error 26- Unable to connect to SQL Express Error: 26-Error Locating Server/Instance Specified

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

SQL Server- Unable to connect to SQL Server Error 26

Error Details: this sql server error 26 error locating server instance message is often encountered when connection to a SQL Server is tried and don’t know where to start to solve the problem.

We get this sql server error 26 error message only … Read the rest

sql server DBA 999

SQL Server Error : 21899 Severity: 0. The query at the redirected pu

SQL Server Error : 21899 Details

SQL Server Error: 21899 Severity: 0 Event Logged or not: No Description: The query at the redirected publisher ‘%s’ to determine whether there were sysserver entries for the subscribers of the original publisher ‘%s’ failed with error ‘%d’, error message ‘%s’. 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 … Read the rest

sql server DBA 999

SQL Server Error : 135, Severity: 15. Cannot use a BREAK statement outside the

SQL Server Error : 135 Details

SQL Server Error: 135 Severity: 15 Event Logged or not: No Description: Cannot use a BREAK statement outside the scope of a WHILE statement. 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

The parameters for XP_READERRRORLOG are:
1. Value … Read the rest

sql server DBA 999

SQL Server Error : 136, Severity: 15. Cannot use a CONTINUE statement outside

SQL Server Error : 136 Details

SQL Server Error: 136 Severity: 15 Event Logged or not: No Description: Cannot use a CONTINUE statement outside the scope of a WHILE statement. 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

The parameters for XP_READERRRORLOG are:
1. Value … Read the rest

sql server DBA 999

SQL Server Error : 138, Severity: 15. Correlation clause in a subquery not per

SQL Server Error : 138 Details

SQL Server Error: 138 Severity: 15 Event Logged or not: No Description: Correlation clause in a subquery not permitted. 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

The parameters for XP_READERRRORLOG are:
1. Value of error log file we … Read the rest

sql server DBA 999

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

SQL Server Error : 139 Details

SQL Server Error: 139 Severity: 15 Event Logged or not: No Description: Cannot assign a default value to a local variable. 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

The parameters for XP_READERRRORLOG are:
1. Value of error log … Read the rest

sql server DBA 999

SQL Server- Unable to connect to SQL Express Error: 26-Error Locating Server/Instance Specified

Error Description:

SQL server error 26- Unable to connect to SQL Express Error: 26-Error Locating Server/Instance Specified

How to fix SQL server Unable to connect

Error Details: this sql server error 26 error locating server instance message is often encountered when connection to a SQL Server is tried and don’t know where to start to solve the problem.

We get this sql server error 26 error message only when we are trying to connect to a SQL Server named instance.

Every time we try to make a connection to SQL Server named instance, we will send a SSRP UDP packet to the server machine UDP port 1434. We need this step to know configuration information of the SQL instance, e.g., protocols enabled, TCP port, pipe name etc. Without … Read the rest

sql server DBA 999

SQL Server- a network-related or instance-specific error occurred while establishing a connection to sql server

SQL Server- a network-related or instance-specific error occurred while establishing a connection to sql server

Error Details or symptoms: Can not connect to a SQL server and you get a error a network-related or instance-specific error occurred while establishing a connection to sql server

This error is seen in SQL Express installation as its installed a named instance by default with name of instance as Servername/SQLExpress.

Some other Errors Similar:

provider: named pipes provider, error: 40 – could not open a connection to sql server which is covered here.

provider: sql network interfaces, error: 26 – error locating server/instance specified which is covered here.

Resolution:

If we are connecting from Windows PC/Client to Windows server/SQL Server (server with SQL Server … Read the rest

sql server DBA 999

SQL Server error 40 could not open a connection to sql server 2016

SQL Server error 40 could not open a connection to sql server 2016

Error related are:
error 40 could not open a connection to sql server

named pipes provider could not open a connection to sql server 53

invoke sqlcmd provider named pipes provider error 40 could not open a connection to sql server

named pipes provider could not open a connection to sql server 5 linked server

I have covered this error in another post as well which is here.

Cause of Error:

This error occurs when the SQL Server can’t be found on Network which means either IP address is not reachable or that the TCP port number is either not open or is not the correct port … Read the rest

sql server DBA 999

Microsoft SQL Server Error: SQL SERVER – Msg 102, Level 15, State 1, Line 2 Incorrect syntax near ‘)’ or msg 102 level 15 state 1 line 3 incorrect syntax near ‘ ‘

Microsoft SQL Server Error: SQL SERVER – Msg 102, Level 15, State 1, Line 2 Incorrect syntax near ‘)’ or msg 102 level 15 state 1 line 3 incorrect syntax near ‘ ‘

Details of Error:

This error message occurs if we use GETDATE() like function as a parameter to Stored Procedure or Function Statement. or the second error is pertaining to problem when inserting data can be solved by making the column not null and also can be made default to some value.

Actual error message:

Msg 102, Level 15, State 1, Line 2 Incorrect syntax near ‘)’.’

Resolution:

This problem can be solved by using a local variable for storing the value of Getdate() instead of passing GETDATE() … Read the rest