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 September 22nd, 2007, 08:59 AM
Registered User
 
Join Date: Sep 2007
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default connection problem

I get the infamous message "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)"

We use:
windows server 2003
ms sql server 2000
The entire application runs locally, db and app are on the same server. This server is a vpc with in the vpc "local only".

The application used to work perfectly on our site, until we installed the latest version of this .net2 application. According to our Indian software developer, the new version of the application works perfectly on his site, and i believe him.

Virtually all posts on this topic i came across specify sql server 2005 features, and that does not a play a role here.
Of the remaining posts, most concern themselves with the connection string, but the connection string at our side remained unchanged (so did his, btw).

Any help would be greatly appreciated - our developers are as much at a loss as i am.





 
Old September 22nd, 2007, 09:28 AM
Registered User
 
Join Date: Sep 2007
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Some more Technical Info on it
There is one perticual SP for which it gives this perticular error( mentioned above by Teun).
We tried to change the SP name to check if the SP is having some problem. But the error is given before the SP is called.
Also all the other methods in this dataset are getting called without any error.
 
Old September 25th, 2007, 09:24 AM
Registered User
 
Join Date: Sep 2007
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default

issue solved

 
Old September 25th, 2007, 10:08 AM
joefawcett's Avatar
Wrox Author
 
Join Date: Jun 2003
Posts: 3,074
Thanks: 1
Thanked 38 Times in 37 Posts
Default

Can you post the solution?

--

Joe (Microsoft MVP - XML)





Similar Threads
Thread Thread Starter Forum Replies Last Post
Connection problem atzplzw Classic ASP Databases 3 November 15th, 2004 03:53 AM
Problem with the connection! Berni016x SQL Server 2000 2 November 9th, 2004 08:51 AM
Problem With Connection ! huyremy VB Databases Basics 2 September 29th, 2004 03:37 AM
connection problem weihoe2004 VS.NET 2002/2003 1 July 10th, 2004 01:46 PM





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