Is there any way to process cube and generate the reports in following
Scenario

1) I have two Windows 2003 Servers

Server 1 has SQL Server / MS Analysis Services installed with latest
updates.

Server 2 has IIS , Pivot Table Services and Latest MDAC.

And I have installed ASP.NET application on Server2.

Our requirement is Displaying MDX Based reports from Server 2 and Processing
Cube from Server 2. Since IIS Server and Analysis Server are separted ,I
have copied the DSO folder from Server 1 to Server 2 and tried to procsss
the cube.

I get the following errror in my attempt

"Unable to connect to the registry on the server (10.0.0.1), or you are not
a member of the OLAP Administrators group on this server"

I have created a Windows User who has acess on both Servers. Still We are
getting the above error.

Is there any way to process the cube from a System where Analysis Services
is not available.
An early reply will be highly appreciated

Thanks,
Murali

Out of curiosity, are your two Windows servers connected via a domain? That
is, is your user below a domain authenticated user or a local user? Often,
you will find problems when the you are trying to connect from one server to
another via local user vs. domain authentication.

While in general, you can definitely process an Olap database which is on
another server, you could always have your DSO scripts running on the Olap
server (Server 1 in this case) and have something like NT Scheduled Tasks or
SQL Job Agent perform the task of processing for you?


--
HTH!
Denny Lee
<dennyglee_at_hotmail_dot_com>

Blog at:: http://spaces.msn.com/members/denster/



"Avadhanam" <avadhanam (AT) hostanalytics (DOT) com> wrote

Another twist to this would be to kick off the DSO task from a stored
proc or if you are brave you can use the sp_OACreate family of extended
stored procs and write the DSO code in a stored procedure.

Beware that both these approaches require opening up the security on the
SQL server. I have not double checked in BOL, but I am that in order to
run the sp_OACreate procedures the user needs to have SysAdmin rights to
SQL Server. And there is a property you need to set to allow non SA
users to run external commands (such as kick of a DSO VBScript)


--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell

Yes,Windows Server are connected via domain.

The option what you suggested is workable only for Scheduled Tasks,
We want to process the dimensions, cubes whenver the data changed at RDBMS
Level.

Could you suggest any alternative solution.

Thanks
Murali



"Denny Lee" <dennyglee (AT) hotmail (DOT) com> wrote

We have evaluated this process already and it worked fine at our development
phase.
But at client place our application do not get SysAdmin rights

Thanks
Murali
"Darren Gosbell" <xxx (AT) xxx (DOT) com> wrote

As it appears that the client will not have sysadmin rights, you can set
your scheduled tasks to run every 10-15 minutes (or whatever frequency you
want). What it will do is check if there are any changes to the RDBMS (new
rows, check your log, etc.) and then will only process if changes exist.

--
HTH!
Denny Lee
<dennyglee_at_hotmail_dot_com>

Blog at:: http://spaces.msn.com/members/denster/



"Avadhanam" <avadhanam (AT) hostanalytics (DOT) com> wrote