Sounds straight forward and generally a SQL connection is, but it had been some time since I had last installed a new version of SQL.
I downloaded Weight loss medication xenicalIs viagra cheaper in canadaCost of lexapro vs generic SQL Server Express 2014 from Microsoft’s site and installed with default options as I am prepping for a small project that will require a small web app with SQL backend.
After installing on my server, I installed the SQL server Management Studio on my workstation.
Once the server was installed and patches applied etc I attempted to connect to it from my workstation using SQL authentication as I don’t have an AD running currently and although I could use local credentials I opted not to.
When I connected to the instance I was greeted with this message:
From the server, I could connect locally without issue. I knew that SQL was up and working.
I checked the server’s firewall as well as DNS and general connectivity and there were no issues there.
After searching a bit on the web for the error, I found that this is related to a common new installation issue with the SQL server. One that I know that i have run into in the past but, again it has been some time since I had occasion to install a new SQL instance.
In the SQL Server Configuration Manager under the SQL Server Network Configuration option TCP/IP was disabled.
I opened the TCP/IP properties for the SQL instance in question and enabled TCP/IP and clicked ok. In order to continue the service will need to be restarted.
Once I restarted the service for the instance I was able to easily connect, Success!
Connectivity issue with new SQL instance installation
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 Interface, error: 28 – Server doesn’t support requested protocol) (Microsoft SQL Server)
Check the following:
- Make sure the server name you are using is correct
- check to ensure DNS is correct
- check general network connectivity
- check Microsoft firewall on the server
- check connectivity settings in Microsoft SQL server configuration manager