Scenario:
Users browsing to a SharePoint site are faced with HTTP 404 response.
Solution:
In my case, there was a missing master page (deployed to the file system on the servers) which the site was referencing. This was because one of the solution was not installed on the farm.
To troubleshoot this issue, I followed the below procedure,
1. Download Process Monitor from technet systinternals website
2. Execute procmon on one of the web front ends. Include column username
3. Hit the site that return HTTP 404 error
4. Filter results in procmon window using specific username
5. Check for non-success results and you should see the file system access entries that will help understand point of failure.
Reference:
http://blogs.technet.com/b/chad/archive/2009/12/30/how-to-use-sysinternals-process-monitor-and-process-explorer-to-troubleshoot-sharepoint.aspx
Users browsing to a SharePoint site are faced with HTTP 404 response.
Solution:
In my case, there was a missing master page (deployed to the file system on the servers) which the site was referencing. This was because one of the solution was not installed on the farm.
To troubleshoot this issue, I followed the below procedure,
1. Download Process Monitor from technet systinternals website
2. Execute procmon on one of the web front ends. Include column username
3. Hit the site that return HTTP 404 error
4. Filter results in procmon window using specific username
5. Check for non-success results and you should see the file system access entries that will help understand point of failure.
Reference:
http://blogs.technet.com/b/chad/archive/2009/12/30/how-to-use-sysinternals-process-monitor-and-process-explorer-to-troubleshoot-sharepoint.aspx
No comments:
Post a Comment