March 25, 2008 at 10:03 am
Hi,
I installed VS 2005 and SQL server 2005. Then I uninstalled SQL server 2005 and then installed SQL server 2000. When I try to connect to SQL 2000 it gives me 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."
Please help to solve this problem. I just want to connect to SQL server 2000. But it seems VS 2005 try to connect to SQL 2005.
Manuka.
March 26, 2008 at 7:09 am
I had the same problem but I don't remember how I fixed it 😀
It could be one of the following :
- Try using another protocol in the ODBC client configuration of your data source (if you are using ODBC of course).
- If you are using windows authentication, do not log in under an account with an empty password.
Patrick Duflot
March 26, 2008 at 10:09 pm
Thats the generic "I can't connect to the SQL server" that .NET 2.0 uses. The hint about SQL 2005 is less than useless in my opinion, because this message means your .NET 2.0 can't even find the SQL server, much less determine what version it is. :crazy:
The three likely most likely causes of this, based on troubleshooting that exact message at clients for 2 years, are:
Make sure the server\instancename in your connect string is correct. VS 2005 tends to default to an instance of SQLEXPRESS, which will more than likely be wrong.
SQL isn't running. Go to C:\Program Files\Microsoft SQL Server\80\Tools\Binn and run the file called SQLMANGR.EXE, this will let you start the SQL service if its not running.
Least likely is a firewall issue. I'm assuming this is a local installation, SQL and Visual Studio on the same computer. If thats the case, firewall is probably not the issue, but if the SQL server is on another computer, make an exception for SQL server in Windows Firewall. The specific file is C:\Program Files\Microsoft SQL Server\MSSQL.xxx\Binn\SQLServr.exe, where MSSQL.xxx will be different on your machine depending on instances.
March 27, 2008 at 11:52 pm
Seems it tries to conenct it MSSQL 2005 ?How to configure SQL Server 2005 to allow remote connections
Can you check the port Number:
1) Right-click the server instance in Enterprise Manager, select 'Properties'
2) Under "General" tab, click the "Network Configuration"
3) Highlight the "TCP/IP" in "Enable Protocols"
4) CLick "Properties" button, it should be "1433"
How you try to connect? Have you try to include the port number in your connection string?
Data Source=190.190.200.100,1433;Network Library=DBMSSOCN;Initial Catalog=myDataBase;User ID=myUsername;Password=myPassword;
March 28, 2008 at 7:40 am
Seems it tries to conenct it MSSQL 2005
Then I uninstalled SQL server 2005 and then installed SQL server 2000. When I try to connect to SQL 2000 it gives me the following error.
This is why I said the error message is less than useless. He clearly said he removed SQL 2005, and installed SQL 2000, but the message fooled you into thinking SQL 2005 is involved.
All that message means is the .NET 2.0 client cannot find the SQL server specified. Doesn't matter if the server is SQL 7/2000/2005/2008. Since it did not find a server, it has no idea if a server even exists, so giving hints about SQL 2005 is deceptive in my opinion.
It could be a bad connection string, could be a firewall, could be the network down between the client and the server, could be SQL server not running.
If he had the wrong database name, or the authentication failed, it would be a different error message.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply