Copy link to clipboard
Copied
Hi Adobe and other readers,
I've made a Creative Cloud Packager (CCP) package to install all current CC apps and updates, with the exception of Acrobat Pro. This builds and outputs a pkg as expected.
When the pkg is installed on a test machine, it fails. In /Library/Logs/Adobe/Installers, the most recently updated log is Adobe InDesign CC 2014 10.0 <datestamp>.log.
Auditing this log, I see the first failure recorded is:
10/07/14 19:35:07:861 | [ERROR] | | OOBE | DE | | | | 63746 | DS015: Unable to read symlink target of source file "/Volumes/VMware Shared Folders/SeagateUSB3/Adobe CC 2014-all but Acrobat/Build/Adobe CC 2014-all but Acrobat_Install.pkg/Contents/Resources//Setup/IDSN10.0en_US/payloads/AdobeInDesign10AppBase-mul/OEM_/Adobe InDesign CC 2014/Plug-Ins/InCopyWorkFlow/Assignment UI.InDesignPlugin/Assignment UI"(Seq 11962)
When I manually dig into the installer pkg and follow that path, I find that Assignment UI is a symlink, but the destination it points to cannot be found. Exploring other sections of the InCopyWorkFlow/*.InDesignPlugin subfolders show each has 2 symlinks: one that matches the name of the parent folder, and a Resources symlink. All of these are broken- they do not link to a source file.
Can Adobe provide guidance regarding how to address this error, and produce CCP pkg output that does not fail due to invalid symlinks?
Copy link to clipboard
Copied
Moving this discussion to the Enterprise Deployment for Creative Cloud, Creative Suite forum.
Copy link to clipboard
Copied
I've found a little more about this: looking at the source pkg on the build machine, the above quoted simlinks are valid. They are not valid when the pkg was transferred to the destination machine. There is some aspect of moving them to other storage that is breaking the links...
Copy link to clipboard
Copied
Output package *does* work as expected when run on hardware. There is an issue with having the installer in a VMWare Fusion shared folder and installing to a VM.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now