Here is the situation :

I am developing asp.net application using owc 11 to connect SSAS 2005
through http access. Analysis server is on different machine (behind
firewall) separate from machine running IIS as web server.

Sql Server 2005 SP1, Owc 11, SSAS 9 OLEDB Provider, are installed on my
development machine.

I have followed through article at
http://www.microsoft.com/technet/pro.../httpssas.mspx , the
only thing that not working is msmdpump.ini file, the file seems useless,
because whatever value I put for <ServerName> section is discarded.

Below is my client script for pivot table’s connection string :

document.pTable.ConnectionString = "Provider=MSOLAP.3;Integrated
Security=SSPI;Data Source=http://localhost/olap/msmdpump.dll; Initial
Catalog=Analysis Services Tutorial;" ;

document.pTable.DataMember = "Analysis Services Tutorial";

The funny thing is, whatever value i put for <ServerName> section at
msmdpump.ini file, pivot table is able to load data!!.

I even delete all contents at msmdpump.ini file, the code still works.
Any help will be appreciated, thanks

if the AS server is on the same computer as you IIS/OLAP access, then, the
msmdpump use default values so its the <servername> = localhost

but its strange that the pump works when you put another server name which
is a non existing server name...

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