Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X
I'm having problems connecting KepserverEX v6.1 to Thingworx v9.3
I can confirm that the pc that kepware is installed on can see the Thingworx server (I'm able to access composer and port query confirms port 443 is open). Thingworx’s Industrial Thing’s Base Thing Template is set to “IndustrialGateway” and the appkey is correct. I have also tried both Host name and IP of the server.
This issue is effecting 2x clients both running kepserver v6.1, the reason for the low version number is that both clients were setup 5 years ago to run an Etch line and Penetrant line and we are only now wanting to connect them to Thingworx. Unfortunatly the OEM who did the initial install has gone bust so I'm unable to raise suport ticket via them
Similar discussions:
Unfortunatly neither discusions resolve the problem.
Updating Kepware from v6.1 is not possible and connecting to ThingWorx via IP produces the same error as connecting by name.
SSL is enabled and working fine and we have other KepserverEX clients connected to Thingworx with the same settings (all version 6.11)
Kepware has the following knowledge base article on the topic:
If there waw 404 error code in the event log, then the following article would apply:
There have been many changes to the product since the v6.1 release to help mitigate the socket connection issue. If you are unable to perform the recommended upgrade, I recommend opening a support ticket with the Kepware team to troubleshoot further. Here is a link to the login page where ticket can be opened:
Thanks,
*Chris
Hi Chris
Unfortunately while the first article does produce a websocket error it is not a 404 error;
"error: could not establish websocket connection."
I've not had any luck finding a solution with articals related to this^ error either. I'll look to raising a ticket with a different licence key.
Thanks both for your help,
Chris