I've set up a virtual directory "olap" in IIS that points to
C:\Inetpub\wwwroot\olap which contains msolap.asp and msmdpump.dll.
(on WinXP with Analysis Services SP4) However, when I go to
http://localhost/olap/msmdpump.dll via the web browser, I only get "The
specified module could not be found." When I was still using the older
dll msxisapi.dll, I can simply point to it and get a soap response.
Can anyone please tell me what I'm doing wrong?

Thanks

You don't need to browse to the dll.

I know if you point a client, like an excel pivot table at the virtual
directory it should work. You should also get some sort of response when
you browse to http://localhost/olap/msolap.asp.

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

In article <1126857896.996131.225590 (AT) g44g2000cwa (DOT) googlegroups.com>,
alanwli (AT) gmail (DOT) com says...

When I try http://localhost/olap/msolap.asp, I only see a blank page in
the browser. Am I suppose to see XMLA responses like it did when
msxisapi.dll was used?

Thanks.

I have not used msxisapi.dll, so I cannot comment on that, but I just
double checked and if you are seeing a blank page that usually means
everything is working OK.

You should now be able to connect to AS2k from Excel or MDX sample using
HTTP access.

If it helps I have included a copy below of a post from a couple of
years ago on how to configure HTTP access.

===========================


1. On the Analysis Services computer, copy the Msolap.asp file from the
Program Files\Microsoft Analysis Services\Bin folder to either the
Inetpub\Wwwroot folder or to a subfolder under Wwwroot.

2. To make sure that Msolap.asp is installed and working properly, in
the Address bar type the URL HTTP://AnalysisServerName/Msolap.asp and
replace AnalysisServerName with the name of your server. Instead of the
error message:
"The page could not be displayed."
or a similar error, you should see a blank page if everything is working
properly.

3. If you are having problems in step 2, try setting the appropriate
authentication mechanisms by using Internet Services Manager (ISM). Set
Msolap.asp to use anonymous, basic, or Microsoft Windows NT
authentication as follows:
a. Right-click the file, and then click Properties.
b. Click the File Security tab, and then edit Anonymous Access
and Authentication Control to make changes.
c. Make sure that the appropriate access is provided to this
file.

4. To display another page with OLAP data, create an .htm or .asp page
with the following connection string and copy it to the Inetpub\Wwwroot
folder:

Provider=MSOLAP;Data Source=HTTP://AnalysisServerName;Initial
Catalog=FoodMart 2000;

Another trouble shooting step is to use the MDX sample application that
ships with Analysis Services and attempt to use the HTTP connection. To
do this, add HTTP:// in front of the server name when connecting. For
example: HTTP://MYSERVER

If you are using Basic Authentication you have to add PROMPT=1 to the
server name line to pass a Username and Password. This displays another
dialog where there are fields for the Username and Password. For
example: HTTP://MYSERVER;PROMPT=1

If you are able to successfully connect and query by using the MDX
sample application then IIS, Msolap.asp, Analysis Services and security
is configured correctly to make HTTP connections work.

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

In article <1127109890.728942.106780 (AT) g14g2000cwa (DOT) googlegroups.com>,
alanwli (AT) gmail (DOT) com says...