Wrox Programmer Forums
|
SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old May 8th, 2008, 10:50 AM
Registered User
 
Join Date: Mar 2008
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
Default SQL Server Error

I have a windows form application in VS 2005 which use sql server 2000. After deploying the application on a client machine, at the login prompt, it gives me 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]"

Please help.

 
Old May 8th, 2008, 10:57 AM
Imar's Avatar
Wrox Author
 
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

Hi there,

Take a look here: http://imar.spaanjaars.com/QuickDocId.aspx?ID=395

Imar


---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of Beginning ASP.NET 3.5 : in C# and VB, ASP.NET 2.0 Instant Results and Dreamweaver MX 2004
Want to be my colleague? Then check out this post.
 
Old May 8th, 2008, 12:20 PM
Registered User
 
Join Date: Mar 2008
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I read the article and double check the user name and password on the server. However, the problem is still there. This application works ok without an error message on the machine it was created on, and on another client machine, the error message comes up but after clicking continue, the application starts, so it seems that some setting need to be in place somewhere to eliminate this problem.

 
Old May 8th, 2008, 12:23 PM
Imar's Avatar
Wrox Author
 
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

Did you read the final section at the end that deals with the specific error?

If that doesn't help, please provide more information. FOr example, explain what scenario you used, how you connect to the server, where the database and web server are located etc.

Cheers,

Imar
---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of Beginning ASP.NET 3.5 : in C# and VB, ASP.NET 2.0 Instant Results and Dreamweaver MX 2004
Want to be my colleague? Then check out this post.
 
Old May 8th, 2008, 01:35 PM
Registered User
 
Join Date: Mar 2008
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I am using a database not a web server. The database is located on SQL Server 2000. During the design phase of the application I can connect to this database ok. All the forms pull their information correctly. After I publish the application and try logging in, on the machine I use to create it, everything is perfect again, however the problem starts when I install it on another machine. On one of the machines that has windows 2000 OS, I am allow to click continue and the app runs inspite of the error. On XP OS, the application produces that error and remain there, nothing happens.

I read the article that either explain ASP or\and sql server 2005. I cannot find an article that addresses sql server 2000 which do not have the sql express.


 
Old May 8th, 2008, 03:01 PM
Imar's Avatar
Wrox Author
 
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
Default

Most of what applies to 2005 applies to 2000 as well. However, it's hard to tell if that's true in your case as you're not really providing enough information:

1. Are the application and database servers physically separated from each other?

2. Which scenario (from my article) are you using?

3. How are the different servers connected to each other (LAN, Internet)?

and so on....

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of Beginning ASP.NET 3.5 : in C# and VB, ASP.NET 2.0 Instant Results and Dreamweaver MX 2004
Want to be my colleague? Then check out this post.





Similar Threads
Thread Thread Starter Forum Replies Last Post
SQL Server Reg. SQL Server does not exist error Arsi SQL Server 2000 1 June 11th, 2008 11:20 AM
error on connecting to sql server angelboy C# 2005 9 March 29th, 2007 07:56 AM
SQL Server Error azwildcat4ever SQL Server 2000 3 December 22nd, 2004 11:36 AM
SQL Server Error Jane SQL Server 2000 0 February 9th, 2004 08:31 PM
Sql SErver Error ciko1973 SQL Server 2000 6 July 23rd, 2003 09:24 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.