![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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. |
#3
| |||
| |||
|
|
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. |
#4
| |||
| |||
|
|
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. |
![]() |
| Thread Tools | |
| Display Modes | |
| |