Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Adobe Acrobat XI Standard 11.0.10 silent install failing with error 1603

New Here ,
Jan 16, 2015 Jan 16, 2015

Hello

I just updated my AIPs for Adobe Acrobat Pro 11 Pro and Standard.  The Pro silent install is working fine.  But I cannot get the Standard install to run on Windows 7 or WIndows 8.   I have gone over every detail that I can think of or find on forums.

I use the Adobe Customization Wizard XI and choose the basic stuff to create my transform.  I don't generally enter a serial number in the customization setup but I tried that and the installation did appear to complete successfully.  But when I tried to open Acrobat it did not work.  Processes like PDapp.exe where running in a loop but never stopped.   Without a serial I get the errors below and the install fails almost immediately.   I have recreated the API and transform a few times hoping it would help.

Installing with the following line msiexec /i "%~dp0AcroStan.msi" TRANSFORMS=AcroStan.mst /qb /L*v c:\acrobat.log I get an error message that just says "error".

Application Event logs

Product: Adobe Acrobat XI Standard --  error.

Windows Installer installed the product. Product Name: Adobe Acrobat XI Standard. Product Version: 11.0.10. Product Language: 1033. Manufacturer: Adobe Systems. Installation success or error status: 1603.

When I run the AcroStan.msi by itself the installation completes successfully so it would appear the issue is in customization process or the .mst file.  Any help would be greatly appreciated.

Thank you

7.3K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 16, 2015 Jan 16, 2015

Create a verbose log. Curious to know if you see this: CustomAction AAMIU_Install.196A45B3_0387_4DF9_9420_597B6F2F9ADD returned actual error code 1603

Ben

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 16, 2015 Jan 16, 2015

I'm assuming that verbose logging is accomplished by adding /L*v c:\acrobat.log ?  No, I do not have CustomAction AAMIU_Install.196A45B3_0387_4DF9_9420 in my log file.  The only items referencing 1603 are below.

CustomAction CheckForPendingOperation returned actual error code 1603 but will be translated to success due to continue marking

CustomAction SetLotusNotesInstalled returned actual error code 1603 but will be translated to success due to continue marking

CustomAction ProcessAbcpy returned actual error code 1603 but will be translated to success due to continue marking

MSI (s) (84:C4) [15:30:14:422]: Note: 1: 1708

MSI (s) (84:C4) [15:30:14:422]: Product: Adobe Acrobat XI Standard -- Installation operation failed.

MSI (s) (84:C4) [15:30:14:422]: Windows Installer installed the product. Product Name: Adobe Acrobat XI Standard. Product Version: 11.0.10. Product Language: 1033. Manufacturer: Adobe Systems. Installation success or error status: 1603.

MSI (s) (84:C4) [15:30:14:458]: Attempting to delete file C:\windows\Installer\9d9a98.mst

MSI (s) (84:C4) [15:30:14:478]: Deferring clean up of packages/files, if any exist

MSI (s) (84:C4) [15:30:14:478]: Attempting to delete file C:\windows\Installer\9d9a98.mst

MSI (s) (84:C4) [15:30:14:478]: Unable to delete the file outside of the engine. LastError = 2

MSI (s) (84:C4) [15:30:14:479]: MainEngineThread is returning 1603

MSI (s) (84:28) [15:30:14:480]: Calling SRSetRestorePoint API. dwRestorePtType: 13, dwEventType: 103, llSequenceNumber: 31, szDescription: "".

MSI (s) (84:28) [15:30:14:483]: The call to SRSetRestorePoint API succeeded. Returned status: 0.

=== Logging stopped: 1/16/2015  15:30:14 ===

MSI (s) (84:28) [15:30:14:484]: User policy value 'DisableRollback' is 0

MSI (s) (84:28) [15:30:14:485]: Machine policy value 'DisableRollback' is 0

MSI (s) (84:28) [15:30:14:485]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (84:28) [15:30:14:485]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (84:28) [15:30:14:485]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

MSI (s) (84:28) [15:30:14:486]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (s) (84:28) [15:30:14:487]: Destroying RemoteAPI object.

MSI (s) (84:54) [15:30:14:487]: Custom Action Manager thread ending.

MSI (c) (E4:0C) [15:30:14:489]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (c) (E4:0C) [15:30:14:489]: MainEngineThread is returning 1603

=== Verbose logging stopped: 1/16/2015  15:30:14 ===

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 16, 2015 Jan 16, 2015
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 16, 2015 Jan 16, 2015

I have tried quotes, no quotes, full path, "%~dp0AcroStan.mst".  Tried running it from the server and local.  But I just tried it again... just in case.  Same error message as before. 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 16, 2015 Jan 16, 2015

1603 is an MSI error: Troubleshooting and Support — Enterprise Administration Guide

It can also be caused by locked files, running programs that take Acrobat plugins, trying to write to an encrypted folder, etc.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 16, 2015 Jan 16, 2015

I have looked at the information that is linked in your post.  I did not not find anything information that resolved my issue.

I have tried several different machines with this failing installation.  The thing is.... my Acrobat Pro 11.0.10 installs perfectly on the very same machines that the standard Acrobat 11.0.10 fails on.  The Pro and Standard .mst transforms are identical except for file names and paths.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 16, 2015 Jan 16, 2015

Well if you're sure destination folders aren't subject to security or encryption, then I'm out of ideas as well. This is the second "standard-only" problem I've seen so I'll ping some others.

Ben

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 22, 2015 Jan 22, 2015

I tried it again today.  I added back the serial number via the customization wizard and also granted the offline exception for serial number option and it worked.  Any idea why the behavior differences in the Standard verses the Pro when creating a customized AIP?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jan 22, 2015 Jan 22, 2015

The Standard install worked and all is a-ok?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jan 23, 2015 Jan 23, 2015
LATEST

Yes.  It appears to be working fine now with the serial number and the offline exception.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines