I did following steps:In the server document where you want to do the remote debug check the two following points :
Server tasks->Remote Debugger tab
set allow remote debugging on this server to enabled
Ports->internet ports->Remote debugger manager
Leave the tcp/ip port to 60000 and set the tcp/ip port status to enabled.
save the server document and RESTART you server (maybe you need only to restart some tasks but I don’t know which one)
Then when your server is started, in the console, use “load rdebug” command.
Then on the agent you want to debug set the trigger of your agent to schedule and the schedule to “never” if it doesn’t need to be schedule.
Do this even if it’s not a scheduled agent !!!
Then on the security tab of the agent (the one with the key) check the option “allow remote debugging” and insert a “stop” at the beginning of the initialize section.
Save your agent.
Then run the agent (or trig it the normal way). At that time from the remote debugger interface select the DB ,
Subject: Could not target agent in Remote debugger?
Are you running the Server Controller? If so, try running without the controller. I’ts been awhile since I’ve tested the remote debugger, but I ran into a similar problem. I stopped using the java server controller and then the debugger started working.
Subject: Could not target agent in Remote debugger?
I have had the same problem. Recently it was a bug.You can only connect to an waiting agent if the DB is in the Domino Data Directory (not in a sub-directory).
I testetd it with Domino 6.0.3 and 6.5.3 on Solaris and Linux (RH). As soon as I moved or copied the DB into the Domino Data Directory I can connect to the waiting agent and everything works as described in the Remote Debugger help.