Problem connecting to SQL

Hello,
I have several ASP.NET 2.0 sites That connect to a SQL 7 database. Up
untill a few days ago they had been functioning just fine . For some reason
all my SQL connections are returning the following error sporaticly:
----------------------------------------------------------
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)
----------------------------------------------------------
This is not happening all the time but there have been an unusual amount
of these errors as of late. I have searched the we web but so far I have
been unable to find any documentation about this error that relates to SQL
7.

Any help would be appreciated.
-Scott

Michael
Tue Feb 05 20:06:54 CST 2008

On Feb 5, 3:55 pm, "Scott" <Sc...@Verifpoint.com> wrote:
> Hello,
> I have several ASP.NET 2.0 sites That connect to a SQL 7 database. Up
> untill a few days ago they had been functioning just fine . For some reason
> all my SQL connections are returning the following error sporaticly:
> ----------------------------------------------------------
> 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)
> ----------------------------------------------------------
> This is not happening all the time but there have been an unusual amount
> of these errors as of late. I have searched the we web but so far I have
> been unable to find any documentation about this error that relates to SQL
> 7.
>
> Any help would be appreciated.
> -Scott

What does the DBA say?

Miha
Wed Feb 06 03:08:23 CST 2008

You might also try peeking into output of SQL Profiler.
But if I have to guess you might have problems with network.

--
Miha Markic [MVP C#, INETA Country Leader for Slovenia]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

"Scott" <Scott@Verifpoint.com> wrote in message
news:vX4qj.31323$R55.8862@newsfe13.lga...
> Hello,
> I have several ASP.NET 2.0 sites That connect to a SQL 7 database. Up
> untill a few days ago they had been functioning just fine . For some
> reason all my SQL connections are returning the following error
> sporaticly:
> ----------------------------------------------------------
> 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)
> ----------------------------------------------------------
> This is not happening all the time but there have been an unusual
> amount of these errors as of late. I have searched the we web but so far
> I have been unable to find any documentation about this error that relates
> to SQL 7.
>
> Any help would be appreciated.
> -Scott
>