February 13, 20224 yr Hello there, I have come across the problem, that the Sim won't load anymore as soon as FS2Crew is installes. When installing (the A320 FBW addon) I get the error message: Exception EDOMParseError in module fs2crew_fbwa32nx_autostart.exe at 001E2CF6 A name contained an invalid character. Line: 2 <SimBAse.DocumentType="Launch"version="1. After the crash the log in my dosuments folder shows the following: 20220213 16:27:46.452000: MS Store Edition XML file exists -> C:\Users\denni\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml 20220213 16:27:46.452000: MS Disc Edition XML file not found -> C:\Users\denni\AppData\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\EXE.xml 20220213 16:27:46.453000: MS Alpha Edition XML file not found -> C:\Users\denni\AppData\Local\Packages\Microsoft.KHAlpha_8wekyb3d8bbwe\LocalCache\EXE.xml 20220213 16:27:46.453000: Steam Edition XML file not found -> C:\Users\denni\AppData\Roaming\Microsoft Flight Simulator\EXE.xml 20220213 16:27:46.455000: XML Validation Check Passed -> C:\Users\denni\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml 20220213 16:27:46.456000: Removing FS2Crew FBW A32NX entry from this EXE.xml -> C:\Users\denni\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml 20220213 16:27:46.456000: ---------- Begin File Contents (Before) ---------------------------------- <?xml version="1.0"?> <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>S:\Programme\FSUIPC\FSUIPC7.exe</Path><CommandLine>-auto</CommandLine><NewConsole>False</NewConsole></Launch.Addon></SimBase.Document> 20220213 16:27:46.456000: ---------- End File Contents (Before) ------------------------------------ Any help on this? If there's any missing information, just let me know, and I see what I can provide additionally. Cheers!
February 13, 20224 yr Author log_file_autostart.log shows: 20220213 16:27:48.296000: MS Store version file exists - C:\Users\denni\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml 20220213 16:27:48.299000: MS Disc version file not found - C:\Users\denni\AppData\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\EXE.xml 20220213 16:27:48.302000: MS Alpha version file not found - C:\Users\denni\AppData\Local\Packages\Microsoft.KHAlpha_8wekyb3d8bbwe\LocalCache\EXE.xml 20220213 16:27:48.305000: Steam version file not found - C:\Users\denni\AppData\Roaming\Microsoft Flight Simulator\EXE.xml 20220213 16:27:48.307000: XML Validation Check Failed - C:\Users\denni\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml (A name contained an invalid character.) 20220213 16:27:48.310000: Folder does not exist, will not create EXE.xml - C:\Users\denni\AppData\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\ 20220213 16:27:48.312000: Folder does not exist, will not create EXE.xml - C:\Users\denni\AppData\Local\Packages\Microsoft.KHAlpha_8wekyb3d8bbwe\LocalCache\ 20220213 16:27:48.314000: Folder does not exist, will not create EXE.xml - C:\Users\denni\AppData\Roaming\Microsoft Flight Simulator\ log_file_community_folder shows: 20220213 16:27:48.388000: MS Alpha Version user config not found - C:\Users\denni\AppData\Roaming\Local\Packages\Microsoft.KHAlpha_8wekyb3d8bbwe\LocalCache\UserCfg.opt 20220213 16:27:48.394000: MS Disc Version user config not found - C:\Users\denni\AppData\Roaming\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\UserCfg.opt 20220213 16:27:48.397000: Steam Version user config not found - C:\Users\denni\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt 20220213 16:27:48.399000: MS Store version user config exists - C:\Users\denni\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt 20220213 16:27:48.403000: MS Store version packages folder - S:\MSFS 20220213 16:27:48.406000: FS2Crew package source folder found - C:\Program Files (x86)\FS2Crew Command Center\community_folder\fs2crew-cmd-center 20220213 16:27:48.408000: Copy the FS2Crew folder - C:\Program Files (x86)\FS2Crew Command Center\community_folder\fs2crew-cmd-center 20220213 16:27:48.411000: To the Community folder - S:\MSFS\Community 20220213 16:27:48.537000: Copying of package completed successfully! log_file_data_proc.log shows: 20220213 16:27:48.476000: MS Alpha Version user config not found - C:\Users\denni\AppData\Roaming\Local\Packages\Microsoft.KHAlpha_8wekyb3d8bbwe\LocalCache\UserCfg.opt 20220213 16:27:48.477000: MS Disc Version user config not found - C:\Users\denni\AppData\Roaming\Local\Packages\Microsoft.FlightSimDisc_8wekyb3d8bbwe\LocalCache\UserCfg.opt 20220213 16:27:48.477000: Steam Version user config not found - C:\Users\denni\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt 20220213 16:27:48.477000: MS Store version user config exists - C:\Users\denni\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt 20220213 16:27:48.478000: MS Store version packages folder - S:\MSFS 20220213 16:27:48.478000: FS2Crew package source folder found - C:\Program Files (x86)\FS2Crew Command Center\wasm\fs2crew-data-proc 20220213 16:27:48.479000: This package version - 1.0.0 20220213 16:27:48.480000: Installed package version - 1.0.0 20220213 16:27:48.480000: Installed package version already up to date!
February 13, 20224 yr Commercial Member I noticed this in the log: A name contained an invalid character. You probably have some bad text (corruption) in your EXE.xml file. Make a backup of your EXE.xml. Then delete the EXE.xml file. Then re-install FS2Crew for the FBW. Our installer will auto generate a fresh new copy of the EXE.xml. Let us know if that helps. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
February 14, 20224 yr Author Bryan, I can't thank you enough! Worked like a charm! Just for my understanding: Will the EXE.xml remain on the system even if the Sim gets uninstalled? Because I've tried to reinstall the Sim three times yesterday with the same outcome each time. I can only explain this, if the (in my case faulty) EXE.xml stays in the folder no matter how many times you reinstall the sim.
February 14, 20224 yr Author FYI these are the contents of the faulty and the newly generated EXE.xml, I dunno maybe this might help you troubleshooting in the future: Faulty: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.DocumentType="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> Fresh: <?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> <Name>FS2Crew Command Center</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe</Path> <CommandLine></CommandLine> </Launch.Addon> </SimBase.Document>
February 15, 20224 yr Commercial Member Please read this guide: https://roystons.github.io/BetterBravoLights/corrupt-exe-xml.html It's pretty good. Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
February 18, 20224 yr byork I found the root cause of this problem. Every user who have FSUIPC 7 for MSFS installed as auto-start with MSFS have the similar problem. I also get the Application Error popup window with: Exception EDOMParseError in module fs2crew_fbwa32nx_autostart.exe at 001E2CF6 A name contained an invalid character. Line: 2 <SimBAse.DocumentType="Launch"version="1. That is caused by FSUIPC7 not use CR+LF on end of each line. Here is how looks like in Visual Studio Code (my xml editor). I try to format as visible the original EXE.xml after FSUIPC installed 1 <?xml version="1.0" encoding="Windows-1252"?> 2 <SimBase.DocumentType="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>K:\FS2020\Official\FSUIPC7\FSUIPC7.exe</Path><CommandLine>-auto</CommandLine><NewConsole>False</NewConsole></Launch.Addon></SimBase.Document> 3 The 2nd line without any tabulator or CR+LFs on end of the each closed blocks. Mytragina fresh line correct for FS2CREW autostart, but not the FSUIPC7 due those autostart missing from that. Here is my correction. I deleted the EXE.xml recreated with FS2CREW how you wrote above and simple added the FSUIPC Addon part with tabulators and CR+LF end of each line. That is started correctly error free. Here is the screen from my Visual Studio Code in temporary format mode: 1 <?xml version="1.0" encoding="Windows-1252"?> 2 <SimBase.Document Type="Launch" version="1,0"> 3 <Descr>Launch</Descr> 4 <Filename>exe.xml</Filename> 5 <Disabled>False</Disabled> 6 <Launch.ManualLoad>False</Launch.ManualLoad> 7 <Launch.Addon> 8 <Name>FS2Crew Command Center</Name> 9 <Disabled>False</Disabled> 10 <Path>C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe</Path> 11 <CommandLine></CommandLine> 12 </Launch.Addon> 13 <Launch.Addon> 14 <Disabled>False</Disabled> 15 <ManualLoad>False</ManualLoad> 16 <Name>FSUIPC7</Name> 17 <Path>K:\FS2020\Official\FSUIPC7\FSUIPC7.exe</Path> 18 <CommandLine>-auto</CommandLine> 19 <NewConsole>False</NewConsole> 20 </Launch.Addon> 21 </SimBase.Document> And in plain text for Ctrl-C/V <?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> <Name>FS2Crew Command Center</Name> <Disabled>False</Disabled> <Path>C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe</Path> <CommandLine></CommandLine> </Launch.Addon> <Launch.Addon> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Name>FSUIPC7</Name> <Path>K:\FS2020\Official\FSUIPC7\FSUIPC7.exe</Path> <CommandLine>-auto</CommandLine> <NewConsole>False</NewConsole> </Launch.Addon> </SimBase.Document> At MSFS boot time when the bottom blue progress bar somewhere in middle the the screen change for black (just the blue progress bar visible) that is when FS2CREW loads and I get the FSUIPC7 popup window. You can test and reproducer it easily just download FSUIPC7 for MSFS before install FS2CREW http://www.fsuipc.com/ Edited February 18, 20224 yr by J737NGX
February 18, 20224 yr Commercial Member Can you please pass this info to the FSUIPC programmer. Thanks, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
February 19, 20224 yr I will try. Just please add notes about it into your Quick Troubleshooting.txt also temporary meanwhile for new users
February 19, 20224 yr Commercial Member I just updated the FAQs thread. I'm sure Mr Dowson will fix the issue shortly. Let's also hope Asobo offers us a better way of auto starting programs rather than having to use XML files 🙂 B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
March 25, 20224 yr This issue just cost me 3 days and several hundreds of GB's of reinstalling. I actually ended up reinstalled Windows 11 due to fudging up my troubleshooting of this problem. But the fix was painless and quick, once I found this thread! Sticky this! Take-offs are optional, landings are mandatory.The only time you have too much fuel is when you're on fire. To make a small fortune in aviation you must start with a large fortune.There's nothing less important than the runway behind you and the altitude above you. It's better to be on the ground wishing you were in the air, than in the air wishing you were on the ground.
March 25, 20224 yr Commercial Member If the crash happens when MSFS starts loading, it's likely you have corruption on your EXE.xml file. The EXE.xml file controls which programs autostart when MSFS loads. Should there be an invalid character on your EXE.xml file, things will not load properly. Please do this: 1. Make a backup copy of your EXE.xml 2. Delete your EXE.xml file. 3. Re-install FS2Crew. FS2Crew will create a fresh, new EXE.xml file that we know is perfect. Your EXE.xml file is located here: MS Store Version: YOUR USER NAME -> AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\exe.xml Steam Version YOUR USER NAME ->AppData/Roaming/Microsoft Flight Simulator Edited March 25, 20224 yr by byork B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
Archived
This topic is now archived and is closed to further replies.