Error Connecting To Remote SQL Server 2000 From ASP.NET 2.0
Jul 11, 2007
My environment is Windows Server2003, ASP.NET 2.0, SQL Server 2000 using SQL authentication (names of DB's, sql id's, passwords are identical on both servers)
My web application successfully connects to my database the web app and the DB are both on the same server (10.144.25.9).This connection string works:
The problem occurs when the DB is mpved to the remote SQL Server (10.144.25.10). I use almost the identical connection string except for the IP address which is changed to the remote machine. The db name, user, password is same on remote machine as on the local, so everything should work but does'nt. This connection string fails:
error (odd error in that I'm connecting to SQL 2000?) -
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 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: 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 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.)
There is no DBA on this project, I'm not sure this is a SQL Server set up problem?
I'm experiencing a problem connecting to a SQL 2000 server through my ASP code. My connection string is as follows: <add name="TheConnectionString" connectionString="driver={Sql Server};provider=MSDASQL;server=10.0.1.42;database=dbname;uid=*********;pwd=*********" providerName="System.Data.Odbc" /> The problem doesn't occur when I run my ASP code from my workstation using VS.NET's builtin webserver. It makes the connections and executes the CRUD commands successfully. However, when I publish my site to the webserver (which resides on 10.0.1.16) it fails out with the following error: System.Data.Odbc.OdbcException: ERROR [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.ERROR [01000] [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). I've verified that the webserver can talk to the DB server by connecting to the remote DB server through SQL Enterprise Manager running locally on the webserver. If I try to do this with a DSN I get the same results. I get the same error from any other webserver on the internal network. The difference between my workstation and the internal network is that I'm using a VPN to connect to our internal network while the webservers are physically connected to it. Firewalling isn't the issue in this case because the webservers and DB server are on a trusted network. I've seen other ways of connecting to the DB server including using Named Pipes (which I would rather not do because I don't want to setup a named pipe on the production db server). I'm relatively new to ASP.NET 2.0, so the above connection string is an adaptation of some old ASP code. If anybody has any suggestions on a better way to construct this connection string, please let me know. I've been racking my brains trying to get this to work outside of the devel env.
I get the following error message in quotes. I have a web application written in ASP.NET 2.0 through which I am trying to connect to a remote SQL Server 2000. My operating system is Windows Vista . I looked at many different sites to find a solution for this but without any luck. I am sure someone would have seen this issue here and I expect them to shed some light. 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 connection string is located in my web.config file which looks like <add name="AMSConn" connectionString="Data Source=xxxx;Initial Catalog=testdb;User ID=sa;Password=xxxx" providerName="System.Data.SqlClient" /> I want to get this issue resolved and I need you guys help. Please let me know if you need any more information. Thanks Bharat
I have been assigned to make a database in some remote machine.The machine has MSSQL 2005.I need to connect to that remote machine's sql server via my pc using my SQL Management express.I do have that computer's IP address(say,123.456.789.000),and the username and password.But when i try to connect to the server ,I get the following error:
Cannot connect to 123.456.789.000sqlexpress
An error has occured while establishing a connection to the server.When connecting to SQL server 2005,this failure may be caused by the fact that unser the default settings SQL server does not allow remote connections,(provider: SQL Network Interfaces,error:26-Error Locating Server/Instance specified)(Microsoft SQL Server)
I am a new programmer and dont know much.But i guess the problem is not in my server but in that server to which i am trying to connect.I guess that server has some instance created or it does not allow remote connections.But i am not sure.Is it so?Or is anything wrong in my server.Any ideas?
I am attempting something that I have done many times before; however, in this instance it continues to fail.
I am trying to connect Management Studio to an instance of SQL Server 2005 Express over a VPN. The Management Studio connect dialog always fails with Error 26.
I have:
Enabled the instance for remote connections €“ both TCP/IP and Named Pipes
Ensured that the instance is enabled for TCP/IP on the VPN address (10.2.1.1) and on port 1433
Ensured that the instance is running
Ensured that SQL Browser is running
Ensured that ports 1433 (TCP) and 1434 (UDP) are open on the firewall for inbound traffic
Rebooted the server following this configuration to ensure that the instance services are refreshed
Tried to connect from three separate clients (albeit on the same remote network)
Disabled the firewall to ensure no further complications (as a last resort)
I have this exact same setup functioning on a separate server.
There is an additional backstory to this problem; however, I will not complicate the scenario with it now. If you feel you can help then I can elaborate further on the server€™s history.
I am trying to connect to a remote sql server 2005. So I have install the Microsoft SQL Server Management Studio Express. When I try to connect I get the error below.
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) (Microsoft SQL Server, Error: 53). Can some one please help. I have even port no 1533 on my pc. Thanks.
My site works fine in VWD2008 express, but I get this error when I try to use it on my live website. 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. According to this article: http://support.microsoft.com/kb/914277 I am supposed to:
1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration. Ok, there is no such program in this folder. The only thing in there is "SQL Server Error and Usage Reporting"... The other thing I am greatly concerned with is this: All is want is for my webpages to be able to access my database for user authentication. I DO NOT want to grant the internet rights to remote connect to my database.
I get the following error and have been trying to figure out why I keep getting it. Initially, I had placed my project under wwwroot folder and ran it under IIS and it gave this error. Then I moved it to my local C drive and same thing. I am sharing this project with two other co-workers and all our config files and code files are same...they don't get this error but I do. I checked that SQL Server Client Network Utility has TCP/IP and the 'Named Pipes' enabled. I thought maybe I have setting in the Visual Studio 2005 that I'm not aware of that's causing this problem...it can't be the server since my co-workers aren't having this error and can't be anything in the code since all of us are sharing this project through vss. I dont' think using different version of .net framework can create this error. I changed the version from 2.0 to use 1.1x and it gave same error... Any help would be greatly appreciated. Thanks in advance.
Server Error in '/RBOdev' Application.
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +739123 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +685966 System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +109 System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +383 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +181 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197 System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.GetConnectionHolder() +16 System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.LoadPersonalizationBlobs(WebPartManager webPartManager, String path, String userName, Byte[]& sharedDataBlob, Byte[]& userDataBlob) +195 System.Web.UI.WebControls.WebParts.PersonalizationProvider.LoadPersonalizationState(WebPartManager webPartManager, Boolean ignoreCurrentUser) +95 System.Web.UI.WebControls.WebParts.WebPartPersonalization.Load() +105 System.Web.UI.WebControls.WebParts.WebPartManager.OnInit(EventArgs e) +497 System.Web.UI.Control.InitRecursive(Control namingContainer) +321 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +692
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
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,
Hi,I have SQL Server Express Edition. I tried working out some ASP.NET Labs in my local system. Here is the link of the Virtual Lab which I tried. http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032286906&EventCategory=3&culture=en-US&CountryCode=USI recieve this error in my local system. 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)I tried working out solutions from various websites. But the no solution is effective. Could anyone help me in solving this issue.
I'm new to using VS2005 and this is my first project connecting to our MS SQL 2000. App worked fine on my dev PC, connection to the same MS SQL Server. Published the web site to the web server (same server running MS SQL Server) and getting the below error. Is this a permission setup problem on SQL Server or does it really think it's connecting with a MS SQL 2005 database? 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) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: 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)
Hi, Here is the syntax of the connection string within the web.config file:<connectionStrings><clear /> <add name="MyConnectionString" connectionString="Data Source=000.000.000;Initial Catalog=Database Name;Persist Security Info=True;User ID=XXXXXX;Password=XXXXXX;" providerName="System.Data.SqlClient" /> </connectionStrings> The test page has a GridView in it which uses the connectionstring fron the web.config file. Error Message:
Facts:1. I am using my account on Godaddy trying to connect to my sql server db.2. I can get into my db using user id and password.3. Godaddy's help file shows this for a connection string: connectstr = "Driver={SQL Server};SERVER=" & db_server & ";DATABASE=" &db_name & ";UID=" & db_username & ";PWD=" & db_userpassword4. My connection string: "Server=whsql-v09.prod.mesa1.secureserver.net;uid=dbasolutions;pwd=***;database=DB_87972;" & _ "Trusted_Connection=False providerName=System.Data.SqlClient"{password **** out}5. Get error message 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) I tried to email Godaddy's help desk with this information. There first response: We do not allow remote connections to our sql server database.There second response was to read the help file!Does anybody have any suggestions? Thanks in advance,bswanson
Hi,I have SQL Server Express Edition. I tried working out some ASP.NET Labs in my local system. Here is the link of the Virtual Lab which I tried. http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032286906&EventCategory=3&culture=en-US&CountryCode=USI recieve this error in my local system. 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)I tried working out solutions from various websites. But the no solution is effective. Could anyone help me in solving this issue.
I have been reading every resource available out there about getting this connection to work. Can someone help me diagnose what the problem is? As the client, what ports do I need to have open? I'm using ReliableSite.net web hosting and trying to connect to their sql server.
I've also asked for help on their forum and opened a ticket to see if perhaps its listening on a different port, but they say its my issue.
For reference: http://forum.reliablesite.net/index.php?topic=232.0
Hi all, I have an application in asp.net 2.0 and iam trying to connect database which is in remote server(Sql server 2000).But iam getting error as follows: 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) i know this is because asp.net 2.0 try to connect sql serverexpress by default.i have removed sql server express from my machine,Still iam getting the same error..any body have an idea how to solve this ... regards anitha
I need to connect to a remote sql server. this is the information i have:
IP address: http://222.224.222 database name: db1 uid: exampleuser pwd: examplepwd
what would be my connection string? here is my connection string that didn't work "Server=http://222.224.222;Database=XyberToursSQL;Uid=exampleuser;Pwd=examplepwd;" i get a invalid connection error
I have a web application installed on a server. I want to connect to a remote database server. I have access to both the servers, I can assign any user privileges or settings that are needed. How do I do this? I tried it the usual way, specifying the conn string and opening the conn, and expectedly it throwed an sql server does not exists error.
I've got a desktop and a notebook and both are connected to the router. On both I've got Sql Server Express and Sql Server Management Studio Express installed. I need to connect to a remote Sql Server (using user ID and password) which works fine on my desktop, but fails on my notebook: Error:0 and Error: 10060.
I checked all router settings and notebook settings, but I don't know what I am doing wrong. I got myself another notebook and installed Sql Server Express plus Management Studio, which did not work either.
I have recently taken over as webmaster at my company and need help connecting to our remotely hosted SQL server. The company who is hosting it will charge me "support time" to explain how to connect to it.
The database is used to store data and application information for our customer service center. So it is ALL database driven...
i have installed SQL Server Enterprise Manager on my machine, but have no ideas on where to even being trying to connect. I have the name of the server, password....etc. But do not know where to configure a connection.
ALSO, when i install my Enterprise Manager the first options askes me whether i want to create a new instance of SQL server on a local or remote machine....i am guessing my local machine right...??
i have sql server 2000 running on a windows server 2003 machine but have my web application on another windows xp machinei'm getting access denied from the client machine.... the 2 computers are connected by workgroup.. anyone can tell me how and what i need to do to connect to the sql server thanks
Hello I wrote a web app (vb.net) with mssql 2005 express edition DB. I created a vs2005 setup project and added it to my app solution. On my local computer it works fine (using IIS 5.1). Now, I'm trying to deploy the app on a remote server (with mssql 2005 express edition installed) but when I try to run my app via the remote server's IIS, I get this Error message: ERROR: Could not connect to database. 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). My app connectionstring looks like that: <connectionStrings> <add name="SiteSqlServer" connectionString="Data Source=localhost;AttachDbFilename=C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataMaxinet.mdf;Integrated Security=True;User Instance=False" providerName="System.Data.SqlClient" /> <add name="MaxinetConnectionString" connectionString="Data Source=localhost;AttachDbFilename=C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataMaxinet.mdf;Integrated Security=True;User Instance=False" providerName="System.Data.SqlClient" /> </connectionStrings> <appSettings> <add key="SiteSqlServer" value="Data Source=localhost;AttachDbFilename=C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataMaxinet.mdf;Integrated Security=True;User Instance=False"></add> Can anybody tell me what I'm doing wrong and how to fix it
I am currently developing a 2.0 asp.net application from my home pc (Windows XP) and am trying to connect to a sql server on my host. This works fine at work but at home I just get the following error message: 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) Any ideas, i have even tried disabling my firewall to see if that made a difference. Your help is much appreciated.
Hi guys ,I connect to internet using a proxy for example 122.158.190.5 : 8080 Most software read it from IE setting and in some cases I have to enter this proxy setting manually so that software can connect to the internet . I want to connect to a remote server using "SQL Server Management Studio" but it doesn't connect. And I couldn't find any proxy setting . How can I set this proxy setting ?And also I need to connect with may asp.net program to that remote server from my local computer how can I set this one ? Thank you in advance .
Hello everybody! Can anyone tell me what steps i should follow in order to get my web site (which is hosted with a web host in ireland) to connect to yet another server (different country) where SQL Server 2005 will be running? Thank you! - Callam
Hey guys, I am new to the SQL server scene and I am having some trouble connecting to a remote SQL Server with SQL Server Management Studio Express. I have the username, password, IP address, and port necessary to log in but am apparently not plugging them into the correct places. Can anyone at all point me in the right direction or somewhere that I might at least find the answer? I appreciate any help that can be provided.
I have set up a SQL Server 2005 to use for testing before moving to another production server. The server works fine when I connect to it with a program on the same computer but not when accessed remotely.
I have set it to to allow remote connections and use TCP IP only and have opened TCP port 1433 on the Windows XP firewall and am using the Teredo service on Port UDP 3544 Also the Server Browser service is running. The server is connected directly to the internet on a static IP (eg. 67.156.18.167) I have set the server to Windows authentication.
When I try to connect to the database from a data grid in Visual Studio on another computer it fails.
I am pretty surethat the problem is that I am not giving the correct information when asked to fill in the information for the data source to find the server as I am new to remote connections in SQL Server.
I've written a piece of database software in Visual Basic (Visual Studio 2005) to use in my office. My office has networked computers all connected to a server (windows server 2003). I have an old-ish version of SQL server on the server computer (version 7). The software works perfectly within the office environment - each computer on the network connects to the SQL server on the server computer and works very efficiently.
I now want to be able to access the database from home by running the software on my home PC. I want the software to somehow connect to SQL server in the office over the internet. Having read many of the threads about remote SQL server connections, I feel totally out of my depth. I vaguely understand that SQL server needs to be somehow configured to receive connections from the 'outside world'. I don't know how to do this. I also don't know what I need to do on the Windows server to allow this to work. I thought I might be able to use the computer's IP address in the connection string, but using IPconfig on the server I only get network IP addresses - the server may be behind a router... How do I get the proper internet address? Once I've set up the server side to work with remote connections, how do I get my software to communicate with that server? Do I just need to change the connection string and that's it? What would the format of the connection string be?
I'm very sorry for asking so many questions in one go! I have ended up a bit frustrated after reading many threads and articles about SQL remote connections - it's all rather advanced and don't understand most of it!
Thank you very much in advance for any help you can provide.
I can connect to a remote SQL server with ADO.NET but not with OLEDB.
I get
------------------------------
Test connection failed because of an error in initializing provider. Login timeout expired 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. Named Pipes Provider: Could not open a connection to SQL Server [233].
------------------------------
Through the SQL Server Connection Manager, if I disable Named Pipes and enable TCP/IP, I get for OLEDB connection:
------------------------------
Test connection failed because of an error in initializing provider. Unable to complete login process due to delay in opening server connection
------------------------------ with Connection and General Timeout are both 0. Appreciate the help
I am quite new to sql server 2005. Now I am going to develop a new asp.net application connecting to sql server 2005 remotely. So what must I have install in order to connect to a remote sql server and also to enable me build the tables too? What are the softwares that I need to install before I can proceed on this ? If possible I wnat to avoiding installing the whole server into my local machine as I dont need it. Thanks.
I am using Visual Studio 2005 with SQL Server 2000. I'm having an issue where I can build my website just fine for long periods of time, and then for what appears to be no reason, my site errors out when trying to connect to the database with the message below -- the thing is I don't want to use a SQL Server 2005 database, nor do I have Server 2005 or Server Express loaded. How can I unhook this and make it use SQL 2000?"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.) "
I am trying to connect to a sql 2k database using a Microsoft Application block. I get the following error. It is saying about 2005, I verified that SQL 2K is running on the server. System.Data.SqlClient.SqlException: 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
