Hello @Ivanov,
You can Collect WinHTTP traces using netsh.exe.
There is also Capturing WinHTTP Logs document in WSDAPI Diagnostic Procedures.
Getting logs for WinHTTP system error.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 87%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EI%3C/text%3E%3C/svg%3E)
Ivanov
0
Reputation points
Hi, All!
Recently, during development of an application, I've started facing troublesome issue: calls to WinHTTP subsystem (specifically, WinHttpReadData/WinHttpQueryDataAvailable APIs) present me with 12004 ERROR_WINHTTP_INTERNAL_ERROR outcome. Doesn't happen always, problem is intermittent. Since this is a very generic error code, I'm out of options for debugging it. I'm wondering, whether there are logging options (Event viewer maybe) that could help in finding the cause? If so, how to turn it on, etc?
Best regards
Windows development | Windows API - Win32
Windows for business | Windows Client for IT Pros | User experience | Other
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 34%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXY%3C/text%3E%3C/svg%3E)
Xiaopo Yang - MSFT 12,736 Reputation points Microsoft External Staff2024-04-17T07:33:11.65+00:00 @Ivanov, does Netsh.exe work for you? You can also use Event Tracing to trace WinHTTP-related providers for example Microsoft-Windows-WinHttp for more information.
Sign in to comment
1 answer
Sort by: Most helpful
-
Xiaopo Yang - MSFT 12,736 Reputation points Microsoft External Staff
2024-04-12T02:40:13.9933333+00:00