Stockalyze

STOCKALYZE => Troubleshooting & Bug Reports => Topic started by: Tony on September 12, 2019, 08:26:21 PM

Title: XML parsing error
Post by: Tony on September 12, 2019, 08:26:21 PM
I'm using version build dated 9/8/3029 and when I launch it I get an error "XML parsing error: 'unclosed token' at line 27".

I thought it may be related to my alert file since I seem to have lost them.

I looked at the altert_repo file and it was missing the close "/>" symbol on the last line.

Once I corrected it all is fine.

These are the last few lines of the file BEFORE I corrected it:
  <AlertSetting Type="10" PriceOfInterest="25.0000">
    <Security Name="Yahoo!|US.AMEX.STOCK|ESP" LastEvaluationTime="20190910152401000">
      <Alert TimeStamp="20190812000000000" Status="2"/>
      <Alert TimeStamp="20190813000000000" Status="2"

Not sure how it removed or failed to put it in the file.

Tony
Title: Re: XML parsing error
Post by: Sacha on September 12, 2019, 08:39:23 PM
 :o I am surprised. To be honest I cannot think of a reason for this, unless the file is modified by hand outside of Stockalyze. If it happens again please let me know. I will try to find the reason.

Thank you for reporting. I very much appreciate your effort to let me know what you experience.
Title: Re: XML parsing error
Post by: Tony on September 13, 2019, 10:21:08 AM
I have never opened this file except for yesterday to see if that was causing the error since I noticed I had lost the alerts when I displayed the portfolio.

One thing to note, I have had problems with my computer lately, causing me to power down and reboot.

I guess it's possible that I powered down while the file was being written back, if it does write back on closing the program.

Thanks,
Tony
Title: Re: XML parsing error
Post by: Sacha on September 13, 2019, 11:43:03 AM
Quote
One thing to note, I have had problems with my computer lately, causing me to power down and reboot.

I guess it's possible that I powered down while the file was being written back, if it does write back on closing the program.

You nailed it and I was suspecting something like this but it is very low probability. But anyways, I am glad it was because of some very rare scenario of powering off the computer at the "wrong" time. :)