I have the following scenario:
3 windows server 2012 virtual servers, all with IIS 8:
- 1 server with Application Request Routing 3
- 2 servers with the web applications that the ARR server routes to
I am getting intermittent 502 3 12002 errors.
I have identified that I need to trace using netsh the WinHttp/WebIO providers to get to the real error code that is mapped to the 12002 error code.
I run the trace as the article suggests:
netsh trace start scenario=internetclient capture=yes persistent=no level=verbose tracefile=c:\temp\net.etl
When analysing the output of the netsh traces, I don't get the level of information that the article suggests I should. Specifically I only get the following types of entry in the trace viewed using netmon:
WINHTTP_MicrosoftWindowsWinHttp:Stopping WorkItem Thread Action... WINHTTP_MicrosoftWindowsWinHttp:Starting WorkItem Thread Action... WINHTTP_MicrosoftWindowsWinHttp:Queue Overlapped IO Thread Action...
I certainly don't get anything detailed enough that would help me understand why am getting any timeouts.
Is there any reason why Server 2012 wouldn't trace the WinHttp API to the level I need?