SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I made a configuration change to my SharePoint 2010 Web Application (earlier question) that enabled Anonymous access and now my site returns 404 errors!? Even when I change the setting back it does not resolve the error. To make matters worse now my Central Admin site returns the same 404 error. Looking at the source for the 404 error page I see an HttpError...CheckSuspiciousPhysicalPath.

Any ideas on how to debug this would be great.

share|improve this question
up vote 1 down vote accepted

For 404's I generally check this

  • Can anyone else access the page?
  • Is the master page published?
  • does the user have permissions to the user page?
  • Is the page layout published?
  • does the user have permissions to the page layout?
  • any other resources, such as controls (ASCX) not available to the user with 404's

For anonymous sites I will most often solve it after verifying publishing status and permissions on the master page.

share|improve this answer

My tools of choice for this would be Fiddler, to see what is going on at the HTTP level, and Process Monitor to see what happens on the file system.

share|improve this answer

Havent tried it, but I saw this trick for SharePoint 404's:

share|improve this answer

Yeah View Source when you see that error and the stack trace will usually point you directly to the control or reference that's missing.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.