Error loading exe xml file

[TobiasM]

Hi,

I'm having serious problems re-installing FSUIPC. I'm running the Steam-Version of MSFS 2020. I was using the FSRadioPanel-App on my tablet - https://play.google.com/store/apps/details?id=com.tambucho.fsradiopanel&hl=de&gl=US)

Unfortunately the app doesn't work every time - sometimes I have to reboot my PC to get it to work. Since there were no known bugs like this, I tried to update the FSUIPC to the newest version. I started the installer, which told me, that it needs to remove the old version, and so I agreed. The old version was deleted then. When I reopened the installer, it would lead me through the installation process, but as soon as the copying of the new files starts, within the copying window the message "Error loading exe xml file" appears and the window closes itself. The only remains of the installation process are the folder C:\FSUIPC7 containing the FSUIPC7.exe, nothing more.

Then I tried to reinstall the old version I was using since then, but also that failed due to the same error. Can you help me out?

 

Thanks in advance!

 

Best regards, Tobias

[TobiasM]

Just found

 

Haven't found it before opening this thread, sorry!

[John Dowson]

No problem. As you have a steam install, could you attach your current EXE.xml file please - this will be what is causing the issue, but I don't know why (if still available). If I can duplicate here with you EXE.xml I can update the installer to handle this more gracefully. Thanks.

[TobiasM]

Hi John,

 

this was the old EXE.xml file (I renamed it by myself) which was causing the trouble. My bugfix was: Only renaming it and FSUIPC-installer created a new one and everything was fine.

EXEold.xml

[John Dowson]

Ok, thanks. Thats quite a screwed-up ini!
It looks like it was also updated to start a plugin from Logitech (for saitek panels). If you want that to run automatically, you can add back in the  <Launch.Addon> section for that. Make sure its within the SimBase.Document element.

 

[TobiasM]

Funny thing: here's my new EXE.xml... and it also contains the Logitech-thing (which I do use), even though I haven't added it after creating the new EXE.xml or even reinstalled the Logitech driver. Something must have added it without telling me. Perhaps a daemon from Logitech is monitoring the file and adding the missing lines again when deleted?

EXE.xml

[spokes2112]

One of the the 2 installers/dameon is providing its own closing </SimBase.Document> closing tag which is part of the "root" document - not good.
The file will not parse, therefore not load due to the error.
Mistake shown shaded below. 
 
This should work by either removing the highlighted selection above from your own file or,
Copy the complete code below and replace all the code in your file with this, save it.

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
	<Descr>Launch</Descr>
	<Filename>EXE.xml</Filename>
	<Disabled>False</Disabled>
	<Launch.ManualLoad>False</Launch.ManualLoad>
	<Launch.Addon>
		<Disabled>False</Disabled>
		<ManualLoad>False</ManualLoad>
		<Name>FSUIPC7</Name>
		<Path>C:\FSUIPC7\FSUIPC7.exe</Path>
		<CommandLine>-auto</CommandLine>
		<NewConsole>False</NewConsole>
	</Launch.Addon>
	<Launch.Addon>
		<Name>Logitech Microsoft Flight Simulator Plugin Steam</Name>
		<Disabled>False</Disabled>
		<Path>C:\Program Files\Logitech\Microsoft Flight Simulator Plugin\LogiMicrosoftFlightSimulator.exe</Path>
		<CommandLine>-r</CommandLine>
	</Launch.Addon>
</SimBase.Document>

 

[TobiasM]

Thanks! I'll try it tonight...

[John Dowson]

1 hour ago, spokes2112 said:

One of the the 2 installers/dameon is providing its own closing </SimBase.Document> closing tag which is part of the "root" document - not good.

The FSUIPC 7 installer only creates the <SimBase.Document>..</SimBase.Document> element if there is no EXE.xml and it crates a new one. Otherwise it will just add a <Launch.Addon> element.

1 hour ago, spokes2112 said:

Mistake shown shaded below. 

The original EXEold.xml is completely screwed-up - two Simbase.Document elements (for FSUIPC), the logitech launch.addon element outside of a Simbase.Document element, and the extra closing simbase.document element. The newer one you posted is nearly as bad, but with just one Simbase.Document.
Ramon's suggested change will work, but I would like to understand how your EXE.xml is getting in such of a mess....check its not being changed again after you update and run MSFS.
 

 

[spokes2112]

Completely agree with you John, in fact I can almost bet 100% that the Logitech installer is using text string based logic rather than using the XML DOM & imports to their program such as system.xml to do the work. ( the tab spacing seems to give it away )

4 hours ago, John Dowson said:

If I can duplicate here with you EXE.xml I can update the installer to handle this more gracefully.

An idea for "gracefulness" when improper <Launch.Addon> additions are made by a program that is not doing it properly IE using text strings to figure it out.  
Use line breaks in key locations.. This should help when a text string based program is trying to add to what you already have. XML doesn't care about whitespaces whereas text string based logic does.

Old :

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0"><Descr>Launch</Descr><Filename>EXE.xml</Filename><Disabled>False</Disabled><Launch.ManualLoad>False</Launch.ManualLoad><Launch.Addon><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Name>FSUIPC7</Name><Path>C:\FSUIPC7\FSUIPC7.exe</Path><CommandLine>-auto</CommandLine><NewConsole>False</NewConsole></Launch.Addon></SimBase.Document>

New:

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0"><Descr>Launch</Descr><Filename>EXE.xml</Filename><Disabled>False</Disabled><Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Disabled>False</Disabled><ManualLoad>False</ManualLoad><Name>FSUIPC7</Name><Path>C:\FSUIPC7\FSUIPC7.exe</Path><CommandLine>-auto</CommandLine><NewConsole>False</NewConsole>
</Launch.Addon>
</SimBase.Document>

Just an idea....

[John Dowson]

Hi Ramon,

the xml created by the latest FSUIPC6 & 7 installers do create the xml without spacing or line breaks. Unfortunately I can't get around this at the moment with the tool I am using (its a NSIS xml plugin). I have been meaning to write my own plugin to get around this, but as its very low priority I haven't had time to look into this, and probably won't for quite a while!
I could, however, verify the integrity of any existing EXE.xml file before updating. I'll look into this when I get a chance.
But I think for the time being I will create a FAQ entry for EXE.xml problems as its seems to be a relatively common problem.

Regards,

John

[TobiasM]

Thanks guys for your help, I really appreciated it. Now everything seems to work fine! Although I now have a problem with the app I'm using FSUIPC for *sigh* The developer seems to be unreachable atm 😞 But you don't need to worry about that...