StrataFrame Forum

XmlException-Root element is missing

http://forum.strataframe.net/Topic10904.aspx

By Keith Chisarik - 8/16/2007

I am getting this at a customer site on a program that has been running without any changes to the program or environment for months, any idea where to start on this one?

XmlException
 Root element is missing.

Source     : System.Xml

Stack Trace:
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlTextReaderImpl.Read()
   at System.Xml.XmlTextReader.Read()
   at System.Xml.XmlReader.MoveToContent()
   at System.Data.DataSet.ReadXml(XmlReader reader, XmlReadMode mode, Boolean denyResolving)
   at System.Data.DataSet.ReadXml(String fileName, XmlReadMode mode)
   at MicroFour.StrataFrame.Xml.XmlBasics.OpenXmlFile(String CurrentVersion, String TableName, String PathAndFileName, List`1 ColumnStructure)
   at MicroFour.StrataFrame.Xml.XmlBasics.OpenXmlFile(String Version, String TableName, String PathAndFileName, List`1 ColumnStructure, Boolean DecryptFile)
   at MicroFour.StrataFrame.Data.BusinessObjects.DbeApplicationData.FillAll()
   at MicroFour.StrataFrame.Data.ConnectionManager.SetConnections()
   at bayshore_scan.AppMain.SetDataSources()
   at MicroFour.StrataFrame.Application.StrataFrameApplication.Raise_SetDataSources()
   at MicroFour.StrataFrame.Application.StrataFrameApplication.RunApplication()
   at bayshore_scan.AppMain.Main()

By Trent L. Taylor - 8/16/2007

Yeah, they corrupted the connection.dat files on their local machine.  We changed the 1.6.1 version to not do in place file conversions, but to correct the issue just remove the connections.dat and the appkeys.dat files on their local machine then go back in.  You will have to re-setup the connection string but you should be good after that.
By Keith Chisarik - 8/16/2007

Awesome I will try first thing in the AM.
By Keith Chisarik - 8/17/2007

This worked like a harm. You say this was a known issue that has already been fixed?



So I can file it in the back of my mind for existing 1.5-1.6.0 installs and forget about it for anything more recent?



Thank you once again for the fast reply, my customer was very happy with the turnaround of less than 1/2 a day, which in the end is what matters to us all Smile
By Keith Chisarik - 8/17/2007

Worked like a charm, that is.
By Trent L. Taylor - 8/17/2007

This worked like a harm. You say this was a known issue that has already been fixed?

Yeah.  We changed the XMLBasics class to no longer do an in-place conversion for any encrypted file.  You generally only run into something like this when they try to execute the program twice in a row on a slower machine or something of that nature.  We changed this so that you can click it a thousand times and not have the issue because it creates a temp file or opens the file in memory so that there is never an issue with the file being decrypted twice.  At any rate, it is fixed. Smile

So I can file it in the back of my mind for existing 1.5-1.6.0 installs and forget about it for anything more recent?

Correct.

Thank you once again for the fast reply, my customer was very happy with the turnaround of less than 1/2 a day, which in the end is what matters to us all

Hey, I totally know what it is like to deal with something in the field when an end-user is trying to use your software and they are having a problem....so I have total compasion, brother Smile  Glad to help Smile