Comments
Sort by recent activity
I'm not using SQLExpress, however I had the same issue. This is what I did to fix it. I had to allow TCP/IP on the server network configuration, it wasn't defaulted to being enabled after a new install of SQL 2005.
In the Start Menu...
Microsoft SQL Server 2005 \ Configuration Tools \ SQL Server Configuration Manager
In the program...
SQL Server 2005 Network Configuration \ Protocols for MSSQLSERVER \ TCP/IP.
Right click on TCP/IP and select Enable.
Close any SQL related programs, restart all the SQL services.
Note: I did not have to enable named pipes.
kind regards,
-Casey Plummer / comments
I'm not using SQLExpress, however I had the same issue. This is what I did to fix it. I had to allow TCP/IP on the server network configuration, it wasn't defaulted to being enabled after a new i...