Web Service returns 404

[September]

I have read numerous posts on this same issue and searched Microsoft's
knowledge base and there are no solutions offered.

I have a web service installed on 4 machines: 2 dev servers, 1 staging
and production. The web service works fine on 3 of the machines,
however, on one dev server, invoking the service returns a 404. You
browse to the .asmx file and view the wsdl no problem, but invoking a
web service call returns a 404.

We tried making sure all the possible .net extensions are mapping to
the asp.net dll. We also reinstalled the .net framework using
aspnet_regiis.

Is there anyone out there who has found what is causing this?

Thanks in advance!
September

[September]

I figured it out - after spending an hour on the phone with Microsoft
support.

In application configuration, where mapping file extensions to the dll
- the asmx extension should not have the checkbox "Check to see file
exists" selected.
Hope that helps other people out - thanks.

se***********@yahoo.com (September) wrote in message news:<ea**************************@posting.google. com>...

I have read numerous posts on this same issue and searched Microsoft's
knowledge base and there are no solutions offered.

I have a web service installed on 4 machines: 2 dev servers, 1 staging
and production. The web service works fine on 3 of the machines,
however, on one dev server, invoking the service returns a 404. You
browse to the .asmx file and view the wsdl no problem, but invoking a
web service call returns a 404.

We tried making sure all the possible .net extensions are mapping to
the asp.net dll. We also reinstalled the .net framework using
aspnet_regiis.

Is there anyone out there who has found what is causing this?

Thanks in advance!
September