As directed by Eugene, starting new topic on Wealth Data since search came up empty.
Don't know how to get this implemented into my WL application.
Don't know how to capture free source data from WLD web site for existing WL user.
Suggestions would be greatly appreciated.
Size:
Color:
Size:
Color:
What am I doing wrong ?
X: Access denied: This symbol is not part of your subscription
GOOG: Access denied: This symbol is not part of your subscription.
NAV: Access denied: This symbol is not part of your subscription.
Most symbols are working, surprisingly, ticker TWTR is not found.
Size:
Color:
Size:
Color:
Hi. I am a new Wealth Lab Pro user. I am also a Fidelity customer so I downloaded Wealth Lab Pro V6.9 from the Fidelity link. I am interested in testing a strategy on Futures data and would like to use the Wealth Data. I have signed up as a user at Wealth Data.
Is the free Wealth Data feed not available to users who download Wealth Lab via Fidelity?
Size:
Color:
Hi, the Wealth-Data feed is available to Fidelity customers. Please note that before they're allowed to install the extension we have to verify their entitlement at Fidelity (see my reply to your open ticket).
Size:
Color:
Hello,
I am always getting with Wealth Data this message for the stock "CON.DE".
Error processing symbol CON.DE File Stream does not open any Win32 devices. For example, disk partitions or tape drives. "\\. \" must not be used in the path.
And for "MUV2.DE": Access denied: This symbol is not part of your subscription! Because should be free!
The rest is fine! Has someone the same problem or an idea?
Size:
Color:
Thanks for your bug report, Damir.
QUOTE:
Error processing symbol CON.DE File Stream does not open any Win32 devices.
So you cannot chart the symbol or use it in backtests, right?
CON (PRN, AUX, NUL, COM1 etc.) are reserved keywords in Windows. Creating such file names should be prohibited. But "CON.DE" translates to "CON%2EDE.WL" file by WL which is safe. Could you enable
hidden file visibility and tell me what's there:
c:\Users\
Windows username\AppData\Roaming\Fidelity Investments\WealthLabDev\1.0.0.0\Data\ZZWealthDataStaticProvider\Daily\C\
QUOTE:
And for "MUV2.DE": Access denied: This symbol is not part of your subscription! Because should be free!
MUV2.DE has long been part of DAX so it definitely must be accessible to any subsciber of W-D. Very odd. Will look into it.
Size:
Color:
QUOTE:
c:\Users\Windows username\AppData\Roaming\Fidelity Investments\WealthLabDev\1.0.0.0\Data\ZZWealthDataStaticProvider\Daily\C\
Size:
Color:
Re: CON.DE. The file name on your screenshot is correct so there shouldn't be an issue. I cannot reproduce the error message. Neither on chart nor in backtest.
QUOTE:
And for "MUV2.DE": Access denied: This symbol is not part of your subscription! Because should be free!
Fixed. Thanks.
We discovered a similar error for a number of MDAX symbols, will get fixed shortly.
Size:
Color:
I get an error when i start Wealth-lab and i cannot connect to Wealth-data.
Error loading Provider.
Size:
Color:
Looks like an "Index out of bounds of an array" in German. Not sure what may be causing it exactly. Let's try this:
1. With WLD closed, open the hidden folder in your file manager:
c:\Users\Windows username\AppData\Roaming\Fidelity Investments\WealthLabDev\1.0.0.0\Data\
2. Rename the ZZWealthDataStaticProvider folder to say ~backup~ZZWealthDataStaticProvider
3. Start WLD, enter your username/password on the W-D tab in the Data Manager and update Wealth-Data.
Size:
Color:
Getting this error at the startup
QUOTE:
Error Loading Provider:Index was outside the bounds of the array
Neither uninstalling and reinstalling (fresh downloaded) the extension nor PC reboot helped
Provider appears in installed extensions but not in Data Manager.
Size:
Color:
What did you do to make it happen? You should not encounter such error in daily usage.
At any rate, try renaming the ZZWealthDataStaticProvider in AppData/Roaming with WLD closed to make sure its config files are not corrupt.
Size:
Color:
QUOTE:
What did you do to make it happen? You should not encounter such error in daily usage.
A PC freeze event occurred before this started to happen.
Your suggestion fixed the problem. Thanks for your help.
Size:
Color:
Glad to see you're up and running again.
Size:
Color: