Skip to main content
S
shanee87688442
New Participant
December 10, 2015
Question

CC install package fails (error 1603)

  • December 10, 2015
  • 5 replies
  • 17455 views

I've created an install package using the CC packager for our School license.  The package creates, and then I've moved it to the machine for installation. 

The .msi file runs for a short time then stops and is no longer running.  Or, at least, I can't find it in the processes under task manager.  In the event viewer, I get an "information" entry that indicates an "error or success" code of 1603.

If I run the setup.exe, it runs.  I even see the icons for the programs before it gets to a certain point and then stops entirely and backs off leaving only the Creative Cloud application installed.  In event viewer, for each of the programs that I was trying to install in the package, I get an information entry with event ID 1 (qualifiers 16386) and an event recordID of 487.

This is extremely frustrating.  Is it a file permission issue?  I'm logged in as a local admin, so it shouldn't be.

    This topic has been closed for replies.

    5 replies

    new erai30146597
    new erai30146597
    New Participant
    April 23, 2018

    Is there any kind of answer from Adobe Support. I have the same issue almost 3 years later.

    S
    shanee87688442Author
    New Participant
    January 12, 2016

    In my case, I ended up recreating the installation package and rerunning.  I ran the msi first and that failed.  I then uninstalled everything adobe again, rebooted, and ran the setup.exe file directly and it installed and is working.

      new erai30146597
      new erai30146597
      New Participant
      April 23, 2018

      The problem with running it this way, is it appears to not apply the licence correctly.

      ___Dom___
      Community Manager
      ___Dom___Community Manager
      Community Manager
      April 24, 2018

      Please open a new thread, as the cause may be different from the issue described above, and the packager has changed since this one was originally opened. You may find more information in the install.log, so you could link that to a new thread.

      D
      dannyh14724980
      New Participant
      December 15, 2015

      yep I have the same issue. I have tried removing dependence on installing Adobe CC Exceptions Deployer first and that didn't help.

      I am using SCCM 2012 R2.

      My log files for the AppEnforce log from SCCM is this -

          A user is logged on to the system.AppEnforce14/12/2015 1:37:29 PM2436 (0x0984)
          Performing detection of app deployment type Adobe CreativeCloudENT - Windows Installer (*.msi file)(ScopeId_0D7880B4-8A17-45FC-9F08-EC1D30E9B0F4/DeploymentType_79da0e94-8a55-4d90-a8c5-ca61ac72bab3, revision 6) for user.AppEnforce14/12/2015 1:37:29 PM2436 (0x0984)
      +++ Application not discovered. [AppDT Id: ScopeId_0D7880B4-8A17-45FC-9F08-EC1D30E9B0F4/DeploymentType_79da0e94-8a55-4d90-a8c5-ca61ac72bab3, Revision: 6]AppEnforce14/12/2015 1:37:30 PM2436 (0x0984)

          App enforcement environment:

      Context: Machine
      Command line: msiexec /i "CreativeCloudENT.msi" /q
      Allow user interaction: No
      UI mode: 1
      User token: not null
      Session Id: 1
      Content path: C:\Windows\ccmcache\4
      Working directory:AppEnforce14/12/2015 1:37:30 PM2436 (0x0984)
          Prepared working directory: C:\Windows\ccmcache\4AppEnforce14/12/2015 1:37:30 PM2436 (0x0984)
      Found executable file msiexec with complete path C:\Windows\system32\msiexec.exeAppEnforce14/12/2015 1:37:30 PM2436 (0x0984)
          Prepared command line: "C:\Windows\system32\msiexec.exe" /i "CreativeCloudENT.msi" /q /qnAppEnforce14/12/2015 1:37:30 PM2436 (0x0984)
      Valid MSI Package path = C:\Windows\ccmcache\4\CreativeCloudENT.msiAppEnforce14/12/2015 1:37:31 PM2436 (0x0984)
          Advertising MSI package to the system.AppEnforce14/12/2015 1:37:31 PM2436 (0x0984)
          Executing Command line: "C:\Windows\system32\msiexec.exe" /i "CreativeCloudENT.msi" /q /qn with user contextAppEnforce14/12/2015 1:37:41 PM2436 (0x0984)
          Working directory C:\Windows\ccmcache\4AppEnforce14/12/2015 1:37:41 PM2436 (0x0984)
          Post install behavior is BasedOnExitCodeAppEnforce14/12/2015 1:37:41 PM2436 (0x0984)
          Waiting for process 2808 to finish.  Timeout = 120 minutes.AppEnforce14/12/2015 1:37:41 PM2436 (0x0984)
          Process 2808 terminated with exitcode: 1603AppEnforce14/12/2015 2:14:06 PM2436 (0x0984)
          Looking for exit code 1603 in exit codes table...AppEnforce14/12/2015 2:14:07 PM2436 (0x0984)
          Unmatched exit code (1603) is considered an execution failure.AppEnforce14/12/2015 2:14:07 PM2436 (0x0984)
      alisterblack
      Community Manager
      alisterblackCommunity Manager
      Community Manager
      December 14, 2015

      Some things to try

      1. restart the Windows Installer service
      2. Give full permissions (i.e. write access for all users) to the directories "C:\Program Files" and "C:\Program Files (x86)"
      3. Install the latest version of Adobe Application Manager from here: https://www.adobe.com/support/downloads/detail.jsp?ftpID=4773
      4. Delete the backup directory cited in the logs, which may fail to be deleted by the installer e.g. "C:\adobeTemp\backup\adobetmp26867789"

      The problem with 1603 is that it is a fairly generic error. To dig deeper we would need to get the log files.

      This tool can help you collect them helpx.adobe.com/creative-cloud/kb/cc-log-collector.html

      Then you can pass these to support either by opening a ticket on the Enterprise Dashboard (for Enterprise) or for teams or individual contact us via https://helpx.adobe.com/contact.html

      alisterblack
      Community Manager
      alisterblackCommunity Manager
      Community Manager
      December 11, 2015

      The following document may be useful https://helpx.adobe.com/creative-suite/kb/error-1603-install-cs3-cs4.html

      S
      shanee87688442Author
      New Participant
      December 11, 2015

      I've tried those solutions and still having the same issues.  Not sure how much of a difference it makes, but the machine I'm attempting to install on is a Windows 10 machine and I'm installing CC 2015.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices