[solved] Can't install FSP P3D in P3d v3.1

[ReinBijlsma]

I just made a clean P3D v3.1 install, with the latest version. 
Now the next thing I tried to install is the latest version of FSP for P3D as administrator in Windows 10.1 64b.  Halfway the installation I get this error popping up: 

File=DLL, Operation=Add, Title=FSPassengersP3D,
Path=C:\Users\Public\documents\FsPassengersP3D\Bin\FsPassengersP3D.dll
DLL XML document could not be read

Logfile: 
-FsPassengers setup ver. Jan 23 2016 started: 29.02.2016 - 15:52


-Search if Prepar3D is running
-OK Prepar3D is not running
-Attempting to find Prepar3D directory.
-Checking 64 byte registry for Prepar3D v2.5
-ERROR while reading 64 byte Prepar3D v2's registry
-Checking 64 byte registry for Prepar3D v3 edition
-64 byte registry not found, checking 32 byte registry for Prepar3D v3 edition
-Prepar3D v3 edition Directory found: G:\Prepar3D\
-Checking Prepar3D path, searching this file: G:\Prepar3D\Effects\Effects.cfg
-Prepar3D found ok
-Detecting OS and FsPassengers install path...
-Windows 10: 10.0
-FsPassengers will be installed in: C:\Users\Public\Documents\FsPassengersP3D
-Getting Prepar3D version
-Prepar3D version returned:  3.1.2.15831
-Prepar3D version OK
-Check free space
-Free space Total Mb available: 6178
-Check needed space
-Needed space: 153
-No previous version of FsP3D 2015 detected.
-AppCompatFlags checked OK
-Start of file copy...
-Extracting file to: C:\Users\Public\Documents\FsPassengersP3D
-Ok: all files extracted correctly
-Attempting to find dll.xml file
-Getting Prepar3D.exe version
-Prepar3D.exe version: 3.1.2
-Executing Prepar3D.exe to write in the DLL.XML
-Attempting to write Config file 'FsPassengersP3D\bin\Prepar3DPath.cfg'
-Config file 'FsPassengersP3D\bin\Prepar3DPath.cfg' written ok
-Creating shortcut in start menu...
-Attempting to write uninstall information in 'bin\uninstallpath.cfg'
-Number of files not replaced by update (to keep user's modification): 0
-Writting FsPassengers's windows in missionpanel.cfg
-missionpanel.cfg - ok
-Adding uninstall key to registry
-Uninstall key added to registry
-Writting Path to effects
-Executing Prepar3D.exe to write new path
-Writting wav path to effects files
-Writting wav path to effects files completed.
-Checking if simconnect and all library are installed
-FsPassengersP3D.dll loaded fine - simconnect and library ok
-Install completed with success
-Writting this log in FsPassengers folder...

There is no FS Passengers entry in the modules folder when I start P3D

How can i solve this problem?

[DanSteph]

The install wasn't probably so clean.
It miss you probably the dll.xml located in "C:\ProgramData\Lockheed Martin\Prepar3D v3"
Check that you have such folder and file and let me know.

Kind regards

Dan

[ReinBijlsma]

The install wasn't probably so clean.
It miss you probably the dll.xml located in "C:\ProgramData\Lockheed Martin\Prepar3D v3"
Check that you have such folder and file and let me know.

Kind regards

Dan

Hi Dan, thxs for the quick reply. The folder and file are there. There's not much in it, only this: <?xml version="1.0" encoding="Windows-1252"?> 

There also a DDL located here: C:\Users\Rein\AppData\Roaming\Lockheed Martin\Prepar3D v3, with the following contents:

<?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>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
</SimBase.Document>

[DanSteph]

I don't know why Prepar3D.exe fail to write into it's own file, it's the first time I hear this problem so it might be very specific.
What you can do is to add manually FsPassengers to your dll.xml.

Replace the content of the second file with this one:

Code:

<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
   <Name>FSUIPC 4</Name>
   <Disabled>False</Disabled>
   <Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
   <Name>FsPassengersP3D</Name>
   <Path>C:\Users\Public\Documents\FsPassengersP3D\Bin\FsPassengersP3D.dll</Path>
</Launch.Addon>
</SimBase.Document>

(Given FsPassengers is in it's legal location C:\Users\Public\Documents\FsPassengersP3D )

[ReinBijlsma]

I don't know why Prepar3D.exe fail to write into it's own file, it's the first time I hear this problem so it might be very specific.
What you can do is to add manually FsPassengers to your dll.xml.

Replace the content of the second file with this one:

Code:

<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
   <Name>FSUIPC 4</Name>
   <Disabled>False</Disabled>
   <Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
   <Name>FsPassengersP3D</Name>
   <Path>C:\Users\Public\Documents\FsPassengersP3D\Bin\FsPassengersP3D.dll</Path>
</Launch.Addon>
</SimBase.Document>

(Given FsPassengers is in it's legal location C:\Users\Public\Documents\FsPassengersP3D )

That did the trick! I added the FSPassengers entry to the second one. Still wondering why P3D can't write to the first file. Anyway, I'll make a backup of the dll.xml file as well in case something goes wrong in the future.