- last edited on
I have tried to connect to 20+ websites that require sign-in credentials using Power Query without success. I am able to login using Chrome so the credentials are correct. The error I receive is below. I have clicked Edit Credentials and re-entered the creds, only to get the same error. I have cleared the permissions in Power Query and re-done numerous times without success. Also, I'm certain I have used the feature successfully around a year ago.
Is there a setting in Power Query that enables connecting with credentials? Any other ideas?
08-31-2017 01:08 AM
We've been suffering from this problem for months and trying to get MS attention - maybe in the wrong places :-(.
My latest response there shows my frustration and it was only through examination of the user-agent heder that Excel supplied that I found a link to this tech community and I was going to post a new thread before I found this one.
To one extent, I am glad we're not the only ones suffering - it might get some attention now.
On the other hand, I'm not holding my breath until I can see that someone at Microsoft has read and understood the problem.
Any tips will be very much welcome.
09-05-2017 12:14 PM
Tim, would you mind sending more details of your issue (along with a Fiddler trace, if possible) to email@example.com? Please mention my name when you do so.
10-16-2017 01:28 AM
Thanks for assisting diagnosis, Ehren. I've posted a new suggestion as a result of this:
09-28-2019 01:34 PM
@Toynk AccountingDo you have updates on this issue? I am currently facing same problem. But I find it a bit weird as it was working fine in my old laptop. I just posted my case few hours back.
09-28-2019 02:54 PM
@lealpermalino I thought I'd posted my workaround, but maybe not here.
Briefly: it won't work with this new style, you have to re-enable the legacy data wizard and use that.
This does still work - I used it last week.
09-29-2019 05:20 AM - edited 09-29-2019 05:31 AM
@Tim Scott Tried to enable legacy data wizard but still didn't work. I also tried to use Power BI and gave me save result. New PC unable to fetch other tables. Is there a special data connector microsoft uses or it is really an issue with credentials?
Btw, Old laptop OS is Windows 10 Home, new PC OS is Windows 10 PRO. Does this affects Excel/PowerBI web data scraping?
09-29-2019 06:03 AM
@lealpermalino From what I gathered, the new method did not handle authentication and the legacy wizards behave in the way they used to. At the risk of making a silly point, you did go to the legacy wizards option on the menu, not the option which now launches the new method, didn't you?
09-29-2019 08:11 AM
@Tim Scott I went to Excel Options >> Data >> Show legacy data import wizards
Hope I did get you correctly.
Just for reference, below are Navigator snapshot using Power BI
09-29-2019 09:07 AM
@lealpermalino first of all, it looks like the query on your old PC hasn't been refreshed in months. From the Query Editor, click on REFRESH ALL and see if it still works. If it does work, click on the Web View tab and post a screen shot of both PC's (redacting any sensitive info of course). Lastly, click on Data Source Settings on the Main tab in Query Editor and then Edit Credentials. See how the old one is set-up compared to the new PC. I'm not convinced your problem is authentication or that your problem doesn't exist on the old PC. This will prove or disprove, I think.
@Tim Scott's legacy wizard suggestions are not at all what you're looking for. the legacy scrape is far inferior and you old PC was not using legacy. Not sure why it's even being suggested.
To answer your question to me, I did figure this out - somehow. Can't recall exactly. But it had something to do with typing my password into the API credentials, I think. I can't quite recall but it wasn't an obvious move. After 2 years with no answer, I just started trying things and it worked. Did it for a few other sites, didn't write it down, now I can't remember.
09-29-2019 10:13 AM
@Toynk Accounting I just click REFRESH ALL in old PC and it is still working.
Below screenshots of each Navigator Web View (Seems like Internet Explorer is causing the error?)
Regarding Data Source Setting, both are same and was reference to old PC
09-29-2019 10:19 AM - edited 09-29-2019 10:20 AM
Well - the legacy wizard solved my problem. If that's not the answer, either Microsoft have changed something in two years or it's a different problem.
09-29-2019 10:53 AM
@lealpermalino interesting. I guess try and turn off the Internet Compatibility settings. Otherwise, I'm a at a loss. Sorry can't be of more help
09-29-2019 12:07 PM
@Toynk Accounting sadly that didn't work as well.
I remember in the past when I was working in the old PC for the same thing, I was able to enter credentials (Username & Password), and after that, query shows all the tables I needed (that was Aug-Sept 2018). I really do not understand why credentials entry are currently not working properly.
09-30-2019 10:51 AM
Hi @lealpermalino. Is it possible that your old PC is using the MSI version of PBIDesktop, and your new PC is using the Microsoft Store version? Are they running the same numeric version of PBIDesktop as well?
09-30-2019 01:22 PM
@Ehren von Lehe Yes, new PC PBI was from Microsoft store. I re-install PBI using the installer, and now it is able to get the table/s. Though still confused because credentials are still invalid, but when I selected anonymous, it worked...
Old PC has Aug2019 version, new PC has Sept2019 version (not sure if this is the numeric versions you were asking..)
I think, it is the installer versions solved the issues. Thank you very much for this.
Regarding EXCEL query, it is also now working... I didn't change any settings. I just tried if the other option for "From Web" function under "Get Data>>From other sources>>From Web", and fortunately succeeded (not sure if this was really the solution...). On this one, I used credentials and was accepted.
Thank you All for your help...
09-30-2019 01:35 PM
@lealpermalino Great. The MSI version overrides a few Internet Explorer settings (which is what Web.Page uses behind the scenes), and the store version isn't (yet) able to override those settings. These settings must be what allows this particular page to work for you.