Hi,
I have got some warning messages appearing in the log on the server. Waring message shown below:
- Wrong destination address, (SYS: 1 Ui -num 1 CONN: 2(R)), DP_MSG_ANSWER
This message seems to only appear when I start up a remote UI on a client workstation, and also when I launch the Gedi.
Would anyone happen to know what this warning message means and how it can be fixed or prevented?
Regards,
Curtis
Warning message: \"Wrong destination address, ...\" in the log
- curtisgibson
- Posts:5
- Joined: Tue Nov 14, 2017 10:41 am
Warning message: \"Wrong destination address, ...\" in the log
- Gertjan van Schijndel
- Posts:634
- Joined: Mon Aug 02, 2010 10:37 am
Re: Warning message: \"Wrong destination address, ...\" in the log
This message means that an answer to a datapoint request message cannot be sent to a user interface over the replica's redundant connection.
To fix this you have to check why this connection is not available (anymore). Perhaps there are other messages in the log that provide additional information to this issue.
To fix this you have to check why this connection is not available (anymore). Perhaps there are other messages in the log that provide additional information to this issue.
- RudiKreiner
- Posts:198
- Joined: Mon May 16, 2011 2:10 pm
Re: Warning message: \"Wrong destination address, ...\" in the log
I' occasionally seen this message too and wondered where it came from but never really looked at it in detail.
Here is an example:
WCCOAui (65), 2018.04.18 14:22:25.485, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Event -num 0 CONN: 1), Connection closed
WCCOAui (65), 2018.04.18 14:22:25.601, SYS, WARNING, 65, Wrong destination address, (SYS: 1 Event -num 0 CONN: 1), DP_MSG_SIMPLE_REQUEST
WCCOAui (65), 2018.04.18 14:22:25.630, SYS, SEVERE, 39, Connection lost, Alive timeout expired, closing connection to (SYS: 1 Data -num 0 CONN: 1) (P) @ STANDARD (10.1.1.31). Last message expected at 2018.04.18 14:22:25.622.
As you can see by the first and third message, the UI was being shut down and I suspect that "wrong address" error could not be delivered properly because the UI was already closing sockets for the shutdown.
After some experimenting I discovered that I get these 5 messages if I stop my UI intentionally:
WCCOAui (56), 2018.04.20 12:52:31.427, SYS, INFO, 181, Closing connection to (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (56), 2018.04.20 12:52:31.431, SYS, INFO, 181, Closing connection to (SYS: 1 Event -num 0 CONN: 1)
WCCOAui (56), 2018.04.20 12:52:31.436, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection closed
WCCOAui (56), 2018.04.20 12:52:31.449, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Event -num 0 CONN: 1), Connection closed
WCCOAui (56), 2018.04.20 12:52:33.636, SYS, INFO, 2, Manager Stop
but only the last 3 messages if the UI loses connection to data and event manager, usually meaning that the whole project has been stopped.
At least is was that way in WinCC V3.9
In V3.14. an UI will not stop if it loses the connections but just issue these messages instead:
WCCOAui (66), 2018.04.20 13:00:43.573, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Event -num 0 CONN: 1), Connection closed
WCCOAui (66), 2018.04.20 13:00:48.128, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection closed
WCCOAui (66), 2018.04.20 13:00:48.134, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection has been closed
and try to connect again, unless it is stopped manually.
Now I understand better how it works, and hope that you do too.
Here is an example:
WCCOAui (65), 2018.04.18 14:22:25.485, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Event -num 0 CONN: 1), Connection closed
WCCOAui (65), 2018.04.18 14:22:25.601, SYS, WARNING, 65, Wrong destination address, (SYS: 1 Event -num 0 CONN: 1), DP_MSG_SIMPLE_REQUEST
WCCOAui (65), 2018.04.18 14:22:25.630, SYS, SEVERE, 39, Connection lost, Alive timeout expired, closing connection to (SYS: 1 Data -num 0 CONN: 1) (P) @ STANDARD (10.1.1.31). Last message expected at 2018.04.18 14:22:25.622.
As you can see by the first and third message, the UI was being shut down and I suspect that "wrong address" error could not be delivered properly because the UI was already closing sockets for the shutdown.
After some experimenting I discovered that I get these 5 messages if I stop my UI intentionally:
WCCOAui (56), 2018.04.20 12:52:31.427, SYS, INFO, 181, Closing connection to (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (56), 2018.04.20 12:52:31.431, SYS, INFO, 181, Closing connection to (SYS: 1 Event -num 0 CONN: 1)
WCCOAui (56), 2018.04.20 12:52:31.436, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection closed
WCCOAui (56), 2018.04.20 12:52:31.449, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Event -num 0 CONN: 1), Connection closed
WCCOAui (56), 2018.04.20 12:52:33.636, SYS, INFO, 2, Manager Stop
but only the last 3 messages if the UI loses connection to data and event manager, usually meaning that the whole project has been stopped.
At least is was that way in WinCC V3.9
In V3.14. an UI will not stop if it loses the connections but just issue these messages instead:
WCCOAui (66), 2018.04.20 13:00:43.573, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Event -num 0 CONN: 1), Connection closed
WCCOAui (66), 2018.04.20 13:00:48.128, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection closed
WCCOAui (66), 2018.04.20 13:00:48.134, SYS, INFO, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection has been closed
and try to connect again, unless it is stopped manually.
Now I understand better how it works, and hope that you do too.