Prev: Search problems - WSS 3.0
Next: ASP.NET Profiles not working in Sharepoint 3.0
From: Justin on 16 Dec 2006 11:50
After performing an in place upgrade from WSS 2 (with hotfix KB915746
installed) to WSS 3, Any time I try to access any unghosted page I
receive this error message: "Error Access Denied ... You are currently
signed in as MYDOMAIN\...."

Anyone in the farm administrator's group can access the unghosted pages
and they all work properly, but no one else can.

I've tried removing and readding users and I still receive the same
error message. I've tried adding users that never had access to the
site and I receive the same message. In every case all the users can
access all the pages on the site they should be able to except for
those pages that were unghosted at the time the upgrade took place.

Has anyone else had success keeping unghosted pages during the upgrade?

Thanks,

Justin

P.S. This is the second time I've attempted the upgrade and ran into
the same issue. Prior to trying this upgrade I reghosted 1 page with
ReGhost.Net and access to that page works just fine in the new site.
If you are willing to give up any functionality you added by unghosting
pages you can download ReGhost.Net at:
http://www.gotdotnet.com/workspaces/workspace.aspx?id=6eff7d8a-92ee-4525-a625-b592bb9d0c95

From: Justin on 17 Dec 2006 10:15
Update: The problem wasn't unghosted pages at all, it is a custom web
part that queries the database and then prints out a list of all the
sites the user has access to. The part runs fine under the farm
administrator account, but if another user tries to access a page with
the part the whole page comes back as this error message: "WSS3 Error
Access Denied ... You are currently signed in as..." Other custom web
parts (such as reset AD password) run just fine.

Any ideas?

On a side note, after using ReGhost.Net on all my pages, the WSS3
prescan tool still counts all of those pages as unghosted.

Thanks,

Justin

From: Justin on 17 Dec 2006 23:55
Still searching for an answer why farm administrators can view a page
with the webpart and others can't. I found this info in the log:
"Potentially excessive number of SPRequest objects (9) currently
unreleased on thread 9."

The web part recurses through the site hierarchy and returns all the
sites a user has access to. Perhaps the server is blocking this
"potentially excessive request" for everyone but farm administrators?

Thanks for any help you can offer.

Justin

12/17/2006 23:41:26.73 w3wp.exe (0x1470)
0x108C Windows SharePoint Services General
0 Medium Potentially excessive number of SPRequest objects (9)
currently unreleased on thread 9. Ensure that this object or its
parent (such as an SPWeb or SPSite) is being properly disposed.
Allocation Id for this object: {6B4F59CA-6E88-48C1-BDA4-1D58B2D58C00}
Stack trace of current allocation: at
Microsoft.SharePoint.SPRequestManager.Add(SPRequest request, Boolean
shareable) at
Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(Boolean
bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[]
UserToken, Boolean bIgnoreTokenTimeout, Boolean bAsAnonymous) at
Microsoft.SharePoint.SPWeb.InitializeSPRequest() at
Microsoft.SharePoint.SPWeb.EnsureSPRequest() at
Microsoft.SharePoint.SPWeb.get_Request() at
Microsoft.SharePoint.SPWeb.InitWeb() at Microsoft.S...
12/17/2006 23:41:26.73* w3wp.exe (0x1470)
0x108C Windows SharePoint Services General
0 Medium ...harePoint.SPWeb.get_WebTemplate() at
HierarchicalSiteAccessWebPart.HierarchicalSiteAccess.EventWay.Traverse(SPWebCollection
wc, Int32 level) at
HierarchicalSiteAccessWebPart.HierarchicalSiteAccess.PopulateDataTable(String
UserName) at
HierarchicalSiteAccessWebPart.HierarchicalSiteAccess.CreateChildControls()
at System.Web.UI.Control.EnsureChildControls() at
System.Web.UI.Control.PreRenderRecursiveInternal() at
System.Web.UI.WebControls.WebParts.WebPart.PreRenderRecursiveInternal()
at System.Web.UI.Control.PreRenderRecursiveInternal() at
System.Web.UI.Control.PreRenderRecursiveInternal() at
System.Web.UI.Control.PreRenderRecursiveInternal() at
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncP...
12/17/2006 23:41:26.73* w3wp.exe (0x1470)
0x108C Windows SharePoint Services General
0 Medium ...oint) at System.Web.UI.Page.ProcessRequest(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest() at
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context)
at System.Web.UI.Page.ProcessRequest(HttpContext context) at
System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step,
Boolean& completedSynchronously) at
System.Web.HttpApplication.ResumeSteps(Exception error) at
System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext
context, AsyncCallback cb, Object extraData) at
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
at S...
12/17/2006 23:41:26.73* w3wp.exe (0x1470)
0x108C Windows SharePoint Services General
0 Medium
...ystem.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)
at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32
iWRType)

 | 
Pages: 1
Prev: Search problems - WSS 3.0
Next: ASP.NET Profiles not working in Sharepoint 3.0