Categories: SQL Server

SQL Server Error : 258, Severity: 15. Cannot call methods on %ls.

SQL Server Error : 258 Details


SQL Server Error: 258
Severity: 15
Event Logged or not: No
Description:
Cannot call methods on %ls.
Severity 15 Description:
Indicates syntax errors in the Transact-SQL command.

Cannot connect to Server, 1433\InstanceName.

ADDITIONAL INFORMATION: 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: TCP Provider, error: 0 – The wait operation timed out.) (Microsoft SQL Server, Error: 258)

The wait operation timed out

Solution for Resolving the Error

  1. Check that ping the target server from the computer the package is running on? If not, the server may be down or there may be routing or DNS issues
  2. Try a telnet session to the server using the port number? If not, SQL Server may not be running
  3. Make sure spelling of the server and instance name is correctly typed?
  4. Make sure the target server have TCP enabled in SQL Server Configuration Manager?
  5. Try connect to the server from anywhere else?
  6. Make Sure SQL Server Browser running on the target computer, or make sure you did supply the port number in the connection string?

Alternate Solutions

  1. Restarting SQL Server Service(non production instances only)

  • To Restart, Start or Stop the SQL Server instance by right click on sql server instance in SSMS or in SQL. You may need to open SSMS as administrator to start, stop the instance.

  • Other ways for restarting SQL server Service

  1. Running SQL Configuration manager from Start menu to restart services
  2. From Services in Windows server
  3. Running Command prompt Cmd using net start and net stop

SQL Server Error Code and solution summary


SQL Server Error: 258
Severity: 15
Event Logged or not: No
Description:
Cannot call methods on %ls.

Make sure SQL Server is running and reachable. TCP enabled etc..

Vamshi B

Recent Posts

sql server detected logical consistency based error

Learn about SQL Server detecting logical consistency based issues and how to resolve them.

5 months ago

sql server error 1222

Learn about SQL Server error 1222 and how to resolve the lock request time out…

5 months ago

Microsoft SQL Server 2022 New Features

Discover the new features of Microsoft SQL Server 2022 and how they compare to previous…

5 months ago

SQL Server Error 1222 lock request time out period exceeded

SQL Server Error 1222 lock request time out period exceeded   Lock request time out…

6 months ago

SQL Server Error : 427, Severity: 20. Could not load the definition for constr

SQL Server Error : 427, Severity: 20. Could not load the definition for constraint ID…

10 months ago

SQL Server Error : 204, Severity: 20. Normalization error in node %ls.

SQL Server Error : 204, Severity: 20. Normalization error in node %ls.

10 months ago

This website uses cookies.