Article ID: 2484317 - View products that this article applies to.
On Microsoft Office SharePoint Server 2007:
You have installed the Dutch language pack. You created a publishing portal with SubSites and additional pages.
You want to migrate the content database to Microsoft SharePoint Server 2010 and attach the database to a new Web Application.
When you navigate to the homepage of the given Web Application you will see an error (Fout) and the navigation is not usable.
With Microsoft Office SharePoint Server 2007 we stored new Publishing Pages in a library called Pages. In SharePoint 2010 it has been translated to Paginas as the default for Dutch. The navigation code assumes that any changes from the default are noted in a specific property, which is not the case for upgraded Dutch sites that have been created with the 2007 default name.
You need to set a particular property to the right value. To accomplish this start SharePoint Powershell and use the following script:
$site = Get-SPSite("http://WebApplicationURL
foreach ($web in $site.AllWebs)
Write-Output("web:" + $web.ServerRelativeUrl);
$pageslistid = $web.AllProperties["__PagesListId"]
Write-Output($web.ServerRelativeUrl +" doesn't have a pages list id set - skipping");
$pageslistguid = new-object System.Guid($pageslistid)
$pageslist = $web.Lists[$pageslistguid]
$pagesurl = $pageslist.RootFolder.Url
$pb = $web.Properties;
Write-Output($web.ServerRelativeUrl +" set pages list to " + $pagesurl);
If you want to disable the Publishing feature for any reason and it will not be enabled again you can use the following workaround instead.
Adding a document-library called ‘Paginas’ to the web (subsite) on which you tried to activate the feature again. After that you may remove the temporary document library.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2484317 - Last Review: January 11, 2011 - Revision: 4.0