I've been trying to setup up the debugger using the direction from this link http://docs.google.com/Doc?id=dhh9ztnx_55k9w39rhf. I did the second approach and when it hits a debug statement or error the website just comes up with CGI ERROR no dubugger.

I changed the service to be able to interact with the desktop. The application debugger is on. shutdown startup flags are 1. I notice my Oengine doesn't show web request. So does anybody know what I could be missing?

Hi Jensen,

Are you looking at the console desktop?

Can you seen an oengine start when the request comes in?

If you un the socketserver on the desktop, not as a serivice, do you see the debugger?

- Bob

Hi Bob

Im looking at the oengine window that you show a example of a web request in the document.

task manager shows OECGI2 request as web request come in.

ran the oesocketserver from command prompt not as service. I can see calls come in through that java console. I went through the text and didn't see it try to call debugger.

so no debugger still.

i did notice that are engine info says

Name "OEC68"

Type "PIPE"

Requests "29956"

My issue was I connect to the server via remote desktop so the debugger never shows up there. you must be on the Console not via remote also having debugger on replacement was the other issue you can change the way the debugger runs through the subroutine Toggle_Debugger it has a equates file also to know what to pass to it

View this thread on the forum...