Not sure if this is the correct forum to post. This week I have been having intermittent issue with accessing Yahoo Finance website. Not sure if anyone else have noticed it.

It used to be fine till last week. When I update the dataset with Wealth-Lab Developer 6.9, it fails to update the symbols. I'm open to any suggestions or workaround.

This is the messages in LastUpdateLog :

Updating DataSet myDaily_US ...

Preparing requests ...
Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 3979 symbols...
Error updating Security Names. The remote server returned an error: (414) URI Too Long.
[0] AACTF Error: The remote server returned an error: (401) Unauthorized.
[4] AAPL Error: The remote server returned an error: (401) Unauthorized.
[2] AAL Error: The remote server returned an error: (401) Unauthorized.
[3] AAOI Error: The remote server returned an error: (401) Unauthorized.
[8] AAWW Error: The remote server returned an error: (401) Unauthorized.
[5] AAPT Error: The remote server returned an error: (401) Unauthorized.
[9] ABAC Error: The remote server returned an error: (401) Unauthorized.
[6] AATV Error: The remote server returned an error: (401) Unauthorized.
[7] AAWC Error: The remote server returned an error: (401) Unauthorized.
[1] AAGIY Error: The remote server returned an error: (401) Unauthorized.
[3] ABKI Error: The remote server returned an error: (401) Unauthorized.
[2] ABEV Error: The remote server returned an error: (401) Unauthorized.
[9] ABMBF Error: The remote server returned an error: (401) Unauthorized.
[8] ABLE Error: The remote server returned an error: (401) Unauthorized.
...
...
Provider update complete for Yahoo! Finance
----------------

Update completed (3 min 51.756 sec)
----------------

Just an update - after reading the other posts, clearing the cookies in the browser seems to work with access to yahoo finance using the browser.

I tried restarting WLD, but it did not fix the problem. Maybe the Yahoo session cookies are not cleared from WLD ?

Yes, restarting WLD clears the Yahoo session cookies. "(414) URI Too Long" followed by Error 404 was what we discussed here:

Yahoo Error: The Uri string is too long (SOLVED)

Thanks Eugene.

Looks like I ran into same problem/solution as discussed in this thread :

https://www.wealth-lab.com/Forum/Posts/Yahoo-cookie-error-caused-data-update-to-fail-39839

(after switching to mobile hotspot, it worked)

Glad to see you're up and running again!