can't connect to sql server in microsoft visual studio express for the web

I am getting this error in visual studio express for the web 2013 when I try to click on my database

icons in the server explorer. It did not happen before yesterday when I had to uninstall and reinstall

sql server. The error is:

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 50 Local database runtime

error occurred. Cannot create an automatic instance. See the Windows application event log for error details.

Can you please give me any help?

June 18th, 2015 4:12pm

Hi,

For this problem, it would be better to post your question at SQL Forum:

https://social.technet.microsoft.com/Forums/sqlserver/en-US/home?category=sqlserver

Free Windows Admin Tool Kit Click here and download it now
June 19th, 2015 7:32am

Check that the server on which SQL Server is running can be accessible. You can use the ping command to test that. The ping command may be blocked by the firewall so make sure that ICMP is enabled in the firewall. 
For more info, check Windows Firewall Quick Fixes.
        Choose appropriate protocol
        Configure Windows firewall accordingly based on what protocol you have chosen to use. For detailed information about how to configure Windows Firewall to allow SQL Server, please check Configure the Windows Firewall to Allow SQL Server Access.
        Enable SQL Server Browser Services
You need to enable SQL Server Browser Services if the following are both true:
1.       SQL Server is not listening on default 1433 port or not use default pipe name \\.\pipe\sql\query;
2.       The corresponding TCP port or pipe name is not specified in the connection string (such as Srv1\SQL2008, 1500).
If you have enabled SQL Server Browser Services, you still need to open UDP 1434 port which is used by Browser Services in the Windows firewall.
You can also try this, under "Resolution for Windows 7 and Windows Server 2008 R2".
You may also need to check your access rights to the database. 
June 19th, 2015 11:22pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics