I have a multilingual SharePoint site which uses variations. However on deployment the content isn't being deployed to the other variation sites. When the "Variations Propagate Sites and Lists Timer Job" timer job runs I get the following error in the logs:

The type 'Example.Fields.ExampleFieldType, Example, Version=, Culture=neutral, PublicKeyToken=2a41e5afbfa097d1' could not be deserialized. Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Example, Version=, Culture=neutral, PublicKeyToken=2a41e5afbfa097d1' or one of its dependencies.

Field type Example is not installed properly. Go to the list settings page to delete this field.

I've checked multiple times and the full name of the field is definitely correct. The field works fine in the root site and the assembly is definitely in the GAC as it's being used in the deployment.

Has anyone had any experience with this? Has anyone got variations working with custom field types. Could something be wrong with my field. I can't see anything untoward about it. It's just a MultiColumn field.

Any ideas would be greatly appreciated.

  • Is there a site feature that adds this column? Do you need to add the feature to the variation label sites? Nov 15, 2013 at 15:11
  • I don't think so. Field types are defined globally in fldtypes_*.XML file. The site column is added with a feature but that's at the site collection level above the variation site. The "could not be deserialized" bit makes me think that it's working properly but is having issues finding the type for some reason...
    – Dan Hayman
    Nov 15, 2013 at 15:40
  • Is the feature Web or Site scoped? (Site Features or Site Collection Features to activate it) Nov 15, 2013 at 16:14
  • It's a site feature activated on the site collection
    – Dan Hayman
    Nov 15, 2013 at 21:38

1 Answer 1


If anyone else ever has this issue. It turns out that restarting the timer job after uninstalling the old solution stops it happening. I'm not quite sure how it knew the assembly was different as though the code and assembly version were the same.

net stop SPTimerV4
net start SPTimerV4



And no more problems.

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.