Forum Discussion
Personalize WebPage - Access Denied CU 16.0.19725.20522 KB 5002893
Hello,
with the current CU August 2026 (2016/2019/SE) users can't "Personalize this Page" (old layout 2010). After the user takes the action "Edit my WebPart" it redirects to Access Denied page.
The user needs the right to the site "Add and Customize Pages"; this is not an option.
Permission check failed. asking for 0x40000, have 0x1b03c4312ef
Access Denied. Exception: Attempted to perform an unauthorized operation., StackTrace:
at Microsoft.SharePoint.SPSecurableObject.CheckPermissions(SPBasePermissions permissionMask)
at Microsoft.SharePoint.WebPartPages.ToolPane.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at Microsoft.SharePoint.WebPartPages.WebPartPage.CreateToolPane(Control ctrl)
at Microsoft.SharePoint.WebPartPages.WebPartPage.ToolPaneCreationAndInitialization(HtmlForm form, WebPartDisplayMode displayMode)
at Microsoft.SharePoint.WebPartPages.WebPartPage.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.DEFAULT_ASPX_337397335.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) .
1 Reply
The trace shows that the patched ToolPane now checks Add and Customize Pages, whose permission mask is 0x40000. Because that permission allows classic-page changes, granting it to ordinary contributors is unsafe. First confirm the August cumulative update is installed on every SharePoint server, reboot where required, and complete the build-to-build upgrade with the SharePoint Products Configuration Wizard or PSConfig on every server. Verify the farm reports no upgrade-required servers or databases. Reproduce the issue on a clean classic Web Part page with an unchanged built-in permission level, then capture the ULS correlation ID and compare behavior before and after the CU in a nonproduction farm. If the clean reproduction persists, treat it as a CU regression and open a Microsoft support case referencing KB 5002893, build 16.0.19725.20522, the permission mask, and ULS trace. Avoid editing web.config, replacing binaries, or broadly adding 0x40000 while awaiting an official fix.
