1

This is regarding an issue coming up in publishing a JavaScript file to live environment from SDL Tridion environment from one publication only. It is possible to publish the file from the other publications to live as well as staging environment.

There are three JavaScript files uploaded with the same name in the unpublished state. The issue is coming up while publishing one of the file to the Live environment while the file gets published successfully to the staging environment. It gives the error

Expected one result and more found: 2

What does this error mean, and how can I solve my problem? After unpublishing and renaming the duplicate files, the issue doesn't get resolved.

4
  • Even on renaming these files and removing the duplicate in name the issue is not resolved. Any help is much appreciated!!!
    – Nidhi
    Commented Mar 18, 2014 at 14:56
  • Are you the same person who asked the question? Is this meant to be an update to the question? I'd suggest editing the question would make more sense. Commented Mar 18, 2014 at 19:28
  • Hi, I am her colleague. Updated details in her absence.
    – Nidhi
    Commented Mar 18, 2014 at 21:24
  • I think it would be better to update the question and delete this answer. Commented Mar 18, 2014 at 22:18

2 Answers 2

4

Your issue is likely caused by duplicate file names. There's already a number of questions/answers on this website to help you resolve this:

Publishing failed in stage Committing Deployment SDL Tridion 2011 SP1 - HR1

Good luck

0

To begin with, ensure the following are true:

  1. All three javascript files inside the components have different file names (I am assuming you are not appending the TCMIDs to the filenames, while publishing)
  2. After un-publishing all three components, there is no file with the same name present at the CD environment (check File system or Broker DB depending on your configuration) for that particular publication.
  3. The publishing output package doesn’t have two or more files(JS, other) with the same name. (you can check the package directly on the deployer server OR use template builder to check the output)
1
  • Hi Saurabh,Thanks for your inputs.The approach has been tried but with no success in getting the actual file published.
    – user961
    Commented Mar 25, 2014 at 9:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.