November 5, 2018 at 5:39 pm
A SQL 2017 dev instance stopped responding while watching a trace using profiler today. The service can be stopped and restarted from SQL Config Mgr. I've uninstalled and re-installed SQL Server 2017 and SSMS. No errors are reported in the logs that I can find. I can connect to instances of SQL 2008R2 and SQL 2012 on the same machine. I've tried all of the client configuration connection options for SQL 2017, and tried using the listening port found in the startup log and nothing allows a connection. The only change to the system recently was an upgrade to SSMS V 17.9. Where can I look to find more details about ports in use or event log entries? ODBC finds it through SQL browser as well as SSMS, but can't connect using SA or network credentials.
Server error message:
"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: 28 - Server doesn't support requested protocol) (.Net SqlClient Data Provider)"
November 5, 2018 at 5:46 pm
notifications 61467 - Monday, November 5, 2018 5:39 PMA SQL 2017 dev instance stopped responding while watching a trace using profiler today. The service can be stopped and restarted from SQL Config Mgr. I've uninstalled and re-installed SQL Server 2017 and SSMS. No errors are reported in the logs that I can find. I can connect to instances of SQL 2008R2 and SQL 2012 on the same machine. I've tried all of the client configuration connection options for SQL 2017, and tried using the listening port found in the startup log and nothing allows a connection. The only change to the system recently was an upgrade to SSMS V 17.9. Where can I look to find more details about ports in use or event log entries? ODBC finds it through SQL browser as well as SSMS, but can't connect using SA or network credentials.Server error message:
"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: 28 - Server doesn't support requested protocol) (.Net SqlClient Data Provider)"
Did you check to make sure you have more than Shared memory protocol enabled? And are remote connection allowed for the instance?
Sue
November 5, 2018 at 6:07 pm
I've tried all of the connection option listed as available.
A working instance on the current Win 10 dev box just stopped allowing any connection. It starts to suggest another app or service grabbed the port it's trying to use.
Ken
November 5, 2018 at 6:24 pm
Success - I started SQL with the -f flag for minimal configuration and was able to connect using SSMS. I checked all of the required DB settings, saved and restarted the instance. I can now connect using SSMS without the startup flag. I'll run some profile traces to see if I lose connectivity again.
Thx,
Ken
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply