Article - CS299048
TCP Socket Connection Errors in PTC Kepware Products
Modified: 22-Aug-2025
Applies To
- ThingWorx Kepware Server (legacy) 8.0 to 6.18
- Kepware Server (formerly KEPServerEX) 5.20.396.0 to 6.18
Description
- Errors in server Event Log when attempting to connect to an Ethernet device using TCP:
- 10013
- 10053
- 10054
- 10058
- 10060
- 10061
- 10065
- 10038
- In the server Event Log, it shows:
- Socket error occurred connecting. | Error = 10061, Details = 'No connection could be made because the target machine actively refused it.'
- Socket error occurred sending data. Error =10054, Details= 'An existing connection was forcibly closed by the remote host.'
- Socket error occurred connecting. | Error = 10038, Details = 'An operation was attempted on something that is not a socket.'
- Process to resolve Socket error in PTC Kepware Products
- Socket error occurred connecting. | Error = 10060, Details = 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.'
- Channel failed to connect. | Status description = 'Could not establish a network connection to remote server.', Status code = 0X80AC0000.
This is a printer-friendly version of Article 299048 and may be out of date. For the latest version click CS299048