5

We have a Tridion 2013 SP1 installation, with workflow enabled in PROD but not in DEV or UAT.

I uploaded a new version of an existing DLL using TcmUploadAssembly.exe (verbose; to the right folder) and it looked successful. This was uploaded using the same .BAT that we used in DEV and UAT, except for changes in the server name and the folder ID. A new class TBB was created for the new class that was in the DLL. All of the previous classes showed as well.

We published a component that used that new class. It worked in DEV and UAT, but in PROD it gave an error that the class reference didn't exist (I'll post the specific error in an update).

I retrieved the DLL from the CMS, compared it to the compiled DLL, and that new class did not exist in the one retrieved from the CMS.

I uploaded the DLL a second time, using TcmUploadeAssembly.exe, and downloaded it again, and the class still didn't exist. This was after confirming the path in the .BAT file and all of the other parameters.

When I uploaded the compiled DLL using the CMS, and then downloaded it again, the class did exist.

Has anyone seen an issue where a class wouldn't exist (it looks like it was removed; even the file size was smaller) when uploaded with TcmUploadAssembly.exe, but would exist with uploading the DLL through the CMS?

Improve this question
2
  • Paul, did you confirm that the BAT file ran on the PROD environment without errors? can you see the version of the dll being incremented after running this BAT file ? What happens if you try to run this BAT file to upload the DLL to a new folder ? Does the newly created assembly contain the functions or not ?
    – Harald Hoffelinck
    Mar 14, 2018 at 8:32
  • Alternatively, Try uploading the DLL directly onto existing TBBs assembly item by manually in CMS to test?
    – Velmurugan ♦
    Mar 14, 2018 at 15:32

1 Answer 1

Reset to default
4

Believe me, the upload tool doesn't analyze your DLL and decide to drop classes at random :)

I can think of two possible explanations for this:

  1. The tool didn't actually work and so your TBB wasn't ever updated. You should check the output to see if there are any errors (run it with /verbose for more details) and verify that you specified all of the right parameters.
  2. The TBB was checked out at the time of the update and couldn't be checked back in. So when you used the TBB, it loaded the previously checked-in version instead of your updated one. Check the versioning history to see what happened (try it again if needed).
Improve this answer
2
  • To answer the questions:
    – Paul Russell
    Apr 4, 2018 at 16:50
  • 1) Yes, the .BAT file completed without error. The classes, including the TBB itself, were not checked out or in any way locked; 2) I did not try it in to a separate folder. I'll do that, should this present itself again 3) I did use the CME to upload it, and then it contained the class 4) The tool appeared to work; as in - there were no error messages. I did not check the version numbers. I'll check the version history. It seems that the previously uploaded DLLs are unavailable though (this is a completely different issue)
    – Paul Russell
    Apr 4, 2018 at 16:57

Your Answer

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

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