Error connecting to remote connections...

That's what appears at my client site. I have virtually the exact same
configuration on a handful of servers using the SQL Reporting Services and
the RDLC which is working great. Except this one server has:
"An error has occurred when establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by teh fact that
under the default settings SQL Server does not allow remote connections.
Named Pipes provider, error: 40 - Could not open a connection to the SQL
Server).
I think the IT admin used SQL permissions when he installed. Could that be
the problem?
Thanks in Advance.
ChrisThis link might help,
http://vadivel.blogspot.com/2007/01/error-has-occurred-while-establishing.html.
daw
"Chris Marsh" wrote:
> That's what appears at my client site. I have virtually the exact same
> configuration on a handful of servers using the SQL Reporting Services and
> the RDLC which is working great. Except this one server has:
> "An error has occurred when establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by teh fact that
> under the default settings SQL Server does not allow remote connections.
> Named Pipes provider, error: 40 - Could not open a connection to the SQL
> Server).
> I think the IT admin used SQL permissions when he installed. Could that be
> the problem?
> Thanks in Advance.
> Chris
>
>|||Sorry, I should have specified this earlier but the SQL DB is SQL 2000 not
2005 which is what is strange. Again, works on multiple other configurations
but not this one.
"daw" <daw@.discussions.microsoft.com> wrote in message
news:D05FF90C-2A0D-43B9-83B4-D348859995E9@.microsoft.com...
> This link might help,
> http://vadivel.blogspot.com/2007/01/error-has-occurred-while-establishing.html.
> daw
> "Chris Marsh" wrote:
>> That's what appears at my client site. I have virtually the exact same
>> configuration on a handful of servers using the SQL Reporting Services
>> and
>> the RDLC which is working great. Except this one server has:
>> "An error has occurred when establishing a connection to the server. When
>> connecting to SQL Server 2005, this failure may be caused by teh fact
>> that
>> under the default settings SQL Server does not allow remote connections.
>> Named Pipes provider, error: 40 - Could not open a connection to the SQL
>> Server).
>> I think the IT admin used SQL permissions when he installed. Could that
>> be
>> the problem?
>> Thanks in Advance.
>> Chris
>>