Re: Client HTTP Status 12031. Server IIS Log 400 w/ Win32 status 121

From: David Wang [Msft] (someone_at_online.microsoft.com)
Date: 09/23/04 

Date: Thu, 23 Sep 2004 15:29:21 -0700

I'm glad you found the problem.

Moving away from WinInet usage on the server is always a good idea -- it was
never designed for usage on the server and performs/scales poorly.

It was probably sufficient to handle low load, but as transaction/requests
grew... it started to be problematic. 

-- 
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"MiddEware" <MiddEware@discussions.microsoft.com> wrote in message
news:848465F7-4DEF-4E4E-8610-11089B7663CD@microsoft.com...
Hi David,
Based on your feedback, we focused our efforts on the client side of things
and a teammate of mine found the problem. The COM component (which we
inherited) has been running successfully for a number of years on other
client servers and workstations which had us going as to why the cold fusion
server was the only client having this problem. The cold fusion server had
also been ok earlier on, but in the past year was starting to see an
increasing number of client 12031 and 12002 errors particularly during peak
traffic hours. This situation coiincided with transaction growth in the
business segment that the cold fusion server was servicing and may have been
exacerbated by our upgrade to Windows 2000 (HTTP 1.1?).
In short, the COM component was changed to use a server post method instead
of a WinInet post method (a one line change). Our problems have since gone
away. We suspect that the root cause revolves around MS KB article 183110
and
a (default) Cold Fusion timeout setting of 60 seconds for idle Cold Fusion
pages.
(Our users told us that they would get a timeclock for a minute and then get
the 12031).
As a side benefit to this problem, we also uncovered the reason we were
getting a "Method '~' of object '~' failed" error in an earlier version of
our COM component. The earlier version was not handling the 12031 and 12002
status codes and, as such, the reference would get lost resulting in the
method failed error coming back to Cold Fusion.
Once again, thanks for your help in this matter. Take care,
Lee

Relevant Pages