MS SQL Server

MS SQL Server

novotnyjannovotnyjan Posts: 1Questions: 1Answers: 0

I get following error message while attempting to connect to a MS SQL Server:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 – The specified network name is no longer available.) (Microsoft SQL Server, Error: 64)
what causes the problem?

Answers

  • tangerinetangerine Posts: 3,365Questions: 39Answers: 395

    How is this relevant to DataTables?

  • KuntumKuntum Posts: 1Questions: 0Answers: 0

    Go to the SQL Configuration Manager. (You can refer to the link above for a walk through with screen shots to get there)
    Expand the SQL Network Configuration and click on the PROTOCOLS node
    Right click on TCP/IP and open up the PROPERTIES panel
    Select the IP ADDRESS tab
    Make sure the values for the IP ADDRESS fields are correct and match the system it is running on.
    Restart the service, and you should be back in business, I was.
    On a side note, this is also the same place where lots of people get hung up when setting up remote access to a SQL Server instance.
    Make sure you fill in the TCP PORT, even if you are using the default 1433.
    7. Now extract and you should have your content without any errors out of RAR files.
    If you are still experiencing the issue read comments here:
    https://social.technet.microsoft.com/Forums/itmanagement/en-US/373cf033-d3f1-4f71-af02-a8a6b8d05828/sql-database-is-corrupted-plz-help?forum=sqltools

  • allanallan Posts: 63,689Questions: 1Answers: 10,500 Site admin
    edited July 2015

    Discussion closed, this is completely off topic - although @Kuntum thank you for offering a helping hand :-)

This discussion has been closed.