Showing posts with label cubes. Show all posts
Showing posts with label cubes. Show all posts

Wednesday, March 21, 2012

I can't access cubes from excel

I try to register the dll in a remote machine but I couldn't.
Do I need to install something else in the remote machine?whats the message / error u r gett5ing. what exactly have u done?"|||The error is Load Library "C:\........................." failed
GetLastError returns 0x00000485
In the client I haven't installed anything. I only copied the dll and try to register it. Should I install something else?
Thanks in advance|||Does anyone has connected with Excel from other computer than the server?
From the server I can connect.
What whould I install in the computer to connect to the server with Excel?
Thanks in advance.|||

Before you can connect from Excel to the Olap 2005 server, you need to install Microsoft OLEDB for Olap 9.0.

The file you need to install is: pts9.msi - Located in
"En_SQL_DEV_x86_ctp_JUNE2005\Redist\Analysis Services\pts9.msi".

Best regards,

Jakobsgaard

|||Yes I have tried this with no luck.
I think is a version problem, my server is April CTP.
I'll try to install client tools in remote client.sql

Monday, March 12, 2012

I am unable to access Analysis Server with AMO

Hi All,

I developed one web service,Here i am making connection to the Analysis Server and working on Database,cubes,partitions.when i deploy this code it is failing to run and it is throwing error like."object reference not set to an instance of the object",so i added Impersonate = true code in my web service config file then it is working fine.

( am expecting My Analysis Server is not allowing to create object ,how to handle this)

But what i want is it should work with out providing Impersonate in config.

Help is needed it is very urgent.

Thanks in Advance.

You code has to run under the priviledges of some sort of account. There are only 3 possible configurations that I can think of.

1. Setup an account in the application pool (if using IIS6)

2. Set a fixed account using the <identity impersonate="true" userName="..." password="..." /> tag in the web.config

3. Set the current client account to be impersonated using <identity impersonate="true" /> in the web.config

Note that 3) will only work if the web service and SSAS are on the same machine, or if you have Kerberos configured. Otherwise the user credentials will not pass from client to Web server to SSAS server.