"[dbnetlib] SQL Server does not exist or access denied"
This often happens when you try to connect to a SQL Server named instance by using TCP/IP sockets. Although there are numerous reasons as to why you may encounter the failure, such as improper connection string, server offline, etc., it may be due to not having the TCP/IP protocol enabled within the SQL Server Configuration Manager tool. Try this procedure to see if it solves your problem:
- Go to Start > Programs > Microsoft SQL Server 2005 > Configuration Tools and click on SQL Server Configuration Manager.
- Expand the "SQL Server 2005 Network Configuration".
- Select "Protocols for MSSQLSERVER"
- In the right-pane set the TCP/IP to Enabled by right-clicking and selecting Enable.
- Click OK if prompted with a warning that it will not take affect until you restart.
- Close the SQL Server Configuration Manager.
- Open SQL Server Management Studio
- Connect to the database engine of the server instance you want to work on.
- Right-click and select Restart. Answer yes to any other services that will be restarted as well.
0 comments:
Post a Comment