Hi all - hopefully someone here can help me out with this. I have an open
ticket on this with MS as well, and none of their techs seem to know how to
help me. I have enabled HTTP access to our Analysis Services 2005 server by
following the steps at
http://www.microsoft.com/technet/pro.../httpasws.mspx -
however, I need to use BASIC AUTHENTICATION instead of Windows Integrated.
Once I enable basic and disable integrated, everything just stops working. I
found another article saying that AS 2005 ignores basic authentication by
default, and gives steps to change the setting, but the screen that they talk
about doesn't exist, and the one that does that looks similar doesn't list
the properties necessary to change. Link to that article is...
http://msdn2.microsoft.com/en-us/library/ms174573.aspx. It says the
following - "Based on the default setting of 1, Analysis Services rejects
client requests that are submitted by using Basic authentication. To accept
client requests that use Basic authentication, change the setting for this
property to 0." I tried to add the property directly thru msmdsrv.ini file,
but that didn't seem to work either. Anyone else have any other ideas? I'm
desperate here - I'm supposed to be on vacation tomorrow, and if I don't have
this fixed by then, i'm in deep $*%!.


Thanks!

Scott Ivey

Once you enabled the Basic Authentication you need to make sure you specify
your credentials.
You can do it ever by specifying "user" and "password" connection string
properties in your connection string.
Or you can add "prompt=1" to your connection string and you will get
additional dialog asking for your credentials.


Edward Melomed
--
This posting is provided "AS IS" with no warranties, and confers no rights.



"Scott Ivey" <iveys (AT) online (DOT) nospam> wrote

I used prompt=1 in the connect string, but that doesn't work - I never get
prompted. Specifying user & password does work - but I'd like to have it
prompt for password instead. Are there any ideas why the prompt doesn't work?


Scott

"Edward Melomed [MSFT]" wrote:

That is strange.

What client application you are using?

If you have MDXSample app , try in the connection dialog specify provider as
"MSOLAP;prompt=1"
And you should see another box appear titled "Multidimensional Connection
9.0"

Edward Melomed
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Scott Ivey" <iveys (AT) online (DOT) nospam> wrote

I'm using OWC 11 as the app, hosted inside sharepoint site. prompt=1 does
nothing. I've tried changing every IE setting that I could think of to see
if that had anything to do with it, but no luck.


Scott

"Edward Melomed [MSFT]" wrote:

Hi Scott,

The following is the connecting string works on my side for basic
authentication:

<script language="vbscript">
sub button1_onclick()
PivotTable1.ConnectionString = "Provider=MSOLAP;" + _
"Data Source=http://localhost/as2005/msmdpump.dll;Initial
Catalog=adventureworksdw;prompt=1"
PivotTable1.DataMember = "adventure works dw"
end sub
</script>

I wonder if you test this on different client machines. In addition, I
suggest that you use a html file to test directly other than a aspx file.
If the VD hosting the html file is different from the VD hosting
msmdump.dll, you may check security settings for both VDs.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

================================================== ===

Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.

This and other support options are available here:

BCPS:
https://partner.microsoft.com/US/tec...rview/40010469

Others: https://partner.microsoft.com/US/tec...pportoverview/

If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/default...rnational.aspx.

================================================== ===

This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
<9C657D31-EA77-4B69-866B-841100DAE9F7 (AT) microsoft (DOT) com>
<#k0D1mE$FHA.2520 (AT) TK2MSFTNGP15 (DOT) phx.gbl>

Come on Edward, there are several posts on this newsgroup documenting that
HTTP with Basic Authentication doesn't work on AS2005.
I have a support incident open for 3 weeks and counting about this, and I
saw somebody else on this newsgroup with another support incident still open.
The issue is caused by OLEDB 9.0, who doesn't let the credentials pass from
IIS to AS2005.
It probably works on your own workstation because you are signed in as a
user that is known to the server, thus bypassing the basic authentication.


"Edward Melomed [MSFT]" wrote:

Hi Pat.
I was looking at your previous postings and it is bit hard to understand
what is going on in your situation.
When you are saying that you alreday authenticated to IIS , what does that
mean?


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

It means that I have authenticated to IIS with basic authentication. When the
client navigates to the page containing the OWC control, IIS requests the
userID+pwd for basic authentication.
With AS2000 that's all you need. The subsequent connection from OWC to
AS2000 is done using this authentication token.

With AS2005, you're suggesting to add a "prompt=1" in the OWC connection
string. What happens is the following: User navigates to the page containing
the OWC control and IIS requests the userID+pwd for basic authentication, as
above.
When connecting OWC to AS2005 though, the prompt=1 causes you to enter your
userID+password once again. This means that the previous authentication to
IIS is completely bypassed.
You have to do that because OLEDB 9.0 and AS2005 are not able to work the
way OLEDB 8.0 and AS2000 did. They cannot use the IIS token.

In my opinion, this is the reason why you cannot connect to AS2005 from
Excel, whichever way you try (even the prompt=1 cheat doesn't help) unless
client and server are in the same domain.


"Edward Melomed [MSFT]" wrote:

Pat - I agree with you that its a bigger problem. My solution worked fine
before I upgraded to AS2005. My current problem is that OWC hosted in my
sharepoint 2.0 site will now NEVER prompt for a username & password, even if
I include prompt=1. My sharepoint server & AS/HTTP server have different
domain names, so it should always prompt for the cross domain data request
anyway, but never does. It always did this with AS2000 before I upgraded to
2005, but since the upgrade, it never prompts. I'm able to use a hard-wired
username & password in the connect string, but would prefer to have it prompt
the user so that I can use their own username & password instead of a single
shared one. Another thing worth noting, is that like pat said, if I'm in the
domain or connected to the server via VPN, it will work, but when I'm not
connected via any other means than my IE browser to the sharepoint site,
nothing works at all.

I've had an open support ticket on this for a week now, and have had a hard
time convincing any of the support techs that I've talked to that this is a
problem for me. I keep getting handed around from group to group inside
microsoft, and everyone says that its the next guys problem. I'm feeling
like my $245 for this incident hasn't been well spent.

Scott

"Pat" wrote: