17.2KVIEWS
32REPLIES
7APPRECIATES
12ACTIVE PEOPLE
05-03-2026LAST POST
Are you sure you have configured esysx correctly with the 3.34.0 64-bit version? I don't experience an issue editing fdl directly from Coding.
VTENGR wroteHave you got more than 1 version of esys installed- install path looks... 'custom'?I belive so - here's my setup and the error I get when I try to "Edit FDL" straight from the CODING tab.
I have the option, 'Edit NCD', not 'Edit FDL'
That's not the normal behaviour of 3.34 with esysx so its something environmental in your setup.
ifr wroteI miss typed ... for 3.34.0 it's "Edit NCD". For 3.27.1 it's "Edit FDL".Have you got more than 1 version of esys installed- install path looks... 'custom'?
I have the option, 'Edit NCD', not 'Edit FDL'
That's not the normal behaviour of 3.34 with esysx so its something environmental in your setup.
I do have a custom path b/c I have both 3.27.1 installed and 3.34.0 installed. Surely that can't be the issue.
VTENGR wroteI've had co-existance work and had it fail. A lot can depend on order of install and registration of launchers.I miss typed ... for 3.34.0 it's "Edit NCD". For 3.27.1 it's "Edit FDL".
I do have a custom path b/c I have both 3.27.1 installed and 3.34.0 installed. Surely that can't be the issue.
I'd take everything off including launcher pro if you have it, then reinstall esys. Maybe go for 3.35.3 while you are at it.
Then install esysx, configure and save the 64bit esys path. See what happens.
Only other issues ive had with esys has related to java versions. I don't have any JRE installed.
I'm not an expert in getting this stuff working, but I do know yours is broken
and don't cal me shirley
ifr wroteThanks - I'll do that. Do you happen to have a link to 3.35.3?I've had co-existance work and had it fail. A lot can depend on order of install and registration of launchers.
I'd take everything off including launcher pro if you have it, then reinstall esys. Maybe go for 3.35.3 while you are at it.
Then install esysx, configure and save the 64bit esys path. See what happens.
Only other issues ive had with esys has related to java versions. I don't have any JRE installed.
I'm not an expert in getting this stuff working, but I do know yours is broken
and don't cal me shirley
VTENGR wroteHi VTENGR,ifr wroteThanks - I'll do that. Do you happen to have a link to 3.35.3?I've had co-existance work and had it fail. A lot can depend on order of install and registration of launchers.
I'd take everything off including launcher pro if you have it, then reinstall esys. Maybe go for 3.35.3 while you are at it.
Then install esysx, configure and save the 64bit esys path. See what happens.
Only other issues ive had with esys has related to java versions. I don't have any JRE installed.
I'm not an expert in getting this stuff working, but I do know yours is broken
and don't cal me shirley
I can upload it and share. Please check your Esysx version, support for 3.35 was added on 20/09/2020 update.
Deja011 wroteThanks!Hi VTENGR,
I can upload it and share. Please check your Esysx version, support for 3.35 was added on 20/09/2020 update.
EsysX64 Version 2.3.1.5 installed 10/10/2020.
VTENGR wroteI have sent you a PM with the link.Thanks!
EsysX64 Version 2.3.1.5 installed 10/10/2020.
ifr wroteJust tried the steps you suggested and updated to Esys 3.35.3 and still get the same runtime error on Esys-X when trying to EDIT NCD straight from the CODING tab.I've had co-existance work and had it fail. A lot can depend on order of install and registration of launchers.
I'd take everything off including launcher pro if you have it, then reinstall esys. Maybe go for 3.35.3 while you are at it.
Then install esysx, configure and save the 64bit esys path. See what happens.
Only other issues ive had with esys has related to java versions. I don't have any JRE installed.
I'm not an expert in getting this stuff working, but I do know yours is broken
and don't cal me shirley
VTENGR wroteTricky one.Just tried the steps you suggested and updated to Esys 3.35.3 and still get the same runtime error on Esys-X when trying to EDIT NCD straight from the CODING tab.
What happens if you just start esys, no esysx? Does Edit NCD still result in a crash or does it open the editor albeit with trimmed codes?
Assumption you are using W10 2004 or 20H2
ifr wroteI get the same runtime error. "Java.lang.NullPointerException at ...." followed by a lot of text that I'm not qualified to interpretTricky one.
What happens if you just start esys, no esysx? Does Edit NCD still result in a crash or does it open the editor albeit with trimmed codes?
Assumption you are using W10 2004 or 20H2
Windows 10 Pro 2004
Edit - Added error details if that helps anyone.
ifr wroteI didn't but I just installed it - Version 8 build 271 and still get the same error.Not esysx then, it's your OS environment. Do you have Java installed?
VTENGR wroteI don't have Java (jre) independently installed on my system.ifr wroteI didn't but I just installed it - Version 8 build 271 and still get the same error.Not esysx then, it's your OS environment. Do you have Java installed?
There seems to be quite a few reports of this error with esys versions newer than 3.27.1. No solutions just the workaround to use 3.27 or use fdl editor.
What I do know is that a new build of w10 2004 or later with esys 3.34.0/3.35.3 works without issue. Just wonder if there is some issue with legacy software registration such as launcher pro / esysx versions.
What happens if you start e-sys.bat instead of exe? Sets a few paths inlcuding some java ones.
ifr wroteProgram just boots like normal - same error.There's a JRE folder thats installed with esys. Sometimes independant installs of JRE can cause conflicts.
What happens if you start e-sys.bat instead of exe? Sets a few paths inlcuding some java ones.
If you want to try uninstalling esys, just make sure the folder is completely removed in EC-apps. Also uninstall esysx, Java, and reinstall esys. then just try esys.
After that it's going to need a deep-dive with log analysis which is probably not worth it. Almaretto and shawnsheridan don't seem to have identified a solution in the posts Ive seen so might be easier to rebuild, or stick with the constraints.
ifr wroteIs there a drawback to just using 3.27.1?If you have access to a virtual environment Id install a clean build of W10 and just esys 3.35.3 just for your own sanity. Confirm it works.
If you want to try uninstalling esys, just make sure the folder is completely removed in EC-apps. Also uninstall esysx, Java, and reinstall esys. then just try esys.
After that it's going to need a deep-dive with log analysis which is probably not worth it. Almaretto and shawnsheridan don't seem to have identified a solution in the posts Ive seen so might be easier to rebuild, or stick with the constraints.
