Home » SQL Server Error : 161, Severity: 15. Rule contains more than one variable.

SQL Server Error : 161, Severity: 15. Rule contains more than one variable.

sql server DBA 999

SQL Server Error : 161 Details


SQL Server Error: 161
Severity: 15
Event Logged or not: No
Description:
Rule contains more than one variable.
Severity 15 Description:
Indicates syntax errors in the Transact-SQL command.

Causes for SQL Srver Error 161

Sql Server Odbc Driver In client Side where we face SQL Server Error: 161 And SQL Server Error: 17

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

By default, we have 6 Server Error Logs kept but we can increase the number of SQL Server Error Logs from the default value of six.

For other ways to read and find error log location please our article https://sqlserver-dba.co.uk/error-log/sql-server-identify-location-of-the-sql-server-error-log-file.html

Solution for Resolving the Error

Check whether the tcp/ip protocol for SQL is enabled for error number 17.

Configuration Tools >> SQL Server Configuration Manager >> SQL Server 2005 Network Configuration >> Microsoft SQL Server 2005 TCP-IP is enabled.

For SQL Server 2005, the amed pipes and TCIP protocols are deactivated by default. Have you checked the “SQL server configuration manager” for them? The protocols can be found in SQL Server Network setup and SQL Native Client xx configuration.

The “Shared memory” protocol is used to establish the connection on the server.

SQL Server Error Code and solution summary


SQL Server Error: 161
Severity: 15
Event Logged or not: No
Description:
Rule contains more than one variable.

Leave a Reply

Your email address will not be published. Required fields are marked *