Connecting to the remote database

Hi!
We have the Reporting Services 2005 installed on the one server and the SQL
Server 2000 database on the other. I am trying to create the report with data
from this database. When I deploy the report on the RS 2005 server, and try
to open it from my client machine, I get the message: Login Failed for user
(null). If I browse the report directly from the server (with my contex), it
works. It seems that this is a delegation problem. Both of the servers are
Windows 2003 servers in the same domain, and I use the windows authentication.
How can I resolve the problem?
Thanks,
Yuliaan.When you deploy a report it also deploys the datasource. However, the
datasource still needs to be configured. Open up the datasource on the
server and go to the properties for it.
BTW, what I do is have all my reports use integrated security for
permission to run the report. Then for where the data is coming from I have
the database running in mixed mode and have a read only user that I create
with for it. This is much much easier than perpetually messing with the
database giving appropriate rights to the users for the data. Plus, if you
have a subscription you have to have a user that is used for the report
anyway (it is run once and then the report can be mailed to multiple users).
Another advantage is the use of connection pooling. If you go your route
then connection pooling will only come into play for a particular user, if
you do what I am suggesting (having a single special user for the database
connection) then all the users of the reports will get the benefit of
connection pooling.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Yuliaan" <Yuliaan@.discussions.microsoft.com> wrote in message
news:BDDF0314-A188-46A3-88EE-5B5A922C7F2E@.microsoft.com...
> Hi!
> We have the Reporting Services 2005 installed on the one server and the
> SQL
> Server 2000 database on the other. I am trying to create the report with
> data
> from this database. When I deploy the report on the RS 2005 server, and
> try
> to open it from my client machine, I get the message: Login Failed for
> user
> (null). If I browse the report directly from the server (with my contex),
> it
> works. It seems that this is a delegation problem. Both of the servers are
> Windows 2003 servers in the same domain, and I use the windows
> authentication.
> How can I resolve the problem?
> Thanks,
> Yuliaan.|||Thank you Bruce, but in our database the different users has the different
rights, moreover I need to connect to the Analysis Services data that also
has the different permissions.So I have to transfer the user context to the
database server. Is it possible?
Thanks,
Yuliaan
"Bruce L-C [MVP]" wrote:
> When you deploy a report it also deploys the datasource. However, the
> datasource still needs to be configured. Open up the datasource on the
> server and go to the properties for it.
> BTW, what I do is have all my reports use integrated security for
> permission to run the report. Then for where the data is coming from I have
> the database running in mixed mode and have a read only user that I create
> with for it. This is much much easier than perpetually messing with the
> database giving appropriate rights to the users for the data. Plus, if you
> have a subscription you have to have a user that is used for the report
> anyway (it is run once and then the report can be mailed to multiple users).
> Another advantage is the use of connection pooling. If you go your route
> then connection pooling will only come into play for a particular user, if
> you do what I am suggesting (having a single special user for the database
> connection) then all the users of the reports will get the benefit of
> connection pooling.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Yuliaan" <Yuliaan@.discussions.microsoft.com> wrote in message
> news:BDDF0314-A188-46A3-88EE-5B5A922C7F2E@.microsoft.com...
> > Hi!
> >
> > We have the Reporting Services 2005 installed on the one server and the
> > SQL
> > Server 2000 database on the other. I am trying to create the report with
> > data
> > from this database. When I deploy the report on the RS 2005 server, and
> > try
> > to open it from my client machine, I get the message: Login Failed for
> > user
> > (null). If I browse the report directly from the server (with my contex),
> > it
> > works. It seems that this is a delegation problem. Both of the servers are
> > Windows 2003 servers in the same domain, and I use the windows
> > authentication.
> > How can I resolve the problem?
> >
> > Thanks,
> > Yuliaan.
>
>|||What you need to do in your case is make sure the user has the appropriate
rights on the database that has the data you are reporting off of. And then
in Report Manager click on the data source and make sure it is using
integrated security. When you deploy this property does not get set and you
need need to do this for all newly deployed data sources.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Yuliaan" <Yuliaan@.discussions.microsoft.com> wrote in message
news:74D2F2F4-CBB2-4882-A275-BCAB3A38EBED@.microsoft.com...
> Thank you Bruce, but in our database the different users has the different
> rights, moreover I need to connect to the Analysis Services data that also
> has the different permissions.So I have to transfer the user context to
> the
> database server. Is it possible?
> Thanks,
> Yuliaan
> "Bruce L-C [MVP]" wrote:
>> When you deploy a report it also deploys the datasource. However, the
>> datasource still needs to be configured. Open up the datasource on the
>> server and go to the properties for it.
>> BTW, what I do is have all my reports use integrated security for
>> permission to run the report. Then for where the data is coming from I
>> have
>> the database running in mixed mode and have a read only user that I
>> create
>> with for it. This is much much easier than perpetually messing with the
>> database giving appropriate rights to the users for the data. Plus, if
>> you
>> have a subscription you have to have a user that is used for the report
>> anyway (it is run once and then the report can be mailed to multiple
>> users).
>> Another advantage is the use of connection pooling. If you go your route
>> then connection pooling will only come into play for a particular user,
>> if
>> you do what I am suggesting (having a single special user for the
>> database
>> connection) then all the users of the reports will get the benefit of
>> connection pooling.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Yuliaan" <Yuliaan@.discussions.microsoft.com> wrote in message
>> news:BDDF0314-A188-46A3-88EE-5B5A922C7F2E@.microsoft.com...
>> > Hi!
>> >
>> > We have the Reporting Services 2005 installed on the one server and the
>> > SQL
>> > Server 2000 database on the other. I am trying to create the report
>> > with
>> > data
>> > from this database. When I deploy the report on the RS 2005 server, and
>> > try
>> > to open it from my client machine, I get the message: Login Failed for
>> > user
>> > (null). If I browse the report directly from the server (with my
>> > contex),
>> > it
>> > works. It seems that this is a delegation problem. Both of the servers
>> > are
>> > Windows 2003 servers in the same domain, and I use the windows
>> > authentication.
>> > How can I resolve the problem?
>> >
>> > Thanks,
>> > Yuliaan.
>>