Named Pipes Provider, error 40 Could not open a connection to SQL

Hi,
I have a big problem, I have a website in a Windows 2003 and SQL Server
2005, and the website usually goes weel, but some times and error appears,
the error is "Named Pipes Provider, error: 40 - Could not open a connection
to SQL Server".
There is not installed a firewall and TCP and Pipes connection are enabled.
Any ideas?
Thanks in advance,
Miguel
I have seen this before in SQL Servers that have been configured to support
N connections and no more. In this case, the named pipe is opened (the
Connection) but the server finds that the connection limit has been reached
so it closes the pipe at the server end. This confuses the connection pooler
who responds that the named pipe has failed and the connection could not be
opened after all.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"JMLA" <JMLA@.discussions.microsoft.com> wrote in message
news:FFF29A16-3C52-4596-AC88-F18D41E31309@.microsoft.com...
> Hi,
> I have a big problem, I have a website in a Windows 2003 and SQL Server
> 2005, and the website usually goes weel, but some times and error appears,
> the error is "Named Pipes Provider, error: 40 - Could not open a
> connection
> to SQL Server".
> There is not installed a firewall and TCP and Pipes connection are
> enabled.
> Any ideas?
> Thanks in advance,
> Miguel
|||Hi William Vaughn,
I have upgraded the MaxUserPort in the registry to 40000, and nothing
happens, any ideas?
Thanks in advance,
Miguel.
"William (Bill) Vaughn" wrote:

> I have seen this before in SQL Servers that have been configured to support
> N connections and no more. In this case, the named pipe is opened (the
> Connection) but the server finds that the connection limit has been reached
> so it closes the pipe at the server end. This confuses the connection pooler
> who responds that the named pipe has failed and the connection could not be
> opened after all.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "JMLA" <JMLA@.discussions.microsoft.com> wrote in message
> news:FFF29A16-3C52-4596-AC88-F18D41E31309@.microsoft.com...
>
>
|||It's not ports, it's "Connections". It might be a license restriction as
well...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"JMLA" <JMLA@.discussions.microsoft.com> wrote in message
news:CB4C9FE7-A3F2-4720-B163-0DF2784C952E@.microsoft.com...[vbcol=seagreen]
> Hi William Vaughn,
> I have upgraded the MaxUserPort in the registry to 40000, and nothing
> happens, any ideas?
> Thanks in advance,
> Miguel.
> "William (Bill) Vaughn" wrote:
sql