Creation of MSI installation package with one-launcher.exe fails
I'm using the Policy Manager Console on Linux. However, building MSI packages for Windows unfortunately still requires a Windows machine.
According to the Policy Manager manual, the command line looks like:
program\inst\one-launcher.exe --install --prepare_msi_only --msi OneClientCS.msi
Although no MSI package will be created.
The last lines of the logfile are:
2022-09-16 08:34:17.072 [34c8.34bc] I: msi_helpers::prepareMsi4Install: Open Msi DB 2022-09-16 08:34:17.112 [34c8.34bc] *E: wmain: Type: MsiException, Reason: , Function: , File: , Line: 0, Error Code : 110 2022-09-16 08:34:17.112 [34c8.34bc] I: *** LOG AUTO-CLOSED ***
That does not really help me at the moment, though.
The exported JAR file is based on fscs-15.30.3961.jar. The Poicy Manager version is 15.30.96312.
What is the problem?
The problem is solved. In the end it was a misunderstanding. - My mistake.
First I had entered the command as it is written in the documentation. Apparently nothing happened.
Later I changed the parameter
--msi D:\fscs-15.30.3961-test.msi, assuming that it was the output file. This in turn led to the error in the log file.
I missed that
OneClientCS.msialready exists in the
program\instdirectory and is being changed. This is done so fast that it seems like nothing happened.
I expected the built MSI package to be in the current directory or at the specified destination. The mistake: the filename given with the
--msiparameter is not a freely selectable output file, but input and output at the same time.1
Could you please confirm if the following steps have been tried?
1. Export the client installation JAR package from Policy Manager Console for Linux.
2. Move the CS JAR package to Windows host.
3. Extract the content of the JAR archive on a Windows host.
4. Run the following command on Windows host:
• For Client Security: program\inst\one-launcher.exe --install --prepare_msi_only
• For Server Security: program\inst\one-launcher.exe --install --prepare_msi_only
Hi @JUB ,
Error 110 means:
The system cannot open the device or file specified
In your scenario , jar is extracted to 'fscs-15.30.3961-exported' directory correct ?
Would be good to check if fscs-15.30.3961-exported\program\inst\OneClientCS.msi is extracted from the archive, is accessible (i.e. UAC does not prohibit the write access), and one-launcher.exe is executed from the fscs-15.30.3961-exported or fscs-15.30.3961-exported\program\inst\ base directories2