I can successfully connect to a test server where IIS and AS are on the same server.
When I change the pump.servername line in msolap.asp file it continues to 'point' to the cubes on the same server.

I can even put in some rubbish like pump.servername = "abcdef123"
and it still returns the data from the same server.

I've read, read and re-read the microsoft article 'Improved web connectivity in MS SQL Server 2K Analysis services" and followed the instructions to the letter.

Any ideas please

verify your name resolution, try to put the IP address instead of the
netbios name.
verify that the virtual directory point on the right msolap.asp file; maybe
you have changed a copy of this file, but not the one really used.

do you have multiple msolap.asp files setup on your server?
Like:
http://server/olap1/msolap.asp --> local AS server
http://server/olap2/msolap.asp --> remote AS server

under IIS6, create a dedicated application pool
after any change, reset IIS to make sure that the changes are reloaded.

"monchopper" <monchopper.2aj41z (AT) no-mx (DOT) forums.yourdomain.com.au> wrote in
message news:monchopper.2aj41z (AT) no-mx (DOT) forums.yourdomain.com.au...

I've isolated the msolap.asp file and know that it's the correct file. But it still doesn't work. The server I want to connect to is called NOR-BL02

If I use
pump.servername = 'NOR-BL02' then is returns an error
if I use
pump.servername = "NOR-BL02" then it looks at the AS on the same server NOT at NOR-BL02.

I have SP4 on. Could it be the version of IIS? This is getting really annoying!!

have you try to use the DNS name? or IP address?
instead of the netbios name.


"monchopper" <monchopper.2b56hz (AT) no-mx (DOT) forums.yourdomain.com.au> wrote in
message news:monchopper.2b56hz (AT) no-mx (DOT) forums.yourdomain.com.au...

I have tried using the IP address in the connection string and in the msolap.asp file.

In one microsoft article is says that IIS needs to be on both servers, but in others it doesn't mention this?

no, only the front end server required IIS
but you can setup IIS on the 2 servers and the frontend server will connect
to the second IIS server instead-of using a direct connection.
But I repeat, its an option, its NOT a requirement.

do you use NTLM (windows integrated) security or the Basic authentication?

"monchopper" <monchopper.2b6stz (AT) no-mx (DOT) forums.yourdomain.com.au> wrote in
message news:monchopper.2b6stz (AT) no-mx (DOT) forums.yourdomain.com.au...

I have tried Annonymous, Basic and Window authentication.

AS standard edition 2K is on the machine running IIS, would this make a difference?

mmm...
not sure if having Std edition on the IIS server could cause this issue.
Maybe verify that you use the datapump dll from the Enterprise Edition
(normally this dll is not in the standard package)

if you have another IIS Server where there is no AS installed on it, try to
setup the msolap.asp on this server.
this will help you to identify if the problem is at the IIS server level, AS
server or a conflict with the standard edition on the IIS server.


"monchopper" <monchopper.2b7c9z (AT) no-mx (DOT) forums.yourdomain.com.au> wrote in
message news:monchopper.2b7c9z (AT) no-mx (DOT) forums.yourdomain.com.au...