May 10, 2006

213 words 1 min read

Ah, SQL 2005 is RETARTED

So we’ve been trying to get one of the testing machines up on SQL 2005 with our product. After all, its still SQL, it should work just fine. Well it didn’t. We tried to connect with the Enterprise Manager using TCP/IP and it refused to work. We tried and tried and tried, but here’s the error we got:

TITLE: Connect to Server

——————————

Cannot connect to TOWER2.

——————————

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 — No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061)

For help, click: <a href=http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10061&LinkId=20476>Here

——————————

BUTTONS:

OK

——————————

Long story short, TCP/IP Connections are disabled by default, because Microsoft thinks that no one uses it. Just dandy… Anyways to fix: Open up “SQL Server Configuration Manager”. Open up the two “Protocols” sub-menu’s and enabled TCP/IP. Also, on one dev machine it was listed as enabled but still didn’t work — so we disabled and re-enabled and it fixed it. YMMV. Make sure to restart MSSQLServer afterwards. Yay Microsoft — you fail again!