Resurrection of the Ninja?

[BankRobber]

As usual, I left my strategy running during the night.
Today when I woke up, I found my Ninja with well known message "NinjaTrader has stopped working, blah, blah..."
When I looked into the Output screen, I was curious to find the moment of death,the last print was around 7:30AM this morning, well, RIP Ninja!
However, when I pulled up the log file of the strategy around 10:00AM , it was still alive and working and making prints there.
I'd like to get an answer from a Ninja specialist, has Ninja really resurrected or actually never died? LOL

[NinjaTrader_RyanM1]

Hi BankRobber,

We can take a look at your trace file for more information on the crash, and subsequent activity. Please send using Help > Mail to support feature, and include a link to this thread. Thanks for sending these in.

[BankRobber]

Strategy doesn't use any external indicators at all. They are all coded as functions inside the strategy, even the simplest one like SMA or EMA. the only way to kill the strategy is to have an open chart ( which i had) with regular slow motion indicators attached.
It takes less time to start the strategy on 28 instruments with 6 time frames 14 days to load, than just one chart , one instrument, one time frame, 14 days to load, with regular indicators

[NinjaTrader_RyanM1]

Thanks, we received the files. The crash message won't always close the platform entirely. There are several different NinjaTrader components -- Each window could be considered separately.

Anytime you see the message "NinjaTrader has detected a problem and needs to close" but NT keeps running, it's a good opportunity to save your work, and manually restart the program.

[BankRobber]

Thanks, we received the files. The crash message won't always close the platform entirely. There are several different NinjaTrader components -- Each window could be considered separately.

Anytime you see the message "NinjaTrader has detected a problem and needs to close" but NT keeps running, it's a good opportunity to save your work, and manually restart the program.

2012-01-06 07:32:27:725 *************** unhandled exception trapped ***************
2012-01-06 07:32:27:725 Object reference not set to an instance of an object.
2012-01-06 07:32:27:725 System.NullReferenceException: Object reference not set to an instance of an object.
at System.Data.SqlServerCe.Accessor.Dispose()
at System.Data.SqlServerCe.Accessor.Finalize()


Is there a way to know where this call was originated from (strategy or some of the indicators)?

Yeah, I know, next time, before I collapse, I'll close everything except the strategy. Then at least I'll know who the cuprit was

[NinjaTrader_RyanM1]

That likely originated from NT internals, unless your strategy is working directly with the NinjaTrader database or another custom db. If it's possible to find the exact conditions for reproducing, we could run this scenario through development to see if it can be improved or fixed.

To isolate lines of code causing exceptions, you could add try-catch blocks. This would be more useful if you were consistently running into exceptions and wanted to find out what parts of your code were contributing:

http://www.ninjatrader.com/support/forum/showthread.php?t=9825