Error 1603 Installing Creative Cloud from Network Path

Report · Apr 15, 2014

I used the same method as I am going to describe below to install CS6 but I cannot do this with Creative Cloud.

After I built a install Package for Adobe Creative cloud I copied it up to a network share that I use for several other remote installations including Adobe CS6. I use Dell KACE to distribute my software and due to the large size of Creative Cloud and Creative Suite before it I do not want to copy the large install files directly to the appliance.

The problem I am having is when I try to install from this network location just as I have with CS6 I get the following error:

Installation operation failed

Windows Installer installed the product. Product Name: Adobe_CC_NoAcrobat. Product Version: 1.2.0000. Product Language: 1033. Manufacturer: Adobe Systems Incorporated. Installation success or error status: 1603.

Adobe_CC_NoAcrobat is what I named the package.

My install commands look like this:

start /wait \\SERVER\AdobeCC\Adobe_CC_NoAcrobat\Exceptions\ExceptionDeployer.exe --workflow=install --mode=pre

start /wait msiexec.exe /i "\\SERVER\AdobeCC\Adobe_CC_NoAcrobat\Build\Adobe_CC_NoAcrobat.msi" /qn /L*v c:\Adobe.log

start /wait \\SERVER\AdobeCC\Adobe_CC_NoAcrobat\Exceptions\ExceptionDeployer.exe --workflow=install --mode=post

I added the Logging after it kept failing to see what was going on and I can paste the entire log file if need be but if I copy the folder with the package contents locally and run the same commands from the same elevated command prompt it installs fine. Error 1603 usually points to some access rights issue but for the life of me I cannot determine what the issue is. I have given full control to "Everyone", "SYSTEM" and all users to the network share and it is only the MSI that fails it seems.

Report · Apr 15, 2014

Please refer the article: http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AdobeApplica....

Regards,

Romit Sinha

Report · Apr 15, 2014

Well that is completely unhelpful. Imagine that.. read the deployment PDF

I do not have SCCM or the other distrubution described in the PDF. The method I described above has worked flawlessly with Adobe Creative Suite versions 5 through 6.

Report · Apr 15, 2014

Having the exact same problem. This worked with an earlier version of creative cloud packager, it appears to of broken with 1.4. There are several other threads floating around detailing this exact issue. Adobe needs to own this problem and find a resolution. This has been dragging out for weeks now with no results or steps to correct the problem.

Report · Apr 15, 2014

Thank You for your reply fooman... I have been digging around for an answer to this as my school district wants to use Creative Cloud starting for Summer School so I wanted to get a handle on deploying this. I have seen several have this or similar issues recently so I know it is an issue with Adobe but they seem to not want to admit that but instead just link the PDF on enterprise deployment like we would be here if we haven't tried to follow the instructions.

As I stated above the method I am trying to use worked flawlessly for CS5 through CS6.

Report · Mar 12, 2018

this forum question will never be answered

Report · Apr 16, 2014

Thanks for posting this bwilk217,

I'm having the exact same issue with *ALL* of the Creative Cloud packages I'm building. I thought for a while I was doing something wrong, but they just will not run from a network share. I'm receiving the same 1603 error, and in the .log.gz file, I only receive one entry: OOBE | DE | 3592 | Cannot Open mediadb

I've tried 1.1 through 1.4 of the packager, and the only way I can get them to install is if I run the packages locally; this, of course, can't happen because I'm in a large corporate environment.

I also have no problems running anything created with the AAMEE packager from a network share.

Are there any updates from anyone regarding this issue?

Thanks in advance for any help.

Report · Apr 17, 2014

Just an FYI to all. I found an old package I made using Creative Cloud Packager months ago and using the same method to distribute the program from a network share works fine. So until Adobe addresses this issue and fixes it I will have to use that. Thank fully I have a script set up to run the Adobe Remote Update manager periodically on all my CS6 and Creative Cloud installations so that they can get the patches and updates.

So if anyone at Adobe is reading this please fix the Creative Suite packager programs as this is clearly an issue with Adobe software as this issue is affecting many people using managment tools to deploy their products.

Report · Aug 30, 2014

bwilk217 - I found what seems to be a way around the problem but haven't tested it yet.

Check out: https://brashear.me/blog/2014/04/02/getting-adobe-creative-cloud-enterprise-to-install-from-a-networ...

Hope this helps.

Keith

P.S. I will be testing this in the next couple of days and may make use of it myself.

Report · Oct 12, 2014

I have just run into this problem. I have made two packages earlier in the year (one of Creative Cloud Design and Web and one with Creative Cloud Master Collection both being for x64) and they both worked flawlessly when deploying via Microsoft Deployment Toolkit (MDT). However I just went to make a new package of Master Collection (only including the applications we actually use) and it is now completely broken (I deleted my Creative Cloud Design and Web package from MDT but still have my old Master Collection package and it still works).

My older packages were created on Windows Server 2008 SP2 Enterprise 32bit and I have tried creating new packages on Windows Server 2012 R2 x64 and Windows Server 2003 SP2 Standard Edition 32bit and both give the same failure. I thought it might have been something about building on a x64 OS this time compared to last time but as I still get the same error when I tried to build from the Windows Server 2003 so that does not appear to be the case so I am guessing something has broken in the Creative Cloud Packager.

Has anyone tried going back to an older version of the Creative Cloud Packager? The current version is 1.6.0 Build 48 so if I can find a download link I will try and give version 1.5.0 a shot. Either way this needs to be fixed ASAP as it did work and I need a working deployment for the new Windows 8.1.1 Enterprise x64 image I am in the process of making.

Report · Oct 15, 2014

We are having this same problem as well. Just like bwill217, we use Dell Kace to deploy all of our software. We never had any problems with CS6 deployments, but none of the x64 packages we build with the latest version of CC Packager work at all in any of our Windows 7 x64 images. I can't even get the packages to install locally on our lab machines using the .exe and a local admin account; the same error occurs. We have been in contact with Adobe Enterprise support and have provided multiple install logs, but they have been less than helpful thus far.

I too am unable to find a download for an older version of CC packager to test, but would be willing to do so and post results here if anyone has a copy of the installer.

Report · Oct 23, 2014

Same issue here on enterprise network, however I have the same problem when I copy the files locally. This post

https://forums.adobe.com/message/5581988

has more details that match my issue exactly, and it sounds very like the OP's issue.. No resolution from Adobe offered. Have lost a lot of time on this (over 100 licenses purchased and as yet cannot be used) lots of money wasted so far. Maybe should ask for a refund.

Report · Oct 24, 2014

Just thought I would let you know we have found a way to fix this problem. If you look in the Windows Event Viewer there are lots of errors about set-up.dat (I have a copy of the Windows Event log if someone from Adobe would like to read them) when you try and install the Creative Cloud package (even if you try from the local machine). What my manager tried was copying the set-up.dat file from my previous Creative Cloud build that I made in May (so probably using the Creative Cloud packager 1.5 or earlier) into our current builds folder and the install works fine.

To me it appear that the Creative Cloud packager 1.6 and 1.7 are corrupting or malforming the set-up.dat file so if you are lucky enough to have an old Creative Cloud build sitting around somewhere you maybe able to copy the set-up.dat file from it into your new build folder and install like normal.