Has anyone experienced this error:

The HTTP server returned the following error: Method Not Allowed

Some of the users are receiving this error when aaccessing the Cube from
excel. I and another user are not getting this error so I am not sure if it
is related to the cube or the IIS server.

do you use AS2000 or 2005?
if 2005, does all the client desktop use the 2005 drivers?
what is the content of the IIS log file? do you see some errors on it?
do you have a proxy server between the users and the IIS server?

what's appends if you open a cube from a working station, save the excel
file and open it from a non-working station?

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

Jeje,
I work with SAM

This is on AS2000.

This is the IIS Log:
2006-09-06 14:30:43 W3SVC1 192.xxx.xxx.xxx POST / - 80 - 64.xxx.xxx.xxx
MSOLAP+9.0+Client 401 2 2148074254
2006-09-06 14:30:45 W3SVC1 192.xxx.xxx.xxx POST / - 80 - 64.xxx.xxx.xxx
MSOLAP+9.0+Client 401 1 0
2006-09-06 14:30:45 W3SVC1 192.xxx.xxx.xxx POST / - 80 - 64.xxx.xxx.xxx
MSOLAP+9.0+Client 401 1 2148074252
2006-09-06 14:30:45 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 2 2148074254
2006-09-06 14:30:55 W3SVC1 192.xxx.xxx.xxx POST / - 80 - 64.xxx.xxx.xxx
MSOLAP+9.0+Client 401 2 2148074254
2006-09-06 14:30:55 W3SVC1 192.xxx.xxx.xxx POST / - 80 - 64.xxx.xxx.xxx
MSOLAP+9.0+Client 401 1 0
2006-09-06 14:30:55 W3SVC1 192.xxx.xxx.xxx POST /iisstart.htm - 80
DOMAIN\user.name 64.xxx.xxx.xxx MSOLAP+9.0+Client 405 0 0
2006-09-06 14:30:55 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 2 2148074254
2006-09-06 14:30:55 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 1 0
2006-09-06 14:30:55 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80
DOMAIN\user.name 64.xxx.xxx.xxx Light+DCube 200 0 0
2006-09-06 14:30:55 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 2 2148074254
2006-09-06 14:30:55 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 1 0
2006-09-06 14:30:55 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80
DOMAIN\user.name 64.xxx.xxx.xxx Light+DCube 200 0 0
2006-09-06 14:30:56 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 2 2148074254
2006-09-06 14:30:56 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 1 0
2006-09-06 14:30:56 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80
DOMAIN\user.name 64.xxx.xxx.xxx Light+DCube 200 0 0
2006-09-06 14:30:56 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 2 2148074254
2006-09-06 14:30:56 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 1 0
2006-09-06 14:30:56 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80
DOMAIN\user.name 64.xxx.xxx.xxx Light+DCube 200 0 0
2006-09-06 14:30:58 W3SVC1 192.xxx.xxx.xxx POST / - 80 - 64.xxx.xxx.xxx
MSOLAP+9.0+Client 401 2 2148074254
2006-09-06 14:30:58 W3SVC1 192.xxx.xxx.xxx POST / - 80 - 64.xxx.xxx.xxx
MSOLAP+9.0+Client 401 1 0
2006-09-06 14:30:58 W3SVC1 192.xxx.xxx.xxx POST /iisstart.htm - 80
DOMAIN\user.name 64.xxx.xxx.xxx MSOLAP+9.0+Client 405 0 0
2006-09-06 14:30:58 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 2 2148074254
2006-09-06 14:30:58 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 1 0
2006-09-06 14:30:58 W3SVC1 192.xxx.xxx.xxx POST /msolap.asp - 80 -
64.xxx.xxx.xxx Light+DCube 401 1 2148074252

This log segment is for one try/failure with the error SAM mentioned.
"Method not Allowed" (http 405) It looks like it's getting 401 errors
also. The odd thing is this is only happening with one client machine.

There is a proxy server between the users and the IIS server.

If the cube is opened and the excel file saved and sent and opened on
the non-working station, the same error occurs after the user tries to
authenticate.

Thank you,
John

Jeje wrote:

if the issue is for 1 station only
take a closer look at the drivers, the versions and any web component
installed.
for example the google bar and other google tools can cause issues for
services like OLAP HTTP access

verify the proxy configuration to access the web etc...



<docjohnboy (AT) gmail (DOT) com> wrote

The problem was, SQL 2000 was also installed on the workstation and was
not at the same service pack level as the Analysis Server.
Installing the service pack got rid of the error message.

Thank you,
John

Jeje wrote:

oohh...
sometimes the connectionstring must contain the "id" of the driver:
provider=MSOLAP.3
by default the system use the MSOLAP provider and scan the registry to find
the current version.
an update on the system can rollback the installation to the MSOLAP.2 (SQL
2000) drivers.

<docjohnboy (AT) gmail (DOT) com> wrote

Ok, Now another client is having this issue, however installing SQL
2000 SP4 did not solve it. We have checked the connection string and it
does in fact say provider=MSOLAP.2. Any more suggestions.

Thanks in advance.
-John

Jeje wrote: