Prb: OLAP Linked Server from SQL Server

Question

Post reply

Prb: OLAP Linked Server from SQL Server

Nick Tornese

SSC Journeyman

Points: 97
More actions
December 7, 2004 at 9:50 am

#112655

This is a very strange behavior that I hope someone can explain.

On my SQL Server 2000 instance, I have a 3 linked servers setup to seperate Analysis Services cubes. They are identical in every way except the data source in which they point. When I display the schema using Enterprise Manager, two of them work just fine. However, the third works only when I access it while terminal serviced to the SQL Server. If I try to access it from any other Enterprise Manager tool that is not local to the SQL Server I get this error.
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSOLAP' reported an error.
[OLE/DB provider returned message: Database 'PLP' does not exist.]
OLE DB error trace [OLE/DB Provider 'MSOLAP' IDBInitialize::Initialize returned 0x80004005: ].

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

stevefromOZ SSC-Forever Points: 43646 More actions · Answer 1

it's possibly a security problem with the catalog. Does the catalog have a role defined and are you a member of it?

Steve.

Nick Tornese SSC Journeyman Points: 97 More actions · Answer 2

This should not be the problem. I am the local OLAP Administrator. So is the Service that is running SQL Server. And so is the account that I am impersonating in the connection. If it was a authenication issue, shouldn't fail when I make the connection while terminal serviced into the SQL Server?

~ Nick

stevefromOZ SSC-Forever Points: 43646 More actions · Answer 3

You're right re: the security.

On the slightly obscur side, when creating the connection (linked server) are/were there two different drivers for AS? (prob listed as OLE DB for OLAP 8.0 and 9.0). I know with Excel connections, if you use the 'old" (sql server 7.0/OLAP services) driver, you can't connect to catalogs that contain AS2000 features. It may be that when connecting via TS, the TS machine has only the latest driver but your client PC/s have both?

Steve.

Nick Tornese SSC Journeyman Points: 97 More actions · Answer 4

Turns out the Analysis Services client was at a different versions. Once I brought the client tools on all systems up to the patch level of the Analysis Services install everything started working. Thanks for the replys.