I had that problem, too. It is easy to reproduce.
Put Application.cfm, OnRequestEnd.cfm and a number of CFM
pages, say, p1.cfm, p2.cfm and p3.cfm in a directory. Run the pages
p1.cfm and p2.cfm. Rename the file OnRequestEnd.cfm to
OnRequestEnd2.cfm.
If you now rerun p1.cfm and p2.cfm, you will get the File Not
Found error. However, p3.cfm will run without error. It is clear
what is happening. The pages that you ran earlier when
OnRequestEnd.cfm was present are the ones that give an error when
OnRequestEnd.cfm is absent.
OnRequestEnd.cfm is just an included page. You can therefore
reproduce the problem with any included page, if you follow the
same steps.
I think it happens because Coldfusion caches the pages it has
run, together with any includes like OnRequestEnd.cfm that the
pages may contain. When a page is subsequently requested,
Coldfusion will, for efficiency, simply recycle the cached copy of
the page when it detects that there has been no change to its
content. Hence the continued File Not Found error.
So, in your case, one obvious way to avoid the error is to
perform some dummy action to the page, like adding a space, and
re-saving the file. A second way out is to clear the template cache
in the Coldfusion Administrator. (Both methods assume that you have
unchecked the
Trusted cache setting in the Administrator).