I wanted to ask what is the reason why I am getting "Internal error processing" when I am updating my datasets?


Is 2gigs of ram not enough for running this application? because I "get out of memory to process request" I usually have to run multiple updates on the same dataset just to get that set up to date.

We only know that 1) you have 2Gb RAM and that 2) you have some errors that we potentially have never seen ourselves.

What we don't know to understand:

* which data provider(s) is(are) this,
* when did it start,
* what O.S. and WL version and bitness you have,
* what kind of data updates you do when it happens (by provider, DataSet only),
* the complete error message (a screenshot could also help),
* the symbols,
* what kind of other WL activity is going on when you're updating (e.g. streaming windows, how many workspaces, or no activity at all, etc.)

Could you help us understand, isolate & reproduce?

* which data provider(s) is(are) this,
Fidelity

* when did it start,
First time I ever tried to update sets

* what O.S. and WL version and bitness you have,
Window vista 32 and WL pro 6 32

* what kind of data updates you do when it happens (by provider, DataSet only),
It happens usually on 1 minute updates for any large set ie S&P 100 for the past year l minute data. I only do 1 minute updates because you can always scale up in back test but never down.

* the complete error message (a screenshot could also help),

Requesting updates for XRX
XRX 673556 bars 3/29/2011 4:00 PM 780 bars added
GILD Out of Memory to process request.
Try closing applications or running fewer tasks.
ABT 359068 bars 3/29/2011 4:00 PM 1 bars added 1171 bars corrected
AMZN 264485 bars 3/29/2011 4:00 PM 1 bars added 1171 bars corrected
BA 526629 bars 3/29/2011 4:00 PM 1 bars added 1169 bars corrected
BMY Internal Error requesting: 0
CL 68264 bars 3/29/2011 4:00 PM 1 bars added 1170 bars corrected

* the symbols,

It happens on a lot of symbols, to many to listed. Up above are just a few out of many symbols I am trying to collect

* what kind of other WL activity is going on when you're updating (e.g. streaming windows, how many workspaces, or no activity at all, etc.)

There is no other WL activity going on. I am sometimes doing research in my browser and I have skype running for calls, however I have tried to update with nothing but WL running and I still get the same errors

Hopefully I have provided you with enough information, if you need more information let me know.

I've seen that happen for large downloads too. It's an unfortunate result of the [32-bit] Windows memory management.

1. To get around the problem create DataSets in small groups of symbols and update the DataSets one at a time from the Data Manager. Restart WLP after each DataSet update is complete so that Windows releases the memory. After the initial download, you can delete the DataSets and create the ones you require without upsetting the data.

2. When you run into memory problems, data files may become corrupt as the "1170 bars corrected" indicates. When you're done downloading your data, use the Bad History Data Check [Rev. A] to check your data files. (See the Strategy Summary for instructions.)

3. If you're going to do serious intraday backtesting with 1-minute bars, you'll need a 64-bit system with lots of memory.

@Cone

Thanks for the information.