Problem With OPC UA Server Port 49320
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Problem With OPC UA Server Port 49320
Hello everybody. We have a server with KepServerEX (6.12.361.0) and Ignition (7.9.21) installed as client of Kepware. In the OPC UA Configuration, the server endpoint is setted as default : opc.tcp://127.0.0.1:49320.
Everything was working fine until last week. but now Ignition is in error becuase can not connect to the OPC server (kepware) . I noticed that even if the KepServerEx service is running, I can not see the port 49320 in Listening state ( I used the command C:\ ....\netstat -aon). I installed a Kepware on my laptop and when the service is running I can find this row (with the same command ...\netstat -aon):
TCP 127.0.0.1:49320 0.0.0.0:0 LISTENING 15340
I tried to change the port number in the server but nothing changes.
Other informations:
The device connected to Kepware (channels) communicate perfectly.
The server is not connected to the internet, the firewall is disabled, OS is Windows Server 2019.
Using a tool the check the port status I see the port 49320 closed, not in error. The other ports are working well.
Do you have any suggestions?
Thank you in advance
Guido De Biase
Solved! Go to Solution.
- Labels:
-
Connectivity
-
KEPServerEX
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Also observe Event log messages and see if you are getting any such errors
- 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.'
If this is the case, refer below article for troubleshooting
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Kepware Runtime request the OS to open a listening socket on the target OPC UA port (typically 49320),
Have you checked if IT policies in place that is preventing this?
Please stop/start the runtime and check if it is works?
If the issue persist; I recommend opening a support ticket with the Kepware Technical Support team. Here is a link to the my kepware login page where a ticket can submitted:
https://my.kepware.com/s/login/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Notify Moderator
Also observe Event log messages and see if you are getting any such errors
- 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.'
If this is the case, refer below article for troubleshooting
