Partager via

"Cannot download the information you requested" executing web query from Excel

  • Article

Have you ever encountered this problem? When trying to pull data via a web query in Excel you get an error saying "Unable to open https://... <your site location> Cannot download the information you requested." and clicking OK dismisses the web query. As in no data. What's going on here?

What's going on is when you execute a web query, Excel will ask URLMON to download a copy of the file given byu the web URL and URLMON has navigated to the address. However, the page has a "Pragma: no-cache" header (see https://support.microsoft.com/kb/165150 and https://support.microsoft.com/kb/222064 for more information) in it, which tells WININET (which IE uses) to avoid saving the web page to the Internet Explorer cache. In order for the download operation to work, the file has to be saved to IE. Not allowing the file to be cached causes the error you see in Excel and in turn, nobody is happy.

To resolve this situation, there are a couple of things you can do:

1. Edit the web page from where you are pulling your data and remove the no-cache header. You would be looking for a meta tag like the following:

<HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE">

or

2. You can direct the client computer to set the Internet Explorer option to bypass the no-cache check for SSL sites (remember the https:// in the sample URL above). To do this, go to START and in the RUN line type REGEDIT. In the registry navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings. Right click Internet Settings and left click New > DWORD Value (32-bit) and name the new value “BypassSSLNoCacheCheck” without the quotes. Double click this value and give it a value of 1.

Then try the web query again.

Comments

  • Anonymous
    January 01, 2003
    The comment has been removed

  • Anonymous
    November 22, 2011
    I would recommend to set the following headers. It worked for me.        response.setHeader("Cache-Control", "max-age=0");        response.setHeader("Pragma", "public");

  • Anonymous
    July 05, 2012
    I ran into this just now.  It was actually fixed by a restart, in the end.  May have had to do with a recent password change.

  • Anonymous
    February 19, 2013
    All of a sudden Excel won't find any of the links in my 6 months work of cases.

  • Anonymous
    May 26, 2013
    Worked for me !   Thanks !!!

  • Anonymous
    July 18, 2013
    Thank you so much. it works perfectly fine for me. All my dashboards are up and running again!

  • Anonymous
    September 26, 2013
    This workaround is useless. The reason I want to put a hyperlink in a workbook is for other users to be able to open it. You can't expect me to tell all those other users to change their registry settings before using my Excel file. Changing the HTTP header is also ridiculous because it assumes I control that web site, which is not the case.

  • Anonymous
    October 18, 2013
    The comment has been removed

  • Anonymous
    June 04, 2014
    Derek Watts' solution worked for me too, thank you

  • Anonymous
    July 21, 2014
    What if it is not a https page and still get this error?

  • Anonymous
    November 12, 2014
    I appreciate the workaround. I've sent this to our IT dept to see if they can implement. However, I would like to point out that this should be considered a serious bug in Excel. There's no reason it should behave like this.

  • Anonymous
    September 25, 2016
    As Andreas says below:This workaround is useless. The reason I want to put a hyperlink in a workbook is for other users to be able to open it. You can't expect me to tell all those other users to change their registry settings before using my Excel file.Changing the HTTP header is also ridiculous because it assumes I control that web site, which is not the case.

  • Anonymous
    September 25, 2016
    Couldn't Microsoft simply fix this bug so that hyperlinks in Excel work properly instead of proposing absurd workarounds - that don't even work (in my case) and are impossible for ordinary users to implement even if they did work.

  • Anonymous
    November 09, 2016
    The registry edit worked for me. Thank you.

  • Anonymous
    February 13, 2017
    The comment has been removed