I have a web page on a web server that pulls data from a cube on another
server that has SQL Server Analysis Serivces installed. When I try to
establish the connection I get the following error:

Microsoft® OLE DB Provider for Analysis Services error '80004005'

Database 'Backoffice' does not exist.

/.../.../....asp, line 154

I have done some reading and tried several things already, but have only
gotten a little bit closer. I have AS installed on the web server as well (I
am moving the cubes from this computer to the other one to reduce the load
on the server) and don't get any problems. Here is what I have done:

Reinstalled SQL Server Analysis Services SP3 on the SQL Server
Reinstalled SQL Server Analysis Services SP3 on the Web Server (this allowed
me to start using the MDX Sample Application to query cubes on the SQL
Server, which did not work before I did this)

I've gotten it so that I can access the server from another computer using
the MDX Sample Application and Microsoft Excel 2003. However, I still cannot
get my web page to see the database. I am using an ado connection object to
try to establish the connection, and then (the code never gets this far), I
have an MDX statement that loads a recordset full of the data to be
displayed. Here is the connection string:

cn.Open "Data Source=SERVERNAME;Initial Catalog=Backoffice;Provider=msolap;"

Can anyone help me out? Thanks!

Chet

I am having the same problem anyone that can help with this would be
greatly appreciated.

"Chet Cromer" <chetsjunk (AT) ccrtc (DOT) com> wrote

80004005 is "access is denied".
Any ACLs on files or registry settings? It could be LOTS of things.

If running from a client machine, then you cannot run the virtual directory
with NTLM -- authentication must be basic or anonymous. This is because of
the NT one-hop limitation for passing NTLM credentials. If this is the case,
what happens if you run the web app from the web server itself?
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Joe Newlin" <jdaccel (AT) netscape (DOT) net> wrote

Chet,
STOP reinstalling things. (we assume here that the OLAP Database
Backoffice exists).
What is the authentication method used by the asp page which is attempting
to use your connection string. The format you are using will us the
identity of the called (the asp page).
Is this user allowed to access the database? look at your security setup.

hope this helps,

dlr

"Chet Cromer" <chetsjunk (AT) ccrtc (DOT) com> wrote

Authentication methods are Anonymous and Basic.

This page is part of an intranet site for a small company, and we
control access to the pages through our own id/password list (do not
utilize any windows security).

The default user for Anonymous is the IUSR... account for the web
server, which now that I think of it, would not have access to ANYTHING
on the other server, since it's not a domain account. If I changed the
default account to a domain account with access to the data on the
server, would that do the trick?

Thanks for your help... I'll stop reinstalling things now.

Chet

"Dennis Redfield" <dennis.redfield (AT) acadia-ins (DOT) com> wrote

Another question...

Can I work the User ID and Password into the connection string instead
of relying on the userid/password of the account being used to access
the asp page? Assume anybody who can GET to this page is allowed to view
it.

Chet

"Chet Cromer" <chetsjunk (AT) ccrtc (DOT) com> wrote

Bingo. Set it up as a domain account. That will be the security context for
accessing the Analysis server.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Chet Cromer" <chetsjunk (AT) ccrtc (DOT) com> wrote

The uid and pwd on the connect string are only used when the connection is
using http access. Normal client-server connections to Analysis Services
*must be* trusted connections (uid and pwd on the connect string are
ignored). For http access, you need to install IIS on your Analysis server.
See BOL under the topics "Connecting Using HTTP" and "How to configure
Analysis Services for the web" for instruction on how to configure http
access.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Chet Cromer" <chetsjunk (AT) ccrtc (DOT) com> wrote

Perfect. Thanks for the assistance. If I remember, you can't access the
Analysis Server over HTTP using SQL Server Standard edition, can you? I
remember coming down this road before, I think.


"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote

Correct. Http access is a feature of SQL Server 2000 Enterprise Edition.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Chet Cromer" <chetsjunk (AT) ccrtc (DOT) com> wrote