This page can't be displayed SharePoint

Question

I have a SharePoint 2019, and  I tried to create a new web application from SharePoint central administration by clicking on the New Button. I filled in the web application info and clicked Ok, the dialog started to create the new application but suddenly it stopped and show this error message

SharePoint Central Administration: This page can't be displayed 

I noticed that the web application is created but I can't create a new site collection and I got this error message

Sorry, something went wrong: This page has encountered a critical error.
Contact your system administrator if this problem persists.

Please guide me to solve this error?

Thanks

Answer 1

SharePoint Central Administration: This page can't be displayed

I have encountered this issue before in SharePoint 2013 due to the lack of resources and high consumption of the CPU and memory on the server.

To solve this issue, you should do the following:

• Check the Processes tab in Task Manager and make sure that there is no process that consumes more resources, then end task for unrequired processes.

• As a workaround, try to increase the Shutdown Time Limit for the application pool of the central administration.

  • Open IIS > Application Pools.

  • Right-Click on the Central Administration Application Pool and select Advanced Settings.

    

  • At Process Model, Increase the Shutdown Limit (Seconds) to 1000.

    

  • Open CMD as Administrator, and Perform IISRESET.

    

  • Try now to create a new web application that should be created successfully.

    Don't forget to delete the web application that stuck on the creation.

• In the end, if the above suggestions don't help you, so you may need to scale up the server resources If your current server specification doesn't match the recommended hardware for SharePoint 2019.

---

See Also

• New web application button was grayed out within Central Administration in SharePoint.
• The server was unable to save the form at this time SharePoint 2016

Comments

The IIS setting helped me to solve this error, thank you