2005 Reporting Services Connection Error...

I have had this error on three different machines that I have tried to setup
reporting services on:
- 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) (Microsoft SQL Server, Error: 2)
And I have yet to find a solution posted that resolves it. Any advice - I
can't get past step 3 of my first tutorial.
Thanks!
Hi
The first obvious question is the Allow Remote Connections to this Server
check box on the Databse engine properties connections tab ticked?
What is the OS, Windows 2003, 2000 and what is the Service pack level?
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uqRXzbm7FHA.2092@.TK2MSFTNGP12.phx.gbl...
>I have had this error on three different machines that I have tried to
>setup reporting services on:
> - 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) (Microsoft SQL Server, Error: 2)
> And I have yet to find a solution posted that resolves it. Any advice - I
> can't get past step 3 of my first tutorial.
> Thanks!
>
|||Also,
Have you enabled remote connections in the SQL 2005 Surface Area
Configuration utility? You should select TCP and Named pipes.
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:uqRXzbm7FHA.2092@.TK2MSFTNGP12.phx.gbl...
>I have had this error on three different machines that I have tried to
>setup reporting services on:
> - 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) (Microsoft SQL Server, Error: 2)
> And I have yet to find a solution posted that resolves it. Any advice - I
> can't get past step 3 of my first tutorial.
> Thanks!
>
|||1 - Yes the Allow Remote Connection is checked.
2 - Windows XP sp2 (up to date)
3 - Yes, I ran the Surface Scan and checked the remote connections for both
tcp and named pipes.
For the install I just accepted the defaults and added all the
AdventureWorks database options in a new instance called "SQL2005".
This is getting rather frustrating
"Nik Marshall-Blank" <Nik@.here.com> wrote in message
news:kPegf.7091$aM1.591@.fe01.news.easynews.com...
> Hi
> The first obvious question is the Allow Remote Connections to this Server
> check box on the Databse engine properties connections tab ticked?
> What is the OS, Windows 2003, 2000 and what is the Service pack level?
> --
> Nik Marshall-Blank MCSD/MCDBA
> Linz, Austria
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:uqRXzbm7FHA.2092@.TK2MSFTNGP12.phx.gbl...
>
|||I have finally figured it out. The good old permissions with the SQL
Database - I had not setup SQL User Security Role and that was the trick.
"Nik Marshall-Blank" <Nik@.here.com> wrote in message
news:kPegf.7091$aM1.591@.fe01.news.easynews.com...
> Hi
> The first obvious question is the Allow Remote Connections to this Server
> check box on the Databse engine properties connections tab ticked?
> What is the OS, Windows 2003, 2000 and what is the Service pack level?
> --
> Nik Marshall-Blank MCSD/MCDBA
> Linz, Austria
> "Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
> news:uqRXzbm7FHA.2092@.TK2MSFTNGP12.phx.gbl...
>
|||Great.
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"Chris Marsh" <cmarsh@.synergy-intl.com> wrote in message
news:eCmVNPq7FHA.3636@.TK2MSFTNGP09.phx.gbl...
>I have finally figured it out. The good old permissions with the SQL
>Database - I had not setup SQL User Security Role and that was the trick.
> "Nik Marshall-Blank" <Nik@.here.com> wrote in message
> news:kPegf.7091$aM1.591@.fe01.news.easynews.com...
>