Failed to Execute DB job Error

[dnoff]

I have recieved about 15-20 of these error messages this afternoon - not sure what this is??

I will also send in the error logs/workspace etc.

[NinjaTrader_Dierk]

We applied some fixes in regards to that issue for next beta. Please try again after next beta is out (likely next week). Thanks

[dnoff]

I have been getting a lot of failed DB job messages related to Strategy updates. I have been running NT 7 with about 7 active strategies to test this out. It is the same strategy running under different instruments.

When certain strategies instances open of close positions I get the following:

"failed to execute DB job "StrategyUpdateJob": There was an error Generating the XML Document: Object Reference not set to an instance of an Object:

The trace file is attached.


It seems like the "virtual entries" associated with this are causing issues???

I can send additional logs etc if required.

[NinjaTrader_Dierk]

>> It seems like the "virtual entries" associated with this are causing issues???
Incorrect, it's the custom code of your strategy which prevents proper XML serialization.

[dnoff]

>> It seems like the "virtual entries" associated with this are causing issues???
Incorrect, it's the custom code of your strategy which prevents proper XML serialization.

So it works correctly for some instruments using a given strategy, but fails for other instrument using the same strategy?

I guess how does the strategy affect the XML serialization?

[NinjaTrader_Dierk]

XML serialization imposes restrictions to your code (details could be found in the MS docs). You should be able to find a couple of related threads on this forums.

[dnoff]

So I guess I am struggling with your comments as it seems vague (at least to me). The strategy I am running working perfectly in NT 6.5, but when I run them in NT 7 some instruments fail with this under the same strategy.

Is there something new NT 7 that we now need to be aware of when writing strategies? How would simple "if/then" type logic using a single time frame cause XML serialization errors - as a strategy am I not using/calling XML anywhere explicity. Is NT wrapping these into XML somehow and now there is something we need to do?

Sorry but what are describing does compute with what I am seeing here.

[NinjaTrader_Dierk]

Unfortunately I'm unable to provide details as this is an issue related to your custom code. You needed to inspect your strategy to see what might be causing the issue. One approach could be starting off some "solid ground" like the SampleMaCrossOver strategy and amend it step by step to isolate the cause of trouble.

Also: Please make sure you reviewed the XML serialization docs from MS to understand the limitations.

[dnoff]

I'm sorry but this is making sense - what XML serialization takes place? I don't do any in the strategy anywhere, none, zip, zilch!

So how the does XML serialization enter into my strategy? This has not been answered and referring to Microsoft's document will help me how?

This is super frustrating as you indicate it is a custom code problem, when it works perfectly in 6.5 - what has significantly changed that would require a change for this? The strategy still identifies entries and exits and takes them, - there are just DB update errors by NT - how is that my strategies problem?

If it helps I can send the strategy

Unfortunately I'm unable to provide details as this is an issue related to your custom code. You needed to inspect your strategy to see what might be causing the issue. One approach could be starting off some "solid ground" like the SampleMaCrossOver strategy and amend it step by step to isolate the cause of trouble.

Also: Please make sure you reviewed the XML serialization docs from MS to understand the limitations.

[NinjaTrader_Dierk]

XML serialization is a standard .NET technology used by NT to persist your strategy. This is nothing NT specific. Please search this forum for pointers and proceed as per my post below. Thanks

[hatori]

XML serialization is a standard .NET technology used by NT to persist your strategy. This is nothing NT specific. Please search this forum for pointers and proceed as per my post below. Thanks

Could you put it in the breaking changes that you can not use enum property anymore , or accept it as a bug?

[NinjaTrader_Dierk]

I just added some code which should push the limits of what's working, so unsupported code like your sample would not longer break on migrating to NT7.

Disclaimer: Your sample code still is outside what we provide for. Nor would my code change above imply, that all issues arising from migrating unsupported NT6.5 code would be resolved.