Hi All,

I have created an HTML page that uses MS Web component to
connect to SQL server cube. Everything is fine when I
call the web page from within the domain in which the SQL
server resides. However, if I try to call the same page
from outside the domain, I get the following error.

"The Query could not be processed". The data provider did
not supply any further information.

I then tried to create a brand new web page from outside
the domain. First, I put in my web component, then tried
to create a data source to link it to the cubes, this
results in the following error:

"Unable to connect to the datasource. Reason: unable to
locate database server. Verify that the database server
name you entered is correct or contact the database
administrator"

I am sure that the database name is correct and that it
was accessible at the time I tried to create the
connection. It seems to me as though it is an
authentication issue i.e. I'm not allowed to connect to
the analysis server because I'm not part of the domain.

As anybody encountered a similar problem ? if so, is
there a solution to the problem ?

Any help would be greatly appreciated.

Regards,

Francois

What you are seeing is a fairly common misconception of OWC. While OWC looks
like it is using IIS to access the Analysis server, in reality, the only
thing that IE is providing is the screen real estate for the ActiveX
control. Behind the user, OWC is making a direct connection to the Analysis
server you specified as the server name -- IIS does not get involved at all
(unless you are using http access which you didn't say that you were). So
the NT account that is being used is the end-user's account. And that
account must be in some trust relationship with the Analysis server for
Analysis Services to allow the end-user to connect. Analysis Services
requires NT authentication.

Another valuable source of information is the Security sections in the
Analysis Services Operations Guide at:
http://www.microsoft.com/technet/pro...e/anservog.asp
You might find that useful as well.

Hope that helps.
--
Dave Wickert [MS]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Francois" <lf4446 (AT) hotmail (DOT) com> wrote

Thanks for your help. It pointed me in the right
direction. I found a way around the problem (not sure
whether it is the best solution, but it will do for now).
I created the same username (AND PASSWORD) in the domain
containing the Analysis server (as the one in the
external domain) and it worked fine.

Thanks again.

Francois

Yup. That is an old NT backdoor.
Look at the Security section in the Analysis Services Operations Guide for
more 'hints' :-)
I listed this and several other options there.
--
Dave Wickert [MS]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Francois" <anonymous (AT) discussions (DOT) microsoft.com> wrote