| Groups | Blog | Home |
asp.net : ASP.NET 2.0 and connection to remote SQL 2000 server
that may include changing that information in the web.config file... This is my connection string: Server=ADDRESS TO SERVER!;Database=SOX;User ID=userxxx;Password=******; [quoted text, click to view] "Mitya Mitriev" <aaa@stopspam.org> wrote in message news:uTDAaqMuGHA.4460@TK2MSFTNGP04.phx.gbl... > Hi > I created ASP.NET 2.0 web application that uses SQL Server 2000 database > and > it works perfectly when website and Sql server were on local machine. > > Then I installed application on production server. Database is placed on > another server. > I received the 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) > > Why it thinks I am trying to connect to SQL Server 2005 ? There is no any > 2005 server on remote server! > > This is my connection string: > Server=servername;Database=SOX;User ID=userxxx;Password=******; > > Query Analyzer and Enterprise Manager connect perfectly (when installed on > production server) to database server! Then I created small console > appplication which uses the same data layer as web application (and > connection string ) - it connected to remote database too! Only ASP.NET > 2.0 application couldn't connect to remote Sql server 2000. > > Can anyone help? > >
Hi
I created ASP.NET 2.0 web application that uses SQL Server 2000 database and it works perfectly when website and Sql server were on local machine. Then I installed application on production server. Database is placed on another server. I received the 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) Why it thinks I am trying to connect to SQL Server 2005 ? There is no any 2005 server on remote server! This is my connection string: Server=servername;Database=SOX;User ID=userxxx;Password=******; Query Analyzer and Enterprise Manager connect perfectly (when installed on production server) to database server! Then I created small console appplication which uses the same data layer as web application (and connection string ) - it connected to remote database too! Only ASP.NET 2.0 application couldn't connect to remote Sql server 2000. Can anyone help?
Mitya i think you might need to take some additional steps
See this page at :http://www.datamasker.com/SSE2005_NetworkCfg.htm Hope that helps Patrick [quoted text, click to view] "Mitya Mitriev" <aaa@stopspam.org> wrote in message news:exiqP3NuGHA.3912@TK2MSFTNGP03.phx.gbl... > Do you mean IP address? I tried, it didn't help :( > > "Henry" <atnorthend_SPAM_@hotmail.com> wrote in message > news:%235WiFKNuGHA.5076@TK2MSFTNGP04.phx.gbl... >> Try changing the connection string to reflect the actual address to >> server, that may include changing that information in the web.config >> file... >> >> This is my connection string: >> >> Server=ADDRESS TO SERVER!;Database=SOX;User ID=userxxx;Password=******; >> >> "Mitya Mitriev" <aaa@stopspam.org> wrote in message >> news:uTDAaqMuGHA.4460@TK2MSFTNGP04.phx.gbl... >>> Hi >>> I created ASP.NET 2.0 web application that uses SQL Server 2000 database >>> and >>> it works perfectly when website and Sql server were on local machine. >>> >>> Then I installed application on production server. Database is placed on >>> another server. >>> I received the 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) >>> >>> Why it thinks I am trying to connect to SQL Server 2005 ? There is no >>> any 2005 server on remote server! >>> >>> This is my connection string: >>> Server=servername;Database=SOX;User ID=userxxx;Password=******; >>> >>> Query Analyzer and Enterprise Manager connect perfectly (when installed >>> on production server) to database server! Then I created small console >>> appplication which uses the same data layer as web application (and >>> connection string ) - it connected to remote database too! Only >>> ASP.NET 2.0 application couldn't connect to remote Sql server 2000. >>> >>> Can anyone help? >>> >>> >> >> > >
Thank you, but I use Sql Server 2000.
[quoted text, click to view] "Patrick.O.Ige" <naijacoder@hotmail.com> wrote in message news:Oup2SRPuGHA.4648@TK2MSFTNGP04.phx.gbl... > Mitya i think you might need to take some additional steps > See this page at :http://www.datamasker.com/SSE2005_NetworkCfg.htm > Hope that helps > Patrick > > > "Mitya Mitriev" <aaa@stopspam.org> wrote in message > news:exiqP3NuGHA.3912@TK2MSFTNGP03.phx.gbl... >> Do you mean IP address? I tried, it didn't help :( >> >> "Henry" <atnorthend_SPAM_@hotmail.com> wrote in message >> news:%235WiFKNuGHA.5076@TK2MSFTNGP04.phx.gbl... >>> Try changing the connection string to reflect the actual address to >>> server, that may include changing that information in the web.config >>> file... >>> >>> This is my connection string: >>> >>> Server=ADDRESS TO SERVER!;Database=SOX;User ID=userxxx;Password=******; >>> >>> "Mitya Mitriev" <aaa@stopspam.org> wrote in message >>> news:uTDAaqMuGHA.4460@TK2MSFTNGP04.phx.gbl... >>>> Hi >>>> I created ASP.NET 2.0 web application that uses SQL Server 2000 >>>> database and >>>> it works perfectly when website and Sql server were on local machine. >>>> >>>> Then I installed application on production server. Database is placed >>>> on another server. >>>> I received the 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) >>>> >>>> Why it thinks I am trying to connect to SQL Server 2005 ? There is no >>>> any 2005 server on remote server! >>>> >>>> This is my connection string: >>>> Server=servername;Database=SOX;User ID=userxxx;Password=******; >>>> >>>> Query Analyzer and Enterprise Manager connect perfectly (when installed >>>> on production server) to database server! Then I created small console >>>> appplication which uses the same data layer as web application (and >>>> connection string ) - it connected to remote database too! Only >>>> ASP.NET 2.0 application couldn't connect to remote Sql server 2000. >>>> >>>> Can anyone help? >>>> >>>> >>> >>> >> >> > >
Do you mean IP address? I tried, it didn't help :(
[quoted text, click to view] "Henry" <atnorthend_SPAM_@hotmail.com> wrote in message news:%235WiFKNuGHA.5076@TK2MSFTNGP04.phx.gbl... > Try changing the connection string to reflect the actual address to > server, that may include changing that information in the web.config > file... > > This is my connection string: > > Server=ADDRESS TO SERVER!;Database=SOX;User ID=userxxx;Password=******; > > "Mitya Mitriev" <aaa@stopspam.org> wrote in message > news:uTDAaqMuGHA.4460@TK2MSFTNGP04.phx.gbl... >> Hi >> I created ASP.NET 2.0 web application that uses SQL Server 2000 database >> and >> it works perfectly when website and Sql server were on local machine. >> >> Then I installed application on production server. Database is placed on >> another server. >> I received the 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) >> >> Why it thinks I am trying to connect to SQL Server 2005 ? There is no any >> 2005 server on remote server! >> >> This is my connection string: >> Server=servername;Database=SOX;User ID=userxxx;Password=******; >> >> Query Analyzer and Enterprise Manager connect perfectly (when installed >> on production server) to database server! Then I created small console >> appplication which uses the same data layer as web application (and >> connection string ) - it connected to remote database too! Only ASP.NET >> 2.0 application couldn't connect to remote Sql server 2000. >> >> Can anyone help? >> >> > >
You have to make sure that the remote server is not "Hidden" which would
prevent a remote connection; also check that BOTH Sql Server and Windows Authentication are enabled. Peter -- Co-founder, Eggheadcafe.com developer portal: http://www.eggheadcafe.com UnBlog: http://petesbloggerama.blogspot.com [quoted text, click to view] "Mitya Mitriev" wrote:
> Thank you, but I use Sql Server 2000. > > "Patrick.O.Ige" <naijacoder@hotmail.com> wrote in message > news:Oup2SRPuGHA.4648@TK2MSFTNGP04.phx.gbl... > > Mitya i think you might need to take some additional steps > > See this page at :http://www.datamasker.com/SSE2005_NetworkCfg.htm > > Hope that helps > > Patrick > > > > > > "Mitya Mitriev" <aaa@stopspam.org> wrote in message > > news:exiqP3NuGHA.3912@TK2MSFTNGP03.phx.gbl... > >> Do you mean IP address? I tried, it didn't help :( > >> > >> "Henry" <atnorthend_SPAM_@hotmail.com> wrote in message > >> news:%235WiFKNuGHA.5076@TK2MSFTNGP04.phx.gbl... > >>> Try changing the connection string to reflect the actual address to > >>> server, that may include changing that information in the web.config > >>> file... > >>> > >>> This is my connection string: > >>> > >>> Server=ADDRESS TO SERVER!;Database=SOX;User ID=userxxx;Password=******; > >>> > >>> "Mitya Mitriev" <aaa@stopspam.org> wrote in message > >>> news:uTDAaqMuGHA.4460@TK2MSFTNGP04.phx.gbl... > >>>> Hi > >>>> I created ASP.NET 2.0 web application that uses SQL Server 2000 > >>>> database and > >>>> it works perfectly when website and Sql server were on local machine. > >>>> > >>>> Then I installed application on production server. Database is placed > >>>> on another server. > >>>> I received the 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) > >>>> > >>>> Why it thinks I am trying to connect to SQL Server 2005 ? There is no > >>>> any 2005 server on remote server! > >>>> > >>>> This is my connection string: > >>>> Server=servername;Database=SOX;User ID=userxxx;Password=******; > >>>> > >>>> Query Analyzer and Enterprise Manager connect perfectly (when installed > >>>> on production server) to database server! Then I created small console > >>>> appplication which uses the same data layer as web application (and > >>>> connection string ) - it connected to remote database too! Only > >>>> ASP.NET 2.0 application couldn't connect to remote Sql server 2000. > >>>> > >>>> Can anyone help? > >>>> > >>>> > >>> > >>> > >> > >> > > > > > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |