Since this happens several times a year, I'll try to update this topic each time it occurs.

There are still 6 hours before the next session opens, but data for March 20 is still not available from Y! Finance. Get your backup provider ready. For another free provider, try Morningstar.

How Do I add Morningstar to the update list?

Question is ambiguous:

* On how to install/uninstall/update Wealth-Lab extensions, review this illustrated tutorial and/or check out the Wealth-Lab User Guide > Extension Manager.

* On how to update data, see the User Guide: Data > Data Manager > Update Data.

Thanks, Eugene.

I installed Morningstar Extension but there are no bars added with EOD data.

Here's a fragment of the latest data update log of Morningstar symbols:

Updating Provider Morningstar Static ...
Provider update complete for Morningstar Static
----------------

Updating Provider Morningstar Fundamental Data ...
^AEX 83 fundamental items updated
...
ZMH 83 fundamental items updated
Provider update complete for Morningstar Fundamental Data
----------------

Update completed (1 min 34.6 sec)
----------------

You've updated the fundamental data by checking "Morningstar Fundamental data" among "Fundamental data providers". The checkbox for static data is above, among "Historical data providers", and is called "Morningstar Static".

I updated Morningstar Static too. This was the outcome:

Updating Provider Morningstar Static ...
Provider update complete for Morningstar Static
----------------

Update completed (0.15 sec)




No bar added...

For some reason, update all data may not work immediately for Morningstar data when you haven't used it before. Try highlighting your Morningstar DataSet and click "Update DataSet (Price)". This should kickstart it, and then data update will start working as expected.

It was a good run for the last 6 months, but Yahoo! is not updating again today for the 17 Sep 2014 session.

any news here? I just tried it again its now after the closing of the session of the 18th of Sept and still there is no data for the 17th?

Might there be some next change in their API / Format as such things tend to occur some times? Ok it seems that on Yahoo finance page its not updated as well.

For news you might want to contact Yahoo support. There are many backup data feeds if you need the data now.

As usual, it was just a temporary condition. Y! is updating to the prior session (18 Sept.) now.

This yahoo URL allows downloading last OHLCV data (as EOD, 15 min delayed) any time of the day.
http://quote.yahoo.com/d/quotes.csv?s=@@@&f=sd1ohgl1v&e=.csv
"@@@@" = Symbol/Ticker
Using this as a standby Yahoo provider will help to circumvent the "missing last EOD data". Off course one would need a provider "Add on" to use it in WL

In that case, open the Data Manager (Ctrl+M), go to the Yahoo! Data tab, and put a check next to "Always return data with partial bar". It works! Good show Harapa ;)

Yes, indeed it works (except for Mutual funds...minor issue for most folks).
Glad I could help!

Cone,
With the above URL one can download last data for symbols without history (for example ^VXX-IV). However, I get no data with Yahoo DL in WL (Partial bar checked). Wonder if this functionality can be Incorporated in future Yahoo provider. If there is a trick to get this even with the existing version, llet me know.

Yahoo! is updating.. .to 12/30/2015 without partial bar checked and to 12/31/2015 with it. Are you having trouble with a specific symbol? Please be more specific.

Yes, there isn't any issue with yahoo updating except for symbols for which there is no history, like the one I mentioned.
I am interested in fetching data for this class (Intraday/EOD data yes, History No)..

Symbol examples
^VXX-IV
^XIV-IV
^NUGT-IV
SPXH16.CME

There is nothing to fix or request here. All these symbols except the futures are happily streaming in a Quotes window. As per the FAQ, it is not possible to get the futures data from Yahoo. Neither is possible to obtain their historical data because Yahoo doesn't have it but it's not a problem for other providers.

Shouldn't Fidelity have symbols like .VXX in their data??

QUOTE:
There is nothing to fix or request here.

My query highlighted the "possibility "of using the above URL to fetch these in WL. At the moment, I do this in another program but then I have to make those accessible in WL (lots of maneuvering...). So I asked...

QUOTE:
Shouldn't Fidelity have symbols like .VXX in their data??

No, checked already...

Actually, most are intraday NAV... examples tickers are for yahoo...other sources may use different ticker

Re: lots of maneuvering

I don't see a good reason to include this URL in the Yahoo! provider as there's no history for those symbols anyway. If you need this for some purpose, you're better off creating a simple script for fetching the data on-the-fly. I already showed you how it can be done, so there's really no need for maneuvering or Excel:

Extracting Shares Related Info for Proshare ETF/Ns
WealthScript Techniques | Access Data from the Internet on-the-fly

/Should you have interest in discussing it please do so outside this thread that deals with "Yahoo! Data Not Updating for Last Session"./

Many symbols are not up to date (missing July 13th prices). The Yahoo! Finance site seems to have had an overhaul recently. Maybe it's connected.

Neopolix wrote in a duplicate thread:

QUOTE:
Hi,
i' ve got no Data today from Yahoo. Is that a General Problem?

This is a problem at Yahoo's side. You might want to contact them (indicating that the "Download Data" link on the Historical Data page doesn't contain the data since Nov 7th) or use one of the many backup providers:

Report a data problem to Yahoo

Thanks Eugene!

ATTENTION

Note that Yahoo does not seem to be returning the Dec 7 bar. Suggestion: use any backup data providers.

If you trade only Nasdaq 100 and S&P 100 stocks, give Wealth-Data a try!

Wealth-Lab Developer customers should already have the Wealth-Data extension installed with 6.9.15, so just sign up at the Wealth-Data site for access.

Even since I activated "Always return data with partial bar"(Data Manger/Yahoo Data), Yahoo provider fetches data anytime of the day without any issue. Never a single missing day.

Harapa, that's good advice. However, after not being able to update the data the traditional way today (last date is still 05/12/2017), I've used the partial bar technique and it couldn't update a few symbols:

QUOTE:
...
Security Names updated.
[1] AXP 11339 bars 15.05.2017 1 bars added
[3] CAT 13937 bars 12.05.2017 0 bars added
[6] DD 13937 bars 15.05.2017 1 bars added

So I had to update it again and this time it worked:
...

QUOTE:
Security Names updated.
[1] AXP 11339 bars 15.05.2017 0 bars added
[3] CAT 13938 bars 15.05.2017 1 bars added
[5] CVX 11951 bars 15.05.2017 0 bars added

Today, in WL, I am not getting any data as well. This must be something to do with yahoo URL.
I am getting bad gateway error instead of no bars added
"CSCO Error: The remote server returned an error: (502) Bad Gateway"

as this works (on a different platform, though)
http://download.finance.yahoo.com/d/quotes.csv?s=@@@&f=sd1ohgl1v&e=.csv

but this worked this morning but stopped working EOD
http://chartapi.finance.yahoo.com/instrument/1.0/@@@/chartdata;type=quote;range=15d/csv

QUOTE:
as this works (on a different platform, though)

This would work in Wealth-Lab too if we kept on using HTTP as in your link (we've switched to HTTPS). However, it's just the current day's snapshot quote - not very useful for historic backfills. Currently, I get a '504 Gateway Timeout Error' for all data update requests. Could be a glitch, could be depreciation of the old API. Let's keep an eye on this:

Yahoo Historical Data - Did they change the URL recently?
Is Yahoo! Finance API broken?
has yahoo stopped history data api service?

QUOTE:
but this worked this morning but stopped working EOD

We weren't using this RESTful API which reminds me of Google API.

Just noticed that the CSV download link on the Y! Finance website has changed to:

CODE:
Please log in to see this code.

The bad thing is this there's more under the hood than this vanilla URL. Now it requires cookie authorization and a "crumb" (the last param) which is sort of CSRF token.

Although there's a way to request the data without cookies it consumes too much network traffic and therefore may not be suitable for all.

Hi there,

what is your opinion. When does it work again?

Hi,

It might work again some day when there's more clarity on what's happened. The outcome depends very much on what it is:

1) an outage? = wait for a few days until it starts working
2) old API decommissioned, API switchover? = fixing it may take a long time

For now it seems like the worst has happened.

At any rate, there's no shortage of alternative data providers. As here we need to focus strictly on the technical aspects of Yahoo APIs, you're welcome to discuss alternatives in other forum threads. Thanks.

Yahoo Provider:
Working URL's for data download/retrieval as of 5/17/2017 AM. No cookies involved...
//@@@ or @@@%%% ...fills in the symbol

Last Trading only. Reports last price (intraday or EOD after market close))
http://download.finance.yahoo.com/d/quotes.csv?s=@@@&f=sd1ohgl1v&e=.csv

EOD...Fetches History
Defined Interval: (Need to define beginning and end dates...e.g 1/1/1950 to today). Note UNIX time stamp after"="
https://finance.yahoo.com/quote/@@@%%%/history?period1=-630961200&period2=1494993600&interval=1d&filter=history&frequency=1d

Thanks for trying to help.

QUOTE:
EOD...Fetches History

I knew that but this is not suitable as every page is a 0.5MB request with tons of supporting stuff packed in whereas a correctly formed Y! request consumes 2 orders of magnitude less traffic (only a handful KB).

QUOTE:
Last Trading only. Reports last price (intraday or EOD after market close))

Question is for how long will it last.

On the bright side, the so called protection (cookie + crumb) is a joke compared to more sophisticated obstacles which we've overcome in some other projects. The strikingly bad news is what I've just read on ET board:

1. Previously, OHLC were unadjusted and now OHL are split-adjusted
2. Sudden injections of random false data - I can confirm e.g. a couple of "null" bars in AAPL
3. Gaps of data (blocks or certain dates) - e.g. a hole of 143 bars in TRV

Time will tell whether this is intentional or just the effects of transition.

Yahoo provider still does not have data (since 12th). It looks they could have changed the links for data fetching, please check it. WLD prints 504 error into the update log.Thank you

Vadim, thank you for letting us know. Please scroll this page up to my post #29. In the conversation that followed you might find some new insight into the problem. Thanks again.

Eugene, thank you. I apologise, It does not work, - I used to load a bunch of stocks every day from indices to check the candidates, now none of the universe is loading even partial bar.

Chisholm's Third Law says, If you explain so clearly that nobody can misunderstand, somebody will. ;)

Vadim, the idea was that if you read the conversation that followed up to post #35 and not just #29, you'd know the verdict: old Yahoo data as we knew it is now broken for everyone in the world. The old API is discontinued. There can be no workaround. Now it's a major effort to adjust to the new API considering all its drawbacks known and unknown (see #35).

An updated Yahoo provider is already being tested. We'll try to release it after we iron out some glitches.

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

Eugene - Thank you. Yes, it appears to be working.

Were you able to implement without cookie/crumb method? If so, are you able to share the approach you used to eliminate the need for C&C?

Also, I see that Yahoo historical data is not currently calculating prices adjusted for dividends (recent problem). However, it looks like WL is correctly adjusting historical Yahoo data for dividends. Did you find a different place to download adjusted data or are you calculating adjusted data within the program or on your server (i.e., post Yahoo download)?

QUOTE:
Were you able to implement without cookie/crumb method? If so, are you able to share the approach you used to eliminate the need for C&C?

I went the cookie/crumb path as the method with faster downloads and minimum network traffic.

QUOTE:
Also, I see that Yahoo historical data is not currently calculating prices adjusted for dividends (recent problem).

Provider now unadjusts the data before storing it in raw format and then adjusts it for splits/dividends on demand. Before the old API got decomissioned it had been easier.

P.S. To the list of issues in post #35 I can add another:

4. For a number of symbols, the data is returned raw (split-unadjusted). This creates a false gap. Compare for yourself:

* An example of how it should be: recent NVUS 1/9 split. Data is adjusted on the website. Provider works correctly.

* A 2/1 split in BLL which isn't reflected in the data. Provider cannot handle this properly.
* Now, see how a historic split in the same stock is reflected correctly on the website: BLL 2/1 split @ 02/16/2011

QUOTE:
Provider now unadjusts the data before storing it in raw format and then adjusts it for splits/dividends on demand. Before the old API got decomissioned it had been easier.

Interesting. Is there an option in the URL string that enables the download of dividend-adjusted data? Or by "on demand" did you mean at the time you download it? It is not dividend-adjusted for symbols I've run history for on their Website. It "magically" got adjusted properly (dividends at least) when downloaded into WL history.

Sounds like this is a widely-known problem by now, so I'm curious how you got it to work.
https://www.bogleheads.org/forum/viewtopic.php?t=219605

QUOTE:
Or by "on demand" did you mean at the time you download it?

Yes. Let's rephrase:

1. The Y! provider has always been storing the raw DTOHLCV. Previously the data had been returned in raw form by Yahoo.

2. Now after the recent Y! website changes which resulted in forced OHLC split-adjustment, the provider has to unadjust the data before saving. Which means to remove the split adjustment from OHLC.

3. Adjustment for splits and/or dividends is enabled by default and is applied on-the-fly in the Data Manager (Yahoo! Data) as the provider keeps a separate database of corporate events (splits and dividend) for all downloaded symbols. You can disable it and see the raw price/volume data after reopening the chart (or F5).

I hope it makes sense.

Eugene - in this explanation, who is the "provider"? Yahoo or a 3rd party that processes Yahoo data for WL? Or are you referring to a software module?

QUOTE:
Adjustment for splits and/or dividends is enabled by default

Enabled where? What software or service are you referring to here? Since these are checkbox options (not default) in the Data Manager for Yahoo tab I am confused about what "default" means in this context.

There's no "3rd party that processes Yahoo data for WL". The Yahoo! (data) provider is the Wealth-Lab extension created by us and built into WLP and WLD. That's where the processing of data takes place:

Yahoo! Finance Static, Real-Time and Fundamental

QUOTE:
Did you find a different place to download adjusted data or are you calculating adjusted data within the program or on your server (i.e., post Yahoo download)?

It's important to stress that the data providers created by us (MS123 LLC) do not redistribute Yahoo or other data. It's not processed on our servers and then returned to you. It's always your own PC that initiates connections to their servers and grabs the data. No redistribution takes place, and there isn't a middleman.

It's clear now. Thank you.

ATTENTION: The data for CAT is currently missing at Yahoo! and you will get an "Error 404" in the update log. When you get an "Error 404" for any stock, check up "Historical Data" on their website's and (optionally) ask Yahoo support.

The Yahoo! data for CAT appear to have returned...

CODE:
Please log in to see this code.

Today I am getting an authorization error (401). Is Yahoo broken again ?
( By the way, with python scripts outside Wealthlab I checked the new Yahoo API and it
was not very reliable. In 3 out of 10 cases I received an empty data message without error indication.
I used the pandas and its new fix_yahoo_finance package )



Updating DataSet Dow 30 ...
Preparing requests ...
Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 31 symbols...
Security Names updated.
[3] BA Error: Der Remoteserver hat einen Fehler zurückgegeben: (401) Nicht autorisiert.
[0] AA Error: Der Remoteserver hat einen Fehler zurückgegeben: (401) Nicht autorisiert.
...
[0] DIS Error: Der Remoteserver hat einen Fehler zurückgegeben: (401) Nicht autorisiert.

Ouch, Error 401 is the last error code you'd ever want to encounter from the new Yahoo as it might indicate a protection change. But it's working for me right now. It also works on Wealth-Data website where we display Yahoo's recent quote to highlight data discrepancies in comparison to the clean Wealth-Data.

Please try to restart WLD. If it won't work, try to change your IP address by switching to your backup ISP. But if you're running WLD on a server (which you've been doing), who knows how does Yahoo react to it?

UPDATE: I restarted WLD, switched to German regional settings, and updated w/o a problem.

P.S. My log (running on a physical PC, not server):

Updating DataSet Dow 30 ...
Preparing requests ...
Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 30 symbols...
Security Names updated.
[4] CSCO 6889 bars 20.06.2017 2 bars added 1 bars corrected
...
[3] CAT 13963 bars 20.06.2017 2 bars added 1 bars corrected
[6] XOM 11976 bars 20.06.2017 2 bars added 1 bars corrected
Update completed (5.346 sec)
----------------

Thank you for your effort, Eugene, it is working here again...
Next time I will be having a little more patience with this Yahoo...

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!

Hi,

I get since today also the error message 401.
I have WL, PC and DSL restarted but the error is still there.
Has anybody an another idea.

greetings damir

Damir, if you scroll the page up one post and read my post #24 from 2 hours ago would this explain everything?

UPDATE 06/25/2017: As "Error 401" is fixed at Yahoo's end, the provider is working again.

Thanks.

@Eugene
RE: #45

---

Yahoo is finally correctly adjusting historical data both on their website and with downloads. I now find an adjusted discrepancy with historical Yahoo data in WL before a dividend payment date on an ETF. I found that I had to *unclick* the "Perform Dividend Adjustment" box in Data Manager > Yahoo! Data to make the data correct.

If I understood your previous explanation (#45), when the Yahoo! Data box is checked, WL will do internal dividend adjustment from *raw* data received from Yahoo. I suspect Yahoo is now (maybe after fixing their website behavior) shipping you adjusted data when you are expecting raw data. Now, with the box checked, dividend is subtracted *twice* from actual close data.

Both symbols ILF and VNQ had very recent dividend payments, so you should be able to easily see what I am referring to. Yahoo is driving all of us crazy with their surprises, so let me know if I got this one right.

cicerotullius wrote in a duplicate thread:

QUOTE:
Was there another change at Yahoo Data provider, sind a few days I only receive from them:

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

for all symbols

Please search the forum before posting. See posts #51 to #56 in this thread. Error can return at any time. As we're dealing with a free data feed, we get what we paid for.

@Eugene: I definitely get the error since a couple of days, not change, what do you suggest, restart WL?

@cicerotullius: As we are not related to Yahoo Finance anyhow, what do you expect me to suggest? Recent changes might have not been propagated everywhere. You're hitting a misbehaving server in their CDN/farm. Patience goes a long way. Or you could use Wealth-Data or alternative providers.

@innertrader: Thank you for the observations, I'll investigate. What's even more important is that Y! has changed the order of columns in downloads (Close and Adjusted Close). Reloading the data ruins it if there were splits or dividends. Fix is in the works.

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.

Yesterday our users noticed wrong data coming from the Yahoo provider, and it was determined that the culprit is yet another change at Yahoo: they've reverted the June website fix and started delivering data with mixed Close and Adj.Close columns again.

To adjust to the change, the v2017.07 Yahoo release has been unrolled. 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.

So, if you have 2017.07 installed, you should:

1. Tools > Extension Manager
2. Click on "Providers"
3. Select "Yahoo! Finance Static..."
4. Click Uninstall
5. Click the "Restart Wealth-Lab" button to complete the uninstall.

Wealth-Lab Developer customers should then go to the Yahoo! Extensions page and reinstall version 2017.06.

Wealth-Lab Pro customers can return to the Extension Manager > Providers view and reinstall directly.

It's easier, no uninstall is required. Just download the WLE file, either drop this into the Extension Manager or click on "Open WLE" there, disregard the warning and restart WLP to update.

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.

Yahoo Cookie TIme Out?

I am on 2017.7 now. But I still have a Time out error. What can I do now?

There's no global issue with Yahoo so it's something specific to your network connection. I never experience this error but if I were in your position, first thing to try would be to switch to a different ISP (e.g. mobile connection) and see if it makes difference.

That's it! It works on a mobile connection.
But what can I do now? What is the problem?

That is the error.

The problem is that your network connection is misconfigured or very slow and accessing Yahoo's servers results in a timeout. Note that the timeout is set high enough to save the cookie. It may be your ISP, your network router, your firewall or antivirus rule - anything but Wealth-Lab.

Look, this thread is overloaded with comments regarding Yahoo's real outages and breaking changes. Since your case does not belong here and only affects you, I'd appreciate if you decide to continue it in a more suitable new thread. Thanks.

Please update to v2017.08. This is a MUST HAVE update..

It seems that Yahoo Finance periodically changes the order of fields in the downloaded data (Close <=> Adj.Close) to confuse robots. Previous provider versions may return incorrect data.

As your already downloaded data may be incorrect, it's advised to review it. Pay attention to historical pre-split values.

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!

Looks like Yahoo is restricting "sweeping".
This morning I couldn't download using "Update Data" but could update individual data sets and "update data set" it worked until I got to R1K (~1000 symbols).. For R1K , "Unauthorized..." message appeared somewhere in the middle of the series. Once that happened I can't download asnymore (even the ones that were downloaded successfully..ie shorter series). Looks like yahoo is placing a cookie..

While I cannot confirm what you're saying, let me suggest to close and reopen WLP/D after you had encountered an "Unauthorized" message and then it has cleared (i.e. temporary condition at Yahoo). Reason: provider keeps Yahoo cookie in memory for some time.

QUOTE:
close and reopen WLP/D

This worked couple of times after the initial encounter but not anymore

Change your IP address by e.g. switching to one of your backup ISPs.

Or better, forget about issues and switch to an alternative data provider like Wealth-Data or Tiingo.

QUOTE:
better, forget about issues and switch to an alternative data provider

Looks like this is the way to go. Verizon (now owner of all Yahoo data) is not known as a "benevolent" organization.

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.

As we're getting asked about issues in updating Yahoo data, let's clear this up. In April 2018, Yahoo made an internal change to their website (an authentication requirement of sorts). One can quickly discover reports of Yahoo webmail login issues related to "guce.yahoo.com" domain in various online communities.

https://github.com/pilwon/node-yahoo-finance/issues/60
https://answers.yahoo.com/question/index?qid=20180322145310AAtnd9O
https://answers.microsoft.com/en-us/ie/forum/ie_other-windows_7/how-do-i-remove-guceyahoocom-as-far-as-the-east-is/6309f05a-45e4-41df-875a-1d78cd5e514d
...and dozens to hundreds more.

Also, check out this page (or a similar service): https://downforeveryoneorjustme.com/guce.yahoo.com. Yahoo data will probably fail to update if you see "It's not just you! guce.yahoo.com looks down from here".

I think this thing is affecting Wealth-Lab's Y! Finance data downloads in an intermittent manner. Restarting WL may not help for a period of time and then out of the blue it works. At the moment we do not plan to change the Wealth-Lab provider. Users basically have two options: retry update after a few minutes until Y! works for you or switch to a backup data provider.

Hello Eugene, the problem has not been resolved yet. Also my backup data provider MSN returns the same message - update impossible. Is it a data provider issue or an interface problem of Wealth Lab?

Thank you for information.

Best
Niels

Niels, I can provide information but it's above me to make users read and understand it. If you haven't seen my post #78 above please carefully review it. Got nothing else to add to it.

P.S. MSN as backup provider? You must be pulling my leg. It stopped delivering data in 2016 and has been decommissioned since then: see old MSN thread, post #27. There are backup data providers but discussing them is off topic in this thread.

Hi Eugene, I haven't used MSN for al long time, because it was not necessary. Now I know where the problem comes from. ;-)

Thanks
Niels

Hi Eugene, I'm using a software for portfolio management which also gets the data from Yahoo. They fixed the problem and it works fine again.
Btw. restarting a software and hoping that sometimes it will work again seems not to be a clever practice.
Regards
Dieter

Hi Dieter,

Appreciate your helpful feedback regarding "clever practice". And as you of course know, neither is fixing what doesn't seem broken. But the validity of troubleshooting suggestion is not at question despite the intermittent nature of the issue (with which I am not affected right now). It would probably be a life saver if I could reproduce the problem. Thanks again for sharing the solution.

Updating DataSet Dow 30 ...
Preparing requests ...
Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 30 symbols...
Security Names updated.
[4] CSCO 7124 bars 25.05.2018 0 bars added
[9] GS 4798 bars 25.05.2018 0 bars added
[2] AXP 11599 bars 25.05.2018 0 bars added
[6] DIS 14198 bars 25.05.2018 0 bars added
[1] BA 14198 bars 25.05.2018 0 bars added
[0] AAPL 9444 bars 25.05.2018 0 bars added
[7] DWDP 185 bars 25.05.2018 0 bars added
[8] GE 14198 bars 25.05.2018 0 bars added
[3] CAT 14198 bars 25.05.2018 0 bars added
[5] CVX 12211 bars 25.05.2018 0 bars added
[4] HD 9250 bars 25.05.2018 0 bars added
[2] INTC 9633 bars 25.05.2018 0 bars added
[9] IBM 14198 bars 25.05.2018 0 bars added
[5] MSFT 8119 bars 25.05.2018 0 bars added
[1] JPM 8674 bars 25.05.2018 0 bars added
[3] MRK 12211 bars 25.05.2018 0 bars added
[7] MCD 12211 bars 25.05.2018 0 bars added
[8] MMM 12211 bars 25.05.2018 0 bars added
[6] JNJ 12211 bars 25.05.2018 0 bars added
[0] KO 14198 bars 25.05.2018 0 bars added
[4] NKE 9453 bars 25.05.2018 0 bars added
[2] PFE 11599 bars 25.05.2018 0 bars added
[5] TRV 7895 bars 25.05.2018 0 bars added
[1] UNH 8472 bars 25.05.2018 0 bars added
[7] V 2566 bars 25.05.2018 0 bars added
[9] PG 12211 bars 25.05.2018 0 bars added
[8] VZ 8701 bars 25.05.2018 0 bars added
[3] UTX 12211 bars 25.05.2018 0 bars added
[0] XOM 12211 bars 25.05.2018 0 bars added
[6] WMT 11539 bars 25.05.2018 0 bars added
Update completed (5.547 sec)
----------------

Hi Eugene,
it wasn't my intention to be ironic. Despite I wanted to show, that others saw this as an error and fixed it. I restarted the wealtlab more than 20 times and it never worked. Where is the problem?
Without the sources I cannot help with a solution, unfortunately.
Regards
Dieter

Eugene, Dieter,

I still have the same problems error 401. restarting WL and/or pc several times did not help.
When I open the website of Yahoo I am forced every time to accept the new GDPR privacy rules. (I do not have another Yahoo ID). It is my hunch that error 401 (authorization) is caused by this GDPR implementation on the Yahoo side.
Maybe Eugene can take a look in this update problem.
Thanks in advance
Hugo

Dieter,
I either discovered or was pointed at various breaking changes affecting the Wealth-Lab data providers several dozen times. It's been my commitment for soon a decade - for example, having fixed our YCharts provider alone a dozen times after their changes of URLs or data formats. One thing I'm trying to put across (with no luck so far) is that this problem must be reproducible on my end to develop and submit a fix. Currently it's intermittent. Neither any quant on the usually vibrant StackOverflow is worried about the recent change in Yahoo authentication cookies (see post #78 above) which seconds my observation. At the moment no fix can be provided.

Hugo,
The problem is probably not GDPR related because I noticed some change took place at Yahoo around mid-April and documented it in my post #77 on 4/25/2018. Not sure what you mean by saying that I might look into the issue: it's my impression that I've been doing so since 5/24/2018.

Once the problem is localized and nailed down it will get fixed. But right now I've just created a random DataSet and updated it without an issue:

Updating DataSet DJ 15 Utilities ...
Preparing requests ...
Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 15 symbols...
Security Names updated.
[1] AES 6782 bars 25.05.2018 6782 bars added
[8] FE 5169 bars 25.05.2018 5169 bars added
[6] EIX 9685 bars 25.05.2018 9685 bars added
[4] DUK 9633 bars 25.05.2018 9633 bars added
[7] EXC 9685 bars 25.05.2018 9685 bars added
[1] NI 9633 bars 25.05.2018 9633 bars added
[9] NEE 9633 bars 25.05.2018 9633 bars added
[8] PCG 11599 bars 25.05.2018 11599 bars added
[0] AEP 12211 bars 25.05.2018 12211 bars added
[2] CNP 12211 bars 25.05.2018 12211 bars added
[5] ED 12211 bars 25.05.2018 12211 bars added
[6] PEG 9685 bars 25.05.2018 9685 bars added
[7] WMB 9180 bars 25.05.2018 9180 bars added
[3] D 9633 bars 25.05.2018 9633 bars added
[4] SO 9180 bars 25.05.2018 9180 bars added
Update completed (5.547 sec)
----------------

Eugene,

apologize for the thought you would not fix problems. I very much appreciate the support of WL.

Anyway. GDPR might affect your own website as well. From Europe the Extension Manager did not find the latest updates for TASC and Community. This used to work flawless in the past. And I noticed a popup from wealth-lab website for cookies. I have not seen that before.Hope this gives you good info

kind regards

On second thought, Hugo may be a champion with his GDPR theory.

The 401 issue which I saw disappearing before I fire up the debugger may be affecting me much less due to the sophisticated way my network routing is set up. Either it helps skip that new GDPR-related consent page (that everyone sees upon opening up a Yahoo page for the first time from a EU IP) or there's a timeout bigger than expected that affects retrieving the cookie. Anyway, we're looking closely into the issue and are not refusing to fix it.

Possible workaround for the time being: use a non-EU VPN.

Kudos to Hugo. The Yahoo issue only affects EU users because it's GDPR related. The provider can't get past the GDPR consent page to set a cookie required for data updates.

Bug fix is in the works. ETA this week.

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 as it doesn't add new features.

Eugene
thanks for the update. the Yahoo update works again :)

Up to today .... Yahoo is really a pain in the a...

2] RVX Error: The remote server returned an error: (401) Unauthorized.
[1] VXX Error: The remote server returned an error: (401) Unauthorized.
[0] SPY Error: The remote server returned an error: (401) Unauthorized.
[3] VXXB Error: The remote server returned an error: (401) Unauthorized.
[2] VXZ Error: The remote server returned an error: (401) Unauthorized.

Yahoo has been working just fine for me here. In your case Error 401 may mean that if you haven't restarted WL for a while the Yahoo cookie has expired. Restarting WLP/D should fix it.

My problem:

Restarting WL has never worked for me with the Yahoo Provider....
Only waiting for hours/days.... and this annoys me quite a bit.

I need Yahoo only for some indices.
Unfortunately, Bloomberg and Google are gone.

Is there any other reliable source available in WL ?
For stocks I use Wealth-Data.

Hmm, we use it ourselves (e.g. to power "See the differences!" widget on the Wealth-Data home page which highlights notable discrepancies in the price) and our ride has been smooth so far after fixing GDPR related Y! website changes last May.

Got a feeling that it may be caused by a cookie timeout or a subtle change to GDPR consent. Let me set up a special test environment to try reproduce the error under debugger. My hunch tells me that using a VPN to hide your EU IP from Yahoo may serve as an immediate workaround. Anything but EU might work to disguise Wealth-Lab traffic. Give it a try for now if it's feasible.

---

UPDATE: Last Friday I noticed how Yahoo made some change to the GDPR consent webpage under the hood and later retracted it (or maybe it depended on EU country as I was trying out different IPs). @ReneW, the provider should be working for you again. Let's revisit this issue next week when dust settles. In case Yahoo puts the new GDPR consent back in production for EU IPs, just let me know.

Update: Indeed, today (on Sunday) the Yahoo provider
working again.

Same here.

Just FYI but if you get error message below that basically means that you should restart WL to clear the saved cookie. Otherwise Yahoo data may stop working during the current session:

---------------------------
Yahoo! cookie error
---------------------------
Saving Yahoo! cookie failed. Error: Time out
---------------------------
ОК
---------------------------

It may have to do with the network connection or Yahoo itself.

Hi Eugene, Hope you are well. Coming back from my holiday the update of my yahoo data is failing all the time. Error 401. Did I miss anything? Support terminated?

Thank you very much for your reply.

Best
Niels

Thanks for the heads-up Niels. Please see posts #93 and #95 above for insight.

Support for Y! data is by no means over. However, the new fix for EU users will take some time to develop, stabilize and test. I expect it to be rolled out next week. Meanwhile you might want to try out a workaround:

1. alternative static data provider (Tiingo, Morningstar, AlphaVantage...) /off topic here/
2. non-EU VPN (see post #95)

Thanks for clarifying. I will try other data provider in the meanwhile. No trading is also an option. ;-)

Best
Niels

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 made an internal change to their GDPR consent page, breaking the provider for EU users (only). We have a feeling that it may not be the last change.

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

Thx, with the update its working again....

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.

Hi all,
for the last few days, my yahoo feed is generating "Error: Input string was not in a correct format" message for some symbols, not all of them. Do you think this is my WLD set-up or the problem is with the yahoo?

Thanks,
Branko

Ditto Here.
Error is interspersed e.g.

[9] WTR Error: Input string was not in a correct format.
[8] WWE 5103 bars 1/30/2020 0 bars added
[5] WWD Error: Input string was not in a correct format.
[0] WYND Error: Input string was not in a correct format.
[7] WYY 5461 bars 1/30/2020 0 bars added
[6] WYNN 4345 bars 1/30/2020 0 bars added
[3] WWW Error: Input string was not in a correct format.
[9] XEC 4367 bars 1/30/2020 0 bars added
[5] XHB 3522 bars 1/30/2020 0 bars added
[4] WY Error: Input string was not in a correct format.
[1] X 7256 bars 1/30/2020 0 bars added
[0] XHR 1256 bars 1/30/2020 0 bars added
[8] XEL Error: Input string was not in a correct format.
[6] XLB 5310 bars 1/30/2020 0 bars added
[9] XLF Error: Input string was not in a correct format.
[2] XII 7197 bars 12/5/2019 0 bars added
[3] XLE 5310 bars 1/30/2020 0 bars added
[5] XLI 5310 bars 1/30/2020 0 bars added
[4] XLK 5310 bars 1/30/2020 0 bars added
[1] XLNX Error: Input string was not in a correct format.
[0] XLP 5310 bars 1/30/2020 0 bars added [/quote]

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.

Back to normal. Thanks

Works again. Thank you Eugene.

Glad I could be of assistance.

Just to shed light on the problem with versions before 2020.02.1, Yahoo has thrown some randomness into the data which came unexpected. No idea if it's intentional but it doesn't appear to be going away.

I only recently noticed that Yahoo! data does not update in WL for the current day until midnight Pacific time (presumably 3 AM Eastern). I had been running daily strategies prior to this time with results similar to the title of this topic. Now I have to run them next day before market open to get correct alerts.

@Eugene Is this an example of what you were referring to in the post above (#109)?

No, it was different.

Yahoo's EOD update (the point of concern of every poster here) is currently working great. It's a free feed so delivery time isn't guaranteed as you understand. If it does update (as opposed to the topic title saying "not updating") the next day, that's perfectly fine.