msi log and unlike the PDT log where there is only a 1603 error there are a couple of lines associated and none of them seem to provide further detail Here is some further contecxt:ĬustomAction installexe returned actual error code 61013 (note this may not be 100% accurate if translation happened inside sandbox)Įrror 1722. The 1722 error comes directly out of the. If anyone can provide insight I would really appreciate it. It would be nice if there was simply some consistency and predictability within these version. I am just getting fed up with the mess that is Java. I am also able to completely uninstall all previous versions of Java using the Remove-MSIApplications PDT commandlet (which also works fine if I manually install 1.8 u 31 before running the PDT process I am not using config files as I have never had the need toīefore (passing the switches always worked until now). however it doesn't seem to come to a definitive conclusion as to what could be done. I have never had an issue where a command line that works when run manually under and admin context won't work when run through Powershell. com installer using just the "/s SPONSORS=0" arguments and that works just fine too when When manually run the install completes just fine without complaint so I know the switches are correct and are fully functional. Msiexec.exe /I "jre1.8.0_31.msi" JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1 /q JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1 /q"
The command line that I am using to install Java is being passed through Powershell Deployment Toolkit as:Įxecute-MSI -Action install -Path "jre1.8.0_31.msi" -Parameters "JU=0 The installer creates the installation directory and copies the files but the installation ultimately fails with the generic 1603 error. Location: C:\Windows\Installer\MSI79FF.tmp, command: /s INSTALLDIR="C:\Program Files (x86)\Java\jre1.8.0_31\\" WEB_JAVA=1 REPAIRMODE=0 Contact your support personnel or package vendor. A program run as part of the setup did not finish as expected. There is a problem with this Windows Installer package.
MSI (s) (50:CC) : Product: Java 8 Update 31 - Error 1722. I getting an installation error as follows with the 32-bit installation:
In the testing process prior to actually deploying the software. While this is an SCCM-centric question I am still I am currently attempting to deploy Java 1.8 update 31 and am having little luck. It seems like I have to re-invent my SCCM Java deployment process each and every time Oracle comes out with a new update.
0 kommentar(er)
