The resource cannot be found. (Off and On)

[tlhawkins]

I'm having a really annoying problem with this error:

Description: 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.

The site has worked just fine for a long time but recently it has started giving this error. It's only on one page (that I've seen it). The home page always works but a search results page will decide it can't be found for hours at a time. Sometimes switching the Debug setting Off and On a few times seems to make it work for a while.

The page is definitely there, if I create an error on the page that error is displayed instead of the 404. I've checked permissions, Application settings, There are no resources being called on that page.

I've done a few google searches for the error and found a few issues it could be but none of them panned out. Anyone have any ideas what this could be?



Travis Hawkins
jobs.bestcodingpractices.com

 

[ca8msm]

I start by making sure you have friendly errors turned off in IE to see if that really is the error you are getting. Then, check the server event logs to see if anything is being entered. Also, check your own error files and IIS logs for any timeout errors or anything similar as that would be my guess as to what is happening.

Mark,

Website Design Darlington
Experts, Information, Ideas & Knowledge
ASP.NET Tips & Tricks

 

[tlhawkins]

thanks,

I always have friendly errors turned off

in the error logs I see a couple of warnings about a control on the site, but it's not on the page with the problem. I think it must be unrelated.

the iis logs do have a couple of timeouts, but the 404 error that is returned is always immediate, there isn't time for it to have timedout. The page is fairly long so it may timeout sometimes, but I don't think that is the issue.

Thanks for throwing out some options, I've checked a lot of things already, but I'm totaly open to any ideas of what could be causing this.

It's basically settled down where switching it to debug="true" makes the problem go away, but we need to go live with this and certainly can't leave it on debug mode.

I'm reading everything I can find about the difference between debug and not on websites to see if I can get any ideas.

Travis Hawkins
jobs.bestcodingpractices.com