CF911: CF pages get "no web application configured", but CF's "running"
Note: This blog post is from 2009. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.If you find you can't run CF pages (they get "There is no web application configured to service your request") but CF seems to be "running", here's one possible explanation and how to diagnose/resolve the problem.
The problem outlined here has to do with being careful when you're modifying CF to enable/disable RDS (or doing any edits in the [cf]/wwwroot/WEB-INF/web.xml file that controls it.) This applies to CF 6, 7, or 8.
best regards,
bill
I wonder if by "log entries being the same" you may have been referring to the error message shown to the user, because the message I pointed to (in the runtime/logs) clearly pointed to an XML problem.
You're not saying that you got THAT error in the runtime logs, are you? I just don't see how that would be solved by an account permission correction.
Indeed, the real point of the blog entry was to point people to the runtime logs to find the root cause. I'd be curious what yours reported, as much to help others who may then find that and search for a solution, in which case they may find this and your helpful observation. To that point, can you clarify what permission you defined for the user, in case it's significant?
I'll say also that did say at the outset that I was offering *one possible explanation* for the general problem of the "no web application configured" error. I don't mind if others may share more observations of other reasons and solutions. But along the lines of the above, I'd say it would be helpful to provide what the key runtime error log message was so people can really connect the dots.
Looking forward to your update, Bill, if you still have the info at hand.