SharePoint 2013 Redirect user to custom PageNotFoundError page

Replace default PageNotFoundError.aspx with Custom Error Page in SharePoint 2013
InfoPath alternatives for form designing SharePoint
Objective
In this article I would like to walk you through the process to change the default page not found error to user customized page not found error with user message.
Scenario:
You all might be thinking why user will get this scenario as page not found error below are the various scenarios:
– Page deleted by admin
– Change in URL of a hyperlink
The default page not found error will be rendered as below:
Replace default PageNotFoundError.aspx with Custom Error Page in SharePoint 2013
Replace default PageNotFoundError.aspx with Custom Error Page in SharePoint 2013
This might not be ok with every user and some want to show their own custom error page. Follow the below approach to change the default error page to a different with user requirement.
This we can achieve in 3 different ways:
1. Replace the default pagenotfounderror page
2. Update the default error page using PowerShell
3. Change the file not found error page in SharePoint designer

Replace default PageNotFoundError page in Pages library:

In SharePoint as soon as you enable publishing features you can see a default error page in Pages library with the path “<<Site URL>>/Pages/PageNotFoundError.aspx”.
Follow the below steps to change the default page:



1. Logon on to sharepoint site
2. Open Site content
3. Click on Pages Library
4. Delete the existing “PageNotFoundError” page
5. Create a new error page by clicking on “Error Page” option.
SharePoint 2013 Redirect user to custom PageNotFoundError page
SharePoint 2013 Redirect user to custom PageNotFoundError page

Update the default error page using PowerShell:

The issue or drawback with the above approach is we will be losing the default error page. We can update the default association of pageNotfoundError page using the below PowerShell commands to a custom or user defined page.
Create a custom page “userErrorPage” by following the steps 3 to 6.
SharePoint 2016 Redirect user to custom PageNotFoundError page custom filenotfound error page
SharePoint 2016 Redirect user to custom PageNotFoundError page custom filenotfound error page
Once you create the custom error page execute the below commands to change the default association.
Syntax:
$objSpSite = Get-SPSite “<<Web site URL>>”
$objSpSite.filenotfoundurl << This will show the existing file not found error page >>
$objSpSite.filenotfoundurl = “<<Custom error page URL>>”
custom filenotfound error page
custom filenotfound error page
Example:
$objSpSite = Get-SPSite “http://sharepoint13:12345/sites/vspsc/”
$objSpSite.filenotfoundurl = “/sites/vspsc/Pages/userErrorPage.aspx”
$objSpSite.filenotfoundurl
$objSpSite.close()
Replace default PageNotFoundError.aspx with Custom Error Page in SharePoint 2013 Tutorial
Replace default PageNotFoundError.aspx with Custom Error Page in SharePoint 2013 Tutorial

Change the file not found error page in SharePoint designer:



With the new Site Options in SharePoint Designer 2013, you can assign the vti_filenotfoundpage property of the site to a Custom Error Page that you might have deployed in the 15 Hive. Simply Open your Site in Designer and Under “Site Options” -> Parameters(tab) modify ‘vti_filenotfoundpage’ property to add a relative URL to your Custom error Page deployed in 15 Hive. See the Screen below.
SharePoint 2013 Redirect user to custom PageNotFoundError page Tutorial
SharePoint 2013 Redirect user to custom PageNotFoundError page Tutorial
SharePoint 2016 Redirect user to custom PageNotFoundError page Tutorial
SharePoint 2016 Redirect user to custom PageNotFoundError page Tutorial

The output will be as follows:

custom filenotfound error page Tutorial
custom filenotfound error page Tutorial

Hope this helps, happy development in SharePoint !!!!

Similar SharePoint 2013 Tutorials

About Krishna Vandanapu

I am Krishna.Vandanapu a SharePoint architect working in IT from last 12 years, I worked in SharePoint 2007, 2010, 2013, 2016 and Office 365. I have extensive hands on experience in customizing SharePoint sites from end to end. Expertise in SharePoint migration tools like Sharegate, Doc Ave and Metalogix. Migrated SharePoint sites from SharePoint 2007 to 2010 and 2010 to 2013 several times seamlessly. Implementing CSOM with Microsoft best practices. Spent quality time in configuring SharePoint application services like User Profile, Search, Managed Meta data services etc. Now exploring SharePoint Framework and SharePoint 2019

View all posts by Krishna Vandanapu →

Leave a Reply