After i create a single setup.exe package with a silent install, the sms installation is failing. I can install it manually all day long but as soon as the sms group sends it out it fails with a Error code 1619. Is there a simple switch im missing?


0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



1619 is kind of a generic error (Thanks Microsoft).  Most times I've seen it's a permission issue with either the account trying to run it or folder permission from SCCM.  Is this a custom exe or a vendor app?  I am wondering... If its a vendor app the setup.exe could be extracting an MSI to a temp location and then SCCM service account doesn't have access.

Does event viewer show anything detailed?

Answered 05/15/2013 by: bretthexum
Yellow Belt

  • it is a custum setup.exe that i created with a msi, it has a no interface, with a corporate logo splashscreen and thats it really.the event viewer only says installation failed with that 1619 error code
  • Use the MSI if possible and get rid of the wrappper. SCCM chats better with MSI for logging and stuff.

    use the cmd line similar to the below.
    msiexec /i blah.msi /qn /l*vx %systemroot%\Temp\Blah.log
  • i cant get rid of the wrapper, its the company standard that everything has to be in a setup.exe. its just the way it is. so can i infer the string would be setup.exe %systemroot%\temp. this would put the package in c:\temp and run it from there. is there a switch to run as admin?
    • If you are using SCCM it should be running as the service account you setup with SCCM. As long as that service account is a local admin on the machines that should be a good test.
  • I will give it a shot, thank you so much for your help.
  • I've gotten this error before. What happened to me was the msi location in the script was different from it's actual location therefor the script couldn't locate the msi upon install. Check if the name of the msi in the script matches the actual name. If this is an upgraded or new version of software then it's possible there is name changes. Another possible reason for this error may be that when you sourced the package the name or file you associated with it was incorrect or in the wrong location. The fix for the 1619 error is usually a simple mistake.
  • Add this in the Registry and each msi installed on that computer will create a log in %TEMP% folder:

    Windows Registry Editor Version 5.00


    You can save it in a reg file and import it to the registry. Upload the log here and we will help you for sure.
Please log in to comment