Using Crystal Analysis to access a cube remotely.

[Flybridge]

I want to use Crystal Analysis to acces an MS OLAP cube on a remote server.

I can run Analysis Server on my laptop to access the other server where the cube is actually created and stored (which is how I created the cube). I can access the cube from my laptop over the network using Excel.

But when using Crystal Analysis, all I see is the Foodmart data base when I register that server.

Anyone seen this before and can shed light on it? I haven't seen anything in the help documentation that actually helps with this.

 

[johnherman]

This *must* be a security/permissions problem. My guess is that it has to do with the way Crystal talks to the database. Analysis services relies on Windows Domain security. Does Crystal use database signons and passwords? If yes, see if there is a switch to use system (or integrated) security. Crystal can see the Foodmart database because of the weaker security. Alternatively, you could open up your OLAP cube(s) to "guest" or some other Windows login.

Sometimes the grass is greener on the other side because there is more manure there - original.

 

[r1ch]

The other possibility is that it's picking up the wrong version of PTS. If cubes use features added in later versions of Analysis services they will be hidden from earlier versions of the PTS. You can choose which version of PTS to use using the "Server Type" drop down list in the Crystal Analysis "Add Server" dialog.

 

[Flybridge]

I guess it was a security issue.

Crystal asks for a userid and password when registering the server. I have been filling in my user details.

If I register the server without my user details I can see the cubes I've just created in AS.

I think Crystal ought to make it clear the user name and password fields are not mandatory.

Thanks to everyone for their thoughts on this.

 

[Acius]

We had the same problem.
The connection only worked if you didn't specify the username/password. Problem is we don't have domains; so had to set up a user with the same userid/password on the server.

Only other way around was to use a HTTP cube and basic authentication.

I'm not sure what the userid/password is .. doesn't look like it's the server userid/password