Freigeben über

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

  • Artikel

 

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(https://<your-Windows-Azure-Storage-Name>.table.core.windows.net)
failed ERROR_WINHTTP_AUTODETECTION_FAILED (12180)

OR

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

OR

WinHttpGetProxyForUrl(https://<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.

Comments

  • Anonymous
    July 12, 2012
    I am still seeing these errors today, 18 months later.  Has there ever been a solution ?

  • Anonymous
    September 12, 2012
    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.

  • Anonymous
    January 11, 2013
    I'm having this issue. This is preventing my logs to be transfered to the blobstorage...

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

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

  • Anonymous
    April 11, 2014
    Hi I am using SDK 2.2 and getting the same error...not sure if it has been resolved in SDK 2.2

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