#1 2015-07-06 08:24:37

Eric
Member
Registered: 2012-11-26
Posts: 129
Website

WinHTTP Error 12175

Using the WinHTTP client, I am sometimes getting a WinHTTP 12175 error, usually after several days of operation and tens of thousandths of queries.

When that happens, the only way to "fix" the errors is to restart the service, and occasionally the errors will not go away until Windows (the server) is restarted.

Interestingly enough, this error appears "gradually": getting some of them for some https queries, then after some time, the service gets them for 100% of https queries, then later on, they popup even for regular http queries (the service makes lots of http & https queries, on the order of dozens per seconds, to many servers).

AFAICT there is no memory leak or corruption, outside the 12175 errors, the rest of the service is operating just fine, no AV, responds to queries, etc.

Anyone else has seen this behavior? Any workarounds?

I have a suspicion this could be related to Windows Update doing OS certificate updates, but I could never positively confirm it.

Offline

#2 2015-07-06 11:10:41

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,713
Website

Re: WinHTTP Error 12175

Never seen that, but we mostly use plain http:// connection, not https//

Perhaps you may ask on StackOverflow, since it sounds like a WinHttp or http.sys issue, which may occur also with .Net apps.
Or the .Net servers are rebooted daily due to GC, so it does not occur. wink

Perhaps there is some kind of "credential renewal" to do on the server side...

Which version of Windows are you using?
Did you try several?

Offline

#3 2015-07-06 13:02:08

Eric
Member
Registered: 2012-11-26
Posts: 129
Website

Re: WinHTTP Error 12175

ab wrote:

Which version of Windows are you using?
Did you try several?

Windows 2012 R2 for the production server.

In other tests (Win 2008 R2) it never occurred, but the test machine is not able to handle the same amount of load or run for days, so it's no apple-for-apple comparison. The backup server did not exhibit it either, but it's mostly inactive in comparison to the production one, so no surprise.

The load is high enough in terms of I/O that a non-virtualized OS is required for production, which makes full-load testing a bit more involved (attempts by different specialist on hyper-v, vmware & kvm all failed miserably, under virtualization performance ended up around 10% of bare-metal, it's a very peculiar workload with relatively little CPU usage, but loads of small disk & network I/O).

Offline

#4 2015-07-06 13:09:41

Eric
Member
Registered: 2012-11-26
Posts: 129
Website

Re: WinHTTP Error 12175

Offline

#5 2015-07-06 17:04:18

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,713
Website

Re: WinHTTP Error 12175

My guess is that it sounds like a problem on the server side.

So I would perhaps add IIS and WCF as tags to the SO question.

Offline

#6 2015-07-07 08:47:16

Eric
Member
Registered: 2012-11-26
Posts: 129
Website

Re: WinHTTP Error 12175

However I am using neither WCF nor IIS smile

Offline

#7 2015-07-07 10:01:53

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,713
Website

Re: WinHTTP Error 12175

But AFAIK WCF does use WinHttp and http.sys, and IIS uses http.sys.

So your issue may occur within those technology context, if it is a WinHttp or http.sys issue.

Offline

Board footer

Powered by FluxBB