I've been having ttouble updating certain tickers in a Fidelity data set. I keep getting the error below:

SPXL  Error: The remote server returned an error: (401) Unauthorized.

I tried logging into Fidelity an rerunning the request. I also tried Yahoo, but that's even worse. It doesnt update any of the symbols in my data set. For each one, it displays an error like this:

[5] SPXL  Error: The remote server returned an error: (502) Bad Gateway.

I'm sure that the source of both 401 and 502 errors is Yahoo, not Fidelity. It's very well documented in a hot thread under this General category:

Yahoo! Data Not Updating for Last Session

Please read from post #30 and to the end.

P.S. A search tip: try typing in the first letters of a keyword (like "Yah...") in forum's search box. It's nearly real-time.

Thanks! Will check through the other posts as well

We're pleased to announce that the Yahoo provider has been fully restored. Update the extension now!

Attention: our Yahoo! provider has been updated to v.2017.07.

This is another MUST HAVE release. Last weekend Yahoo has made some breaking changes to:

1. the order of fields in the exported data (swapped Close and AdjustedClose)
2. split/dividend adjustment of the Close price
3. improve the way some historic split/dividend adjustments are handled

If you updated the data this week or downloaded symbols from scratch, it's highly recommended to truncate this week's bars using the Data Tool and to repeat update using v.2017.07.

On the bright side, the number of splits that you'd put on the "Ignore Selected Splits" list has visibly decreased.

Hi Eugene,
I just updated to the Yahoo 2017.07 and used the datamanager to delete all data (of all yahoo datasets). I verified by creating a Chart that there are no data available. I updated my dataset, but the data seems to be corrupted in the past.
Reproduce for example AA: every data before 2016-11-01 seems not to be ok.

Thanks for checking

Sample Screenshot

Right click and "Reload chart history". AA is now the "new AA". The data history for the former AA is now in symbol ARNC. More info: http://www.stockspinoffs.com/2016/11/03/alcoa-completes-spinoff-newly-renamed-arconic/

Cone,
thanks for the prompt reply - my fault. "Reload chart history" does not make any change.
But can you also take a look at AAPL or CSCO for example? (attached) Also Looks very strange....

Well, Yahoo has changed something again in their data for the 3nd time since May! I fixed the thing twice in May and June.

Please take a look at this in recent quotes of CSCO on their website (the order is OHLC + Adj.Close):

Jun 29, 2017 31.79 32.03 31.25 31.12 31.41
Jun 28, 2017 31.78 32.28 31.76 31.78 32.08

As can be seen, its Close is below the Low price. I think they have again changed the order of fields. This time we're probably going to wait until the dust settles and Yahoo fixes their data bugs and wildly changing order of fields.


So, if Wealth-Data doesn't have some symbols you're looking for, please choose the recently released Tiingo provider, it's a great drop-in replacement for Yahoo. Be sure to sign up at their website, though:

Tiingo Static, Real-Time and Fundamental
Online user guide

Eugene,
thanks for analysing. I'll give Wealth-Data and Tiingo a try.

@Eugene

QUOTE:
I think they have again changed the order of fields.

By downloading into spreadsheet from Yahoo site, I can confirm that data in the Close and Adj Close columns have been switched. Column header titles have not changed order, only the data.

So I've unrolled the v2017.07 extension build. This should fix Yahoo data but I'm puzzled at how they let this erroneous order of fields exist in the data, fix it, and then break it again.

Please reinstall v2017.06 from our server if you're on v2017.07. This should fix Yahoo data until they make unannounced breaking change again.

As any data downloaded since June 29 can be incorrect, it's advised to check your Y! data using the Data Tool and, if errors were found, either truncate some last bars in symbols which existed before June 29 or reload from scratch the new symbols you added since June 29.

The Close and Adj Close columns have again been switched in Yahoo data. Working on an automated solution to this problem.

Please update to v2017.07 if you're on v2017.06. This should work around Yahoo data until we make the fix.

As any data downloaded since ca. July 10 can be incorrect, it's advised to check your Y! data using the Data Tool and, if errors were found, either truncate some last bars in symbols which existed before ca. July 10 or reload from scratch the new symbols you added since ca. July 10.

@Eugene

I am not sure if this is related to issues discussed above in this thread, but I recently noticed that Yahoo! does historical data splitting on Close prices, even if you uncheck the relevant box in data manager. If you do check the split box, it spits *twice* so for a 5:1 split; it divides historical Close prices by 25.

This may be something you are already aware of. If you are not, then take a look at what happens to symbol EEM before 5:1 split on 7/24/08. You can see that the Close data (only) is adjusted for splits by default. If you check the split box, then OHL data will be now split, and C data will be split a second time.

This behavior is not limited to this symbol, based on my brief research. Please inform whether this is a known issue and any fix or workaround.

The split behavior looks correct to me. By the way, the split on 7/24/2008 looks like a 3:1.

1. Which version of the Yahoo! Provider are you using? Check in Tools > Extensions > Providers

2. If you're using the current version 2017.08, try right-click the chart > Reload Chart History.

@innertrader

1. Do not make changes to the Yahoo! options while you have an open chart. Reopen the chart or restart WLP. If it doesn't help, I second Cone's suggestion:
2. Reload Chart History. Yahoo has made a lot of conflicting changes which could have reflected in your existing data.



3. If still no go, close all chart windows and delete this file (how to enable hidden file visibility), then take step #2 again.

C:Users\Windows username\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0\Data\YahooFundamentalProvider\E\EEM.WLF

@Cone

QUOTE:
The split behavior looks correct to me. By the way, the split on 7/24/2008 looks like a 3:1.

You are correct. I was confusing with another symbol I was looking at with 5:1, ILF.

QUOTE:
1. Which version of the Yahoo! Provider are you using? Check in Tools > Extensions > Providers

In the Extension Manager>Providers there are 3 listed:
1. ASCII Files Static (2017.07)
2. WL Files Static (1.2.5.0)
3. Yahoo! Finance Static, .... ( 2017.07)
I don't see any updates available. I've seen threads about updating to Yahoo! Provider 2017.07 but don't know how to get 2017.08.

@Eugene
Tried all of your suggestions above . attached is an image of what I'm seeing with no boxes checked on Yahoo! tab of data manager, as compared to the one you shared.

BTW, it looks like the data in your image is split 3:1. Prices should be ~$150 during the time period you are displaying, as you will see in attached image.

It's my bad, I forgot to upload v2017.08 - was full of wishful thinking that Yahoo has settled down. Sorry.

I've downgraded to v2017.07 to see that Yahoo has changed again the order of fields so said version is now broken (and v2017.06 is probably working again but that doesn't matter). Cone's expressed suspicion that they must be doing it intentionally is now confirmed.

Fixed. Please update the extension to v2017.08 with the automatic detection.

Voila! That did it.

Once again, I'm getting a "(401) Unauthorized" error when trying to update Yahoo data. However, when I visited their website and tried to download data in the browser I got this response:

QUOTE:
{
"finance": {
"error": {
"code": "Unauthorized",
"description": "Invalid cookie"
}
}
}

This indicates that it's an issue on Yahoo's end. It's not a Wealth-Lab problem. You have to wait until's it's resolved by Y!

Short question:

How do I get rid of the wrong company names ?
Even after reloading symbol details with the new Yahoo Data provider they are wrong.

When you update the symbols in the Data Manager, it should refresh the names. Give us some examples of symbols with incorrect company names so that we can check.

I reloaded my SP600 dataset and the symbol names changed for many, but not all, from one wrong name to another wrong name.
APA is my standard example, which should be "Apache", now its "Air Products And Chemicals ,Inc").


I reloaded Symbol Details and restarted WL to avoid caching issues.


See picture.

QUOTE:
How do I get rid of the wrong company names ?

1. Set up your Extension Manager to check for extension updates on startup.
2. When an update to the Yahoo provider is detected, update it and restart WLD.
3. In the same Extension Manager window, check change logs of the extension that causes you trouble. This would let you be informed about what has recently happened to Yahoo streaming data and company names, for example:

Yahoo provider change logs

Re: APA

APA works fine here:



P.S. If there's something that I cannot reproduce, chances are that Yahoo is returning bad output to break the automated downloaders. Like they already have been periodically randomizing the order of OHLC in the exported data. This happens with free feeds, that's life.

During startup my WL checks for extension updates. The Installed Yahoo component is 2017.12

I attached a picture of the latest updatet dataset. The first companies have the correct name,
then all other companie names are wrong.

What do you advise is the best solution for my problem ?

Rene,

Solution is easy:

1. In the update log, note down any symbols that return a "(404) Not found" error and weed them out of your DataSet.
2. Update the DataSet to reload its symbol names.

To be fixed in upcoming Y! provider build. Thanks for the heads-up.

Thank you, Eugene. I noticed eventually, that small datasets, containing only valid symbols are updated correctly.

You're welcome. While waiting for the fix any DataSet (small or big) will do. Simply make sure it doesn't contain any invalid symbols.

To every Yahoo provider user out there:

If you get an occasional "(401) Unauthorized" error when updating (most) every Yahoo symbol, first try to restart Wealth-Lab and repeat update.

So as not to duplicate my response, here's an update regarding "(401) Unauthorized" error:

Yahoo! Data Not Updating for Last Session, post #78

Attention Wealth-Lab Developer users of Yahoo provider from European Union!

If Y! provider stopped downloading data you will need to update the extension to v2018.06 and restart WLD.

To comply with GDPR, Yahoo introduced a forced consent page for those trying to access any Yahoo web page from a EU IP. New version fixes this breaking change.

Non-EU customers as well as Wealth-Lab Pro users need not update their installed extension yet as it doesn't add new features.

Attention Wealth-Lab Developer users of Yahoo provider from European Union!

If you experience Error 401 on data update then please update the extension to v2019.04 and restart WLD.

Yahoo's been making internal changes to said GDPR consent page. (We have a feeling that it may not be the last one).

Non-EU customers as well as Wealth-Lab Pro users need not update their installed extension as it doesn't add new features.

Hey guys,

Tried 6.9.20 when it came out some 10 days ago or so, and it failed (I am running Windows 10, and it should be 64-bit). So, it would not open at all. Disappears somewhere in the system. Invisible, once you "open" it.

Luckily I reverted back to 6.9.19 (original one from Fidelity website). Everything working fine. Until yesterday and today. And that is with Yahoo data (error 401, not authorized). [tried to download forex daily data].

I would have installed 6.9.20 update, but after reading threads I see still some issues with it (especially on 64 bit), so I will wait for the new build rather, to avoid all those hassles that I read there.

I would not be contacting you if it weren't for the Yahoo data. I don't know why it's not working as of yesterday. It worked perfectly fine last week. Last data update (day) from July 19.

Do you know why that might be the case?

Thank you... See below the update progress and errors. Started yesterday.


Updating DataSet Yahoo Forex ...
Preparing requests ...
Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 20 symbols...
Error updating Security Names. The remote name could not be resolved: 'download.finance.yahoo.com'
[0] AUDCAD=X Error: The remote server returned an error: (401) Unauthorized.
[9] EURUSD=X Error: The remote server returned an error: (401) Unauthorized.
[3] AUDUSD=X Error: The remote server returned an error: (401) Unauthorized.
[7] EURJPY=X Error: The remote server returned an error: (401) Unauthorized.
[1] AUDNZD=X Error: The remote server returned an error: (401) Unauthorized.
[8] EURNZD=X Error: The remote server returned an error: (401) Unauthorized.
[2] EURCAD=X Error: The remote server returned an error: (401) Unauthorized.
[4] EURAUD=X Error: The remote server returned an error: (401) Unauthorized.
[5] AUDJPY=X Error: The remote server returned an error: (401) Unauthorized.
[6] CADJPY=X Error: The remote server returned an error: (401) Unauthorized.
[0] GBPAUD=X Error: The remote server returned an error: (401) Unauthorized.
[9] GBPCAD=X Error: The remote server returned an error: (401) Unauthorized.
[1] GBPNZD=X Error: The remote server returned an error: (401) Unauthorized.
[8] NZDCAD=X Error: The remote server returned an error: (401) Unauthorized.
[2] NZDJPY=X Error: The remote server returned an error: (401) Unauthorized.
[5] USDCAD=X Error: The remote server returned an error: (401) Unauthorized.
[7] GBPUSD=X Error: The remote server returned an error: (401) Unauthorized.
[6] USDJPY=X Error: The remote server returned an error: (401) Unauthorized.
[3] GBPJPY=X Error: The remote server returned an error: (401) Unauthorized.
[4] NZDUSD=X Error: The remote server returned an error: (401) Unauthorized.
Update completed (4.714 sec)

Hi Berislav,

Problem is, WLP 6.9.20.7 ships with an outdated version of the Yahoo! provider from 2017 which is broken. To fix the issue please simply reinstall the extension from our website (click) and restart WLP to apply.

As to why it starting failing now, the reason is that you're trying to download the data from a EU IP. The location makes difference to the Yahoo website which would show a GDPR consent page which must be accepted by the user. The outdated Y! provider's version cannot do it.

Thank you! Worked. Great.
Thumbs up...

My pleasure to help!

Noticed errors in the Yahoo! data for many symbols today, mostly ETFs but also stocks. For example, the website may show it correctly for DOG...


...while the downloadable data has errors/zeroes all over:

CODE:
Please log in to see this code.

The provider is not to blame: it just takes the data with zeroes as supplied. Try to update at a later time. If necessary, truncate the last faulty bar using the Data Tool (convenient for bulk operations) before update. And just to remind, there's no shortage of alternative data providers in our Extension gallery.

I had to recreate the topic because I could not find the thread in the forum.

The 2019.11 Yahoo Finance extension has been working so far,
alas starting this afternoon I am getting again the dreaded error:

Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 9 symbols...
Security Names updated.
[0] BSV Error: The remote server returned an error: (401) Unauthorized.
[3] GLD Error: The remote server returned an error: (401) Unauthorized.
[2] EEM Error: The remote server returned an error: (401) Unauthorized.
[1] DBC Error: The remote server returned an error: (401) Unauthorized.
[0] IWM Error: The remote server returned an error: (401) Unauthorized.
[3] SPY Error: The remote server returned an error: (401) Unauthorized.
[2] TLT Error: The remote server returned an error: (401) Unauthorized.
[1] VNQ Error: The remote server returned an error: (401) Unauthorized.
[0] VTI Error: The remote server returned an error: (401) Unauthorized.
Update completed (1.26 sec)


I tried several times and waited some time, hopefully Yahoo has not again changed all kind of stuff
----------------

I'm getting the same result, even after restarting/authenticating. I'm sure Eugene will keep an eye on it and react as necessary. Thanks for the heads up!

I suspected a repercussion of EU (GPDR consent related) issue yesterday. But it works for me today from both EU and non-EU IPs. Probably it was a glitch on Yahoo side - which happens too from time to time.

After a long wait its working again.... strange ...

Nothing strange actually. Periodically Yahoo has outages and experiences glitches. That includes the GDPR consent page that the provider faces when a EU (only) user accesses any Y! page for the first time. Something broke there, ceasing the normal provider operation for EU users (only). No other parts of the world were affected.

Consider this the (cheap) price to pay for the modern laws which have extraterritorial reach like GDPR, FATCA and US sanctions. Part of the crazy word we're living in after Y2K.

Unfortunately the 401 error has occured again since 3 days .. and this time it seems not to
be going away ...

[2] TLT Error: The remote server returned an error: (401) Unauthorized.
[0] VNQ Error: The remote server returned an error: (401) Unauthorized.
[1] VTI Error: The remote server returned an error: (401) Unauthorized.
Update completed (2.262 sec)

Cannot reproduce - and I did try. No problem updating Y! data from both a EU IP (your case) and non-EU IPs (these aren't affected anyway).

In addition to retrying later, here's a couple suggestions:

1. Change your connection type (WiFi to LAN etc) or ISP.
2. Get a non-EU VPN.
3. Use a backup data provider.
etc

Same issue here as ReneW describes.

@Eugene: Your suggestion #1 did not solve the problem on my side. Regarding suggestion #2: Never did that before and I am not familiar with the steps to get a non-EU VPN

Seems that suggestion #3 is the way to go for me right now.

Hope the problem can be located soon.

The problem is located: please refer to post #43 above.

Suggestion #4: wait and retry after a few days.

Like I said, the problem cannot be reproduced at the moment.

Hi,
i am using bitdefender premium VPN. I have choose to connect with Australia and it works with 98% accuracy. Left 2%, maybe with an another Country :-)

Glad to hear it works for you. Just turn it off when you visit our website ;)

Hi Eugene,

maybe the analysia of #43 is a bit sloppy. I'm using a german software for portfolio mgt which also works with yahoo data. It still works without any break.

Good for you. It also works for me and users from the most part of the world including U.S. without any break. It just fails if your IP is European. The issue is clear but reproducing it has been a challenge. I will look into it maybe next week. For now you have workarounds in post #45.

Attention Wealth-Lab Developer users of Yahoo provider from European Union!

If you experience Error 401 on data update then please update the extension to v2020.01 and restart WLD. The issue has finally been fixed (hopefully, for good). Sorry for the delay.

After updating and restarting WLD were all my Yahoo datasets gone.

It's not our fault. Most likely, you chose Uninstall instead of Update. See FAQ: Some DataSets are gone. Some previously installed providers can't be found

I made sure the Extension contains the required components (our Market Manager and HtmlAgilityPack). Just double checked by upgrading an installation of Y's previous version, ensuring that all DataSets are in place.

The link is the Wealth-Lab Wiki. See Is Wiki down?, last post.

UPDATE 01/07/2020: Other users from EU have no trouble updating Yahoo! data.

Hello, still trying since last post and still not working

always Error 401.


And happy new year!!

Update the extension to v2020.01 and restart WLD.

Nowadays I update Y! data on a daily basis from a EU IP and it works 100% of the time.

Happy New Year to you too!

Hello, this is the error I get when I try to execute Yahoo.WMS_2020.01.wle (size:5K)

You will get this for any extension not just Yahoo. We emailed a letter with solution to you and other customers with outdated 6.9.15 builds back in November. See Errors installing/updating Extensions > "Solution #2: Applies to Wealth-Lab Developer users running v6.9.15 ONLY"

Everything installed and working!!!!
Wonderfull software and wonderfull team.

At your service. Glad you like Wealth-Lab!

Attention:

Lately we encountered sporadic errors updating Yahoo! data: "Error: Input string was not in a correct format". The data for affected symbol(s) is not updated until you repeat update several times.

Version 2020.02.1 of Yahoo! provider fixes it.

Attention Yahoo provider users

If you notice incorrect backtesting results or false gaps on Yahoo charts (see screenshot) even with "Enable split adjustment" activated, you have to:

1. Update to the latest version 2020.02.9 of Yahoo! provider
2. Reload your data.

For a handful of symbols only, right click on the chart and do a "Reload Chart History". For bulk reload, install the Data Tool and choose "Remove all data" on your DataSet, then simply update it.

Hi Eugene,

Unfortunately we are revisiting this nasty issue, this time with Yahoo static data. (I realize this thread is about Fidelity data, but it is the same problem as above.) There are a bunch of symbols that I suddenly can't get full data in chart and after reload chart data I get Data Not Available error. I am also getting this strange error message from Yahoo update:

QUOTE:
Updating Provider Yahoo! Finance ...
Preparing requests ...
Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 67 symbols...
Security Names updated.
[6] AMRN Error: Input string was not in a correct format.
[3] BABA 1356 bars 2/7/2020 1 bars added 1 bars corrected
[9] AMZN Error: Input string was not in a correct format.
[0] ^DJI 8829 bars 2/7/2020 1 bars added
[2] ^RUT 8169 bars 2/7/2020 1 bars added
[4] AMD Error: Input string was not in a correct format.
[7] ^MID 9860 bars 2/7/2020 1 bars added
[1] ^NDX 8660 bars 2/7/2020 1 bars added
[5] AAPL Error: Input string was not in a correct format.
[8] ^GSPC 17639 bars 2/7/2020 1 bars added
[3] BYND 195 bars 2/7/2020 27 bars added
[0] CSCO Error: Input string was not in a correct format.
[9] CHK Error: Input string was not in a correct format.
[4] EEM Error: Input string was not in a correct format.
[7] EFA Error: Input string was not in a correct format.
[6] BAC Error: Input string was not in a correct format.
[8] FB 1943 bars 2/7/2020 1 bars added 1 bars corrected

Does "Error: Input string was not in a correct format" provide any clue as to how I might proceed to fix this, other than reinstalling WL?

Also, I notice that most of the broken symbols will only display bars until 1/27/20, if that's another clue.

I suspect this is why some trades have not been triggering a signal on certain symbols. Need to clean this up ASAP.

Robert

Hi Robert,

I've moved your offtopic post from a totally unrelated thread here where it belongs. Hope you find it or another Yahoo thread and notice that it's already been resolved days ago. To review the extension change logs and/or search the forum before making a post is actually a very useful acquired habit. ;)

Hi Eugene,

As I am preparing to migrate to WLD, I created small data set in still WLP to test the End of day historical data Yahoo provider Instead of currently used but going away Fidelity provider.
However I got errors for QQQ, MSFT and PFE with Data Update log saying Error: Input string was not in a correct format.
Please, advise.

Updating Provider Yahoo! Finance ...
Preparing requests ...
Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 7 symbols...
Security Names updated.
[0] BLV 3348 bars 7/24/2020 0 bars added
[1] GLD 3947 bars 7/24/2020 3947 bars added
[6] TLT 4529 bars 7/24/2020 4529 bars added
[5] SPY 6922 bars 7/24/2020 6922 bars added
[4] QQQ Error: Input string was not in a correct format.
[2] MSFT Error: Input string was not in a correct format.
[3] PFE Error: Input string was not in a correct format.
Provider update complete for Yahoo! Finance

Hi Felix,

Please update the Yahoo provider in the Extension Manager to v2020.02.23. Your outdated version was affected by this error (a change at Yahoo's end).

Hi
I am having trouble updating BND, LQD and IEF for some reason through Yahoo. Please see attached image. It gives a 422 error.

Everything else is fine. My Yahoo extension manager is dated 23 Feb with no updates showing as required.

Any ideas please?

My WL version is 6.9.15 64 bit, non US user.

Thanks

Rod

Hi Rod,

First of all, your provider version is outdated - like your Wealth-Lab build which cannot update extensions. Please update WLD to 6.9.23 and then the Yahoo provider to v2020.2.23.

Hint: If for some reason a related topic doesn't come visible on "Most Recent Posts" instantly, try searching the forum for a keyword as simple as "422". There's a good chance it was raised and answered before:

Yahoo errors 422 (unprocessable entity), 404 (not found)

Thanks Eugene. You are always so incredibly helpful and responsive. Have a good day.

You're far too kind. If the issue persists after following suggestions in the topic please let us know and we'll have a closer look.

Yahoo errors 422 (unprocessable entity), 404 (not found)

Thanks Eugene,

Yes, Installing Yahoo provider v2020.2.23. fixed data update.