November 12, 2007 at 5:37 am
Hi there,
Has anyone ever encountered problems making .Net applications connect to a SQL database on SQL 2000 with SP3a?
It's running on a virtual machine with a Windows Server 2000 Std with SP4, the .Net application is working with .Net Framework 1.1.4322.573. For some reason it can't connect to the SQL database using the specified username and password in the web.config file even though the user exists in the SQL database. I've tried using the SA password but this still doesn't work. I can logon to SQL Query Analyzer using the SA password but not using the other username.
The .Net application does work on other systems of mine all of which can run on Windows Server 2000 and 2003, I have compared them but can't find any differences.
Any ideas anybody?
Thanks,
Chris
November 12, 2007 at 6:34 am
I have a very similar situation: we use virtual machines for testing our application. the virtual machines can connect to dozens of sql servers on our network with no problem.
I just received a new server machine, and the machine does not have a default instance of SQL server on it...it has an 2000 instance named MSSQL, as well as a 2005 named SQLEXPRESS, but no default.
when developing from that new server machine, I can connect to any of the databases on either instnace , but my virtual machines cannot connect to the databases there;
specifically, if my machine is named "d223", the virtual instances cannot find the server D223\MSSQL or D223\SQLEXPRESS
I;'ve tried swtiching to ip address port number, like 192.168.0.91,1114 but i still can't connect to it yet. (port found with aa tsql script if you need it)
i'm thinking the lack of default instance might be the root of my connection problem to that specific server, but I'm still looking at it.
Lowell
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply