When I close the setting editor, and open PC-DMIS, I get this error, even if I wait that the process finish.
In this case, I have to reboot the controller (DC800).
Any idea ?
Every time I have to open the settings editor I have to restart the computer. It would leave a ghost instance of PCDmis open and fail to startup or throw a communication error. Restarting the PC is less painful than having to pop the controller, so I'm resigned to it since it's rare I have to go into the settings editor.
I have seen this before and not just with the most recent version.
When you run the settings editor it fires up PC-DMIS in the background. For reasons unknown when the settings editor is closed you will still have the executable pcdlrn.exe running in the background. You need to kill it before you will be able to run PC-DMIS again.
It is not a big deal except when you have a system that has even a moderate amount of security (situations where you need IT help to run programs with admin rights such as the settings editor). This is when it gets complicated. When running the settings editor with admin rights then pcdlrn.exe is also running with admin rights and to kill it you need to start an instance of the task manager with admin rights as well. Rebooting the computer is another work around.
I am pretty sure this problem goes back at least four or five major version releases of PC-DMIS. As for why they don't fix it? You need to ask them.
Maybe it's not fixed at all, but it works now !!!!
I just open / close the setting editor with the controller off.
Since then it has been working as it should.
Check your anti-virus and firewall settings to make sure they're not intercepting communication with the controller, that might explain why it's holding onto the connection when the controller is on.
