Analysis service: pb when archiving/restoring from 1 machine to another

I have to install cubes on another machine (not on the same site/NT domain).
I have archived the OLAP db and generated a .cab file.

I have retored on the destination server.
It works fine in Analysis Manager console (I can process and lokk at the data).
But when I want to access the cube from Excel using OLAP cube, I have an error msg.

Is there something I need to do on the distination server ?
Langage, SP, role, version of SQLServer/Analysis services ...

ThanksWhat is the error message that you get?|||In Excel: (translated from French)
"OLAP cube not found
OLAP database ha been modified or you do not have necessary authorisation to connect to the cube
Contact your database admin"

It has something to do wuth SSPI authentication ?|||It could have something to do with the access rights...
I once saw something similar to this, and then the problem was solved by adding the user account to the OLAP admin group.

Analysis Server 2000 memory vs. SQL Server 2000 memory

Here is the situation:
Server is installed with both Analysis Services(OLAP
Cubes) and SQL Server 2000. O/S is Windows Advanced
Server 2000. Server currently has 6 GB of RAM. AWE
extension is used with 5 GB of RAM allocated to SQL
Server.
Does this mean only 1 GB of RAM is left for Analysis
Services and O/S? What is the max RAM can be allocated to
Analysis Services in a Windows 2000 Advanced Server?
Need to understand why at times (once a month) we
encounter "running low on virtual memory" on this server
causing DTS packages to stall occasionally. Realize that
best practice is to separate OLAP server from SQL Server,
but budget is a limitation at this time.Steven,
Analysis Services 32-bit edition uses up to 2GB memory. It can be exapanded
up to 3GB (check the article at
http://support.microsoft.com/default.aspx?scid=kb;en-us;295443 how to do
it). So in your case, AS and SQL are competing for the same memory. Maybe
you could limit SQL Server on 4GB, so you have 2GB for AS.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Steven Wong" <anonymous@.discussions.microsoft.com> wrote in message
news:02e501c48af8$b4cc31e0$a601280a@.phx.gbl...
> Here is the situation:
> Server is installed with both Analysis Services(OLAP
> Cubes) and SQL Server 2000. O/S is Windows Advanced
> Server 2000. Server currently has 6 GB of RAM. AWE
> extension is used with 5 GB of RAM allocated to SQL
> Server.
> Does this mean only 1 GB of RAM is left for Analysis
> Services and O/S? What is the max RAM can be allocated to
> Analysis Services in a Windows 2000 Advanced Server?
> Need to understand why at times (once a month) we
> encounter "running low on virtual memory" on this server
> causing DTS packages to stall occasionally. Realize that
> best practice is to separate OLAP server from SQL Server,
> but budget is a limitation at this time.
>|||Hi Dejan:
Thanks for your response. Just want to clarify....
Is AS and SQL competing for the memory OR AS only has up
to 1 GB of RAM to use since AWE is enabled with 5 GB
allocated to SQL in this case?
How about the option to add 2 GB of RAM to server, and
allocate 6 GB to SQL and leave 2 GB to AS? What do you
think?
Thanks in advance.
>--Original Message--
>Steven,
>Analysis Services 32-bit edition uses up to 2GB memory.
It can be exapanded
>up to 3GB (check the article at
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;295443 how to do
>it). So in your case, AS and SQL are competing for the
same memory. Maybe
>you could limit SQL Server on 4GB, so you have 2GB for AS.
>--
>Dejan Sarka, SQL Server MVP
>Associate Mentor
>Solid Quality Learning
>More than just Training
>www.SolidQualityLearning.com
>"Steven Wong" <anonymous@.discussions.microsoft.com> wrote
in message
>news:02e501c48af8$b4cc31e0$a601280a@.phx.gbl...
>> Here is the situation:
>> Server is installed with both Analysis Services(OLAP
>> Cubes) and SQL Server 2000. O/S is Windows Advanced
>> Server 2000. Server currently has 6 GB of RAM. AWE
>> extension is used with 5 GB of RAM allocated to SQL
>> Server.
>> Does this mean only 1 GB of RAM is left for Analysis
>> Services and O/S? What is the max RAM can be allocated
to
>> Analysis Services in a Windows 2000 Advanced Server?
>> Need to understand why at times (once a month) we
>> encounter "running low on virtual memory" on this server
>> causing DTS packages to stall occasionally. Realize
that
>> best practice is to separate OLAP server from SQL
Server,
>> but budget is a limitation at this time.
>
>.
>|||> Is AS and SQL competing for the memory OR AS only has up
> to 1 GB of RAM to use since AWE is enabled with 5 GB
> allocated to SQL in this case?
I think they are competing for the first 4 GB.
> How about the option to add 2 GB of RAM to server, and
> allocate 6 GB to SQL and leave 2 GB to AS? What do you
> think?
This would be even better than limiting SQL Server :-)
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com

Analisys Services OLAP Error

running sql server 2000 w/ analisys serv sp4 on w2k3 sp1. Yes, also we are running sql 2000 sp4.

I keep getting an event id 6034.

The mssqlserverolapservice service terminated unexpectedly. It has done this 134 times.

Now, i went ahead and installed the suggested rollup hotfix already, which is a post AS SP4 rollup hotfix that fixes this.

It didn't.

What next?

Mike,

This is just one of the possible options:

I have seen this happening with corrupted database. To fix this, you have to find corrupted database and remove it from data folder. I was doing this:

1. Stop Analysis Services service.

2. Go to analysis services data folder and copy folder for one database to another outside folder. Also copy related file from root data folder (I think something like DBName.odb, forgot extension)?

3. Try to start analysis services, if same problem, choose another database and do step 2.

If you'll find corrupted databases, copy all other ones back. Restore corrupted database from backup.

Vidas Matelis

sql

AMO: refresh DSV and accept changes..

I tried the sql server OLAP newsgroup, but without success... this is fairly urgent, so will try in here:
I am stumped on this, how can I programmatically do what can be done in
Visual Studio by:
1. Right clicking inside datasource view
2. Choosing refresh
3. Accepting the changes

I am trying to get new fact table columns into the DSV, obviously
without doing the manual steps above.

I have tried dsv.Refresh() and dsv.Update() but it is not as simple as
that or the sequencing is incorrect (or, most likely, I am looking in
entirely the wrong place).

Thanks for any help.

There is no programmatiic way to do refresh on DSV. However, You can use data adapter to fill schema and get a new datatable and merge the table yourself.

For adding a column, you can use data adapter to do FillSchema() with the table you want to refresh and add the new column into existing table. Finally, call DSV.Update().

|||Thanks for the response - this was pretty much the only way we could solve this as well.... but why isn't the method that MS uses to do this exposed for our use as well? It seems like they have a pretty efficient way of doing this. Nearly everything else allows you to "script the action", why not this?
|||This refresh of DSV from relational DB is part of the execution of DSV but not on AMO. Although we found that it is useful if we move the code to AMO, it is to late of the cycle. Since it has work around, so we cut this feature. We will consider it in next release. Thanks