ado.net - .NET application will not connect to to SQL Server 2000 -


i've been pulling hair out on one. have legacy app (asp.net 2.0) have moved different machine , trying connect sql server 2000 database on same machine, failing every time general error:

a network-related or instance-specific error occurred while establishing connection sql server. server not found or not accessible. verify instance name correct , sql server configured allow remote connections.

what weird .net apps (windows or web). can connect fine - using windows or sql server authentication - enterprise manager, query analyser, server explorer in visual studio. works fine on xp machine, new setup in on win 7

  • i've checked tcpip enabled sql server , listening on port 1433.
  • the server setup mixed mode authentication. have tried both methods of trying connect. removed mixed mode , tried windows authentication , still did not work.
  • i have double checked using right server name\instance name , correct credentials.
  • port 1433 open on firewall (not matters - same machine)
  • i have rebooted, checked services etc - said, know running because can connect other means.

any ideas? different using connection string through ado.net?

update: funny - found out how answer here few minutes after posting question (though didn't realise related before): how specify port number in sql server connection string?.

this new machine had sql server 2008 express installed before 2000 got put on , though 2000 'says' listening on 1433, not. anyway, changed default port 2000 installation (to 1633 @ random) changed connection string server name\instance name server name,port. , loaded.

hopefully prevent having last few hours did....

answered more research on site few minutes later: please see question update details!


Comments

Popular posts from this blog

css - Which browser returns the correct result for getBoundingClientRect of an SVG element? -

gcc - Calling fftR4() in c from assembly -

.htaccess - Matching full URL in RewriteCond -