ConfigMgr Deployments fail with exit code 1619

Question

_{Wednesday, February 8, 2017 5:56 PM}

Hello,

Recently, we were hit with a virus and had to restore our Config Manager software share from backup.  Now when I attempt to deploy software, the client machines fail with exit code 1619.  I am thinking this may have something to do with permissions, but am not sure.  Has anyone else run into this and were you able to fix it?

Thanks in advance for any advice anyone has to fix this.

All replies (5)

_{Friday, February 10, 2017 7:38 PM ✅Answered}

I was able to figure this out on my own through trial and error.  It was a permissions issue on the folder where we have the software that is deployed in our organization ("software share").

_{Wednesday, February 8, 2017 11:43 PM | 1 vote}

1619 is not a ConfigMgr code, it is a Windows Installer error code returned from msiexec.exe. It means "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." Thus, whatever you've specified as the msi on the msiexec command-line is not valid. Without knowing more details about what you are doing, what command-line you've specified, etc. nothing more can be said.

Jason | http://blog.configmgrftw.com | @jasonsandys

_{Thursday, February 9, 2017 8:01 AM}

All new software have the same problem? what about previously deployed software?

Have you tried to install the software manually under admin/user/system context? ConfigMgr client will enforce installation under system context by default.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

_{Thursday, February 9, 2017 1:04 PM}

Jason - I understand it's a Microsoft error code.  I am just trying to gather information to try to come to a solution because I was able to deploy the packages successfully before the restore.

Hi Frank - I have not tried creating a new package to deploy yet, but I will try that.  And yes, the software installs fine if I run it as me at a command prompt.  It's just when the packages are deployed to clients via SCCM that I'm having issues.

_{Thursday, February 9, 2017 3:47 PM}

I didn't say "Microsoft error code", I said "Windows Installer error code" and gave you the exact meaning. I also gave you an interpreted cause that msiexec.exe can't find the MSI that you've specified on the command-line but since we don't know anything else about what you are doing, nothing more can really be said.

What's a Microsoft software share? Is that where you keep your source files for your packages and application in ConfigMgr? If so, that has no impact on the clients or the content they use *unless* you also updated the content in ConfigMgr in which case, it's possible the MSI was deleted. Check your source location for the package/application and also check the content library in ConfigMgr using the DP Content Explorer tool from the toolkit to validate whether the specified MSI exists anymore.

Jason | http://blog.configmgrftw.com | @jasonsandys