**EDIT:RESOLVED - SYSTEM HANG -- Saving Database...

[bsteed]

For some reason, my XL2 (PRECALRAD) program hangs, after I click refresh/update database. After an hour of "waiting it out", I click "Close". Everything looks normal, then I click "refresh/update" again, and my database is wiped out. I panic, and restart XL, it remains gone and I get this error message:

When I restart XL, I get this xlobby prompt error message:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Xml.XmlException: Root element is missing.
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 xlobby2.CategoryObject.RootFromXML(String file, String name, Control control)
at xlobby2.Control.LoadDatabasesFrom(String dir)
at xlobby2.Control.LoadDatabases()
at xlobby2.Control.LoadAll()
at xlobby2.GdiScreenForm.GdiScreenForm_Shown(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnShown(EventArgs e)
at System.Windows.Forms.Form.CallShownEvent()
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
xlobby2
Assembly Version: 1.0.2613.31320
Win32 Version: 1.0.2613.31320
CodeBase: file:///C:/xlobby/xlobby2.exe
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
XPluginSDK
Assembly Version: 1.0.2612.4380
Win32 Version: 1.0.2612.4380
CodeBase: file:///C:/xlobby/XPluginSDK.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
CDEX
Assembly Version: 1.0.1685.4787
Win32 Version: 1.0.1685.4787
CodeBase: file:///C:/xlobby/plugins/CDEX.dll
----------------------------------------
xusbuirt
Assembly Version: 1.0.1767.29466
Win32 Version: 1.0.1767.29466
CodeBase: file:///C:/xlobby/plugins/xusbuirt.dll
----------------------------------------
XWeather
Assembly Version: 1.0.2797.31302
Win32 Version: 1.0.2797.31302
CodeBase: file:///C:/xlobby/plugins/xweather/XWeather.dll
----------------------------------------
Interop.Shell32
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/xlobby/Interop.Shell32.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Thank God I had backed it up previously.

I was editing my XML file (via Notepad++), and removing certain aspects of tags that I didn't want (E.G. the text after R, PG, PG-13 -- I limited everything to 1 genre selection, and cut all the BS out of the runtimes). I did all this only to add to the cleanliness of my new skin after I had spidered all the information.

I know I haven't damaged the XML structure, and just to assure myself, I checked over it twice (line by line, took me like 7 hours). Not to metion, if the syntax was damaged, it wouldn't allow me to open XL after resaving the file. After a fresh save from backup, the program starts fine, and all my data is there.

[bsteed]

Weird, but after looking over my XML file a 3rd time (determined not to revert to previous file and re-edit all over again), I realized a character was outside of an xml tag. I use a Logitech gaming keyboard, with a set of gaming keys to the left, close to where my SHIFT and CTRL keys are on the left. One of them types a "6". It stuck me and held me up for almost two days.

LESSON LEARNED: BE VERY CAREFUL WHEN MANUALLY EDITING YOUR XMD DB FILES. ONE SIMPLE MISTYPE AND BE DISASTEROUS.

[S Pittaway]

another really good leason... always make copies of the xml files

[lar282]

I agree, one should back them up. here's the script I use everyday from scheduled task
I then get a backup everyday in sep directories so I have all 7 of them.

On Error Resume Next
Dim objNET : Set objNET = CreateObject("Wscript.Network")
Dim objHOST : Set objHOST = CreateObject("WScript.Shell")
Dim objFILE : Set objFILE = CreateObject("Scripting.Filesystemobject")
Dim dayofweek


dayofweek=(Weekday(Date))
'MsgBox dayofweek
'MsgBox """" & "c:\program files\xlobby\databases\movies.xml" & """"
'MsgBox "S:\XL_DBS\" & dayofweek & "\" & "movies.xml"
'WScript.Quit


objFILE.CopyFile "c:\program files\xlobby\databases\movies.xml", "S:\XL_DBS\" & dayofweek & "\" & "movies.xml" ,True

objFILE.CopyFile "c:\program files\xlobby\databases\movies2.xml" , "S:\XL_DBS\" & dayofweek & "\" & "movies2.xml" ,True

objFILE.CopyFile "c:\program files\xlobby\databases\pictures.xml" , "S:\XL_DBS\" & dayofweek & "\" & "pictures.xml" ,True

objFILE.CopyFile "c:\program files\xlobby\databases\music.xml" , "S:\XL_DBS\" & dayofweek & "\" & "music.xml" ,True

WScript.Quit

[bsteed]

Oo! SAVED, and thank you for sharing. I am going to look into doing this myself. Thanks!!!