My strategies are day bars. I suspect that I may have created some data sets that are intra day data. When I run my strategies, I get runtime errors about bar conversions. I have tried to delete what I suspect to be the offending data sets and then re-create the data with daily bar option. However, when I re-run the strategies, I get the same errors shown in the Editor's lower display:

QUOTE:
Runtime error: Cannot convert 1936003584 Bars to Daily Scale
at WealthLabPro.ChartForm.q()
at WealthLab.BarsLoader.GetData(DataSource ds, String symbol)
at WealthLab.BarScaleConverter.ToDaily(Bars sb)

This occurs with my updated Russell 3000 DataSet, for example these 4 symbols gave me difficulty - ATK ATLO ATLS ATMI. There are other symbols before these alphabetically, but perhaps I had them in other viable data sets (S&P 500, et cetera) and so they remained ok in the newer Russell 3000. After initial errors, I deleted the R3000 and re-created the R3000 data set carefully noting the daily bar option, but the runtime error persists (but I did not exit the program before re-generating the R3000 data).

I tested the "Bad" dataset of 4 stocks ATK ATLO ATLS ATMI using various standard canned Wealth Lab strategies, and they all choked with the same error message, so I know it is not my custom strategy that is at fault here. Also, for what it is worth, I have run my custom strategy on a dataset of 1800 symbols without any error messages.

Am I correct in my diagnosis? Any ideas on procedures to cleanse my problem here?

Thanks.

I do not know if you delete the data file or not?!! Delete the dataset& recreate it clearly not fixing the problem. Sound like the problem is the A-folder data file.

Try: go to Your User directory -> AppData -> Roaming -> Fidelity Investments -> WealthlabPro -> Data -> Fidelity Static Provider -> Daily -> A -> delete files: ATK ATLO ATLS ATMI. Then update data in WL again, run your strategy, if it generates the same error on ATML ATN ... . Go back & delete the data file of ATML ATN ... . The point is not only delete the dataset& recreate it but also have to delete the datafile because it the data file being corrupted. Same thing happens to me once a while when I sync the data between 2 computer system weekly. I had to delete the whole folder, take a while to update the history but daily data won't take long as intraday.

Hmmm. Perhaps I should run chkdsk / spinrite first.

Sounds like I may have to, am willing to delete all data history from drive folders and then regenerate it. Because on 3000 symbols and problems already in the A symbols, that suggests a possible iterative grind.

thanks.

There are 3 ways (at least) to physically delete/re-write static data:

1. As marron pointed out, physically delete it from the \Data\[Some Provider]\.. folder. The same symbol can exist in several different scales, as denoted by the "Scale" folder (i.e., Daily, 5 Minute, etc.)

2. Right click the chart and choose the option to Reload the data. This is a good option if you've identified just a small number of bad-acting symbols.

3. Make sure that the symbol(s) are not included in any DataSet (we have a script to help with this), and then in the Data Manager > Update Data, enable the option to "Delete data for Symbols that are not contained in DataSets"

The Fidelity provider also has an option to delete quarantined symbols.

Thanks for summing this up, finally added to the Wealth-Lab Wiki FAQ.

It must have been data corruption / hard drive error.

I always have difficulty running chkdsk from cmd dos prompt as administrator, same nullity from the F8 bootup to dos; only way is to boot from Windows installation CD into dos command prompt. Anyway I decided to run Spinrite at level 5 on my 200 GB drive. Took 11.5 hours to complete the revitalization of the drive. So that is done. Same runtime error.

There is only Daily folder, no other time scale folder. So I renamed Daily to Junk. Then I did an WL data update. Though the Data Manager still had my symbols, update completed in 0.0 seconds (did nothing). I added a new Daily folder (empty), no benefit. Added a new folder A (empty) into Daily, still no benefit.

The problem is that I don't know which or how many of the reconstituted R3000 symbols are bad (I just choked on one, moved that to "Bad", then moved the next 3 chokes to "Bad" and I'm still in the early "A" symbols. So I'd like to just wipe out the whole underlying data folders for all symbols and just simply run update on my existing named data sets to re-create them.

Is this possible somehow? Or do I have to also delete the symbols from the named data sets in data manager and re-create and re-initialize each data set one by one?

Thanks.

By the way, I have 118 data sets.

Ha! I decided to see if the "live update" feature might work. So I ran a strategy on the R3000, and by golly, it is working.

It has progressed pass the A folder, and appears to be updating into the D symbols (I only had created a single empty A folder under Daily folder).

Hopefully this roundabout method will suffice, though I would have preferred a single batch update to have worked. So I will have to run some simple strategy on my core data sets.

Once the individual symbols are initiated through Live Update, then a regular update should freshen up the data sets to round out the historical data.

Fingers crossed and hoping it all works out.

It froze on SKH saying:

QUOTE:
Root element is missing.
Unable to get Data on Demand for symbol SHK

I clicked on the proffered "OK" and it continued updating subsequent symbols.

Wish it had an option to not pause the update, and to just report a summary of errata symbols that failed to fully process and with more details below the summary.

Yes it created alpha folders populated with symbols.wl and no entry for SKH.wl

Later then.

Yes, this work around suffices. Thanks Marron, Cone, and Eugene.

Re: Root element is missing.
This is a [xml] data transmission error. So for sure you need to refresh that symbol at a minimum. However, if it appears that the SKH.WL data file is corrupt, I'd like to see it (Try loading a chart and see if you get an error other than "No Data Avaiable").


Re: Wish it had an option to not pause the update
We think the next release will finally disable modal dialogs during data updates. Fingers crossed.

There is no skh.wl file, so not a data corruption on the disk. Hopefully will be created on a later update.

The skh.wl file has been created on a recent update.

That seems fine then, right?

Yup. Thanks for all the guidance.