Skip to main content
T
TonyHeslington
Participating Frequently
October 17, 2017
Pregunta

Creative Cloud Packager & SCCM - Acrobat DC - Package install starts but quits.

  • October 17, 2017
  • 2 respuestas
  • 4952 visualizaciones

Hello,

I have the task of packaging Adobe CC applications in my environment.

W10 64bit - v1606

SCCM - v1606

Adobe Acrobat Reader 2015 - Normally on machines by the time a CC user comes along.

All other packages have been created and installed successfully.

The Adobe DC application is proving to be challenging.

I have repeated the packing process twice with the same result.

The Job via SCCM completes.  (Exit code 0) however no icons for the product show up.

I manually run the .MSI package and it attempts the install only getting so far... suddenly the install progress indicator goes backward and quits.


Any idea what is going on?


Thank you,Tony H.

Este tema ha sido cerrado para respuestas.

2 respuestas

L
licensingm39260983
Participant
October 19, 2017

i have the exact same problem.  Can't seem to find an answer anywhere.  I guess my only solution is to try and bundle Acrobat DC alongside some of the other packages and hope that it works.

pensionc16073137
pensionc16073137
Participant
October 19, 2017

I have the exact same problem.

I've narrowed it down to the Visual Studio 2013 C++ redistributable that Adobe is expecting.

I'm running Windows 10, and it auto installs version 12.0.406....

However Adobe doesn't recognise this as being installed and is prompting for an "ok" or "cancel" to continue installing.

You can't install the run bundled with Acrobat, as it's an older version.

So we're stuck being unable to deploy the application as it's expecting a response so throws an error.

pensionc16073137
pensionc16073137
Participant
October 19, 2017

You could try using this install PROPERTY to get around installing the MS C++ Redistributatables in the Acrobat installer.

Adobe Properties — Enterprise Administration Guide

InstallationDC and laterIGNOREVCRT64Since Acrobat looks for Visual C++ x64 2013 Runtime (VC) by default, set IGNOREVCRT64 to 1 if it is not present AND not needed. IGNOREVCRT64 need only be used when all of the following are true:
  • During Acrobat installs on 64-bit machines
  • When Visual C++ x64 2010 SP1 Runtime is not installed
  • Installation is NOT done via setup.exe.
  • The following functionality is NOT needed: 1) Acrobat PDF Creation add-on (PDFMaker plugin) for Microsoft Office 64-bit applications (viz. Word, Excel, PowerPoint & Outlook) and 2) sending emails or resolving addresses via 64-bit Microsoft Outlook.
Since Acrobat looks for Visual C++ x64 2013 Runtime (VC) by default, set to 1 if it is not present AND not needed. During non-setup.exe installs when VC is not present, installation behavior is as follows:
  • Command line installs abort if IGNOREVCRT64=1 is not passed.
  • UI installs display a dialog asking the user whether they would like to continue or cancel.
  • Setup.exe installs succeed. Installs never abort as the property is passed while spawning the MSI.
For MSI installs, use Require64BitVC10RT in the Setup.ini file under the Startup section.
Installation11.x onlyIGNOREVC10RTIGNOREVC10RT need only be used when all of the following are true:
  • During Acrobat installs on 64-bit machines
  • When Visual C++ x64 2010 SP1 Runtime is not installed
  • Installation is NOT done via setup.exe.
  • The following functionality is NOT needed: 1) Acrobat PDF Creation add-on (PDFMaker plugin) for Microsoft Office 64-bit applications (viz. Word, Excel, PowerPoint & Outlook) and 2) sending emails or resolving addresses via 64-bit Microsoft Outlook.
Since Acrobat looks for Visual C++ x64 2010 SP1 Runtime (VC) by default, set IGNOREVC10RT to 1 if it is not present AND not needed. During non-setup.exe installs when VC is not present, installation behavior is as follows:
  • Command line installs abort if IGNOREVC10RT=1 is not passed.
  • UI installs display a dialog asking the user whether they would like to continue or cancel.
  • Setup.exe installs succeed. Installs never abort as the property is passed while spawning the MSI.
For MSI installs, use Require64BitVC10RT in the Setup.ini file under the Startup section.

Hi Steve

Thanks - should've looked there.  That works for me, hopefully it resolves the OP's issue too.

S
Adobe Employee
Steve Cordero
Adobe Employee
October 18, 2017

You will want to get a verbose installation log.  Here is the Microsoft KB on enabling this Windows Installer feature.

https://support.microsoft.com/en-us/help/223300/how-to-enable-windows-installer-logging

After you have the log, then you can look at the error(s) that may be causing the installation problem.

Términos y condicionesAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices