6 Replies Latest reply on Jan 12, 2009 6:42 PM by _AZ_

    The requested URL /pls/apex/f was not found on this server. - out of blue

    _AZ_
      Hello,
      i started receiving "The requested URL /pls/apex/f was not found on this server." error while trying to "run" the page. I can edit it and, if iexport/import it it works fine, until after i start making changes to all items switching from "item displayed as text basedo n lov, doesn't save state" to " save state". It doesn't seem to be some specific item...
      Where can i see the log of what erectly is hapenning during the execution of this page ?
      Thank you
      Andrew
        • 1. Re: The requested URL /pls/apex/f was not found on this server. - out of blue
          _AZ_
          the approach i used to nail down the region is link: strange url not found on a single page
          but the question remains. I actually want to add 2 more :

          1. Where do i see apex and page(s) logs?
          2. Where can i see the error(s) thrown by applications processes? ( basically smth that is not visible in "debug" messages" ?
          3. How can i debug the application processes?
          one option is to run them in the sql browser, but i want to see actual binding, for example....

          Thank you
          ANdrew

          Edited by: andrey on Jan 6, 2009 7:40 PM
          • 2. Re: The requested URL /pls/apex/f was not found on this server. - out of blue
            60437
            Andrew,
            1. Where do i see apex and page(s) logs?
            There's a report on the user activity logs. Not sure what logs you mean though.
            2. Where can i see the error(s) thrown by applications processes? ( basically smth that is not visible in "debug" messages" ?
            No errors are thrown. In PL/SQL, exceptions are raised. If they are handled, you don't see them. If they aren't handled, sometimes the effect ripples up the call stack and you get the situation you are seeing. When application processes raise exceptions and you are running with the developer toolbar shown, this statement is issued:

            htp.p('sqlerrm:'||sqlerrm);

            ...so you should see the result of that. Running the page in debug mode doesn't give you granular enough trace to be able to know exactly where a problem occurred, either with application processes or just during the normal rendering (show) or accept request. So the methodology I described (which you used) is the easiest way.

            3. How can i debug the application processes?

            What type of application processes? Those that run on every page view or those called on demand from ajax?

            Scott
            1 person found this helpful
            • 3. Re: The requested URL /pls/apex/f was not found on this server. - out of blue
              _AZ_
              Thank you Scott.

              RE : 1 - For now i just want to be able to see step-by-step what is happening when rendering or submit has occurred.

              RE: 2 - you said :"So the methodology I described (which you used) is the easiest way." i'm not sure i understood - what methodology?

              RE: 3 - any type. It's not clear ( for me at least ) if the binding occurs correctly, what values get passed to the pl/sql . Did i refer to the session variable correctly or i made a typeoff, etc, etc;

              I'm sort of vining, i guess, - i can't really get used to the fact that i have to jump all over the place when i need to trace a call to the process or understand why and what is breaking.
              • 5. Re: The requested URL /pls/apex/f was not found on this server. - out of blue
                60437
                Andrew,
                RE : 1 - For now i just want to be able to see step-by-step what is happening when rendering or submit has occurred.
                Running in debug mode will show you that.
                RE: 2 - you said :"So the methodology I described (which you used) is the easiest way." i'm not sure i understood - what methodology?
                You said in the second post in this thread, "the approach i used to nail down the region is link: here", and you linked to a post where I described how I would do it, shown again here:

                I would systematically disable everything on the "show" side of the page. Start with regions. Put a Never condition on each. Run the page. If the error stops, you know the problem was in one of the regions. If not, disable processes and computations, etc. Then enable these components one at a time until the problem recurs. When you isolate the problem region (if it is a region), then disable items and buttons in the region and so forth. The problem may be due to an unhandled exception somewhere inside one of the components.
                RE: 3 - any type. It's not clear ( for me at least ) if the binding occurs correctly, what values get passed to the pl/sql . Did i refer to the session variable correctly or i made a typeoff, etc, etc;
                Again, more specifics about the situation would help. When the page debug output is not sufficient, and instrumenting your own code isn't enought, you can always trace your database session and see what happened. Add &p_trace=YES to the URL, run the page and/or submit the page and then check the database dump destination for the trace file and use tkprof to get a report.

                Scott
                • 6. Re: The requested URL /pls/apex/f was not found on this server. - out of blue
                  _AZ_
                  Thank you Scott. That should satisfy my needs for now.