Wednesday, 10 February 2010

SharePoint 404: The resource cannot be found

If a page element is missing—either a user control hasn’t been deployed or something else that needs to be in place for the page to compile dynamically is awol—you might be the proud owner of a 404 even though the page itself does exist.

HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.

After setting the SafeMode element’s CallStack element true in web.config, turning off CustomErrors, and setting the debug=”true” attribute on the compilation element, you’re possibly looking at a beautiful ASP.NET error message with no stack trace and not a lot to go on.

Well here’s a trick: view source on the error page and and scroll down below the closing HTML tag. Behold the stack trace! It should tell you exactly where to look for the problem.

15 comments:

  1. Fuckin awesome!

    ReplyDelete
  2. That's gold. Just helped me work out a master page issue.

    ReplyDelete
  3. Great discovery... thanks for sharing!!

    ReplyDelete
  4. Thankyou! Now I just have to figure out why we're missing welcome.ascx and all's sorted ;o)

    ReplyDelete
  5. @Anonymous: Want my guess? A user deleted it... been there, done that! ;-)

    ReplyDelete
  6. yes thank you very much great article

    ReplyDelete
  7. Thank you for sharing this!

    ReplyDelete
  8. Great! Helped me a lot

    ReplyDelete
  9. Love it ... thanks ..

    ReplyDelete
  10. This has to be THE BEST SHAREPOINT TIP I have had! Thank you so much - it's saved me huge amounts of time!

    ReplyDelete
  11. Wow.... thanks!

    ReplyDelete
  12. Awesome mate!
    Great tip!

    ReplyDelete