Hello,

I see from other posts that this is a somewhat nondescript error, and I can't find anything specifically applies to my problem.

Using: Wealth-Lab Pro 6.9

Problem: I have a number of very basic charting Strategies that I built some time ago (over a year), they've worked fine until recently when a few of them have started failing. The strategy will not display, instead it throws up an error message.

Error Message: "Object reference not set to an instance of an object. Unable to get Data on Demand for symbol: FCG."

I thought something might be wrong with the Strategy so I tried to just launch a new chart window and that fails too for the same error. So the problem appears to be related to these certain symbols, e.g. FCG, TVIX. I tried "Update Dataset Pricing" in the Data Manager and that says that it downloaded the data for these symbols just like all the others, but still I would have to suspect there's something wrong in the data. How do I track down what's gone wrong here?

Thanks,
John

Hi John,

Whenever you have an issue please review the Wiki Knowledge Base for an instant solution. In particular, this looks like another incarnation of a known bug with Fidelity reverse splits:

Open Issues > Fidelity data can not be updated except for N minute

FCG and TVIX had reverse splits earlier this year. Please review the KB article for several workarounds to the problem.

Despite the reverse split, at the same time the issue may be of a different kind i.e. corrupt chart drawing object in one or more bar intervals (less likely). So if the workarounds above won't help, here's a different troubleshooting technique:

Errors | Other > (scroll down to) Error message on a chart and/or copying chart to clipboard

Update:

When the error message reads "...Unable to get Data on Demand for symbol..." as in this thread, it may also make sense to uncheck "Update Data on Demand" in the Data Manager.

Eugene,
Unchecking "Update Data on Demand" does not solve the problem. You don't get the error message anymore, but you don't get the data. Is this a problem with Fidelity's data after the split. Or is the problem with the old data stored on the PC.
Gary

Gary, I have no idea what "you don't get the data" means for you as this is ambiguous. (Here's a guide on explaining problems in detail and another on asking questions the smart way).

But this is only half measure for Fidelity data that cannot be updated. If your issue is exactly like described in "Fidelity data can not be updated except for X minute", then the Wiki link above contains 4 workarounds to try.

Eugene,
When try to use the symbol TQQQ I get message "Object reference not set to an instance of an object. Unable to get Data on Demand for symbol: TQQQ" I tried the WIKI and have not found anything that works including the application that is suppose to delete the old data file for TQQQ. I just keep getting that message above.

Gary

QUOTE:
including the application that is suppose to delete the old data

Well, that Data Tool extension is really easy to find on our website (Extensions section) but it's not really required. As one symbol TQQQ is affected you just have to reload the data manually as suggested in the Wiki. Keep your data up to date by updating DataSets manually and make sure "Update data on demand" is unchecked.

If this doesn't help, you might want to reread post #2 to the end. There's one more solution in bold that you haven't tried.

Eugene,
I unchecked getting data on demand and then loaded the data manually. I almost thought I had it as it read "TQQQ up to date." But them when I try to chart it, the data stops at 5/22/2018. I have also tried the last line above. No luck.

That's a clue.

1. Is there a chance your chart's data loading range was not set to "All Data" but the chart data range ended on 5/22/2018?

2. Could you show me the last data update log for your TQQQ DataSet?

3. What steps have you done exactly to alleviate the issue on your 3 PCs? "I tried the WIKI and have not found anything that works" will not work. Please be verbose this time. This concerns both the 4 steps described in Open Issues as well as workaround #5 in Error message on a chart and/or copying chart to clipboard (as referred in my post #2 above).

Eugene,
I did the update data with Delete data for symbols not contained in data sets. If I uncheck "update data on demand" and then try 30 minute bars, the data goes to 5/22/2018 and shows the unsplit price and no error message. For Daily and 10 minute bars the data shows split price to 5/25. The same thing for UPRO except the split date 5/21. Somebody forgot to split the price for 30 minute bars.

Here is the last history log.

QUOTE:
Updating Provider Fidelity Investments ...

Updating 1 Minute data ...

Updating 15 Minute data ...

Updating 30 Minute data ...
Requesting updates for TQQQ,UPRO
Processing 3:1 Stock Split for TQQQ ...
Provider update complete for Fidelity Investments
----------------


Update completed (0.741 sec)

It says the update was made, but it never happened for the 30 minute bars.
Gary

Gary, this update log looks like a typical log for those affected by "Fidelity data can not be updated except for N minute" problem. I don't have anything else to suggest because our third party company isn't responsible for developing the Wealth-Lab application. But so far the Wiki workarounds have worked for everyone so I'm sure your case is not the exception - if you follow them precisely as described.

In Post #10, this is a know bug.

1) Delete the TQQQ and UPRO from your 30-minute dataset.
2) Run a Data Manager update with the option to "remove symbols not in datasets" checked.
3) Check the Data Manger log to verify it removed these two symbols totally.
4) Now add these two symbols back into your dataset(s).
5) Rerun Data Manager to download the entirety of these two symbols from scratch.

That should fix your problem. I do this all the time whenever there's a stock split. I've had lots of practice with this.

You might call Fidelity's Active Trader Pro help line, (800) 544-7595, and mention you want this WLP stock-split updating bug fixed soon so it gets higher priority. Be sure to tell them the problem is for 30-minute static updates.