Stefan Goßner

Senior Escalation Engineer for SharePoint Products and Technologies

Some comments on common Variation problems (last updated: May 21st, 2008)

Some comments on common Variation problems (last updated: May 21st, 2008)

  • Comments 26
  • Likes

Jeremy Jameson created an article series which talks about serious problems he ran into when using the variation feature. Unfortunatelly I cannot comment his articles directly as he disabled anonymous comments - and my blog is not on MSDN but on TechNet so I cannot login in MSDN so I have to provide my comment here.

1) Incompatibilty between OOTB variation feature and OOTB content types

The correct solution for this problem is to create a custom site definition template which already uses the correct content types. Adjusting the content type of a page will indeed lead to problems in the content deployment and migration API which is used by the variation feature.

A custom site definition template should be defined for all customized sites and the site should then be propagated with this site defintion template rather than adjusting the content type afterwards.

Background info on the problem: when propagating a site through the variation feature the site definition template used to create the source site is used to create the destination site. This means the default.aspx page will be created based on the content type in the site definition. When later the variation features trys to pair up the pages in the source label with the pages in the destination label it sees the different content types and this causes the problem.

Using a custom site definition that has the correct content type for the default.aspx configured will avoid this problem - and will also reduce the overhead for authors as they don't have to change the content type for the pages over and over again.

2) Enabling of content types on destination labels

Jeremy complains that the variation feature does not enable content types on the Pages library in other labels. This issue has been identified as problem in MOSS 2007 and a hotfix for this issue is currently in the works and should be available short after release of Service Pack 1.
[Update 2008-02-19] The fix for this issue has been included in Service Pack 1

3) Performance Problems when populating the variation

This has been reported by a couple of customers and the product group is currently investigating the issue. Additional indices as outlined in the article are currently not supported as already mentioned by Jeremy.
[Update 2008-05-21] Two hotfixes for this issue have meanwhile been released as KB 952698 and KB 952704. Both hotfixes are required to address this issue.

4) Attempting to create a new variation label after creating a large number of sites and pages results in an out-of-memory error on the server

This issue has been identified as a problem in MOSS 2007 and a hotfix for this issue is currently in the works.

Background info: we identified that the variation feature holds SPSite/SPWeb/PublishingWeb objects of opened sites during the propagation for caching purposes. At the end these objects are properly disposed but if many sites have to be propagated the amount of memory can be to much on 32-bit machines. On 64-bit machines with more virtual memory per process this problem would not cause the variation feature to fail. The hotfix being developed will address this as it will dispose the SPSite/SPWeb/PublishingWeb objects earlier and if required recreates them later rather than caching them in memory.

Be aware that contrary to the statement from Jeremy only part of this change will be included in SP1. To completly address this issue you need the hotfix which will be available shortly.
[Update 2008-02-19] The hotfix for this issue has meanwhile been released as KB 941274

  • PingBack from

  • How can I programmatically add content type to list of available content types? I am trying to fix up already confirmed bug in variations that don't associate content types with page libraries in destination variation sites.

  • Thanks for the update! I ran into a lot of issues regarding variations but also found solutions. Posted on

  • Jeremy Jameson has blogged about his adventures in variations. Allthough I don't agree with everything,

  • Jeremy Jameson has blogged about his adventures in variations. Allthough I don't agree with everything

  • Shortly before I headed out to the airport last Wednesday, I received the fateful email from my customer

  • In part 1 and part 2 of this series, I talked about some major issues with the variations feature in

  • I've received a number of responses to my series on the problems we encountered with Microsoft Office

  • I've received a number of responses to my series on the problems we encountered with Microsoft Office

  • It appears that number 2 above still have some problems.

    My logs return a The variation system failed to pair up pages

    because their Content Types do not match. We have SP1 installed, and we have the language packs installed.

  • Hi SPMike,

    if you already have incorrect content types in your system then you will see this.

    But it should not happen for new pages.



  • Hi,

    I created a Variation label and created hierarchies for Arabic version of my portal, now I can see 2 home page tabs and one more tab for Arabic version portal. Now I just want to delete what I created. How can I delete? any ideas? And want to  inform you one thing, home page of my portal has been changed to the Arabic version. please do needful..



  • Hello Gary,

    It was an awesome post.

    I have a few confusions, I hope you would be able to help.

    I have the site collection already created. The pages are customized. The site is huge, so have to enable variations on the same site.

    1. For customized pages, is it necessary to write customized site definitions and propagate using those definitions. Is it possible in my case.

    2.Its a huge site, is there a way to do variation on it step by step i.e. taking a few sites at one time etc.

    Thanks for sharing!

  • Hi Gary,

    1) you would have to create the site definitions BEFORE the sites are created. Not afterwards. As your content already exists it is to late to change the site definitions if you don't want to recreate all content. In addition this is only necessary if your default pages in the site have to be of a different content type/page layout. If the default content type/page layout is ok, then there is no need for a custom site definition.

    2) yes. You can disable automatic propagation of the sites and pages. Then you can create the variation for each item/site manually



  • Thanks for your cooperation Stefan,

    But Im a little confused about creating variations manually per item/stie.

    Scenario is that we have the site restored as a backup, which is the english(en) version, and is acting as a source.

    How can I create hierarchies out of it per item/site?

    If this is possible life's gonna be different :).

    Thanks for your help.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Raw Html Fix