I know there are topics addressing this subject, but my problem is not
covered by them.

I have a aspx 2.0 application connecting to Analysis Services 2005.

When I open and run the application in Vs.net 2005 via the file system
it works fine.

When I open and run it via IIS it fails to connect to analysis server
(giving the message "Provider cannot be found. It may not be properly
installed.")

My first thought was that this must be a permissions issue, relating to
the user accounts that are being used by either the Asp.net process of
the internet IUSR account etc.

However adjusting permissions in all kinds of ways made no difference.

The connection string I am using is:

"Provider=MSOLAP.3;Data Source=XEON;Integrated Security=SSPI;Initial
Catalog=OLAPDemo")

Any help much appreciated.

Did you install PTS9 on the web server? This contains the MSOLAP
provider that is needed by any client that access an AS2k5 server (in
your case the web server is the client of the AS server)

--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell

In article <1130319185.295800.81350 (AT) f14g2000cwb (DOT) googlegroups.com>,
Andrew (AT) Bindon (DOT) org says...

Thanks for responding, Darren, however this is not the solution to my
problem.

The provider for Analysis Services 9 is installed on the server.

Also, don't forget that the web site runs fine in VS.net 2005 when I
load it via the file system
eg. c:\inetput\wwwroot\sitename\default.aspx

It only gives me the error when I load it via http
eg. http://localhost/sitename/default.aspx

My latest thought was to use impersonation in the web.config eg.
<identity impersonate="true" userName="xxxx" password="xxxx" />
but this also made no difference.

Sorry, I did not realize you were talking about localhost. I thought
that the server was a separate machine.

This will probably be something to do with the ASPNET account if you are
running on IIS 5 (WinXP or 2000) or the application pool settings if you
are running on IIS 6 (Win2k3 Server)

This would have been my next suggestion, userName would have to be a
domain user that has been set up in a role on the AS server with access
to the cube(s) or a local account that has the identical username and
password on both your machine and the AS server.

If you are on Win2k3 Server, you could try setting up an application
pool using a domain account that has access to the AS cubes and setup
you virtual directory to use this app pool.

Another option is to use HTTP authentication and pass a username and
password to AS, avoiding the need to do any impersonation on the ASP.NET
side.

--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell

In article <1130374942.337386.71510 (AT) g14g2000cwa (DOT) googlegroups.com>,
Andrew (AT) Bindon (DOT) org says...