Excel OLAP "Excel cannot find OLAP cube Test02...."

[ajc123]

I created a cube on my server, then connected to that cube using MS Excel from a client system. I didn't like some of the dimensions, so I deleted and re-created the first cube, and created a second cube. Now I can't connect to any of the cubes from Excel.

I get the message "Excel cannot find OLAP cube Test02. Either the OLAP database has been changed or you don't have permissions to connect to the cube.
Consult your database administrator."

I get this message even after rebooting both client and server and creating new external data specifications in Excel. I can't connect to OLAP anymore!

What's more, I'm getting this message from every client on the network.

I've set security options so that "everyone" has all read permissions on those two cubes.

I'm not strong on Network Admin. I suspect I've overlooked something. Anyone out there have any suggestions?

 

[ajc123]

Additional note -- I can connect to those two cubes from the client when I use Analysis Manager.

I've got the right version of MDAC -- 2.7.

 

[corilynn]

Ok so I'm sorta just guessing because there isn't quite enough information:

1. Make sure you've fully processed the cubes your refering to, if they aren't done processing you won't be able to connect to them (I have this issue ALL THE TIME with my users). Quick test would be to browse some of the data from the Analysis Manager window, if it comes up this isn't your issue.

2. Try and "Delete" your connection from the excel "Choose Data Source" dialog box and making a new one. I've neeeded to do this a few times.

3. If your using NT authentication, make sure the user your trying to connect as exsists in the "Manage Users" dialog for Analysis Services. Common bummer for me is selecting the right user name, but wrong domain, doh! Your message says you selected "everyone" to read the database, so this isn't likely your issue.

Hope I'm being helpful...

 

[ajc123]

Thanks again Corilynn.

I eventually resorted to Microsoft SOP, and checked my version levels on everything. It turns out that I hadn't installed SP2 for Analysis Services on the client machines. They worked, but not properly! The Analytics Services upgrade is seperate from the Server 2000 upgrade. (It can be found in the MSOLAP directory).

Running the upgrade has fixed the problem -- for now.