JSL Debugger Not WorkingAnyone else having trouble getting the debugger to work? I try to run it, and after about 90 seconds I get:
JMP Alert-- A time-out encountered while attempting to connect to the JSL Debugger GUI.
I read up online, and see that this is generally caused by an Windows Socket timeout, related to McAfee antivirus, contact your local I/T dept, etc.. I'm not running McAfee. I am running:
Windows 10
Norton Antivirus
JMP14.0 (though I get the same problem with 13.2)
Anybody else run across this, and managed to fix it? Next stop is Tech Support, but thought I'd start here first.
Thanks,
Jerry
Re: JSL Debugger Not WorkingThanks Martin! I'll try the debugger and see where my opinion falls. It certainly has the potential to help JSL code writing... now that it works (based on Mark Bailey's reply), I can start figuring it out.
Jerry
Re: JSL Debugger Not WorkingTHANK YOU MARK!!!! What a simple solution! Hope this question/answer post helps others down the road.
Thanks,
Jerry
Re: JSL Debugger Not WorkingHi Jerry,
me not, but I must confess I'm not using the debugger at all. I tried it when I started using JMP, doing some JSL scripting and found it (sorry for that hard word) useless. May this is due to my past working with MATLAB and its debugger which is way more comfortable and functionable. (same for other programming editors). However this is also a different interface and interpreter there. So I don't want to compare it further.
I've heard from some customers having issues but not because of the McAfee.
Sorry,
Martin
Re: JSL Debugger Not WorkingI had this problem last summer. Yes, it is the socket collision/conflict that is preventing JMP Debugger from starting. The collision was with the Cisco AnyWhere VPN connection. No connection, no problem. I am a Remote Worker, so I must connect.
Help Desk told me to change my VPN connection to "Direct to SAS" because that connection uses a different socket. Voila!
