|
Home > Archive > MS SQL Server OLAP > November 2005 > HTTP Access to AS 2005 not working
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
HTTP Access to AS 2005 not working
|
|
|
| I have been following the article on Windows 2003, at
http://www.microsoft.com/technet/pr...5/httpasws.mspx and I get
a 500 error when trying to access the "http://MyMachine/olap/msmdpump.dll"
URL from Internet Explorer, running IE on the same server as AS 2005. The
client and the server are the same physical machine.
The article in itself is quite confusing as the pump path sometimes is
" C:\wwroot\olap\msmdp
ump.dll", sometimes " C:\inetpub\wwroot\ol
ap", and
sometimes " D:\tmp\isapi\msmdpum
p.dll".
Anyway, I'm running a named instance of the DB Engine, and a named instance
of the AS engine, both with the same name. Would that cause the issue?
I'm also running default instances of SQL and AS 2000 on that machine.
I've tried with Anonymous access and Windows auth, as per the article.
| |
|
| I have the same issue.
but in my case, I can create an initial connection, play with the cube, save
my analysis, but I can't reopen it! this is locally on the server
remotly, nothing works (initial access doesn't works)
"Pat" <pat@online.nospam> wrote in message
news:FD259FC7-BDF8-4341-BD8D- 9E3F104EF036@microso
ft.com...
>I have been following the article on Windows 2003, at
> http://www.microsoft.com/technet/pr...5/httpasws.mspx and I
> get
> a 500 error when trying to access the "http://MyMachine/olap/msmdpump.dll"
> URL from Internet Explorer, running IE on the same server as AS 2005. The
> client and the server are the same physical machine.
>
> The article in itself is quite confusing as the pump path sometimes is
> " C:\wwroot\olap\msmdp
ump.dll", sometimes " C:\inetpub\wwroot\ol
ap", and
> sometimes " D:\tmp\isapi\msmdpum
p.dll".
>
> Anyway, I'm running a named instance of the DB Engine, and a named
> instance
> of the AS engine, both with the same name. Would that cause the issue?
> I'm also running default instances of SQL and AS 2000 on that machine.
>
> I've tried with Anonymous access and Windows auth, as per the article.
| |
| ChrisHarrington 2005-11-20, 3:23 am |
| Hey Pat,
I have the same configuration and just setup the OLAP XMLA vdir yesterday
and it worked fine for me.
You are correct that the instructions have some errors in paths but you can
figure out what they really mean. Perhaps if you send the specific setup
steps you used then I could see where it differs from mine (I took notes
which I'll be posting to my blog shortly).
Chris
"Pat" <pat@online.nospam> wrote in message
news:FD259FC7-BDF8-4341-BD8D- 9E3F104EF036@microso
ft.com...
>I have been following the article on Windows 2003, at
> http://www.microsoft.com/technet/pr...5/httpasws.mspx and I
> get
> a 500 error when trying to access the "http://MyMachine/olap/msmdpump.dll"
> URL from Internet Explorer, running IE on the same server as AS 2005. The
> client and the server are the same physical machine.
>
> The article in itself is quite confusing as the pump path sometimes is
> " C:\wwroot\olap\msmdp
ump.dll", sometimes " C:\inetpub\wwroot\ol
ap", and
> sometimes " D:\tmp\isapi\msmdpum
p.dll".
>
> Anyway, I'm running a named instance of the DB Engine, and a named
> instance
> of the AS engine, both with the same name. Would that cause the issue?
> I'm also running default instances of SQL and AS 2000 on that machine.
>
> I've tried with Anonymous access and Windows auth, as per the article.
| |
|
| Hi Chris,
I followed the article exactly. I took the same path from beginning to end
(c:\inetpub\wwwroot\
olap\msmdpump.dll), none of this D:\tmp\...
The only other difference with the article is that I can see the ASP.NET tab
in the IIS virtual directory properties dialog, whereas this tab doesn't
appear in the screenshot of the article.
By the way, I just renamed my AS 2005 instance to have a different name from
my SQL 2005 instance, and the problem persists.
| |
| Darren Gosbell 2005-11-20, 8:23 pm |
| > I get a 500 error when trying to access the
> "http://MyMachine/olap/msmdpump.dll" URL from Internet Explorer
I don't think this URL is meant to work from IE. I get the same error,
yet my HTTP connection is working.
Try using "http://MyMachine/olap/msmdpump.dll" as the server name in the
MDX sample application from AS2k.
> Anyway, I'm running a named instance of the DB Engine, and a named instance
> of the AS engine, both with the same name. Would that cause the issue?
> I'm also running default instances of SQL and AS 2000 on that machine.
I have this exact same set up. All I had to change was the msmdpump.ini
file to point to my named instance.
HTH
--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
In article <FD259FC7-BDF8-4341-BD8D- 9E3F104EF036@microso
ft.com>,
pat@online.nospam says...
> I have been following the article on Windows 2003, at
> http://www.microsoft.com/technet/pr...5/httpasws.mspx and I get
> a 500 error when trying to access the "http://MyMachine/olap/msmdpump.dll"
> URL from Internet Explorer, running IE on the same server as AS 2005. The
> client and the server are the same physical machine.
>
> The article in itself is quite confusing as the pump path sometimes is
> " C:\wwroot\olap\msmdp
ump.dll", sometimes " C:\inetpub\wwroot\ol
ap", and
> sometimes " D:\tmp\isapi\msmdpum
p.dll".
>
> Anyway, I'm running a named instance of the DB Engine, and a named instance
> of the AS engine, both with the same name. Would that cause the issue?
> I'm also running default instances of SQL and AS 2000 on that machine.
>
> I've tried with Anonymous access and Windows auth, as per the article.
>
| |
| ChrisHarrington 2005-11-21, 3:23 am |
| When I access the URL via IE I get
<Error ErrorCode="3238920194" Description="Parser: The syntax for 'GET' is
incorrect." Source="Unknown" HelpFile=""/>
But no HTTP error.
What do you have in your ini file?
"Pat" <pat@online.nospam> wrote in message
news:5468304C-34F4-4C56-8141- 9CA8654152C3@microso
ft.com...
> Hi Chris,
>
> I followed the article exactly. I took the same path from beginning to end
> (c:\inetpub\wwwroot\
olap\msmdpump.dll), none of this D:\tmp\...
> The only other difference with the article is that I can see the ASP.NET
> tab
> in the IIS virtual directory properties dialog, whereas this tab doesn't
> appear in the screenshot of the article.
>
> By the way, I just renamed my AS 2005 instance to have a different name
> from
> my SQL 2005 instance, and the problem persists.
>
| |
|
| Thanks Darren,
This brings me one step further, the MDX Sample does work.
But I still cannot connect with the Office Web Components 11. I get the "XML
parsing failed at line 1, column 9: DTD is prohibited" error.
Here is the code I'm using in the OWC:
PivotTable1.ConnectionString = "Provider=MSOLAP.3;" + _
"Data Source=http://MyServer/olap/msmdpump.dll;Initial Catalog=MyOlapDB"
PivotTable1.DataMember = "MyCube"
| |
| Darren Gosbell 2005-11-22, 3:24 am |
| Hmm... not sure.
I tested by doing the following.
1) created a pivot table in excel, connecting to the http address
2) went to File > Save As Webpage
3) click on the Publish... button
4) choose to publish the pivot table
5) make sure to select the option to add interactivity with the
PivotTable functionality
6) save the file.
you should then be able to open up the htm file you just created in IE
and see a working/interactive pivot table.
if you open up the file in notepad (or some half decent text editor :) )
you will see that the pivot table properties is all stored as one but
xml string, the connection string is in there, but I cut mine down to
just the parameters that you listed (Provider, Data Source & Initial
Catalog) and it worked fine.
Maybe the problem is not in the connection, but in one of the other
properties.
--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
In article <BC2C085E-E44B-4E88-9C04- 91C239679214@microso
ft.com>,
pat@online.nospam says...
> Thanks Darren,
>
> This brings me one step further, the MDX Sample does work.
> But I still cannot connect with the Office Web Components 11. I get the "XML
> parsing failed at line 1, column 9: DTD is prohibited" error.
> Here is the code I'm using in the OWC:
>
> PivotTable1.ConnectionString = "Provider=MSOLAP.3;" + _
> "Data Source=http://MyServer/olap/msmdpump.dll;Initial Catalog=MyOlapDB"
> PivotTable1.DataMember = "MyCube"
>
>
>
| |
| Peter Yang [MSFT] 2005-11-22, 3:24 am |
| Hello Pat,
The error message does not seem to related to this line. I wonder how you
use OWC in your Web page. Will you provide a simple sample of the page?
The example in following link is for AS 2000 and OWC 10 but it shall be
similar for AS 2005.
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.
====================
====================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: HTTP Access to AS 2005 not working
| thread-index: AcXuhJTqqleJ+yrpSpK/EPihasn0gQ==
| X-WBNR-Posting-Host: 84.147.191.141
| From: =?Utf-8?B?UGF0?= <pat@online.nospam>
| References: <FD259FC7-BDF8-4341-BD8D- 9E3F104EF036@microso
ft.com>
<MPG. 1debcbcd41447e029897
db@news.microsoft.com>
| Subject: Re: HTTP Access to AS 2005 not working
| Date: Mon, 21 Nov 2005 02:16:05 -0800
| Lines: 12
| Message-ID: <BC2C085E-E44B-4E88-9C04- 91C239679214@microso
ft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.olap
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.olap:64684
| X-Tomcat-NG: microsoft.public.sqlserver.olap
|
| Thanks Darren,
|
| This brings me one step further, the MDX Sample does work.
| But I still cannot connect with the Office Web Components 11. I get the
"XML
| parsing failed at line 1, column 9: DTD is prohibited" error.
| Here is the code I'm using in the OWC:
|
| PivotTable1.ConnectionString = "Provider=MSOLAP.3;" + _
| "Data Source=http://MyServer/olap/msmdpump.dll;Initial
Catalog=MyOlapDB"
| PivotTable1.DataMember = "MyCube"
|
|
|
| |
|
| Thanks Darren, this was also a good idea, unfortunately I cannot connect in
Excel 2003. Although I go as far as being able to choose the cube for the
HTTP connection, I subsequently get "either a connection cannot be made to
the MyServer server, or Analysis Services is not running on the computer
specified".
However, the MDX application works fine with HTTP access (connection string:
http://MyServer/olap/msmdpump.dll;prompt=1)
Also, OWC works fine when going non-HTTP. (connection statements:
PivotTable1.ConnectionString = "Provider=MSOLAP.3;" + _
"Data Source=MyServer\MyIn
stance;Initial Catalog=MyOlapDb"
PivotTable1.DataMember = "MyCube")
The "olap" virtual directory is set up with Basic Authentication
To sum it up, OWC with HTTP isn't working, but OWC with direct connection is
working, and MDX sample App with HTTP is working.
Why I need OWC to work with HTTP is that we're using OWC as a client, and we
don't have a Windows network, so we need basic authentication.
| |
|
| Here is the complete page:
<%@ Page language="vb" AutoEventWireup="true" %>
<html>
<head>
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>Cube</title>
</head>
<body>
<OBJECT CLASSID = "clsid:5220cb21-c88d-11cf-b347-00aa00a28331">
<PARAM NAME="LPKPath" VALUE="license.lpk">
</OBJECT>
<p>
<object classid="clsid:0002E55a-0000-0000-C000-000000000046" id="PivotTable1">
<param name="XMLData" value="<xml
xmlns:x="urn:schemas-microsoft-com:office:excel">
<x:PivotTable>
<x:OWCVersion>11.0.0.5531 </x:OWCVersion>
<x:DisplayScreenTips/>
<x:CubeProvider>msolap</x:CubeProvider>
<x:CacheDetails/>
<x:PivotView>
<x:IsNotFiltered/>
</x:PivotView>
</x:PivotTable>
</xml>">
<table width='100%' cellpadding='0' cellspacing='0' border='0'
height='8'><tr><td bgColor='#336699' height='25' width='10%'> </td><td
bgColor='#666666'wid
th='85%'><font face='Tahoma' color='white' size='4'><b>
Missing: Microsoft Office Web Components</b></font></td></tr><tr><td
bgColor='#cccccc' width='15'> </td><td bgColor='#cccccc' width='500px'><br>
<font face='Tahoma' size='2'>This page requires the Microsoft Office Web
Components.<p align='center'> <a
href='http://www.microsoft.com/downloads/details.aspx?FamilyID=7287252c-402e-4f72-97a5-e0fd290d4b76&DisplayLang=en'>Click
here to install Microsoft Office Web Components.</a>.</p></font><p><font
face='Tahoma' size='2'>This page also requires Microsoft Internet Explorer
5.01 or higher.</p><p align='center'><a
href='http://www.microsoft.com/windows/ie/default.htm'> Click here to install
the latest Internet Explorer</a>.</font><br> </td></tr></table>
</object>
<br>
<br>
<input type="button" id="button1" value="Click Here">
<script language="vbscript">
sub button1_onclick()
PivotTable1.ConnectionString = "Provider=MSOLAP;" + _
"Data Source=http://MyServer/olap/msmdpump.dll;Initial Catalog=MyOlapDb"
PivotTable1.DataMember = "MyCube"
end sub
</script>
</p>
</body>
</html>
| |
|
| It has to do with Authentication.
When I add "prompt=1" to the OWC connection string, I'm asked for UserID +
password again, and I can subsequently work with the cube. That works when I
call the OWC page from within the server.
When I try calling the same page from a remote client, I'm also asked for
userid + password again (once for basic auth before the page loads, and once
because of the OWC connection string) and I then get: "Either a connection
cannot be made to the MyServer server, or Analysis Services is not running on
the computer specified".
| |
| Edward Melomed [MSFT] 2005-11-22, 8:24 pm |
| Download and install
http://download.microsoft.com/downl...ED
B9.msi
on your client.
Edward Melomed.
----
This posting is provided "AS IS" with no warranties, and confers no rights.
"Pat" <pat@online.nospam> wrote in message
news:52DA05D1-181B-49EC-A724- 924F4A465694@microso
ft.com...
> It has to do with Authentication.
>
> When I add "prompt=1" to the OWC connection string, I'm asked for UserID +
> password again, and I can subsequently work with the cube. That works when
> I
> call the OWC page from within the server.
>
> When I try calling the same page from a remote client, I'm also asked for
> userid + password again (once for basic auth before the page loads, and
> once
> because of the OWC connection string) and I then get: "Either a connection
> cannot be made to the MyServer server, or Analysis Services is not running
> on
> the computer specified".
>
| |
|
| The problem occurs on the server. I shouldn't have to have "prompt=1" in the
OWC connection string, since I've authenticated myself to IIS.
The prompt=1 causes OWC to ask for authentication again. This shoudn't be
necessary, and will prevent any client from connecting to the AS. And yes,
the clients have OLEDB 9 installed.
"Edward Melomed [MSFT]" wrote:
> Download and install
> http://download.microsoft.com/downl...ED
B9.msi
>
> on your client.
>
> Edward Melomed.
> ----
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Pat" <pat@online.nospam> wrote in message
> news:52DA05D1-181B-49EC-A724- 924F4A465694@microso
ft.com...
>
>
>
| |
| Darren Gosbell 2005-11-22, 8:24 pm |
| In article <E81223C9-A241-4B5C-8EB0- 8397A3858C3C@microso
ft.com>,
pat@online.nospam says...
> The problem occurs on the server. I shouldn't have to have "prompt=1" in the
> OWC connection string, since I've authenticated myself to IIS.
>
> The prompt=1 causes OWC to ask for authentication again. This shoudn't be
> necessary, and will prevent any client from connecting to the AS. And yes,
> the clients have OLEDB 9 installed.
>
I have not tried to use basic authentication with AS, but I might have
and idea why you have to authenticate twice.
What I think might be happening in this scenario is that the user
authenticates to IIS and it sends down a web page which has code in it
referring to the OWC ActiveX control. OWC then fires up and makes it's
own connection to AS. What some people do not realize is that OWC is a
client side technology, it uses PTS on the client to connect back to AS
and execute queries.
Can you try turning off basic authentication on the website that is
serving the pages and just leaving basic authentication on the virtual
folder containing msmdpump.dll?
--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
| |
|
| Hi
I have tried a lot of option from this list:
http://msdn2.microsoft.com/en-us/li...tionstring.aspx
first, when I'm using basi authentication, nothing works. (exception:
Additional information: The connection either timed out or was lost.)
using NTLM, the connection works locally only, not remotly (user outside the
domain)
When I setup: Integrated Security=Basic
I receive an error: Basic authentication NOT supported on HTTP / HTTPS
connections!!!!! (Additional information: The integrated security 'Basic' is
not supported for HTTP or HTTPS connections.)
but the web page says "An HTTP connection can use only the setting of
Basic."
So I'm confused about which parameter could be used or not.
"Darren Gosbell" <jam@newsgroups.nospam> wrote in message
news:MPG. 1dee657bc31fbf939897
e8@news.microsoft.com...
> In article <E81223C9-A241-4B5C-8EB0- 8397A3858C3C@microso
ft.com>,
> pat@online.nospam says...
>
> I have not tried to use basic authentication with AS, but I might have
> and idea why you have to authenticate twice.
>
> What I think might be happening in this scenario is that the user
> authenticates to IIS and it sends down a web page which has code in it
> referring to the OWC ActiveX control. OWC then fires up and makes it's
> own connection to AS. What some people do not realize is that OWC is a
> client side technology, it uses PTS on the client to connect back to AS
> and execute queries.
>
> Can you try turning off basic authentication on the website that is
> serving the pages and just leaving basic authentication on the virtual
> folder containing msmdpump.dll?
>
> --
> Regards
> Darren Gosbell [MCSD]
> Blog: http://www.geekswithblogs.net/darrengosbell
| |
|
| Hi Darren,
This exact same set-up works for AS 2000, once the user is authenticated to
IIS you can even open several different pages and connections without ever
being asked for credetientials again.
In any case I verified that the Default Web site doesn't have Basic auth
enabled and that the "olap" virtual directory has basic auth enabled.
| |
| Peter Yang [MSFT] 2005-11-23, 7:24 am |
| Hello Pat,
I agree with Darren that this Activex control such as pivottable on client
side need to authenticate to server by itself when connecting.
Based on my test, this issue does not occur when using Windows integration
authenction.
When using basic authentication without prompt=1, I received the exact
error message you encountered.
When setting prompt=1, I could access from both server console and client
but prompted to input credential to access of server (basic authentication
behavior) and configure AS server/connection in dialog.
I believe this is normal behavior when using basic authentication on olap
VD as Darren mentioned.
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.
====================
====================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: HTTP Access to AS 2005 not working
| thread-index: AcXvqzj6g7+8TXDoTVSM
CCa+UGH+CA==
| X-WBNR-Posting-Host: 145.254.241.103
| From: =?Utf-8?B?UGF0?= <pat@online.nospam>
| References: <FD259FC7-BDF8-4341-BD8D- 9E3F104EF036@microso
ft.com>
<MPG. 1debcbcd41447e029897
db@news.microsoft.com>
<BC2C085E-E44B-4E88-9C04- 91C239679214@microso
ft.com>
<52DA05D1-181B-49EC-A724- 924F4A465694@microso
ft.com>
<#Bxoov57FHA.1484@tk2msftngp13.phx.gbl>
| Subject: Re: HTTP Access to AS 2005 not working
| Date: Tue, 22 Nov 2005 13:25:12 -0800
| Lines: 40
| Message-ID: <E81223C9-A241-4B5C-8EB0- 8397A3858C3C@microso
ft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.olap
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.olap:64748
| X-Tomcat-NG: microsoft.public.sqlserver.olap
|
| The problem occurs on the server. I shouldn't have to have "prompt=1" in
the
| OWC connection string, since I've authenticated myself to IIS.
|
| The prompt=1 causes OWC to ask for authentication again. This shoudn't be
| necessary, and will prevent any client from connecting to the AS. And
yes,
| the clients have OLEDB 9 installed.
|
|
| "Edward Melomed [MSFT]" wrote:
|
| > Download and install
| >
http://download.microsoft.com/downl...C2-A67D-48053B8
F9FAD/ SQLServer2005_ASOLED
B9.msi
| >
| > on your client.
| >
| > Edward Melomed.
| > ----
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| >
| > "Pat" <pat@online.nospam> wrote in message
| > news:52DA05D1-181B-49EC-A724- 924F4A465694@microso
ft.com...
| > > It has to do with Authentication.
| > >
| > > When I add "prompt=1" to the OWC connection string, I'm asked for
UserID +
| > > password again, and I can subsequently work with the cube. That works
when
| > > I
| > > call the OWC page from within the server.
| > >
| > > When I try calling the same page from a remote client, I'm also asked
for
| > > userid + password again (once for basic auth before the page loads,
and
| > > once
| > > because of the OWC connection string) and I then get: "Either a
connection
| > > cannot be made to the MyServer server, or Analysis Services is not
running
| > > on
| > > the computer specified".
| > >
| >
| >
| >
|
| |
|
| This cannot be normal behavior. HTTP with basic authentication worked with AS
2000, it must work with AS 2005 too.
People are paying hefty license fees for the Enterprise Edition to have HTTP
functionality.
| |
|
| Also please make sure that client and server aren't in the same domain, and
you will be unable to connect to AS 2005 from the client, even with prompt=1.
| |
| Akshai Mirchandani [MS] 2005-11-23, 8:24 pm |
| I think that the issue may have to do with WinInet versus WinHttp. I believe
that MSOLAP80 used WinInet to connect to the server -- and WinInet probably
shares cookies within a process. So my guess is that if MSOLAP80 is running
inside Internet Explorer, the cookies obtained by Internet Explorer will be
automatically available to the MSOLAP80 HTTP connection.
But MSOLAP90 uses WinHttp (a similar but better and more secure API) -- I
think WinHttp does not automatically obtain the processes' WinInet cookies
and therefore you are required to re-validate.
As of now this is still just theory... I've filed a bug on this for further
investigation.
Thanks,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Pat" <pat@online.nospam> wrote in message
news:8AE32C67-CF39-4EDC-9AB9- 64144C198AFC@microso
ft.com...
> Hi Darren,
>
> This exact same set-up works for AS 2000, once the user is authenticated
> to
> IIS you can even open several different pages and connections without ever
> being asked for credetientials again.
>
> In any case I verified that the Default Web site doesn't have Basic auth
> enabled and that the "olap" virtual directory has basic auth enabled.
| |
| Akshai Mirchandani [MS] 2005-11-23, 8:24 pm |
| What is your connection string?
Thanks,
Akshai
--
This posting is provided "AS IS" with no warranties, and confers no rights
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Jéjé" < willgart@BBBhotmailA
AA.com> wrote in message
news:u$lx5i97FHA.3232@TK2MSFTNGP12.phx.gbl...
> Hi
>
> I have tried a lot of option from this list:
> http://msdn2.microsoft.com/en-us/li...tionstring.aspx
>
> first, when I'm using basi authentication, nothing works. (exception:
> Additional information: The connection either timed out or was lost.)
>
> using NTLM, the connection works locally only, not remotly (user outside
> the domain)
>
> When I setup: Integrated Security=Basic
> I receive an error: Basic authentication NOT supported on HTTP / HTTPS
> connections!!!!! (Additional information: The integrated security 'Basic'
> is not supported for HTTP or HTTPS connections.)
> but the web page says "An HTTP connection can use only the setting of
> Basic."
>
> So I'm confused about which parameter could be used or not.
>
>
> "Darren Gosbell" <jam@newsgroups.nospam> wrote in message
> news:MPG. 1dee657bc31fbf939897
e8@news.microsoft.com...
>
>
| |
|
| Thanks for the update Akshai. This fits the symptoms.
|
|
|
|
|