FSDreamTeam forum
Products Support => Los Angeles support FSX/P3D => Topic started by: aal763 on July 14, 2016, 06:21:44 pm
-
Hello, I just bought and installed P3D last night. I also purchased your ORD, IAH, & LAX sceneries. ORD and IAH installed perfectly. However, when I go to install LAX, I get the following:
https://s31.postimg.org/uqdziog17/error1.png (https://s31.postimg.org/uqdziog17/error1.png)
After pressing OK on that, then this pops up:
https://s32.postimg.org/kjnvw8l0l/error2.png (https://s32.postimg.org/kjnvw8l0l/error2.png)
Any ideas on how I can fix this?
Regards,
Rob
-
It seems one of your XML files is corrupted, do as indicated in this post:
http://www.fsdreamteam.com/forum/index.php/topic,12680.msg103947.html#msg103947
-
Alright, here are my dll and exe files in the zipped folder. It appears that the line is at the top.
-
Alright, here are my dll and exe files in the zipped folder. It appears that the line is at the top.
Exactly, the EXE.XML file is clearly corrupted. Your file is like this:
<?xml version="1.0" encoding="windows-1252"?>
<Launch.Addon>
<Name>as_btstrp_config_manager</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp_config_manager.exe</Path>
</Launch.Addon>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
</SimBase.Document>
when it should be like this:
<?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>as_btstrp_config_manager</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp_config_manager.exe</Path>
</Launch.Addon>
</SimBase.Document>
The culprit seem to be the ASN installer, which placed its own lines in the wrong place. That's not the first time we have reports of corruption of the XML file caused by ASN.
-
I made those changes and it works great now! Thank you so much! Just for future error reports if it helps anyone, this was with AS 2016 instead of ASN.