Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pamyral_279
Posting Yak Master
143 Posts |
 Posted - 2007-02-08 : 04:37:33
|
| I setup a both of sql server 2000 and sql server 2005 in a same machine.Bug found when i manage to access code by asp.net. (access database is sql server 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: 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).How to solve this problem ?Thank you very much. |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2007-02-08 : 04:39:25
|
| I assume SQL Server 2005 is an instance, and SQL Server 2000 is the default?Have you tried the Surface Area Configuration?Peter LarssonHelsingborg, Sweden |
 |
|
|
pamyral_279
Posting Yak Master
143 Posts |
Posted - 2007-02-08 : 05:07:53
|
quote:
Originally posted by Peso
I assume SQL Server 2005 is an instance, and SQL Server 2000 is the default?Have you tried the Surface Area Configuration?Peter LarssonHelsingborg, Sweden
Thank for your reply.The first i setup sql server 2005 and then i setup sql server 2000.I do everything with two database fine.No errors. |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2007-02-08 : 05:11:13
|
| Both databases can't be default database, so I assume SQL Server 2005 is default and SQL Server 2000 is an instance?Did you try the Surface Area Configuration Tool as I suggested?Peter LarssonHelsingborg, Sweden |
|
|
|
a4nsd
Starting Member
20 Posts |
Posted - 2007-02-11 : 02:01:07
|
| Dear pamyral_279I think the problem is in your webconfig file. Set "Data Source=Your Sql2000 Server" NOT "Data Source=Your Sql2000 Server\SQLEXPRESS" |
|
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2007-02-11 : 02:39:22
|
quote:
Originally posted by Peso
Both databases can't be default database, so I assume SQL Server 2005 is default and SQL Server 2000 is an instance?Did you try the Surface Area Configuration Tool as I suggested?Peter LarssonHelsingborg, Sweden
You mean default server right ?
KH |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2007-02-11 : 03:36:20
|
| Yes. Thanks khtan.Peter LarssonHelsingborg, Sweden |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2007-02-11 : 12:15:31
|
| has SP3 or greater been applied to the SQL 2000 install? on win2k3 TCP/IP for SQL2K will be disabled if you aren't running atleast SP3.-ec |
|
|
|
|
|
|
|
|
run both sql 2000 and sql server 2005