in AS 2005 it was not possible to state a user and password in order to
connect to a cube. All end user access was controlled by a windows accont. Is
it possible to state a username and password in the connectionstring using
msolap.3???

Does AS 2005 support connecting via HTTP in the same manner as SQL server
2000?

Regards Gustaf

No AS2005 http connectivity won't work in your case. You have to stay with
AS2000.
Have a look at the thread "MDX Sample App broken by 2005" in this newsgroup.

"Gustaf" wrote:

Ok. thanx pat.

Any idea on how to connect if a user does not logon to the same domain as
the SQL server?

Regards Gustaf

"Pat" wrote:

You need to set up a windows account for each user on each AS2005 server and
connect using the SERVERNAME:PORT syntax in the data source, after assigning
a fixed port to AS2005.
You also need to install oledb 9 at each client, and this will cause their
existing http access to AS2000 to fail, since my experience is that oledb 9
is not backwards-compatible with oledb 8.

Basically, AS2005 connectivity only works if you're a Microsoft-only shop.
Otherwise, you've got to stick to AS2000


"Gustaf" wrote:

AS2005 does allow a similar HTTP connection option to AS2000.

Actually the "MDX Sample App broken by 2005" thread only referred to an
issue where the person was using basic authentication with prompt=1
turned on and the end users were being asked to authenticate twice. HTTP
authentication does still work in 2005, the issue was the users had to
enter their username and password twice.

If you want to put the userid and password in the connection string you
should not see this issue.

Check out:
http://www.microsoft.com/technet/pro.../httpasws.mspx
....for configuring HTTP access on Win 2003

And:
http://www.microsoft.com/technet/pro.../httpssas.mspx
....for configuring HTTP access on Win XP

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

In article <0ECC73AD-25D1-4AC9-9B08-5920169F50F8 (AT) microsoft (DOT) com>,
pat (AT) online (DOT) nospam 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.

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.

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 (AT) microsoft (DOT) com>,
pat (AT) online (DOT) nospam says...

Not sure what you mean in your first paragraph. Do you find it good that
Microsoft comes up with a product upgrade that shuts off anybody not on a
Microsoft network from using the product?

I note that you aknowledge that people cannot concurrently work on AS2000
and AS2005 servers. You can't ask users to fiddle with the registry every
time they use a different server.

How many companies do you have out there that will flick a big switch one
morning and suddenly replace all AS2000 applications by AS2005 applications?
Not one.



"Darren Gosbell" wrote:

Sorry.. It's hard to convey tone of voice in a newsgroup post

I think it is a large oversight on behalf of MS not to have made sure
that the HTTP connectivity would have worked at least the same as it did
in AS2k.

I am hoping that with an admin deployed registry file you might be able
to switch the default OLAP provider back to the 8.0 version so that http
access and "open in excel" from OWC still work.

If you are interested in trying to come up with a solution that can get
the 9.0 and 8.0 drivers co-existing, I am happy to help if I can. Of
course in your situation I would not be surprised if you just wanted to
back out the 2005 version completely.

Not one, but there could be some that spend a significant amount of
funds on an upgrade, expecting http connectivity to work as it did in
AS2k only to hit this issue.

So once again - thanks for sharing your hard won knowledge. I hope that
others might benefit from this and also that MS might fix it in the near
future.

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

In article <3E568801-8C65-472E-9DE4-2F2E536CA9CE (AT) microsoft (DOT) com>,
pat (AT) online (DOT) nospam says...

Do you have a case# for this incident? I'd like to look it up.
This is certainly is not our intention for this feature.
It is a bug and I want to make sure it is being treated as such internally.
You can just email it to me directly.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Pat" <pat (AT) online (DOT) nospam> wrote