Bad Communication error and ports closed

Unified Architecture topics related to OPC UA Specification, compliant behavior and any technical issues of OPC UA, like Security, Information Model, Companion Specs DI, PLCopen, ADI, ...

Moderator: Support Team

Post Reply
chifo
Jr. Member
Jr. Member
Posts: 1
Joined: 11 Sep 2019, 01:55

Bad Communication error and ports closed

Post by chifo »

I have a problem with the connection between OPC Server and couple of machines. when y try to connect the machine send us a Error "could no connect to server BadCommunicationError", "uastack OPcUa_secureConnection_onNotify:connect event Error 0x80050000"
Any suggestion?

here's the log
:21.572 | General | | Error: Publish failed [status=0x800a0000]
13:50:22.556 | General | | [uastack] OpcUa_Channel_ResponseAvailable: Request failed! (0x800A0000)
13:50:22.556 | General | | [uastack] OpcUa_Channel_ResponseAvailable: Request failed! (0x800A0000)
13:50:22.572 | General | | Error: Publish failed [status=0x800a0000]
13:50:22.572 | General | | Error: Publish failed [status=0x800a0000]
13:51:23.556 | General | | [uastack] OpcUa_Channel_ResponseAvailable: Request failed! (0x800A0000)
13:51:23.556 | General | | [uastack] OpcUa_Channel_ResponseAvailable: Request failed! (0x800A0000)
13:51:23.571 | General | | Error: Publish failed [status=0x800a0000]
13:51:23.571 | General | | Error: Publish failed [status=0x800a0000]
13:51:26.274 | General | | [uastack] OpcUa_Channel_ResponseAvailable: Request failed! (0x80AD0000)
13:51:26.274 | General | | [uastack] OpcUa_Channel_ResponseAvailable: Request failed! (0x80AD0000)
13:51:26.290 | Server Node | Chiron | Connection status of server 'Chiron' changed to 'Disconnected'.
13:51:26.290 | DA Plugin | Chiron | Deleting subscription 22
13:51:26.306 | Server Node | Chiron | Disconnect succeeded.
14:12:18.942 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: ERROR 0x80050000!
14:12:18.942 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: Notifying owner! 0x80050000
14:12:18.958 | Server Node | G352-1559 | Could not connect to server: BadCommunicationError
16:28:38.965 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: ERROR 0x80050000!
16:28:38.965 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: Notifying owner! 0x80050000
16:28:38.981 | Server Node | G352-1556 | Could not connect to server: BadCommunicationError
16:28:44.668 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: ERROR 0x80050000!
16:28:44.668 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: Notifying owner! 0x80050000
16:28:44.668 | Server Node | G352-1557 | Could not connect to server: BadCommunicationError
16:28:49.559 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: ERROR 0x80050000!
16:28:49.559 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: Notifying owner! 0x80050000
16:28:49.559 | Server Node | G352-1558 | Could not connect to server: BadCommunicationError
16:28:56.800 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: ERROR 0x80050000!
16:28:56.800 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: Notifying owner! 0x80050000
16:28:56.800 | Server Node | G352-1559 | Could not connect to server: BadCommunicationError
16:29:01.800 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: ERROR 0x80050000!
16:29:01.800 | General | | [uastack] OpcUa_SecureConnection_OnNotify: Connect event: Notifying owner! 0x80050000
16:29:01.800 | Server Node | G352-1735 | Could not connect to server: BadCommunicationError

User avatar
Support Team
Hero Member
Hero Member
Posts: 2522
Joined: 18 Mar 2011, 15:09

Re: Bad Communication error and ports closed

Post by Support Team »

Hello,

this error could have hundrets of reasons, can not say by the informatin given. You should analyse using wireshark. Might be some decoding error or wrong implementation of UA protocol. Make sure you only use servers and clients that were tested for compliance with the UA specification.
Best regards
Unified Automation Support Team

Post Reply