On a fully working 2013 SP1 dev environment, we have just installed the legacy pack and upgraded a legacy CM database containing VB script templates. We have replaced the legacy event system with a .NET rewrite, which consists of an Events dll and a referenced Common dll (which in turn references log4net.dll) all of which sit in the Tridion/bin folder and the Tridion/webservices/bin folder.

After shutting down the Tridion COM+ process, when I preview a page which uses a VB script template, I get an error:

Error: Could not load file or assembly 'Example.Project.Common, Version=, Culture=neutral, PublicKeyToken=abcdefghijklm' or one of its dependencies. The system cannot find the file specified.

Note that this error is only shown in the GUI and not in the Tridion event log.

If I ignore the error and re-run the preview, it works fine. It also works fine if I disable my .NET event system. Previewing Modular templates works fine, and also my events are all executed just fine. On another environment without the legacy pack, I never see this error (but I dont have any VB script templates on that environment, so I cannot reproduce the same conditions).

This all seems properly weird to me as the preview does not have anything to do with the event system (no events are triggered when previewing). Does anyone have any clue as to what might be happening here???

1 Answer 1


I managed to workaround the problem by putting the referenced assemblies in the GAC. I am not sure exactly what the problem is, but it seems that when a VB Script template is executed it can trigger the event system to be loaded, but in a different way (under a different process and user - the COM+ user) to normal, which might lead to problems loading referenced assemblies. I guess my advice from the troubleshooting is to use the GAC for referenced assemblies, as otherwise you could be chasing round in circles for ages trying to work out why things aren't loading properly

  • The Legacy pack also adds the Legacy Event Adapter, maybe that triggers the loading of your event in combination with your VB script templates, although that should not touch the .NET event DLL... I agree it is wierd... Commented Mar 13, 2014 at 16:13

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.