2 front-end servers (one on DMZ) and OLAP Cube Error - please help

[max.schnorr]

Hi,

we have the following scenario:

Server A
- Intranet
- Analysis Services
- originally single server installation with an external SQL database

Server B
- DMZ
- added later
- connected to the same ProjectServer Database as Server A

From Server B only SQL Connection is allowed to the intranet. No

connection to Analysis Services!

Everything was working on Server A then we've added Server B. Installed
front-end, Connection Manager and View Notification Services (otherwise
installation couldn't be completed, becaus ViewNS on the internal
Server cannot be accessed through firewall)

Now the could couldn't be built with error message "DSO are not
installed on Project-Server Computer". And, yes, they are not installed
on the Server B, but on Server A. (I thought Server B was not necessary
because AS are not reachable in intranet)

Then we disabled View Notification Service and Schedule processing
Service on Server B and tried to start the building process by "Update
Now". But nothing happened. Even the "Current Cube status" has not
changed (Same date, same point of time, same message)

So the View Notification Services couldn't even update the status
message? The server was under heavy weight as I restarted the Views
Notification Service, but nothing else happend. No Cube, no refreshed
status.

Any ideas?

Your help is really appreciated! Regards, Max

 

[Nico Oosthuysen]

Hi Max,

I don't really have any ideas at this stage as to why you are having
problems with building the cube, but i do have a workaround to suggest.
If the cube is still building fine on serverA, then there is no need
to build it on ServerB. Your only issue will be with having users
accessing the cube through their PA views. Currently the people on
servera will access it fine, since the view definitions points to
ServerA, although the people using Serverb will obviously have an issue
there. To solve this one you would need to configure your analysis
services installation to be accessible via HTTP, and yes, this will
mean that your AS installation will have to be exposed on the internet
on HTTP (or HTTPS rather).

Nico

 

[max.schnorr]

Hi Nico,

thanks, but the problem is that on Server A the Cube can't be build.
(Server B can't and should not build the cube). Before the installation
of Server B everything was fine on Server A. I have no idea what's the
impact of Server B to the Cube on Server B...

Cheers, Markus

 

[max.schnorr]

Additional question:

Any Ideas why even the "Current Cube Status" in Project Webadmin is not
refreshed? No matter how often I click "Update Now" the Status shows
still a 1 month old message.

 

[Nico Oosthuysen]

Hi Marcus,

hmm - well, i am not sure either why its battling to build on the old
server - have you tried removing and reinstalling Analysis Services and
the SP? Another thing is to migrate the OLAP repository to a SQL
databases, that sometimes helps with cube issues although i do not
think it will help in this case
(http://support.microsoft.com/kb/324838/).

Do you notice any XML files being dropped in the ViewDrop folder when
you initiate a new build request?

As to your question on why the status is not changing - i would think
its simply because its failing to initiate a new build. If you have a
look in the WADMIN_CUBE_LOG_STATUS_TEXT field in the MSP_WEB_ADMIN_CUBE
table there might be some more information as to the current status.

Nico

 

[max.schnorr]

Hi Nico,

The repositoy is already on the SQL Server, but I had not tried the
reinstallation.
Yes, XML files are appearing in the ViewDrop Folder.

Thanks for the hint with the log table. I'll have to check this!

Thanks, Markus