Cannot create Variation site because the parent Publishing web cannotbe found. Ensure the parent Publishing web has been spawned and tryagain

To create a child variation to root variation we create a new label under Variation Labels [http://newServerName/_Layouts/_Layouts/VariationLabels.aspx] and after this click on Create Hierarchies button on this page. 

When timer job "Variations Create Hierarchies Job Definition" runs , it tries to create the child variation site including subsite of child variations. This also includes publishing Pages Library and publishing pages.
Current status can be verified under Variation Logs[http://newServerName/_Layouts/VariationLogs.aspx]
I was trying to use timer job "Variations Create Hierarchies Job Definition" to create a child variation [es-LA] to root variation[en-US] .

But I was getting error (under Variation Logs) :

A new site sub1Site1 did not get created under Label es-LA by the variation system for source site http://newServerName/en-US/sub1Site1. Cannot create Variation site because the parent Publishing web cannot be found. Ensure the parent Publishing web has been spawned and try again.
AND

Pages did not get created under Label es-LA by the variation system for source publishing web http://newServerName/en-US/sub1Site1 because the target publishing web cannot be determined.

Below mentioned solutions did not work for me :

1. Fix the possible misalignments like problem in the relationships list[http://newServerName/Relationships List/AllItems.aspx] using VariationFixUpTool.
2. In the SharePoint file C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Resources\cmscore.es-ES.resx (installed by the language pack for Spanish)

Change the value of List_Pages_UrlName as seen below

<Data Name="List_Pages_UrlName">

<Value>Pages</Value>

</Data>

to

<Data Name="List_Pages_UrlName">

<Value>Paginas</Value>

</Data>

Save the file. Now go and restart the SharePoint 2010 Timer service. Then create the Spanish Variation.  [

Eventhough "List_Pages_UrlName" solution did not work for me for this specifc problem , but with Spanish sites you get funky behaviour out of URLS retrived from Microsoft.SharePoint.Publishing.PublishingWeb.PagesList SPobjects ,
you can give it a try !!!!]

Below mentioned solution worked for me :
1. Disable all custom built features on root variation. (spweb level features)
2. Now create new Label , submit variation creation on Variation Labels and run timer job "Variations Create Hierarchies Job Definition".
3. I was still facing issue 0x80070057 which is discussed here as a separate thread.
4. After resolving issue 0x80070057 , child variation was created.
5. Now enable all custom built features on both root variation and child variation.





0x80070057
Access "Pages" Library for Chinese Locale

Few Questions to be answered before you start a SharePoint project

Few Questions to be answered before you start a SharePoint project:

1. Are you looking for a public facing site or an intranet portal? Do you need subset of information available on intranet to be published to outer word? Do you want to develop a portal as one stop solution for whole organization or it will be in parallel with various other system with scattered information e.g. user profiles , etc.


2. What are the maximum users we want to target in next 5 years?


3. Do you want to pre-plan for multilingual scenarios?


4. The user policies and permission must be strictly defined well ahead and direct access (without SharePoint user groups) to content must be eliminated. Owners who define will manage the security must be clear and precise and well trained how to manage security in SharePoint.  Administrators and owners, who don’t know how to manage security, are the biggest loop holes in the security chain.


5. Ownership of servers and management is a pain in butt at later stages, so must be documented and defined during initial stages.


6.  Read only search accounts must be predefined. Using administrators as search accounts is a big security loop hole.


7. Security patches and Upgrades for Windows Servers SharePoint SQL must be scheduled and monitored.  Blocking them forever is inviting hackers to dump the system.


8. Antivirus scans are often ignored during planning stages. Never do that.


9. It must be defined clearly what all need to be blob cached and duration of caching must be precise and documented. According front end server configuration might have to be changed. You may never want to blob cache secured contents.


10. To avoid more expenditure on future upgrades maximize utilization of out of box features of SharePoint.


11. You may never want to expose underlying framework information through headers . Plan for that during initial stages , if it is a public facing site .


12. You may want to rely on Google analytic to understand Visitor flow and improvise the site accordingly during later stages . Plan for this .


13. What might be the external systems from where information flows in or goes out of SharePoint future system . Plan security and minimize / define  and document the limitations .


14. Do you want to go for automatic TFS / 3rd party deployments or want a more controlled deployments with dedicated administrator ?


15. Have you take sign off on all the relevant SharePoint features to be accommodated in the ecosystem with capacity planning and infrastructure involved to avoid performance hits at later stages ?

You are requested to add more here as comments based on what you had to go through in your previous projects  . 

You may also like:
MOSS 2007 Troubleshooting Guide