Error: Strategy Error on calling 'OnStartUp' method for strategy '': Bad IL range.

[Luigio]

Hello,
I have strategy using 3rd party indicator (dll). But sometimes (very often) get this error:
Strategy Error on calling 'OnStartUp' method for strategy '': Bad IL range.

I get the same error when I tried to used the 3rd party indicator in my own indicator.
Any idea what's wrong?

Thanks a lot.

[NinjaTrader_Jesse]

Hello Luigio,

Thank you for the post.

The error you mentioned is not one that I have seen in the platform previously, however, there are some details surrounding " Bad IL range." in contrast to C#.

This specifically mentions OnStartUp which is a NinjaTrader state, so the script is failing in its OnStartUp override. The message Bad IL range seems to come up for a few C# situations relating to either corruption or incorrect format.

From the given details, this could possibly be that the dll is corrupt and needs to be reinstalled. This could also be something that the script is doing in its code because the error states OnStartUp. I would suggest reaching out to this vendor to get a new download of the files and then re-import it. This would be a good first step at diagnosing this situation, or to make sure the files are all valid and up to date. You can also pass this information along to the vendor to see if they have any reported cases of this happening.

I look forward to being of further assistance.

[bltdavid]

Strategy Error on calling 'OnStartUp' method for strategy '': Bad IL range.

Contact the vendor.

This might help,
https://stackoverflow.com/questions/...exception-mean

[bltdavid]

This might help, too,
https://stackoverflow.com/questions/...ange-net-error

[bltdavid]

Maybe indicator's DLL is 64-bit and you're running 32-bit version of NinjaTrader?

Some vendors do not expose the DataSeries and other needed properties from their
indicators, so they're not that useful to the NinjaScript programmer -- but not sure
how *that* issue would cause the error you're seeing ...

I don't know, contact the vendor of the 3rd party indicator for support. Ask for help
confirming your DLL is correct and not corrupted.

I have a feeling this problem may require you to find a solution via a long process
of elimination -- it appears the cause may be any number of things.