Activating SharePoint Server Publishing Infrastructure. Error on PortalSiteMapProvider

Question

Hello,

After upgrading a SP2007 to 2010. Everything seems to work perfectly, except after activating SharePoint Server Publishing Infrastructure on site collection level. The application web is claim based authentication using Forms.

The error says:

Web Content Management Publishing Unexpected PortalSiteMapProvider was unable to fetch current node,
request URL: /default.aspx, message: Se produjo una excepción de tipo 'System.ArgumentException'.
Nombre del parámetro: encodedValue, stack trace: en
Microsoft.SharePoint.Administration.Claims.SPClaimEncodingManager.DecodeClaimFromFormsSuffix(String encodedValue) en
Microsoft.SharePoint.Administration.Claims.SPClaimEncodingManager.DecodeClaim(String value) en
Microsoft.SharePoint.SPUserToken.GetClaimsUserLoginName() en
Microsoft.SharePoint.SPSite.CopyUserToken(SPUserToken userToken) en
Microsoft.SharePoint.SPSite.SPSiteConstructor(SPFarm farm, Guid applicationId, Guid contentDatabaseId, Guid siteId, Guid siteSubscriptionId, SPUrlZone zone, Uri requestUri, String serverRelativeUrl, Boolean hostHeaderIsSiteName, SPUs... 81bbf9eb-ea33-4d22-9fdc-6e428bcb8adb

I don't know where is the problem. Does anyone has a idea? please I'm very frustrated

Answer 1

If you have migrated on the same  application, you can give that error and errors certifications,
as has happened to me and the experience has led us to load it into another
application new rules also configure permissions again. According to what to
investigate when I had that problem when it goes from classic to claims is irreversible
incompatibility. and similar replies to this forum.

I only recommend you if you've done on the same application you make to a new
application.

Answer 2

If you have migrated on the same  application, you can give that error and errors certifications,
as has happened to me and the experience has led us to load it into another
application new rules also configure permissions again. According to what to
investigate when I had that problem when it goes from classic to claims is irreversible
incompatibility. and similar replies to this forum.

I only recommend you if you've done on the same application you make to a new
application.

Hi Marco,

thanks for response but I have migrated to a new web application. I've followed this steps.
To configure a new FBA web application I've followed this steps.
And finally I've executed this instruccions on PowerShell:

$wa = get-SPWebApplication $WebAppName
$wa.MigrateUsers($true)

Do you think there is another action I must to do?

Thanks for all

Answer 3

Hi Jordi,

One thing when you created the application you made in classic and after the change??

The application the got involved in new pool

is that we gave a similar need to create all new and just attach the database is the most appropriate migration of database attached.

test new pool and port.

regards

MC