An attempt was made to deploy the binary to a location where another binary was already saved. Existing binary

Question

I get the error below. I see this being mentioned in other SO ( here ) posts, and I contacted SDL support, but I'm still having trouble fixing the problem. Can anyone suggest an EASY solution? I think the steps that lead to this are as follows:

1) publish a page with a link to PDF 1001.
2) Remove PDF 1001 from the page and remove it from CM. 3) Download PDF 1002 with the same name as 1001.
4) Now, if you try to post a message, you will receive an error message.

Therefore, I need to unpublish PDF 1001, but it has been removed from CM. How can I fix this problem? SDL support recommended a fix related to editing a ZIP file created during transaction publication. But I went to the publication of all pages of the publication and confirmed that they were not. The error is saved ...

ERROR:. Phase: Deployment. Prepare the phase of the completed phase. Unable to prepare transaction. tcm: 0-11111-66560. An attempt was made to deploy binary 1002 to a location where another binary was already saved. Existing binary: 1001 :, Trying to deploy binary 1002 to a location where another binary was already saved. Existing binary: 1001 :, Unable to prepare transaction: tcm: 0-13573-66560, Attempting to deploy binary 1002 to a location where another binary has already been saved. Existing binary: 1001 :, Attempted to deploy binary 1002 to a location where another binary was already saved. Existing binary: 1001:

Answer 1

Thus, the file was deleted from CM, but there is still a link to it on the CD (according to the CD, it still exists and is still used by something).

You should publish the page after removing 1001, but before adding 1002. This should remove the link from the CD database. Then you should be fine to add 1002 and publish the page again.

[EDIT] Sorry, just now read that you say that you did not publish everything. Clearly, no, since there is still a link to it ... opening a virtual machine will return with updates.

[EDIT2] Still don't understand how it remains a conflict if you cancel the publication, but this is what I observe on my server:

• Add binary to page, publish
  • Link added to table "REFERENCE_ENTRIES" on CD
• Remove binary from page, publish
  • Link removed from table "REFERENCE_ENTRIES", binary removed.
• Unpublish the page (after re-adding binaries, republishing)
  • Link removed from table "REFERENCE_ENTRIES", binary removed.

So, in my case, I see what I would expect. Try publishing the page after deleting the binary, and if possible, check that the REFERENCE_ENTRIES table is in.

Answer 2

This error is often caused by the fact that, by default, Tridion uses the original file name of the downloaded binary file as the file name on the content delivery side. If you did not specify a separate group of structures for deployment, then if you have two multimedia components with the same source name of the downloaded file, Tridion will try to deploy them in one place when delivering the content. Fortunately, the content delivery libraries are smart enough to detect potential correspondence, and you get this error instead.

First, this scenario is more likely in test situations. For example, you need to create a group of test MMCs, so you copy and paste some of them that you already have. Guess what - their file names will be the same.

The solution is to make sure that the file name is unique in the group of the structure into which you are deploying. You have a lot of choices on how to do this, but the general approach is to enter the identifier of the component in the file name when calling AddBinary ().

Answer 3

We are faced with this fault-tolerant process for almost every installation. Although this is much more common in development and testing environments, fault tolerance can occur in other situations. In fact, it can effectively destroy your entire site if you try to post an image that already exists (where the images are replaced by a “broken image” icon). Not sure how this works, but it can.

To make sure that the downloaded downloaded binaries are unique, I would recommend writing TBB, which checks all the binaries and adds tcm uri to the file name. Add this to each page template to prevent this from happening. The sooner you do this, the less likely it is to make a mistake. Keep in mind that this may mean that the download will always publish a new binary, and if you add Tbb templates to COMPONENT, the pages will have a conflict. However, this eliminates the need to explain the workflow to editors who do not understand (or better, accept) fault tolerance.

This page can help you get started: Unique binary file names.