Share via

SharePoint Server error when opening Page Layouts: “The server could not complete your request” (500 error, webpartpages.asmx)

Deval Katherina 60 Reputation points
2026-02-03T05:00:03.94+00:00

We are encountering a server-side error in SharePoint Server when attempting to access Page Layouts (e.g. WelcomeLinks.aspx) from SharePoint Designer.

When clicking or opening a page layout, SharePoint Designer shows the error:

The server could not complete your request

Error detail:

Module: ManagedPipelineHandler
Notification: ExecuteRequestHandler
Handler: ScriptHandlerFactory
Error Code: 0x00000000
Requested URL: http://<site>/_vti_bin/webpartpages.asmx
Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\isapi\webpartpages.asmx
Logon Method: Federated Logon
Logon User: <User>

SharePoint 2013 Designer issue: Server could not complete ...

User's image

The request results in an HTTP 500. The physical path exists on the server, and the user has sufficient design permissions. The issue reproduces consistently and appears to be server-side, not client-related.

What are the common root causes of webpartpages.asmx returning 500 errors when accessing Page Layouts, and which logs or configuration areas should be checked to troubleshoot this issue effectively?

Microsoft 365 and Office | SharePoint Server | Development
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Teddie-D 12,335 Reputation points Microsoft External Staff Moderator
    2026-02-03T06:10:13.8233333+00:00

    Hi @Deval Katherina 

    Thank you for posting your question in the Microsoft Q&A forum. 

    Please note that this is a user-to-user support forum. Moderators, contributors, and external Microsoft employees do not have access to back-end systems to investigate root causes. Our role here is limited to sharing technical guidance based on publicly available resources and experience. 

    From my findings, a 500 Internal Server Error is a generic IIS or HTTP status that indicates the server encountered an unexpected condition and could not provide more specific details. Because the error is server‑side, start by reviewing the ULS logs and Event Viewer for error entries. 

    In SharePoint, common causes of this error include:  

    -The Web config file might have been modified in an incorrect format.  

    -The SharePoint Application Pool stopped.  

    -The Security Token Service Application Pool stopped.  

    For step-by-step troubleshooting, you may find these resources useful: 

    Note: Microsoft is providing this information as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link. 

    I hope this information is helpful. 

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.