Wednesday, August 13, 2008 12:51 PMWe are in the process of moving over local development to a live server for a public facing site. One problem we have is Manage Content and Structure returns a "Not found" error while logged into sharepoint remotely browsing the site. It does work when on remote desktop browsing locally so it leads me to believe it is a permission problem. I've gone through and set any sharepoint/iis permissions I can think of on this folder with no luck. Any suggestions? Full error is below:
File Not Found. at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken userToken)
at Microsoft.SharePoint.SPSite..ctor(String requestUrl)
at Microsoft.SharePoint.Publishing.Internal.VariationSettingsFactory.GetCachedVariationSettings(String requestUrl, Boolean elevatedSite, HttpContext httpContext)
at Microsoft.SharePoint.Publishing.Internal.VariationSettingsFactory.CreateVariationSettings(String requestUrl, Boolean elevatedSite)
at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.SharePoint.Publishing.Internal.WebControls.EcbEnabledTreeNode..ctor(EcbEnabledTreeView owner, PublishingWeb area)
at Microsoft.SharePoint.Publishing.Internal.WebControls.SmtTreeNode..ctor(EcbEnabledTreeView owner, PublishingWeb area)
at Microsoft.SharePoint.Publishing.Internal.WebControls.SMTreeView.CreateNode(PublishingWeb area, EcbEnabledTreeNode parent)
at Microsoft.SharePoint.Publishing.Internal.WebControls.EcbEnabledTreeView.OnLoad(EventArgs e)
at Microsoft.SharePoint.Publishing.Internal.WebControls.SMTreeView.OnLoad(EventArgs e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Tuesday, November 18, 2008 3:53 AMI encountered the same problem. The culprit was a master page located at the root of the site. I deleted the master page with sharepoint designer, and the problem went away.
Wednesday, July 22, 2009 12:10 PMHi,
I'm having the same problem... How did you manage to solve it? (I haven't any MasterPage at the root of the site, mine is located in my http://<mysite>/_catalogs/masterpage/ folder.
Wednesday, January 13, 2010 3:48 PMHello!!!
I have the same issue..please can you let me know..how did you get it working...
Wednesday, January 13, 2010 4:57 PMHI,
Could you please describe your AAM, this problem faced me but i discovered that my AAM didnot configured properly.
Best Regrads, Ahmed Madany
Friday, May 14, 2010 3:59 AM
Checkout the following link. I had the same problem and it fixed it. In my case I was using a dns alias. As soon as I started using the actual server name, I didn't get the error.