This assumes the data in the ISS is valid for the installation and does not change if the setup is run under different user environments. The other possibility is this setup is authored to do something that does not work while running under the SYSTEM account.įor the ISS file, the path passed should be using C:\Windows\System32 as the setup.exe is 32-bit, so it will automatically be redirected to the 32-bit System32 (SysWOW64) folder. One, the path to the ISS file is invalid or inaccessible from the installation, causing the -3 result code (or it doesn't contain valid data for the installation it is passed to). There are a couple of basic possibilities. It is difficult to determine what the cause of this behavior is without knowing how the setup was authored. The error is reproduced: again only from command run as SYSTEM the install fail with error above. ![]() I have checked the extracted command line used for installation in cmd.exe window, launched from my adm* account and from system account (I started it using "psexec -i -s cmd.exe" command). In my case file is correct and, as I previouslr written, install script reads it without problem when launched from administrative account, but not from SYSTEM account (used by SCCM). The script installs the software fine when running from my administrative account however when I run it from SCCM client it will fail, dropping in setup.log in source directory:Īs I already figured out in the forum it is relatively common error and possibly related to problem reading *.iss file. I have developed a script to install IDM UltraEdit v17 powershell is used for this. I script for MS SCCM software distribution. Hi, I am one of the scripters in my company.
0 Comments
Leave a Reply. |