I have been following the article on Windows 2003, at
http://www.microsoft.com/technet/pro.../httpasws.mspx and I get
a 500 error when trying to access the "http://MyMachine/olap/msmdpump.dll"
URL from Internet Explorer, running IE on the same server as AS 2005. The
client and the server are the same physical machine.

The article in itself is quite confusing as the pump path sometimes is
"C:\wwroot\olap\msmdpump.dll", sometimes "C:\inetpub\wwroot\olap", and
sometimes "D:\tmp\isapi\msmdpump.dll".

Anyway, I'm running a named instance of the DB Engine, and a named instance
of the AS engine, both with the same name. Would that cause the issue?
I'm also running default instances of SQL and AS 2000 on that machine.

I've tried with Anonymous access and Windows auth, as per the article.

I have the same issue.
but in my case, I can create an initial connection, play with the cube, save
my analysis, but I can't reopen it! this is locally on the server
remotly, nothing works (initial access doesn't works)

"Pat" <pat (AT) online (DOT) nospam> wrote

Hey Pat,

I have the same configuration and just setup the OLAP XMLA vdir yesterday
and it worked fine for me.

You are correct that the instructions have some errors in paths but you can
figure out what they really mean. Perhaps if you send the specific setup
steps you used then I could see where it differs from mine (I took notes
which I'll be posting to my blog shortly).

Chris

"Pat" <pat (AT) online (DOT) nospam> wrote

Hi Chris,

I followed the article exactly. I took the same path from beginning to end
(c:\inetpub\wwwroot\olap\msmdpump.dll), none of this D:\tmp\...
The only other difference with the article is that I can see the ASP.NET tab
in the IIS virtual directory properties dialog, whereas this tab doesn't
appear in the screenshot of the article.

By the way, I just renamed my AS 2005 instance to have a different name from
my SQL 2005 instance, and the problem persists.

I don't think this URL is meant to work from IE. I get the same error,
yet my HTTP connection is working.

Try using "http://MyMachine/olap/msmdpump.dll" as the server name in the
MDX sample application from AS2k.

I have this exact same set up. All I had to change was the msmdpump.ini
file to point to my named instance.

HTH

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

In article <FD259FC7-BDF8-4341-BD8D-9E3F104EF036 (AT) microsoft (DOT) com>,
pat (AT) online (DOT) nospam says...

When I access the URL via IE I get
<Error ErrorCode="3238920194" Description="Parser: The syntax for 'GET' is
incorrect." Source="Unknown" HelpFile=""/>
But no HTTP error.

What do you have in your ini file?

"Pat" <pat (AT) online (DOT) nospam> wrote

Thanks Darren,

This brings me one step further, the MDX Sample does work.
But I still cannot connect with the Office Web Components 11. I get the "XML
parsing failed at line 1, column 9: DTD is prohibited" error.
Here is the code I'm using in the OWC:

PivotTable1.ConnectionString = "Provider=MSOLAP.3;" + _
"Data Source=http://MyServer/olap/msmdpump.dll;Initial Catalog=MyOlapDB"
PivotTable1.DataMember = "MyCube"

Hmm... not sure.

I tested by doing the following.

1) created a pivot table in excel, connecting to the http address
2) went to File > Save As Webpage
3) click on the Publish... button
4) choose to publish the pivot table
5) make sure to select the option to add interactivity with the
PivotTable functionality
6) save the file.

you should then be able to open up the htm file you just created in IE
and see a working/interactive pivot table.

if you open up the file in notepad (or some half decent text editor )
you will see that the pivot table properties is all stored as one but
xml string, the connection string is in there, but I cut mine down to
just the parameters that you listed (Provider, Data Source & Initial
Catalog) and it worked fine.

Maybe the problem is not in the connection, but in one of the other
properties.

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

In article <BC2C085E-E44B-4E88-9C04-91C239679214 (AT) microsoft (DOT) com>,
pat (AT) online (DOT) nospam says...

Hello Pat,

The error message does not seem to related to this line. I wonder how you
use OWC in your Web page. Will you provide a simple sample of the page?

The example in following link is for AS 2000 and OWC 10 but it shall be
similar for AS 2005.

Best 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.

--------------------

Thanks Darren, this was also a good idea, unfortunately I cannot connect in
Excel 2003. Although I go as far as being able to choose the cube for the
HTTP connection, I subsequently get "either a connection cannot be made to
the MyServer server, or Analysis Services is not running on the computer
specified".
However, the MDX application works fine with HTTP access (connection string:
http://MyServer/olap/msmdpump.dll;prompt=1)

Also, OWC works fine when going non-HTTP. (connection statements:
PivotTable1.ConnectionString = "Provider=MSOLAP.3;" + _
"Data Source=MyServer\MyInstance;Initial Catalog=MyOlapDb"
PivotTable1.DataMember = "MyCube")

The "olap" virtual directory is set up with Basic Authentication

To sum it up, OWC with HTTP isn't working, but OWC with direct connection is
working, and MDX sample App with HTTP is working.

Why I need OWC to work with HTTP is that we're using OWC as a client, and we
don't have a Windows network, so we need basic authentication.