Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Named Pipes Provider: Could not open a connection to SQL Server [53] Expand / Collapse
Author
Message
Posted Saturday, June 18, 2011 11:55 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, July 2, 2014 11:29 AM
Points: 1, Visits: 29
I am running SQL Server 2005 - 9.00.3042.00 On a Windows 2003 server service pack 2. I have a VB application that has been running for 2 years and connecting fine to the database. Suddenly the application generates an error when connecting to the server/DB (Named Pipes Provider: Could not open a connection to SQL Server [53]) . The error also occurs when opening visual studio 2010 and trying to run queries or stored procedures. I am trying to figure out what changed. It is a named instance, sql browser service is running, named pipes and tcp and shared memory are enabled. Allow remote connections is also turned on. Something has changed and I am trying to find out what?? The network admin said the firewall has been disabled on the server in question. It is configured using dynamic ports. I was able to connect from a client machine using sqlcmd using trusted connection and I ran a query from the DB. Any help is appreciated.

Thanks in advance!!!



Post #1127826
Posted Monday, June 20, 2011 12:55 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, June 12, 2014 2:04 PM
Points: 1,786, Visits: 1,014
Are u able to ping the server , could u try creating a file with .udl extn and see if your able to connect using sal native client.I would double check the firewalls , try running a tracert . Are other servers accessible ?

Check the connect timeout settings.


Jayanth Kurup
Post #1127988
Posted Monday, June 20, 2011 5:50 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, September 24, 2014 8:54 AM
Points: 5,579, Visits: 6,363
Check the Configuration Manager for SQL Server. Someone may have turned off Named Pipes as a protocol.

EDIT: Also, check the box that the application is running on. Did someone turn off Named Pipes at the source?

It might be a good idea to run a network sniffer from the application server to see where all the traffic goes.


Brandie Tarvin, MCITP Database Administrator

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Post #1128131
Posted Tuesday, June 21, 2011 10:03 AM


SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Thursday, September 4, 2014 9:58 AM
Points: 472, Visits: 711
Does the application run on the same host as the database server? If the application is on a different host, try connecting from a client using the application's connection string, e.g. "sqlcmd -S np:\\myhost\pipe\mssql$myinstance\sql\query -U myuser".

Try connecting on the database server using the connection string as well as a connection string without the computername, e.g. "sqlcmd -S np:\\.\pipe\mssql$myinstance\sql\query -U myuser".

If you can connect on the sql server host with . (dot) as the computername, it implies that the computername is not resolving from the remote host. Possibly the IP address, hostname, or FQDN has changed in some way.

HTH
Post #1129106
Posted Tuesday, June 21, 2011 11:25 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, January 3, 2013 10:59 AM
Points: 21, Visits: 228
Firstly thanks for all the replies. I verified settings and everything looks good. We verified the firewall is turned off and the ports are not blocked. I successfully connected from my desktop to the instance on the server using sqlcmd -S np:\\host\pipe\mssql$instance\sql\query -E (we are connecting using Integrated Security). I also tried the same command on the server using the dot and it worked fine??? So I was able to connect using np from sqlcmd but the developer still cannot connect using this Visual Basic 2010 Studio, we still get the named pipes error??? I also restarted the SQL Browser service. We only have named instances on this box.
Post #1129179
Posted Tuesday, June 21, 2011 12:23 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, September 24, 2014 8:54 AM
Points: 5,579, Visits: 6,363
Have you had any service pack updates or anything applied to your box or the server recently? Right about the same time that this error started.

Brandie Tarvin, MCITP Database Administrator

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Post #1129216
Posted Tuesday, June 21, 2011 12:35 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, January 31, 2013 8:01 AM
Points: 1,228, Visits: 1,046
What is the connection string being used?

Does this only happen on the VS 2010 system?

Can he connect to the Application database using the Server Explorer in VS 2010?

Does the VS 2010 system have MDAC 2.8 or better and SQL 10 Native SQL drivers installed?

My guess is what changed in your VB.NET app was the version of Visual Studio. If the app is over two years in production it could not have been created with VS 2010 originaly.
Post #1129236
Posted Tuesday, June 21, 2011 1:37 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, January 3, 2013 10:59 AM
Points: 21, Visits: 228
OK we seem to have found the issue. A consultant had some synonyms in a DB that was pointing to a server that no longer existed. Once we changed the server name in the synonyms now the connection works fine. What is odd the synonyms are at a DB level and we also tried a different DB and it failed when the synonyms in the other DB pointed to the wrong server. Now all the connections work since the synonym server name has been corrected!!!

Thanks to everyone who provided help on this subject!!!
Post #1129288
Posted Wednesday, June 22, 2011 8:00 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Wednesday, September 24, 2014 8:54 AM
Points: 5,579, Visits: 6,363
Glad you found your issue and thanks for posting the details about it.


Brandie Tarvin, MCITP Database Administrator

Webpage: http://www.BrandieTarvin.net
LiveJournal Blog: http://brandietarvin.livejournal.com/
On LinkedIn!, Google+, and Twitter.

Freelance Writer: Shadowrun
Latchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.
Post #1129668
Posted Monday, February 25, 2013 1:12 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, March 1, 2013 2:49 PM
Points: 2, Visits: 14
We began getting the following error this morning, from a php script that's been running for months:

[25-Feb-2013 01:10:17] PHP Warning: odbc_connect(): SQL error: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53]. , SQL state 08001 in SQLConnect in C:\Admin\Scripts\extract_to_sqlserver.php on line 665

The script connects to the local host, and was using the IP address "192.168.0.40". When we changed it to "localhost", it started working again.

Now, to figure out what changed in the environment that caused the IP to stop working all of a sudden...
Post #1423761
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse