I have a problem with Analysis Server

When I open Analisys Manager on our production server and look at OLAP
databases, I see 3 OLAP databases.

When we open Analisys Manager on another server and look at OLAP databases
on production server, I see only 2 databases. The third OLAP database / cube
is not visible.

When we open Analysis Manager on yet another server and look at OLAP
databases on production server,
we see only 1 OLAP database.

We were logging the same way (same user) every time.

But even if we didn't, there is nothing like database owner on Analisys
Server.
You are either OLAP Administrator and you can see all databases on the server
or you are not and you cannot connect with Analysis Manager.

I've found a reference to something simmilar on Knowledgebase.
The article was recommanding to install sp1 for AS.
We have sp3 on all machines (according to version of Analysis Manager).

Does anybody have any idea where to start with this?

Dejan

Our DBA actualy says that we have sp3a (but I do not know how to diffeentiate
between sp3 and sp3a).

We also tried to create an OLAP database 'test' from one of the clients.
We created data source, dimension and we loaded it.

We are not able to see it though Analysis Manager on server (only on client).
However, our metadata and data ddin't go to some other server.
We do see 'test' subfolder under Data folder.

"Djn" wrote:

Btw, AS uses SQL Server db as OLAP Repository.

Three possible sources of the problem:

1) has your DBA updated to SP3 with the Analysis Service download? There are
two SP3 downloads; one for the RDBMS and one for Analysis Services. It is
easy to apply one and forget to do the other.

2) Might you be missing the "Everyone" role in your database? It is present
in Foodmart, but not in a new cube. Without it, no one but administrators
can see your cube.

3) Lastly, it might be that your client machines do not have the latest
version of PTS. This can easily happen if you have older versions of Office
installed, which includes the SQL 7 version of PTS. If you are running the
older version, then it will display only those cubes which are using SQL 7
only features, such as Foodmart. It is easy to design a SQL 2000 cube which
uses a feature which is not compatible with the older versions of PTS. The
latest version of PTS can be installed by running either PTSLITE or
PTSFULL.EXE contained in the \msolap\install\pts folder on your Analysis
Services SP3 download.

Hope this helps.

--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Djn" <Djn (AT) discussions (DOT) microsoft.com> wrote

Yes. I've checked. We have sp3 for AS.

As far as I know, there is no need for Everyone OLAP database role (it not
mandatory).
We have one other role name for our users, but that gives access only
through OLAP Viewers like Proclarity or Excel. If you are not member of OALP
Administrators you cannot open server in Analysis manager. (Which is probelm
that we are facing.)

I was suspecting this.
That someone have installed older drivers on top of new ones, but it's the
server - it should be the case.

I have a feeling that we are pointing to wrong servers.
The only probelm is that we were able to load the data on the right server.

Dejan

Mistery seems to be resolved.
Conection string from OLAP Server to OLAP Repository contained a
reference to a Data Source (server name) that was resolved as a
different SQL Server on all clients.

I am not sure why, but it seems that someone was playing with HOSTS file or
SQL Aliases.

I was suspecting that we are pointing to the wrong server.
But I thought that we took that possibility from the list when we loaded a
data in new db on that server. Strange thing is that OLAP server was puting
meta-data on repository on a wrong server, but data on the right server. (I
saw it in a folder.)
I guess it is understandable when you think how AS connects to OLAP
Repository.

Djn