Creative Cloud Package CustomAction CADeploy returned actual error code 1603

[Marist-Sion College]

Hi,

We've created numerous packages and are seeing the same problem installing, Acrobat will install fine but the suite fails with CustomAction CADeploy returned actual error code 1603. Any ideas?

Ben

[Marist-Sion College]

We're using 1.7.0 Build 93 of the Packager, it fails about 10 seconds after starting. We're trying to deploy it through SCCM, it also fails manually. Not sure if there's some sort of conflict with some prerequisite. Quite frustrating, wasted a great deal of time trying to resolve it.

[smpl82]

I'm having the same issue but only with the Scout application 64-bit edition. I've managed to download, package & install multiple other Adobe applications but for some reason this one continually fails with the CustomAction CADeploy failing with error code 1603. I've tried packaging on a freshly built or reimaged machine along with two others. The packager just will not successfully create a working MSI.

[Cfn64]

Has noone ever found a resolution to this? I am getting this issue with an InDesign CC 2014 install. Creative Cloud App (that I do not want) installs but InDesign Fails. Why??

Does anyone ever update these forums or just admit that there is no solution?

Thanks

[jpt65]

You can add my name to the list.  I just downloaded the packager to a new server, and created a package for Acrobat Pro DC.  I get this 1603 error everywhere I try to install it.

[alisterblack]

The most likely cause for this error is a conflict on installation. If Creative Cloud Packager is running then close it. Similarly other Adobe processes.

For a list see the following document Resolving process conflicts

[Guest]

I'm having the same issue Adobe FrameMaker 12. I have repackaged the application and Adobe FrameMaker application installs fine but for some reason this one continually fails with the CustomAction CADeploy failing with error code 1603 on uninstallation. I've tried packaging on a freshly built or reimaged machine along with two others. The packager just will not successfully execute the MSI itself using command line.