When it comes to application deployment, SCCM is a good tool to package and deploy applications across your estate. However sometimes the application deployment fails and further troubleshooting is a must to determine the cause of error.
In this post I will discuss about SCCM application install error – Unmatched exit code 1619. This is an uncommon error and you don’t encounter this if you package the application correctly.
In order to simulate this error, I will be deploying 7zip application as an example. In your case it could be some other application as well. 7-Zip is free software with open source and you can download the installer here.
SCCM Application Install Error – Unmatched exit code 1619
So I download and package the 7zip application in SCCM. When you go to 7zip download page, you can download either a .msi installer or executable (.exe).
Let’s assume that when you deploy an application, the application install fails. The software center shows error 0x653(1619). You cannot know the actual cause for this failure unless you examine the SCCM log files on client computer.
On the client computer if you examine the AppEnforce.log file, you will find the exact error. Unmatched exit code (1619) is considered an execution failure.
Found executable file msiexec with complete path C:\Windows\system32\msiexec.exe AppEnforce 6408 (0x1908) Prepared command line: "C:\Windows\system32\msiexec.exe" /i ”7z1900-x64.msi” /q /qn AppEnforce 6408 (0x1908) Executing Command line: "C:\Windows\system32\msiexec.exe" /i ”7z1900-x64.msi” /q /qn with user context AppEnforce 6408 (0x1908) Working directory C:\Windows\ccmcache\3 AppEnforce 6408 (0x1908) Post install behavior is BasedOnExitCode AppEnforce 6408 (0x1908) Waiting for process 4256 to finish. Timeout = 120 minutes. AppEnforce 6408 (0x1908) Process 4256 terminated with exitcode: 1619 AppEnforce 6408 (0x1908) Looking for exit code 1619 in exit codes table... AppEnforce 6408 (0x1908) Unmatched exit code (1619) is considered an execution failure. AppEnforce 6408 (0x1908) ++++++ App enforcement completed (0 seconds) for App DT "7-Zip 19.00 (x64 edition) - Windows Installer (*.msi file)" [ScopeId_BD9C0939-01F6-4C99-ABD7-1E6DD2E41AD6/DeploymentType_21d8474a-881e-44c5-8d56-69035aa69382], Revision: 1, User SID: ] ++++++ AppEnforce
Exit Code 1619 translates to this installation package could not be opened. Verify that the package exists and that you can access it. Or contact the application vendor to verify that this is a valid Windows Installer package.
We know that the 7zip installer is fine, the error could be related to something else. Notice setup command and you will realize where the issue is.
There could be three reasons why you see the Unmatched exit code (1619).
- Sometimes we copy the install command from a forum thread or a blog. In most cases we forget to correct the quotation marks. You can notice the same issue in the below screenshot. The quotation marks around the setup file are incorrect and hence SCCM cannot install the application.
- The reference to the .msi file in the command line of the policy is incorrectly referenced.
- The application is invalid or corrupt. In such cases, you must download the installer again and package it. Try manually installing the same application on a computer to verify if it installs fine.
If something else resolved your issue, please write down in the comments section. I hope this post helps.