Unable to Edit Network: Toolkit 1.14.4 & Windows 10.

We have two Windows 10 laptops (one pre-major Windows 10 update, one post-major update) upon both of which we are unable to Edit Network from within Toolkit 1.14.4 to change the connection details - an Unexpected Error always results. On another laptop with Windows 8.1, Edit Network is working fine.

We have reported the issue to CIS Tech Support who are aware of the issue and are investigating.

In the mean time, the current work-around for a Windows 10 PC with this issue is to manually edit the project XML file to change the interface settings:
- Location: C:/Clipsal/C-Gate2/tag
- Edit the project XML file with a text editor, search for "InterfaceType", edit this setting and the following "InterfaceAddress" setting.
- Other project XML files can be used to provide references to valid settings options.

 

Hi Brendan

If it is any help, my Windows 10 desktop PC does not have any problem to edit the network of a project with Toolkit 1.14.4

I just swapped from TCP to a com port on PACA and back to try it out.

 

Thanks DarylMc,

CIS Tech Support advised that they have received other reports of the same issue, and also that it does not occur on every Windows 10 machine (including all of theirs). CIS are trying to identify the cause, and hope that as many users as possible will allow the email reporting of the issue to be sent to them from Toolkit when it occurs, to help them in this regard.

 

Hi Brendan,

Thanks for following that up, I have exactly the same issue and have been doing the same workaround. I will send the details to Schneider if they are actually wanting the crash reports!

 

Hi guys
Here is some more info about my system it can be of any help.

I have a fresh install of Windows 10 Pro 64 bit not an upgrade.
Version 10.0.10586 Build 10586
The current Windows install aside from any updates was August last year.
I am not running preview builds.
No antivirus protection aside from Windows defender.
Automatic updates is on.

Actually I did the upgrade from Windows 7 64 bit to authenticate the hardware first.
Then I reinstalled from a fresh image downloaded from Microsoft.

The PC hardware is several years old and does not support encryption.
Maybe it does but in any case it is not turned on.

I did not import any existing CBus projects to the new desktop system but I did just try one and had no problems editing the network connection settings.

The Toolkit 1.14.4 install was the first Toolkit install on this machine and done to default folder locations.
From past problems mentioned on the forum I think you would be asking for trouble to choose another location.

I run CGate in a window instead of as a service purely because I like to be able to shut it down easily.
There is no other Java programs on the machine except for what is installed with Toolkit.

My CBus network connections are RS232 PCI via an Ethernet device server and I have also tried the PACA via USB without any issue editing the network connection setting.

Daryl

 

I just noticed there may be 2 versions of Toolkit 1.14.4?
Mine is build 2318

 

Hi Guys, I also had a technically capable client who had the same 'Unexpected Error' problem editing or opening network with newly upgraded to 1.14.4 on a Windows 10 PC.

Additional problem was that after the error, the Wiser 2 interface being used for CNI access to the C-Bus LED turned to red and seemed to have locked up one of the two C-Bus interfaces.

This client's machine was a good quality private assembly tower, and had been upgraded to Windows 10 with an in-situ upgrade rather than a clean build (in case that adds info). CIS was said to be looking closely at .NET framework differences.

I found that by setting the Toolkit.exe and C-Gate.exe to Windows 7 compatibility mode, it made Toolkit run more successfully, but it still had one or two quirks during a 3 hour session.

Hope this helps,

Brad

 

Hi DarylMc,

Yes, the latest build is 2323 which is what we had installed.

Since you brought this up, we tried rolling back to build 2318 and the Edit Network function now works - so the issue seems to be limited to build 2323 when working on a Windows 10 laptop.

Thanks.

(We have informed CIS tech support of this observation.)

 

Solved on my system

If it helps - I had a similar problem
Upgraded toolkit to 1.14.5 (build 2333) a few days ago it prompted to make sure Win10 Telnet service was installed, Win10 on my machine was not setup with Telnet service, All good now

 

Me too, enabled TelNet and all works OK