Discussion:
sc-win32-status=121 and zero byte sent
(too old to reply)
Freds
2006-09-14 16:00:02 UTC
Permalink
I have a standard ASP.Net web-service (W2003 SP1/II6.0/.Net 1.1), which runs
fine, except from some client site.
Basically, the server does not send a response back.
Looking at the server logs, I see that the missing responses are logged with:
- http status = 200 (fine)
- sc-win32-status = 121 (not fine)
Using the logman utility, I found out that no bytes have actually been
sent!!?!?
e.g.:
IISGeneral: GENERAL_REQUEST_END - IIS ends processing a request
HttpStatus: 200
HttpSubStatus: 0
BytesSent: 0
BytesReceived: 1341
ContextIDSeq: 1
Timestamp: 13:21:34.718.750000

How could that be?
What could be the issue?

Regards
chris crowe [iis mvp]
2006-09-15 10:22:39 UTC
Permalink
121 aparently means that a Semaphere timeout has occured what ever that
means.

May be IIS could not send back to the client - is it only affecting one
client?
--
Chris

Chris Crowe [IIS MVP - 1997 -> 2006]
Post by Freds
I have a standard ASP.Net web-service (W2003 SP1/II6.0/.Net 1.1), which runs
fine, except from some client site.
Basically, the server does not send a response back.
- http status = 200 (fine)
- sc-win32-status = 121 (not fine)
Using the logman utility, I found out that no bytes have actually been
sent!!?!?
IISGeneral: GENERAL_REQUEST_END - IIS ends processing a request
HttpStatus: 200
HttpSubStatus: 0
BytesSent: 0
BytesReceived: 1341
ContextIDSeq: 1
Timestamp: 13:21:34.718.750000
How could that be?
What could be the issue?
Regards
Freds
2006-09-15 10:58:01 UTC
Permalink
At least one other client reported the issue. The thing is, the network
topology is a little bit complex (and out of my hands!).
What I don't get is:
- why a simple HTTP request succeeds?
- why no errors are logged in the HTTPERR file?
- if it's a firewall/proxy issue, how can I diagnose that from my server?

Freds
Post by chris crowe [iis mvp]
121 aparently means that a Semaphere timeout has occured what ever that
means.
May be IIS could not send back to the client - is it only affecting one
client?
--
Chris
Chris Crowe [IIS MVP - 1997 -> 2006]
Post by Freds
I have a standard ASP.Net web-service (W2003 SP1/II6.0/.Net 1.1), which runs
fine, except from some client site.
Basically, the server does not send a response back.
- http status = 200 (fine)
- sc-win32-status = 121 (not fine)
Using the logman utility, I found out that no bytes have actually been
sent!!?!?
IISGeneral: GENERAL_REQUEST_END - IIS ends processing a request
HttpStatus: 200
HttpSubStatus: 0
BytesSent: 0
BytesReceived: 1341
ContextIDSeq: 1
Timestamp: 13:21:34.718.750000
How could that be?
What could be the issue?
Regards
Loading...