Adobe update using Application Manager

Right Click Tools- Enterprise
1

Trying to create Adobe Acrobat DC update using Application Manager. The app runs and downloads but then errors with "Failed to create some of the dependency application(s).
Get a similar error when trying to create an Adobe Reader DC application for SCCM. Runs then ger an error "Failed to get an application dependency @Applicaitn {then a code}’ Error only shows when hovering over the error so hard to get the code. Google has no indications of what the dependencies are. Anyone successfully managed to create Adobe Acrobat DC or updater package for SCCM ?

2

I’m told that more details can be found within the proxy logs. But the belief is that the dependency was deleted from ConfigMgr. Re-importing the app should solve this problem.

Hope this helps

3

Hi mbartlett,

First install dependency Microsoft Visual C++ 2013 Redistributable (x64) then Adobe Acrobat DC will install with the Recast Application Manager.

Greetings Gijs

4

Hi Malcolm,

I hope all is well. Could you please submit this issue along with your most recent Recast Proxy logs to support@recastsoftware.com so that we can assist you further?

Log location: C:\ProgramData\Recast Software\Logs

Best regards,
Destiny | Recast Technical Support

5

If you see the error “Failed to create some of the dependency application(s)” in Adobe Acrobat DC via Application Manager, it’s almost always because a runtime dependency is missing, not because the app itself is broken.

The Visual C++ Redistributables (2013 x64/x86, depending on your system) are what most SCCM/Recast deployments fail on.

I had to install the necessary C++ runtime first through a separate package in SCCM, then set it as a dependency in the Application Manager definition, and finally create the Acrobat DC app. The dependency errors go away after that is set up.

Also, check your Recast Proxy logs again. Sometimes the error shows a GUID for a dependency that was removed from ConfigMgr.

Re-importing that app into Recast fixes the “ghost dependency” problem. This combination usually makes both Acrobat DC and Reader DC installations go more smoothly.

1 Like