Re: MDX Sample App broken by 2005
- From: "James" <aa1948@xxxxxxxxxxxxx>
- Date: Fri, 25 Nov 2005 10:27:02 -0800
That sounds like a solution. I hope it works on AS 2005 and Win 2003, because
having the same user and pwd on both client and server didn't work for me.
I'll try it as soon as I get in the office on Monday. Many thanks.
"Dave Wickert [MSFT]" wrote:
> I talk about this a bit in the AS Operations Guide in the security
> section -- I give several workarounds (albeit with various security issues
> associated with the). You might find it useful as an alternative to http
> access if this is all you are using http access for (i.e. to cross untrusted
> domains)
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx
> --
> Dave Wickert [MSFT]
> dwickert@xxxxxxxxxxxxxxxxxxxx
> Program Manager
> BI Systems Team
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "James" <aa1948@xxxxxxxxxxxxx> wrote in message
> news:E5282060-8882-4FF4-9659-E58E1FD7BC55@xxxxxxxxxxxxxxxx
> > Hi Peter, Windows authentication wouldn't work since client and server are
> > in
> > different non-trusted domains. If Windows auth would work, I wouldn't need
> > HTTP.
> >
> > I did follow the article you mention and also installed OLEDB 9 on the
> > client.
> > Can you get it to work in a scenario where client and server are in
> > separate
> > non-trusted domains? The user signed-in at the client must not exist with
> > the
> > same password on the server.
> >
> > I'm open to suggestions as of how I can access my AS server from outside
> > the
> > domain.
> >
> >
> >
> > "Peter Yang [MSFT]" wrote:
> >
> >> Hello,
> >>
> >> To understand the issue better, I'd like to know how you configure
> >> authentication method for the 2005 olap VD, do you use Windows
> >> authentication or basic authentication?
> >>
> >> You may want to refer to the following article:
> >>
> >> http://www.microsoft.com/technet/prodtechnol/sql/2005/httpasws.mspx
> >>
> >> 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: MDX Sample App broken by 2005
> >> | thread-index: AcXw6UpsN93v0MLXRzyzy1AsszoI2Q==
> >> | X-WBNR-Posting-Host: 84.147.161.107
> >> | From: "=?Utf-8?B?SmFtZXM=?=" <aa1948@xxxxxxxxxxxxx>
> >> | Subject: MDX Sample App broken by 2005
> >> | Date: Thu, 24 Nov 2005 03:22:01 -0800
> >> | Lines: 20
> >> | Message-ID: <096FD515-5DA8-45C7-97A4-CC632553028D@xxxxxxxxxxxxx>
> >> | 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:64833
> >> | X-Tomcat-NG: microsoft.public.sqlserver.olap
> >> |
> >> | I'm using the MDX Sample Application to access our AS2000 SP3 cubes via
> >> HTTP,
> >> | with success.
> >> |
> >> | I've tried the same with AS2005, and I get all sorts of errors,
> >> although
> >> I
> >> | allways try to connect in the same manner.
> >> | For instance "Unable to establish connection. Object or provider is not
> >> | capable of performing operation", or
> >> | "XML parsing failed at line 1, column 0: A document must contain
> >> exactly
> >> one
> >> | root element"
> >> |
> >> | The connection string for the failing AS2005 access:
> >> | "http://SERVER/olap/msmdpump.dll;prompt=1", and the provider MSOLAP.3
> >> |
> >> | For AS2000 access (and this is working fine): "http://SERVER/VirtDir/",
> >> and
> >> | the provider MSOLAP.2
> >> |
> >> | The client and the server are in 2 separate, non-trusted domains
> >> (otherwise
> >> | I wouldn't need to use HTTP)
> >> |
> >> |
> >> |
> >>
> >>
>
>
>
.
- Follow-Ups:
- Re: MDX Sample App broken by 2005
- From: Dave Wickert [MSFT]
- Re: MDX Sample App broken by 2005
- References:
- RE: MDX Sample App broken by 2005
- From: Peter Yang [MSFT]
- RE: MDX Sample App broken by 2005
- From: James
- Re: MDX Sample App broken by 2005
- From: Dave Wickert [MSFT]
- RE: MDX Sample App broken by 2005
- Prev by Date: Re: Referenced dimension causes fact table to be filtered
- Next by Date: Re: Referenced dimension causes fact table to be filtered
- Previous by thread: Re: MDX Sample App broken by 2005
- Next by thread: Re: MDX Sample App broken by 2005
- Index(es):
Relevant Pages
|