[Bug]: Silent Install with Enterprise Deployment (SCCM) Fails #3067
Description
JASP Version
0.19.1
Commit ID
No response
JASP Module
Unrelated
What analysis are you seeing the problem on?
No response
What OS are you seeing the problem on?
Windows 10
Bug Description
I'm attempting to deploy JASP via Microsoft's System Center Configuration Manager. I've packaged the installer, but the install fails when imaging a computer (Automated process of erasing the disk, installing windows, installing apps, etc.)
The application installs via the command line:
msiexec /i "JASP-0.19.1.0-Windows.msi" /qn /norestart /L*V "C:\Windows\Temp\JASP_Install.log"
However, when installing during imaging, it hangs. The log file from SCCM indicates the install took too long and timed out:
Exceeded timeout of 120 minutes while waiting for process 5244 to finish. AppEnforce 12/5/2024 12:59:14 PM 2240 (0x08C0)
The MSI log produced by the installer gets to this line, then stops (followed by the hard failure at the 2 hour timeout mark):
MSI (s) (14:04) [11:00:43:799]: Executing op: CustomActionSchedule(Action=FixModulesJunctions,ActionType=3106,Source=C:\Program Files (x86)\JASP,Target=C:\Program Files (x86)\JASP\JASP.exe --junctions,)
I can provide the full installation log file via email if needed.
Expected Behaviour
The install should complete successfully, even when running in this automation.
Steps to Reproduce
I've reproduced this by packaging the application install two different times in SCCM. Both application packages resulted in this issue.
I don't know that you could reproduce this without having access to an SCCM environment.
Log (if any)
No response
More Debug Information
No response
Final Checklist
- I have included a screenshot showcasing the issue, if possible.
- I have included a JASP file (zipped) or data file that causes the crash/bug, if applicable.
- I have accurately described the bug, and steps to reproduce it.