Discussion:
IIS logs win32 status codes 121, 1229, 1236
(too old to reply)
Ryan Steckler
2006-01-23 22:22:32 UTC
Permalink
Hi,

Sorry for this dupe but I'm reposting with my managed newsgroup account,
hoping for an answer.

These sc-win32-status codes show up a couple of hundred times per day. The
HTTP response is either 200 or 304 (which would indicate that everything is
ok) but the client doesn't always get the response.
This is most evident when serving webctrl_client treeviews that result in a
text-only treeview, or a missing image.

NET HELPMSG list the errors as:
121 - The semaphore timeout period has expired.
1229 - An operation was attempted on a non-existant network connection.
1236 - The network connection was aborted by the local system.

The rest of the client page looks fine (with the exception of the particular
line item that failed) and moves on with it's session.

These are 2 Windows 2003 Server systems load balanced running ASP.NET. The
errors occurr in the logs of both machines. I think 1236 may just be the
result of spotty connectivity, even though this is a LAN and the machines
are within a few feet of each other.

Any information anyone could give me on these codes, or what they mean would
be GREATLY appreciated.

Ryan Steckler
Sr. Software Engineer
CompassLearning
WenJun Zhang[msft]
2006-01-24 10:04:36 UTC
Permalink
Hi Ryan,

These Win32 errors indicate there is networking or proxy issue between the
client and your IIS server. If you can properly browse the web site from
your internal network or on the local machine, then it's confirmed to be a
networking issue. You can post to our Windows networking newsgroup for
assistance.

Have a nice day.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.
Continue reading on narkive:
Loading...