I have one PC that starts editorX (community edition) just fine and an old development unit that hangs on the pathwave automation screen checking connection Attached is a log file, any insight as to the issue? The machine having issues once had a 8400 license but that is long expired and shouldn’t be required.
Latest.txt (25.8 KB)
Hi @craig.petku ,
I think the problem is that the NJsonSchema depends on a specific version of newtonsoft.json. Unfortunately we had to bump the Newtonsoft.json to v 13 due to a security issue. You can probably fix it by updating the NJsonSchema package. If NJsonSchema did not come from you, you might be able to fix the issue by updating the Runner package to v 1.16.1+ab000ba9.
Here is the error:
2025-12-19 17:29:52.295451 ; Resolver ; Debug ; Found match for NJsonSchema, Version=10.6.10.0, Culture=neutral, PublicKeyToken=c2f9c3bdfae56102 in C:\Users\cpetk\Documents\OpenTapInstruments\rugby\bin\Release\Dependencies\NJsonSchema.10.6.10.0\NJsonSchema.dll
2025-12-19 17:29:52.300579 ; Resolver ; Debug ; Found match for Newtonsoft.Json, Version=9.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed in C:\Users\cpetk\Documents\OpenTapInstruments\rugby\bin\Release\Dependencies\Newtonsoft.Json.13.0.0.0\Newtonsoft.Json.dll
It seems like NJsonSchema depends on v NewtonsoftJson v 9.0.
Solver it by deleting the V12 directory. V13 had been installed but it was still pulling from the V12…
Note that Editor-X will be discontinued as Pathwave Test Automation (KS8400B) version 9.29 (and forward) support the same and more, using a free community license. Read more here: Keysight Test Automation 9.29 Released — Community License Now Available