Avkash Chauhan's Blog

Windows Azure, Windows 8, Cloud Computing, Big Data and Hadoop: All together at one place.. One problem, One solution at One time...

WinHttpGetProxyForUrl(***) failed ERROR_WINHTTP_AUTODETECTION_FAILED (12180) - Error message in Windows Azure Infrastructure log

WinHttpGetProxyForUrl(***) failed ERROR_WINHTTP_AUTODETECTION_FAILED (12180) - Error message in Windows Azure Infrastructure log

  • Comments 7

 

When you have your diagnostics enabled application running on Windows Azure, you might see that your Infrastructure Logs filled with lots of "ERROR_WINHTTP_AUTODETECTION_FAILED (12180)" errors related to Windows Azure storage access. Most of these errors are appeared in Infrastructure Logs, when you access table, blog or queue within your Windows Azure storage.


The error message look like as below: 


WinHttpGetProxyForUrl(http://<your-Windows-Azure-Storage-Name>.table.core.windows.net) failed ERROR_WINHTTP_AUTODETECTION_FAILED (12180)

OR

WinHttpGetProxyForUrl(http://<your-Windows-Azure-Storage-Name>.queue.core.windows.net) failed ERROR_WINHTTP_AUTODETECTION_FAILED (12180)

OR

WinHttpGetProxyForUrl(http://<your-Windows-Azure-Storage-Name>.blob.core.windows.net) failed ERROR_WINHTTP_AUTODETECTION_FAILED (12180)


Even when you will see these error in your Infrastructure logs still you will not see any functional problem within application. 


 

I would like to say that these error messages are coming from the monitoring agent and do not indicate a problem on their own.  It just means that there is no auto proxy set up and it defaults to use the static proxy, which is normal in a role environment and not a cause of concern. You sure can discard such error messages. 


Hopefully the new SDK should have something to reduce these errors to very minimum level. 

 

 

Leave a Comment
  • Please add 3 and 5 and type the answer here:
  • Post
  • I am still seeing these errors today, 18 months later.  Has there ever been a solution ?

  • I recently encountered this error whilst doing a simple hello world application. The solution was to switch the IIS that I was using from Express to IIS webserver.

  • I'm having this issue. This is preventing my logs to be transfered to the blobstorage...

  • I am still seeing these messages in sdk v 2.0. 2,5 years later.

  • September 2013 ... I am still seeing these messages ... this simply makes the Infrastructure Logs unusable ... I just have to switch them off :(

  • Hi

    I am using SDK 2.2 and getting the same error...not sure if it has been resolved in SDK 2.2

  • Using the latest and greatest and still seeing these messages fill my Azure Table for Diagnostic Trace. Very annoying.

Page 1 of 1 (7 items)