Cannot set debug breakpoint in 3.4.27

Cannot set debug breakpoint in 3.4.27

I recently upgraded to 24x7 Scheduler, version 3.4.27. I'm now in Debug Mode and am attempting to set a breakpoint on a JAL instruction and I am receiving: "Breakpoint line must contain an executable statement!". Message appears as a result of attempting to set a breakpoint via all traditional methods on a valid JAL source line, in 24x7 scripts written on current release and on the prior release - 3.4.26. Message appears when attempting to set a breakpoint on any valid JAL line regardless of the specific instruction (ConcatEx, MailSend, FileExists, DirEx, IfThen, etc.).

Thanks in advance for your help.
Mike Mather

This could happen in case if you using some kind of a remote access software, pcAnyWhere or similar and that software doesn't report correctly coordinates of mouse clicks.

A workaround for this issue is to use F8 keyboard shortcut.

Access to 24x7 Debug is direct - not using PCAnywhere, etc. Already tried the workaround (F8) - same results. I can re-download 3.4.27 and/or reinstall if this problem appears to be isolated.

Does the script editor correctly show current line number in the status bar of the editor screen?

The line number does not correctly show in the status bar of the editor screen for both Edit & Debug Modes - it always shows: 0001:0001 regardless of the line I'm actually on.

This seems to be the root cause of the problem. The editor is unable to figure out the current cursor position. Please let us know which Windows version and service pack you run.

Windows XP Professional, service pack 2 (my machine). Our production 24x7 machine is Windows 2000 + service pack 4, however I probably won't install 3.4.27 on it until tests from my machine yield satisfactory results. Thanks.

We're checking file dependencies on different systems. I'll get back to you when any new information will come to light.

I get this too on win server 2003 r2, over an rdp connection