Dear all.
I'm wondering how I can give access rights to an OLAP cube on one server to
the ASPNET account from a different server.

A client has the following setup:

1 Windows 2003 server running SQL Server 2000 sp 3.
1 Windows 2003 server running Analysis Services sp 3.
1 Windows 2003 server running Reporting Services sp 2.

All my reports are based on data from OLAP cubes, but with some "functional"
data from SQL Server. There are no problems with getting data from the SQL
Server, but there are problems with the OLAP reports. When I run the reports
from the Reporting Services server, they work. When I run the same reports
from a different computer, they fail. I'm logged into the second computer
(WInXP) as the same user (administrator) as on the RS Server, so it's not
about an account that doesn't have access to the RS reports.

It looks a lot like an earlier problem I had, with the local aspnet account
not having access to the OLAP cube. I solved this problem by creating a very
limited role in Analysis Manager and adding the aspnet account to this role.
Problem is, this time AS and RS are running on different servers. The AS
server doesn't have an aspnet account at all.

How can I give the ReportServer\aspnet account access to the OLAP cube on
this other server? Or should I create a different account all toghether?
We're in a AD domain, so can I create a AD user that both Report Server and
OLAP role can use? Or is there another trick to do this? I've found
guidelines on how to run RS against a remote SQL server, but not with a
remote AS / OLAP server. I'd be very happy if someone can point me in the
right direction.

All help appreciated with this one!

Sincerely,
Kaisa M. Lindahl

This a common problem. The problem lies with the passing of the user
credentials from the client computer mutliple-hops. Two options: you can
hard-code a windows domain user account for the username/password on the
reports' datasource, and grant access to the olap cubes to that windows
domain user. This might work for you if you don't need to specify user-level
security.

The other option, if you want to pass on the user credentials to the cube
itself so the cube restricts the user's access, is to use kerberos. Search
for articles to set it up.

Steve

"Kaisa M. Lindahl" wrote: