dbTalk Databases Forums  

OLEDB 9 Nightmare

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss OLEDB 9 Nightmare in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
James
 
Posts: n/a

Default OLEDB 9 Nightmare - 12-07-2005 , 06:02 AM






We have an existing SSAS 2000 OLAP database,
and we have developped the next version of the
database with SSAS 2005.

We've installed OLEDB 9 on the client, since we
cannot view SSAS 2005 cubes with OLEDB 8

Now, the client is unable to view SSAS 2000 cubes.
From what I read in various posts on this
newsgroup, OLEDB 9 doesn't pass authentication
tokens across applications, which OLEDB 8 did.

Since Excel creates OLAP connections through
MS Query, the connection becomes invalid as soon
as it is created, as the token won't be passed between
MS Query and Excel.

We can change the default OLEDB version that the
client is using by modifying Hkey_Classes_Root in the
registry. When we revert back to OLEDB 8, we are
able to view SSAS 2000 cubes again. But then we can't
view SSAS 2005 cubes of course.

Am I missing something? Why is OLEDB 9 designed to
be non backwards compatible with OLEDB 8?
Is a hotfix in planning to allow us to access SSAS 2000
and SSAS 2005 from the same client?

PS: when testing this scenario, please run the profiler
for SSAS 2005 and verify that the user connecting to
SSAS is not a local user on the server, but the actual
user specified in the connection string.
We're not running Windows Authentication.

Reply With Quote
  #2  
Old   
Chris Webb
 
Posts: n/a

Default RE: OLEDB 9 Nightmare - 12-07-2005 , 11:10 AM






You should be able to specify which version you use in the Provider property
of your connection string, ie
Provider=MSOLAP always returns the most recent version
Provider=MSOLAP.3 always uses version 9.0
Provider=MSOLAP.2 always uses version 8.0

I know it doesn't solve your exact problem (that's probably one for MS
support), but it might provide a workaround.

HTH,

Chris
--
Blog at:
http://spaces.msn.com/members/cwebbbi/


"James" wrote:

Quote:
We have an existing SSAS 2000 OLAP database,
and we have developped the next version of the
database with SSAS 2005.

We've installed OLEDB 9 on the client, since we
cannot view SSAS 2005 cubes with OLEDB 8

Now, the client is unable to view SSAS 2000 cubes.
From what I read in various posts on this
newsgroup, OLEDB 9 doesn't pass authentication
tokens across applications, which OLEDB 8 did.

Since Excel creates OLAP connections through
MS Query, the connection becomes invalid as soon
as it is created, as the token won't be passed between
MS Query and Excel.

We can change the default OLEDB version that the
client is using by modifying Hkey_Classes_Root in the
registry. When we revert back to OLEDB 8, we are
able to view SSAS 2000 cubes again. But then we can't
view SSAS 2005 cubes of course.

Am I missing something? Why is OLEDB 9 designed to
be non backwards compatible with OLEDB 8?
Is a hotfix in planning to allow us to access SSAS 2000
and SSAS 2005 from the same client?

PS: when testing this scenario, please run the profiler
for SSAS 2005 and verify that the user connecting to
SSAS is not a local user on the server, but the actual
user specified in the connection string.
We're not running Windows Authentication.

Reply With Quote
  #3  
Old   
James
 
Posts: n/a

Default RE: OLEDB 9 Nightmare - 12-07-2005 , 11:49 AM



I meant to say "...verify that the user connecting to
SSAS is not the windows user logged-in at the
client, but the actual user specified in the
connection string ..."

"James" wrote:

Quote:
We have an existing SSAS 2000 OLAP database,
and we have developped the next version of the
database with SSAS 2005.

We've installed OLEDB 9 on the client, since we
cannot view SSAS 2005 cubes with OLEDB 8

Now, the client is unable to view SSAS 2000 cubes.
From what I read in various posts on this
newsgroup, OLEDB 9 doesn't pass authentication
tokens across applications, which OLEDB 8 did.

Since Excel creates OLAP connections through
MS Query, the connection becomes invalid as soon
as it is created, as the token won't be passed between
MS Query and Excel.

We can change the default OLEDB version that the
client is using by modifying Hkey_Classes_Root in the
registry. When we revert back to OLEDB 8, we are
able to view SSAS 2000 cubes again. But then we can't
view SSAS 2005 cubes of course.

Am I missing something? Why is OLEDB 9 designed to
be non backwards compatible with OLEDB 8?
Is a hotfix in planning to allow us to access SSAS 2000
and SSAS 2005 from the same client?

PS: when testing this scenario, please run the profiler
for SSAS 2005 and verify that the user connecting to
SSAS is not a local user on the server, but the actual
user specified in the connection string.
We're not running Windows Authentication.

Reply With Quote
  #4  
Old   
Raman Iyer [MS]
 
Posts: n/a

Default Re: OLEDB 9 Nightmare - 12-07-2005 , 11:57 AM



Are you accessing your server using HTTP? There is a known issue in a
specific scenario (cross-domain./cross-network) with HTTP only. In all
other respects, the 9.0 OLE DB provider is backward compatible with AS 2000.

Your issue might be that you installed Office/Excel after you installed the
AS 2005 client components, which causes the 8.0 provider to get registered
as the default MSOLAP provider. All you need to do is re-register "Program
Files\Common Files\System\Ole DB\msolap90.dll" and connectivity to both
AS2005 and AS2000 cubes should work fine from Excel/OWC.

Also, note that AS2005 only supports Windows authentication for TCP.

--
-Raman Iyer
SQL Server Data Mining
[This posting is provided "AS IS" with no warranties, and confers no
rights.]

"James" <aa1948 (AT) nospam (DOT) nospam> wrote

Quote:
We have an existing SSAS 2000 OLAP database,
and we have developped the next version of the
database with SSAS 2005.

We've installed OLEDB 9 on the client, since we
cannot view SSAS 2005 cubes with OLEDB 8

Now, the client is unable to view SSAS 2000 cubes.
From what I read in various posts on this
newsgroup, OLEDB 9 doesn't pass authentication
tokens across applications, which OLEDB 8 did.

Since Excel creates OLAP connections through
MS Query, the connection becomes invalid as soon
as it is created, as the token won't be passed between
MS Query and Excel.

We can change the default OLEDB version that the
client is using by modifying Hkey_Classes_Root in the
registry. When we revert back to OLEDB 8, we are
able to view SSAS 2000 cubes again. But then we can't
view SSAS 2005 cubes of course.

Am I missing something? Why is OLEDB 9 designed to
be non backwards compatible with OLEDB 8?
Is a hotfix in planning to allow us to access SSAS 2000
and SSAS 2005 from the same client?

PS: when testing this scenario, please run the profiler
for SSAS 2005 and verify that the user connecting to
SSAS is not a local user on the server, but the actual
user specified in the connection string.
We're not running Windows Authentication.



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.