FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: aroberts12 on October 17, 2015, 08:56:31 pm
-
Hello
When I try to install GSX or Addon Manager for v3 of P3D I get an error pop up saying "Runtime Error (at 135:1909) NIL interface exception"
In the background of the installer I can see it says "Adding Couatl section to the DLL.xml" not sure if this has anything to do with the error
I am using the latest installers and picks up my P3D V3 directory
Any help is appreciated
Thanks!
-
We found the problem, and it was due to your DLL.XML or EXE.XML missing this line:
<Launch.ManualLoad>False</Launch.ManualLoad>
This line can be True or False, but it's usually present. If you add it to your DLL.XML and/or EXE.XML, the installer will continue with no errors.
The top part of the EXE.XML file should look 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>
The top part of the DLL.XML file should look like this:
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
Then, you see the various <Launch.Addon> sections for each module you have installed.
The XML files are located at:
%APPDATA%\Microsoft\FSX ( FSX or FSX:SE if you installed FSX Steam edition without having FSX already installed )
%APPDATA%\Microsoft\FSX-SE ( FSX or FSX:SE if you installed FSX Steam edition alongside FSX )
%APPDATA%\Lockheed Martin\Prepar3d
%APPDATA%\Lockheed Martin\Prepar3d V2
%APPDATA%\Lockheed Martin\Prepar3d V3
If you use P3D, depending on your version
Be sure you use a pure text editor to edit the files (Notepad it's fine), and check both the DLL.XML and the EXE.XML files. We are also updating all the installer to handle this case, but there's no need to download them again, if you just fix the XML files this way.
-
Thanks Umberto,
for tracking this issue. This line was indeed missing in my exe.xml file.
Kind regards, Michael
-
Good day.
I have the same problem, so I have tried to do what you say but it doesn`t work it is the 148 runtime error and after that appears: list of index bounds. And after that two errors the addon manager installation doesn`t continue!
Thanks, Joan.
-
I have the same problem, so I have tried to do what you say but it doesn`t work it is the 148 runtime error and after that appears: list of index bounds. And after that two errors the addon manager installation doesn`t continue!
Your error is not exactly the same as the one reported here, but it's clearly a problem with your XML files. If you could post them here, I can tell you where they are corrupted.
Do not post the lines. ZIP both files together, and use the Attach function of the message (click "Additional Options...") to Attach them to your post.
The files are located here:
%APPDATA%\Microsoft\FSX\DLL.XML
%APPDATA%\Microsoft\FSX\EXE.XML
-
I think that you want to see this two files.
-
I think that you want to see this two files.
I'm not seeing any files. I'm seeing a "screenshot" of your screen, which is not helpful at all, since as you can see, the 2nd file is larger than the screenshot, so it's not possible to see the whole file.
Which is why, I posted clear instruction how to ATTACH a file to a message, that I'll repeat here:
Do not post the lines. ZIP both files together, and use the Attach function of the message (click "Additional Options...") to Attach them to your post.
-
I`m spanish, not from America or United Kingdom, sorry.
-
I had a look at your files and yes, of course, one of them was corrupted. It included a "BOM" (Byte Order Mark) which should normally used only by files encoded in UTF-8. But the XML header said the file used a Windows Latin1 encoding, which is the default. So, basically, the XML "lied" about itself, since the header didn't match the encoding.
This can usually caused by:
1) A bugged installer of another product. We had reports that ASN installer mistakenly changed the encoding in UTF-8 without changing the header accordingly. But it was fixed in later version, maybe your version is not up to date.
OR
2) Editing the file manually with a text editor that changed the encoding when saving.
In any case, I fixed the files, which should now work.
-
Thank you so much, i will try to replace it in 30min and I will notify you!
-
The installation works and the problem doesn`t appear, but unfortunately i upload the p3d client to 3.3.5 and the control panel(shift+f12+ctrl) still not appearing so I think that I will have to reinstall all p3d.
Thanks a lot!
-
The installation works and the problem doesn`t appear
That was to be expected, since the problem was your corrupted XML file.
but unfortunately i upload the p3d client to 3.3.5 and the control panel(shift+f12+ctrl) still not appearing so I think that I will have to reinstall all p3d.π
That's another entirely different issue, which also doesn't have anything to do with GSX or any of our products, and it's more like a P3D installation bug that will affect any 3rd party application with a menu: since LM forgot to update some files in the "Client" installer, no application with a menu will work unless you install the P3D "Content" or the Full installer.
There's no need to reinstall the sim, just download the Content.
-
Okey, i will do it, thanks!
-
You are the best! jeje i upload my content and all works okay! perfect job!!
-
Good afternoon,
I have the same problem as roigjoan. Would you be so kind and be able to fix my dll.xml and exe.xml from my C:\ProgramData\Lockheed Martin\Prepar3D v3 ?
Or would you give me the tip how to do that?
Thank you very much for your time.
Laci
-
I have the same problem as roigjoan. Would you be so kind and be able to fix my dll.xml and exe.xml from my C:\ProgramData\Lockheed Martin\Prepar3D v3 ?
No, you don't have the same problem. Your XML files are perfectly fine.
If you HAVE the GSX menu under the "Addons" menu, it means GSX is clearly working, and you are affected by the very well known bug of the missing Simconnect menu in P3D 3.x updates, which will be fixed by installing the P3D "Content", which is exactly how roigjoan fixed it, once he fixed his *other* previous problem with corrupted XML files.
-
Thank you for answer, however the problem is still pending. I updated p3d content. I attached problem message.
I don t understand it because until todaz it worked all good and today in p3d i clicked to update GSX and it crashed with error and when i downloaded Standalone manager it is still like on the picture.
Thank you for answer.
-
Thank you for answer, however the problem is still pending. I updated p3d content. I attached problem message.
Then you have a problem with the OTHER DLL/EXE.XML file, not the one you posted, but the one under %APPDATA%
The new location suggested for P3D V3 is %PROGRAMDATA%, and all our installers now use this one but, they will also check the files under %APPDATA%, to be sure you don't have lines from a previous version still there.
So, the corrupted XML files are probably the ones under %APPDATA%. Just to make it more clear: the problem doesn't have anything to do with any of our products, our installers are only indicating a clear error condition caused by other bugged installers (or having edited the file by hand), but they won't dare touching them if they are already corrupted!
-
I hav uploaded EXE and DLL from APPDATA. May I ask u please to check them as well if they are ok?
-
As I suspected, your EXE.XML is corrupted, missing the closing tag. Find the fixed file attached.
-
You ve got it ;) Thank you so much now everything is perfect :)