Hi,

I've created a Framemaker XI package with the "Adobe Application Manager Enterprise Edition", provided the serial number and added patch 11.0.2. The package was successfully created on a network share the installing admin account has full access rights to. Target system is a W2K8 R2 64bit terminal server.

When installing, the msi rolls back, throwing error 1708/1603 after collecting all it's msi properties, nothing gets installed. In the LOCAL folder of %APPDATA%, I find a file called PDApp.log with the follwing content:

 

6/27/2013 17:16:47 [INFO] DeploymentManager - Build Version - 3.1.105.0
6/27/2013 17:16:47 [INFO] DeploymentManager - Logging Level verbosity Set  to 4
6/27/2013 17:16:47 [INFO] DeploymentManager - Executing the deferred custom action.
6/27/2013 17:16:47 [INFO] DeploymentManager - Obtained the following as CustomActionData
6/27/2013 17:16:47 [INFO] DeploymentManager - mode=install;sourceDir=H:\TIMRS\4 ACME_Framemaker_XI\Build\;installDir=;origDB=H:\TIMRS\4 ACME_Framemaker_XI\Build\ACME_Framemaker_XI.msi
6/27/2013 17:16:47 [INFO] DeploymentManager - mode=install;sourceDir=H:\TIMRS\4 ACME_Framemaker_XI\Build\;installDir=;origDB=H:\TIMRS\4 ACME_Framemaker_XI\Build\ACME_Framemaker_XI.msi
6/27/2013 17:16:47 [INFO] DeploymentManager - Original database path is : H:\TIMRS\4 ACME_Framemaker_XI\Build\ACME_Framemaker_XI.msi
6/27/2013 17:16:47 [INFO] DeploymentManager - OptionXML saved at location :: C:\Users\User\AppData\Local\Temp\{65DEE398-291E-476D-B68C-5ABD59EC6C4 9}\\{12E9F8D1-641B-4C27-A165-D3C34F200ECB}
6/27/2013 17:16:47 [INFO] DeploymentManager - Build Version - 3.1.105.0
6/27/2013 17:16:47 [INFO] DeploymentManager - Logging Level verbosity Set  to 4
6/27/2013 17:16:47 [INFO] DeploymentManager - Initializing Custom Action Data from parameters
6/27/2013 17:16:47 [INFO] Utilities - Folder does not exist
6/27/2013 17:16:47 [INFO] DeploymentManager - Provisioning Tool path is (C:\Users\User\AppData\Local\Temp\{65DEE398-291E-476D-B68C-5ABD59EC6C 49}\\{DF00B53B-6298-4B11-B2BB-4221D161D441}).
6/27/2013 17:16:47 [INFO] Utilities - Folder does not exist
6/27/2013 17:16:47 [ERROR] DeploymentManager - Failed to Initialize....The Setup base path does not exist.
6/27/2013 17:16:47 [ERROR] DeploymentManager - Failed to Initialize from parameters.
 

I don't know where the problem is, but it seems that installation fails because something is missing in the package?

Anyone?

best regards
Olaf

4 Comments   [ + ] Show Comments

Comments

  • Is this installing it manually? From a ESD solution?
  • We need a verbose log in order to see why is ending with 1603 error.

    You can create the log in %TEMP% folder if you add this in your Registry:
    "
    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
    "EnableAdminTSRemote"=dword:00000001
    "Logging"="voicewarmup"
    "
  • I'd say the clue is in the odd-looking user-profile folder, 'C:\Users\User[etc]'

    I strongly suspect that the account you're using isn't one called 'User'!
  • @VBScab,
    true, USER is a valid USER in reality, sure. That was just to cloud identities.

    @terebent,
    the msi log I created with "/L*v" wasn't of much help here because the installation "intelligence" is in the PDApp.log. I skipped it for that reason.

    However, the problem is solved for unknown reason, but most likely because of some strange GPO which controls local admin rights perhaps a little to much.

    Whatever I tried with a local admin user and UAC off, it failed. However, package can be installed using SYSTEM rights perfectly well (used a scheduled installation to test that).

    best regards and thank you for your thoughts.
    Olaf
Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity

Share