It is great! <g>
I'm not a configuration wiz, but here are some things you could do until you
figure out how to get reporting services to correctly pass the user's
credentials to AS:
1) change the datasource in report manager for the OLAP conection to use a
domain user that has the necessary privileges on AS (preferrably a domain
account that's not an admin in AS).
Ideally, RS will pass the credentials of the user to AS during the
connection.
A good enterprise configuration for a smaller group could be to split sql
server, analysis services and reporting services across 3 boxes, preferrably
64bit.
[quoted text, click to view] <jhcorey@yahoo.com> wrote in message
news:1150824174.761885.143160@h76g2000cwa.googlegroups.com...
>I just tried deploying everything to Server 2, and it works fine.
>
> So my conclusion is that for a report that goes against an AS cube, RS
> must be on the same machine as AS. But it would be great if I was
> wrong.
>
> Jim
>
> Tim Dot NoSpam wrote:
>> Hi Jim.
>>
>> Could 'devserver' have firewall on for its network connection?
>>
>> <jhcorey@yahoo.com> wrote in message
>> news:1150819548.395205.74950@r2g2000cwb.googlegroups.com...
>> > I've successfully created a data source and reports against an Analysis
>> > Services database.
>> > The AS database is on the same machine as RS (let's call this Server
>> > 1).
>> >
>> > I tried this against a second AS database (on Server 2), and it works
>> > fine from Visual Studio, but when I deploy it to RS (on Server 1) and
>> > try to run it, I get the error:
>> >
>> > "...Cannot create a connection to data source 'DevServer'.
>> > (rsErrorOpeningConnection)
>> > A connection cannot be made. Ensure that the server is running.
>> > Unable to read from the transport connection: An existing connection
>> > was forcibly closed by the remote host."
>> >
>> > I'm not doing anything complicated. It's just that the AS database is
>> > on a different machine from the RS server. Shouldn't this work?
>> > Ideas?
>> >
>> > TIA,
>> > Jim
>> >
>
