IIS returning HTTP 404 error
rich
I am testing a BizTalk application. I am using the SoapUI tool to send
messages to a web service on BizTalk, through IIS. BizTalk and IIS 5.0 are
running on a Windows XP desktop.
When I send the message, IIS is returning an HTTP 404 - File Not Found error
for 1 specific file. This occurs only on a Post operation. If I send a Get
request, it succeeds. That is, I can browse to the file representing the web
service. It comes up and displays as expected. It is only when actually
sending this SOAP message that the 404 gets returned.
I've changed security on the target file/folder, but get exact same results.
So, the file is definitely there.
What could cause a 404 error when you're certain it is there, and you're
certain that security is not preventing access?
Thanks in advance,
Rich
Brian Cryer
news:C5CC8B57-9995-4758...@microsoft.com...
> Hello,
>
>
> I am testing a BizTalk application. I am using the SoapUI tool to send
> messages to a web service on BizTalk, through IIS. BizTalk and IIS 5.0
> are
> running on a Windows XP desktop.
>
> When I send the message, IIS is returning an HTTP 404 - File Not Found
> error
> for 1 specific file. This occurs only on a Post operation. If I send a
> Get
> request, it succeeds. That is, I can browse to the file representing the
> web
> service. It comes up and displays as expected. It is only when actually
> sending this SOAP message that the 404 gets returned.
>
> I've changed security on the target file/folder, but get exact same
> results.
> So, the file is definitely there.
Just a thought, if you look at the logs is the request definitly for the
page you think it is?
> What could cause a 404 error when you're certain it is there, and you're
> certain that security is not preventing access?
I have seen a GET request fail because the file or folder name is reserved.
I had trouble showing a file called /bin/1.htm even though the file existed.
Unlikely to be the issue in your case if GET works but POST doesn't.
> Thanks in advance,
>
> Rich
--
Brian Cryer
http://www.cryer.co.uk/brian
rich
#Software: Microsoft Internet Information Services 5.1
#Version: 1.0
#Date: 2010-08-18 12:20:00
#Fields: date time c-ip cs-username s-sitename s-ip s-port cs-method
cs-uri-stem cs-uri-query sc-status sc-win32-status
2010-08-18 12:20:00 19.39.57.127 - W3SVC1 109.22.57.127 80 POST
/ESBReceiver/Receive.svc - 404 0
2010-08-18 12:20:38 127.0.0.1 - W3SVC1 127.0.0.1 80 GET
/ESBReceiver/Receive.svc - 200 0
2010-08-18 12:20:51 19.39.57.127 - W3SVC1 109.22.57.127 80 POST
/ESBReceiver/Receive.svc - 404 0
2010-08-18 12:20:51 19.39.57.127 - W3SVC1 109.22.57.127 80 POST
/ESBReceiver/Receive.svc - 404 0
2010-08-18 12:20:52 19.39.57.127 - W3SVC1 109.22.57.127 80 POST
/ESBReceiver/Receive.svc - 404 0
2010-08-18 12:21:00 127.0.0.1 - W3SVC1 127.0.0.1 80 GET
/ESBReceiver/Receive.svc - 200 0
2010-08-18 12:21:14 19.39.56.18 - W3SVC1 109.22.57.127 80 GET
/ESBReceiver/Receive.svc - 200 0
2010-08-18 12:21:16 19.39.56.18 - W3SVC1 109.22.57.127 80 GET
/ESBReceiver/Receive.svc - 200 0
2010-08-18 12:21:16 19.39.56.18 - W3SVC1 109.22.57.127 80 GET
/ESBReceiver/Receive.svc - 200 0
2010-08-18 12:21:16 19.39.56.18 - W3SVC1 109.22.57.127 80 GET
/ESBReceiver/Receive.svc - 200 0
2010-08-18 12:21:47 19.39.57.127 - W3SVC1 109.22.57.127 80 POST
/ESBReceiver/Receive.svc - 404 0
2010-08-18 12:21:47 19.39.57.127 - W3SVC1 109.22.57.127 80 POST
/ESBReceiver/Receive.svc - 404 0
2010-08-18 12:21:49 19.39.57.127 - W3SVC1 109.22.57.127 80 POST
/ESBReceiver/Receive.svc - 404 0
I have changed my IP addresses above so don't be swayed by them. Some of
the Get requests came from the local machine where IIS/BizTalk is running,
and several are from my desktop.
Brian Cryer
I suspect this will lead to a dead end, but each of the GETs and POSTs are
from a different IP address, is the IP address significant in that if you do
a GET and POST from the same IP address then the GET works and the POST
fails?
No other ideas, sorry.
rich
On the host where BizTalk/IIS are running (via remote desktop session)...
- Browse to the webservice (ESBReceive.svc) from IIS Admin. Successful GET
- Browse to the webservice (ESBReceive.svc) from IE: Successful GET
- POST the SOAP message from SoapUI: Failed with the 404
On my desktop...
- Using IE, browse to the web service. Successful GET operation
- POST the SOAP message from SoapUI: Failed with the 404
For the Reserved Word possibility, I don't think any words are reserved.
The service is called "ESBReceiver/Receive.svc".
Could "Receive" possibly be a reserved word?
Thanks,
~Rich
In all situations, browsing to the service (Get operation), will succeed.
In all situations, Post operation from SOAPUI fails with the 404.
"Brian Cryer" wrote:
> .
>
Brian Cryer
> For the IP Address question, requests are sent from 2 different computers.
> On the host where BizTalk/IIS are running (via remote desktop session)...
> - Browse to the webservice (ESBReceive.svc) from IIS Admin. Successful
> GET
> - Browse to the webservice (ESBReceive.svc) from IE: Successful GET
> - POST the SOAP message from SoapUI: Failed with the 404
>
> On my desktop...
> - Using IE, browse to the web service. Successful GET operation
> - POST the SOAP message from SoapUI: Failed with the 404
>
> For the Reserved Word possibility, I don't think any words are reserved.
> The service is called "ESBReceiver/Receive.svc".
> Could "Receive" possibly be a reserved word?
Very unlikely. No.
<snip>
rich
Brian Cryer
> Yes Brian, that is correct. All the PUTs are failing with the 404.
If its every POST which is failing - regardless of your IP address - then
I'd look at whether its a BizTalk issue. Specifically does it accept POSTS?
or whether there is any configuration that needs to be in place to allow it
to accept POSTS. (Don't know BizTalk so this isn't something I can help
with.)
rich
"Brian Cryer" wrote:
> .
>
Brian Cryer
> There is no indication that the message ever makes it to BizTalk.
Does it make it as far as IIS? So can you see a request in the logs?
If no then look at the generated HTML to see where the request is going and
is yes then I can't think what it might be if it isn't a BizTalk issue.