Connecting ASP.NET To MS SQL Server 2005 On Remote Server
Apr 11, 2008
hi,
I recently finished designing an ASP.NET website which connects to MS SQL Server 2005 on my local machine. I have now just uploaded my ASP.NET website to a remote server and the MS SQL Database to another remote server. Unfortunately when I try and access the database through the website I get an error - I believe this is due to the website still trying to connect the database to my local machine instead of the remote server.
In my web.config I have the following ConnectionString code:
<connectionStrings>
<add name="EcoHouse" connectionString="Server=localhostSqlExpress;Database=EcoHouse;Integrated Security=True" providerName="System.Data.SqlClient" />
<remove name="LocalSqlServer" />
<add name="LocalSqlServer" connectionString="Server=localhostSqlExpress;Database=EcoHouse;Integrated Security=True" providerName="System.Data.SqlClient" />
</connectionStrings>
I attempted to use Microsoft .NET Framework SDK 2.0 to configure the remote server. I entered the following however got an error:
Setting environment to use Microsoft .NET Framework v2.0 SDK tools.
For a list of SDK tools, see the 'StartTools.htm' file in the bin folder.
Unable to connect to SQL Server database.
I'm unsure on the code I need to use in order to connect the website to a database on a remote server instead of a local machine. If anyone knows or has any suggestions on the steps I need to take to connect the website approriately it would be very much appreciated.
Thanks
Daniel
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.
When my default.aspx page loads I get this error for the connection to my SQL 2005 DB. 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 have already gone to Surface Area Configuration to ensure that Remoting with both Named Pipes or TCP/IP is enabled and it's set to both for remoting.I verified that my local account has access to the DB.Not sure what else to check.
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 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 use ASP.NET 2.0 and VS.NET 2005. I have the following expression in my code: string connectionString = "server='localhost'; user id='sa'; password=''; Database='Northwind'"; When I executed the code I have 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)." The Microsoft Access was successfully connected in the Server Explorer window. How do I solve this problem? Thanks, Andy.
I'm using Visual Studio 2005 Pro and am attempting to connect to a remote SQL Server 2005. I have the server name, SQL login credentials, and database name. However, when I try connecting I get this 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)" I know that remote access is enabled because I received the connection instructions directly from the database administrator. I've tried turning off my firewall. I've tried connecting with Data source: Microsoft SQL Server using both Data providers: ".NET Framework Data Provider for SQL Server" and ".NET Framework Data Provider for OLE DB". Nothing seems to work. Any suggestions for what I may be doing wrong? Do I have to have certain software installed on my computer to make this work (other that VS2005)? -Mathminded
Hi. Im trying to get a asp.net web aplication to write data to an sql express server located on another server. However when i try to connect with VS 2008 it says: "Named pipes provider, error 40: - Could not open a connection to SQL server". What do i need to do to get this to work. Do i have to set something in the sql server, and i assume i have to open some ports in my firewall aswell? Any help sugestions would be aprichiated
I'm trying to connect to a sql server machine from another machine on the network and I'm getting this 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)" More information about the machines: All machines are on the same private netwrok, all in the same workgroup. Machine1: this is the DB server, Win 2003 server, it has SQL 2005 developer edition, .Net runtime 2.0. Machine2: trying to connect to machine 1, Win 2003 server, .Net runtime 2.0 On the DB server, TCP/IP is enabled with port 1433, also named pipes are enabled. I checked the ERRORLOG and it says it's ready for connections and it's listening...Also there are no firewalls between the machines, I also added the sql server service .exe and the sql explorere .exe to the windows firewall exceptions on the DB server (although it's disabled)... I'm not sure what else to do, I checked all sources online, applied anything related to this issue but not luck. This has wasted 3 hours of my time, this was a task that wouldn't take you a minute in older versions!! , Microsoft thinks it's making our life easier but in fact, I spend more time now on trouble shooting than before... Let me know if you have a solution.. thanks, Tamer
I am unable to connect to a remote server on Computer A from Computer B, but when I reverse it I am able to connect to a remote server on computer B from computer A. I have SQL Server 2005 Developer Edition on both computers. I am using the using the SQL Management Studio to connect. Both Computers have these settings
Using Surface Area Configuration both have local and remote connections checked. Both computers using tcp/ip only checked.
Using Configuration Manager both the sql server and the sql browser are running. Both computers have tcp/ip protocols enabled.
Under the server properties on both computers, under the Security Tab, I have SQL Server and Windows Authentication Mode checked. Under the Connections tab I have Allow remote connections on this server checked.
I believe I have the Security for both the server and databases done properly giving them both proper Logins and User Roles with the proper permission.
Also went to my window firewall settings and under the Exceptions tab, I added both the sql server.exe and sql browser.exe programs on both computers on my remote network.
But when I connect on Computer B, I get an error message stating:
TITLE: Connect to Server ------------------------------
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: 233)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
------------------------------ BUTTONS:
OK ----------------------------
I tried pinging server a and then server b and they both pinged.
Could someone please tell me what could be wrong on my remote computers.
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 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.
Here is the information that I have... ( ps all information is not the actuall information )
1) URL abc.somehostingcompany.com IP: 211.11.111.1 PORT: 1433 ( NOTE: if I go to a cmd promt and type in ping abc.somehostingcompany.com I get a response )
2) dbname = mydatabase
3) userUid = sa pwd = sa
Inside SQL Server Configuration Manager --> SQL Server Network Configuration --> Protocols for SQLEXPRESS, I enabled TCP/IP and Shared Memory. Inside the properties of TCP / IP, I made sure under the "IP Address" tab that the
IP1: Active = yes
IP1: Enabled = yes
IP1: IP Address = abc.somehostingcompany.com
IP1: TCP Dynamic Ports = 0
IP1: TCP Port = < empty string >
I clicked "OK", and I stopped and started the SQL Server 2005 Services --> SQL Server (SQLEXPRESS). Then I started up SQL Server Brower.
Lastly I go to SQL Server Management Studio Express and try to connect to this remote server and database and I keep getting timeout issues and a message saying that the default settings for SQL Server Express do not allow remote connectioning by default.
Any ideas what I could be doing wrong? Should I use the port number instead of Dynamic Ports? Should I use the real IP address? Does the LOG ON AS under SQL Server (SQLEXPRESS) properties need to be updated?
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 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'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 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
Hi All.. I am having a problem while connecting to a remote sql server through VS.NET 1.1 , an asp.net application. It says :"SQL Server does not exist or access denied". I have connected to the same server from my home using the same connection string through an asp.net 1.1 app.. So it cant b a prob with Server permissions. I can connect to the same server frm my office through asp.net2.0 app.. So its got nothing to do with office permissions. I need this connection from my office from asp.net1.1 app 2 debug n find solution for a bug as im unable to simulate it here. Will this be smth to do with .net installation, some security enabled in vs.net.. I have no idea.. Please help me at the earliest.. Thanks in advance.. aLLEN
