When editing .ccp file fails with "corrupted package" error

[Systems U-tad]

Hello.

I usually créate packages on my local computer, and then copy them to a network drive, for deployment.

However when I try to edit a package I made, the creative cloud packager fails with a "Selected package is corrupt" message. I tried to map the folder to a network drive, or copy to a local folder but it doesn't work.

It seems to only work if I copy it in the very same folder where it was created. However, I have a few packages of which i don't knwo the original location.

What can I do to edit this packages?

Thanks.

[romar20820909]

Hello Adobe support team..

I am experiencing the same error. I have successfully download the whole (full) package of Adobe Creative Cloud products, however when I deploy all of them, it takes 2,5 hours to complete the installation. I want to edit the installer by removing some Adobe product. However when I try to load the .ccp file using Creative Cloud Packager, I got error "Selected package is corrupt".

1. Where can I find the log so you can examine your product?

2. Is there any easy way to modify the Adobe Package so I don't have to download another giga bytes of your installer? You have small upstream, I need a whole night to download your products and 50% must be failed that I have to delete AAMUpdater folder.

Thanks.

[alisterblack]

Hi,

You can find logs at the locations noted here:

https://helpx.adobe.com/creative-cloud/packager/deploying-packages.html#Adobe%20Creative%20Cloud%20P...

You don't need to download applications again. If you already downloaded the applications they are cached.

[romar20820909]

Hi alisterblack.. Thanks for your response.

But, how can I know the cause of "selected package  is corrupt"..? I never touch that .ccp file.

I downloaded the full package some months ago in one virtual machine which already been deleted. I got the full package of 13 GB then I moved them to my file server and now it is successful to be deployed with 2,5 hours to complete each computer. So this full package is valid, however the time to deploy is unacceptable and I need to edit the package. How come your package manager refer to cache instead of the full package that is already downloaded completely?

Can you make your Adobe Package Manager has ability to edit my downloaded package? Or alternatively, is there any other method to deploy/install the selected Adobe program one by one?

I hope you know how it is

-when it takes 2,5 hours to complete the installation to a client computer with Core i7, 16 GB of RAM

-when it takes the whole night (more than 7 hours) to download some gigabytes of your packaged while my internet connection is 80 Mbps

-when I re-download to re-build the package, the chance to success is 50% with the same error message [ERROR] AdobePackageBuilder - Failed to unzip the file blablabla..

Thank you for your understanding.

[alisterblack · Accepted solution]

Hi,

The .ccp file that you are loading is actually just a small xml file that should only be a few kilobytes. It contains pointers to cached downloads, and you state that you have deleted these cached downloads.

Each time you build a package you could be using different parameters. For example named user or serialized deployment. Editing the .ccp file only allows you to change the applications and updates included not any of the other details such as licensing information and how to handle updates.

If you only wish to deploy certain individual applications I would suggest building a package containing just that application. There are no limits in the packager concerning which of your licensed applications you include in your package, what you call it or how many packages you build. I think that would save you some time and give you a bit more flexibility, after all it is probably the case that not all your users need all the software in CC.

[romar20820909]

Hi alisterback,

how can you say that this is an XML file?

Thanks Ric, for sharing your experience. You make me know that I am not alone experiencing this difficult deployment of Adobe products.

[Ric5]

I'd like to add a "me too" to this. I've had packages that I've built simply sit in storage and when I went back to edit/update them I received an error saying they were corrupt. It happens with some and not others and my only solution is to rebuild them. Also, the first indication I get that there's a problem is with the CCP error. These are packages that have been deploying successfully in the field.

Fortunately, I keep good records of what is included in each package I build, but still it's something of a nuisance because each build or rebuild involves some hours of testing and moving to our distribution points.

Ric

[jasonf97419504]

I had this problem also, until I realized I changed the contents of the Build directory. Apparently, it expects the Build folder to be in the same directory as the .ccp file and the contents of the Build directory  should be exactly the same as it was when it was last saved: <PackageName>_Install.pkg and <PackageName>_Uninstall.pkg.

Once I returned those files to the Build directory and renamed them to their original names, I could load the .ccp file. If you don't know what  <PackageName> it is looking for, read the .ccp file using a Unicode-compatible text editor (I use TextWrangler for Mac) to find the  <PackageName> XML key; it should be within the first 5 lines of text.

[Ric5]

jfilice,

I have to say that hasn't been my experience. The only change I make is (for Windows) to place a batch file in the installer's root directory, the directory that contains the Build directory and the .ccp file. For Mac installers, I don't do a thing create a shortcut for the installer .pkg in the root directory and then make a .dmg that I distribute to our techs. I do this for all the installers I build, but the corrupt .ccp file is a fairly random occurrence, happening most often on the Windows side.

That being said, I do appreciate your tip about looking at the .ccp files in TextWrangler, which works wonderfully for Mac files. I still can't find a way to look at the Windows version (even with TextWrangler.

Ric