SharePoint 2013

Get 404 Status Code from Custom Error Page.

Scenario We had to figure out how many pages in our site are broken (throwing 404 status code). But the problem was that we implemented a custom designed error page for broken ones. This page was designed in the context of site look and feel, so we associated the site master page as well with this Get 404 Status Code from Custom Error Page.

Resolved: An unexpected error with a provider-hosted app for SharePoint

Scenario: You developed and hosted an ASP.NET  MVC site on IIS and planning to consume this provider-hosted app in SharePoint. When accessing standalone, the MVC site is working fine but when installing and called from SharePoint, it throws an error “An unexpected error has occurred. Please try again by launching the app installed on your Resolved: An unexpected error with a provider-hosted app for SharePoint

SharePoint Best Practices : Part 1

Create SQL Server Alias in SharePoint Farm Recently we ran in to a problem, where our production application suddenly started throwing 502 errors due to performance degradation. After analyzing few things, we suspect that our database server has some problems. As this was a production server and we didn’t want to keep this problem for SharePoint Best Practices : Part 1

SharePoint search is returning 500 internal server error page : Resolved

Recently i was working on a Intranet Portal and most part of it was based on documents collaboration. So to easily find a document i configured search for the site. I created a new content source in existing search service application and crawl the source. It was crawled successfully without showing an error or warning, SharePoint search is returning 500 internal server error page : Resolved

Remove orphan feature(s) entry from SharePoint’s ManageFeatures.aspx

At times we need to get rid of feature(s) from SharePoint farm, those are no longer required. This is kind of cleaning and managing your SharePoint Farm. Most of the time due to inappropriate procedure or by using a 3rd party tool, Feature gets removed but it still displays on Feature.aspx page. When you try Remove orphan feature(s) entry from SharePoint’s ManageFeatures.aspx