Serialization Error

[NinjaTrader_Dierk]

Guys, this is not a damon but a limitation of XML serialization.

XML serialization is a standard MS .NET technology which NT uses to persist e.g. your indicator settings. Unfortunately there are limitations with that technology. None of the NT standard indicators/strategies would suffer from that limitation but your custom indicators/strategies could (if not coded correctly to reflect these limitations).

If you googled e.g. for "xml serialization .net" you would find several references on that subject.

[Harry]

Serialization error for standard EMA

When backing up my workspace today I got once again a serialization error (see below). This time it was a standard NT indicator. It is likely that NT developpers have correctly coded EMA, but the demons are not impressed with this. I tried to backup several times, but only could do so after I had removed all EMAs. I then added them again, and this time NT would do the complete backup.

This is my standard procedure for serialization errors. They do occur, and usually they are not reproducible.

[NinjaTrader_Dierk]

I never have seen that issue on a NT standard indicator before. It would be great to have scenario which would allow us to reproduce the problem.

[Harry]

Not reproducible

It is not an important problem, as it only occurs during backups. The fact that standard NT indicators also suffer from serialization errors just shows that it is not the indicator code that produces this behaviour.

[NinjaTrader_Dierk]

Your understanding is correct. I would speculate that it's a general issue regarding your installation. May be completely reinstalling .NET (and NT) would make a difference ?!?

[Harry]

I have already done this once. My installation is stable otherwise. NT uses 470 MB of RAM (3 GB installed for XP), there are no other issues except those relating to backfill.

[NinjaTrader_Dierk]

Hmm .. then I'm of ideas for now.

[max-td]

Harry - i can confirm this kind of serialization-popup with a @EMA or @WMA i have it from time to time when saving a workspace.

if it happens - i put the indie off the chart + save workspace again + its OK. normaly i close workspace + NT then -- start new and all is fine - i can put the @WMA in and save -- everything OK then again.
it happens maybe once in a moth or 2 - no clue in wich special situations/combinations - but it happens - thats what i can confirm.

i share your thoughts to that :
It is not an important problem, but he fact that standard NT indicators also suffer from serialization errors just shows that it can not only be the indicator code that produces this behaviour.

BTW -
clean system
enaugh RAM
real stabil NT

[NinjaTrader_Dierk]

Still strange ... I just added some trace code to our new NT7 so get some more info in case that would happen on NT7 and it's new .NET 3.5 still.

[DynaMike]

Like Dave in post #9 I encounter same serialization error on my custom indicator (NT6.5-15) which exposes publicly 1 BoolSeries when saving my Workspace. Indicator works fine. However exposing the BoolSeries publicly creates the issue. I've tried all solutions presented here, as well as repairing the db. To no avail.

Anyone find a solution to this since ?

[NinjaTrader_Bertrand]

Welcome to our forums DynaMike - do you see the same issue when working with the SampleBoolSeries sample code we provide?

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

[DynaMike]

Hi Bertrand,

Thx for the reply. I did indeed see the same isssue with the sample code provided, however I resolved the issue by declaring the BoolSeries public in the variable section of the indicators.
Regardless the fact that I have no code at all in the Properties section to expose the BoolSeries I'm now able to call it in strategies.
While the latter does not seem to my layman's programmer mind as the proper way to expose the Series, it works !!

[phoenix]

Serialization Error

I know this thread is over a year old, but I got the 'error' message this evening.

Checked for the declared 'public' in varibles, not an issue.

Did the remove indie, then reinstalled it...and that fixed it.

I know you guys at NT are always looking for feedback, so there you go.

Also, thanks for keeping these threads open, a simple solution was available because of it.

[victory12]

I have already done this once. My installation is stable otherwise. NT uses 470 MB of RAM (3 GB installed for XP), there are no other issues except those relating to backfill.

Your understanding is correct. I would speculate that it's a general issue regarding your installation. May be completely reinstalling .NET (and NT) would make a difference ?!?
____________________
virtual assistant

[Harry]

This is an old - but harmless - NinjaTrader bug. From time to time NinjaTrader refuses to save a chart template or a workspace and a message pops up that an indicator could not be serialized.

Sometimes this points to a coding error in a custom indicator. But from time to time this message also is triggered for system indicators and other indicators that have no coding errors.

If this happens, just shut down and restart NinjaTrader, then recreate that workspace or template and it should work without any problems.