Article - CS394697
Kepware fail to connect to ThingWorx with no obvious reason in event log after ThingWorx server restart
Modified: 13-Jun-2023
Applies To
- ThingWorx Platform 9.5
- ThingWorx 9.2.12
- KepServerEX 6.10.623.0
Description
- Kepware connect to ThingWorx server normally. However after restart ThingWorx server, Kepware fail to reconnect to ThingWorx
- Need to restart Kepware runtime in order to reconnect to ThingWorx after ThingWorx server is restarted
- No other warning or errors in Kepware event log except below
-
Warning ThingWorx Native Interface Connection to ThingWorx was closed. | Platform = xxxx
-
- Error in ThingWorx Application/Communication log
-
[L: ERROR] [O: c.thingworx] [I: ThingWorx Kepware Server\ThingWorx Native Interface @ 2023-05-22T09:30:11.416Z thingname='***'] [U: ****] [S: ] [P: ] [T: ****_BulkLog] Connection to ThingWorx failed. | Platform =******/Thingworx/WS, error = could not initialize a secure socket connection.
-
This is a printer-friendly version of Article 394697 and may be out of date. For the latest version click CS394697