RE: Connecting to AS 2005 using a specified user

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Whoa... thanks for sharing that with everyone. I think you are right in
that most people on this group are working with a windows based network
infrastructure. I suppose all we can do is to keep an eye on the service
pack releases and see if anything happens on this front.

> The next problem is that once you have installed OLEDB 9 on your clients
> machines, they cannot access AS2000 through http any more in the following
> scenario: connect to an AS2000 cube with OWC, click "Export to Excel", then
> try to refresh in Excel. This fails with OLEDB 9, works with OLEDB 8. So
> their existing application is broken.

This is probably because the export to excel probably just specifies to
use the MSOLAP provider, which will default to the latest version -
MSOLAP.3 (the 2005 version) instead of MSOLAP.2 (the 2000 version).

You probably don't have any nice solutions here either. You could try
re-registering msolap80.dll to try and get it to set itself as the
default provider. Even if you uninstall the OLEDB 9 driver you may find
you need to re-register the 8 driver - I don't know how clean the
uninstall is. The only other approach I can think of which would be a
bit riskier would be to alter the registry to reset the default provider
to the version 8 driver.

--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell

In article <A5950AD0-DE8B-4EC6-8113-E0AE8567A608@xxxxxxxxxxxxx>,
pat@xxxxxxxxxxxxx says...
> I have opened a support call with PSS and after 2 weeks of hard work, the
> conclusion of the escalation engineer is that you cannot use http and basic
> authentication on AS2005, which worked on AS2000.
> People on this newsgroup tend to be connected to the server through a
> Windows network and use windows authentication (or have the same user on the
> client and the server, which is not workable in a production environment).
>
> The problem is that the new OLEDB 9 driver prevents the authentication
> information to be passed from IIS to AS2005, so you have no way to
> authenticate to AS2005, unless you connect directly to it the way I indicated.
>
> The next problem is that once you have installed OLEDB 9 on your clients
> machines, they cannot access AS2000 through http any more in the following
> scenario: connect to an AS2000 cube with OWC, click "Export to Excel", then
> try to refresh in Excel. This fails with OLEDB 9, works with OLEDB 8. So
> their existing application is broken.
>
> Basically, you don't want to go for AS2005 if you don't have all of your
> users and the server in one single Windows domain, or in trusted domains.
>
>
.



Relevant Pages

  • Re: Connecting to AS 2005 using a specified user
    ... > authentication on AS2005, which worked on AS2000. ... > Windows network and use windows authentication (or have the same user on ... > client and the server, which is not workable in a production environment). ... > The next problem is that once you have installed OLEDB 9 on your clients ...
    (microsoft.public.sqlserver.olap)
  • Re: Windows based authentication?
    ... >> authentication information and let the driver take care of all the ... You can't have Windows authenticate a user not on windows! ... It's just that there's no way for the driver to get ... It actually logs into SQL Server simply by sending the Windows user ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Re: Windows based authentication?
    ... > Alin Sinpalean wrote: ... You can't have Windows authenticate a user not on windows! ... >> SQL Server authentication (which the Microsoft driver cannot do, ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Re: Windows based authentication?
    ... Abhishek Srivastava wrote: ... will allow their jdbc driver to connect from one windows machine to ... the DBMS via windows authentication, but a pure type-4 driver will ...
    (microsoft.public.sqlserver.jdbcdriver)
  • Re: Windows service and oledb
    ... connection is closed, what did you get if you using the sql profiler to ... non-issue in internal db on using OLEDB provider for SQLServer in windows ... | user account, to see if it has something to do with access to the database ...
    (microsoft.public.dotnet.framework.adonet)