Unattended Installation fails without logging a reason


Trying to install as unattended using records of previous sessions in the terminal.
Always get the same error:
{{[ Starting automated installation ]
[ Automated installation FAILED! ]}}

I was playing with the debug logs and I can trace the logs until the checks. The last messages that I get are these:
{{2020.02.05 09:41:14 FINE: Version comparison: 11.0.3 GREATEREQUAL 1.8 (flags: 1)
2020.02.05 09:41:14 FINER: Effective number of version parts: 2
2020.02.05 09:41:14 FINER: Compare version parts: 11 <-> 1
2020.02.05 09:41:14 FINER: Raw version comparison result: 1
2020.02.05 09:41:14 FINE: 11.0.3 geq 1.8: true
2020.02.05 09:41:14 FINE: Created lock file:C:\Users\NIETOR~1\AppData\Local\Temp\2\iz-CodeProfiler for ABAP.tmp}}

I was checking the code and the last log entry comes from the lockChecker.check() and seems to be OK.
After this comes the expiredChecker.check() but no messages related seems to be also OK (it could be nice a messages telling this)
After this. it comes installerRequirementChecker.check(). In the code I see a possibility of fail without message:

In case the !condition.isTrue() and the message == null, the installation will exist without saying that the reason was an installer requirement nor which one.

I am upgrading from Izpack 4.3.3 and the AutomatedInstallation file generated is identical. In the 4.3.3 the unattended installation works and in 5.1.3 doesn't. The installation with 5.1.3 using the GUI works perfectly.

Please let me know if I can provide more information to help with this issue.


Windows 10, Windows Server 2012


René Krell
February 5, 2020, 11:27 AM

Did you regenerate the auto-install.xml with the IzPack 5 installer? If not, please do it and use the new XML file as parameter.

Hugo Nieto Rey
February 5, 2020, 12:53 PM

Hi René,

thank for your message. Yes, I have the FinishPanel in my install.xml file, so I generate it everytime and I use this auto-install.xml file generated with IzPack 5 to make the test and then it fails.

Hugo Nieto Rey
February 12, 2020, 8:00 AM

Hi again,

you were right. The application didn’t take the right generated auto-install.xml file but an older one. Thanks for your help.

The ticket can be closed.

I’ll close the ticket




Hugo Nieto Rey




Affects versions