Anyone got any tips for resolving this error?
"There was an error generating the XML document"
It happens on a custom indicator of mine with just 1 simple parameter.
#region Properties
[NinjaScriptProperty]
[Display(Name="AutoT", Description="Autotrade", Order=0, GroupName="Parameters")]
public bool AutoT
{ get; set; }
I sent the indicator to support, but as you can put this part in code itself in a clean indicator and it does not error... I have always had an issue with this one indicator. The whole NT app has been uninstalled and re-installed from clean many times, no difference, so I know it is the indicator code causing it.
The trace log only shows the error as
2017-05-11 18:07:25:328 ERROR: Could not save indicator 'pjsLights:' There was an error generating the XML document.
So no help there as to what might be causing it. These are 'unhandled exceptions', so bugs, in my mind. If they were handled errors, they obviously would be 'caught' and reported cleanly.
This error can be reproduced when saving any chart window with the indicator on, or trying to save as a template.
I'm not asking for a NT support response (I have, but tired of being told it's my pc and to asked to uninstall and rebuild my workspace which takes me hours when I know it is OK), but if anyone has come across this and has any luck resolving, please do let me know. This (apart from a documented bug in NT) is the only other issue I have with the platform, despite daily use, but unfortunately they are show stopping issues going forward.
Given the above sample can be put in a new indicator and it will save and this is the only coded parameter, I wonder what else re an indicator NT tries to save as XML?
In case it makes any difference, this indicator adds 6 plots and 6 dataseries, but as far as I know, that's just coded and not stored as XML when saving a template. The indicator itself works perfectly, just as a result of the error, the charts do not save and have to be rebuilt on every load.
Many thanks.
"There was an error generating the XML document"
It happens on a custom indicator of mine with just 1 simple parameter.
#region Properties
[NinjaScriptProperty]
[Display(Name="AutoT", Description="Autotrade", Order=0, GroupName="Parameters")]
public bool AutoT
{ get; set; }
I sent the indicator to support, but as you can put this part in code itself in a clean indicator and it does not error... I have always had an issue with this one indicator. The whole NT app has been uninstalled and re-installed from clean many times, no difference, so I know it is the indicator code causing it.
The trace log only shows the error as
2017-05-11 18:07:25:328 ERROR: Could not save indicator 'pjsLights:' There was an error generating the XML document.
So no help there as to what might be causing it. These are 'unhandled exceptions', so bugs, in my mind. If they were handled errors, they obviously would be 'caught' and reported cleanly.
This error can be reproduced when saving any chart window with the indicator on, or trying to save as a template.
I'm not asking for a NT support response (I have, but tired of being told it's my pc and to asked to uninstall and rebuild my workspace which takes me hours when I know it is OK), but if anyone has come across this and has any luck resolving, please do let me know. This (apart from a documented bug in NT) is the only other issue I have with the platform, despite daily use, but unfortunately they are show stopping issues going forward.
Given the above sample can be put in a new indicator and it will save and this is the only coded parameter, I wonder what else re an indicator NT tries to save as XML?
In case it makes any difference, this indicator adds 6 plots and 6 dataseries, but as far as I know, that's just coded and not stored as XML when saving a template. The indicator itself works perfectly, just as a result of the error, the charts do not save and have to be rebuilt on every load.
Many thanks.
Comment