Last night, our Assets Management Server crashed and left us cramming. Our server admin gave us a temporary server where we can setup the application. The server is a Windows 2003 machine which has MS SQL Server 2000 installed. After an hour of data restoration, we tested our ASP.NET application and found the following error: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
The tricky about it is that we are using MS SQL 2000 and not 2005. We are quite sure that the remote connections was enabled and there were no firewall activated. To check if SQL is listening at port 1433, I tried the following:
1. using "TELNET AFE_Server 1433" on command prompt but it returns "connection failed".
2. Running the following command "osql -SAFE_Server,1433 -E" and the server returns "[DBNETLIB]SQL Server does not exist or access denied"
We are about to lose hope when out of nowhere I suggested to install SQL Service Pack 4. And like a miracle answered... It works!
For more SQL Server fixed and tips, subscribe now.
0 comments:
Post a Comment