Jobs are running longer than be before and show the following error in the Job Report:
-1 - Wrong message type 20240903/105132.118 U0009909 TRACE: (wrong type error) 0x11fc910 01268 00000000 53455353 494F4E5F 4552524F 52000000 >SESSION_ERROR...< 00000010 00000000 00000000 00000000 00000000 >................< 00000020 2A414745 4E540000 00000000 00000000 >*AGENT..........< 00000030= 00000000 00000000 00000000 00000000 >................< 00000060 00000000 00000000 756E6B6E 6F776E00 >........unknown.< 00000070= 00000000 00000000 00000000 00000000 >................< 000000F0 B9851E00 2A414745 4E547C6F 6E5F636F >....*AGENT|on_co< 00000100 6E6E6563 74696F6E 2F313131 28436F6E >nnection/111(Con< 00000110 6E656374 696F6E20 72656675 73656429 >nection refused)< 00000120= 00000000 00000000 00000000 00000000 >................< 000004F0 00000000
The secondary error is: on_connection/111(Connection refused)
In the [TCP/IP]-section of the Agent's ini-file the parameter 'port=2300' was missing.
Add the listening port to the ini-file of the Agent.
By default, this is: port=2300
The value can be adapted according to the environment.
The error 'wrong message type' / 'SESSION_ERROR' can appear with different secondary errors.
See also:
https://broadcomcms-software.wolkenservicedesk.com/external/article?articleNumber=268287 (secondary error: TLS-handshake/1(stream truncated)
https://broadcomcms-software.wolkenservicedesk.com/external/article?articleNumber=278932 (secondary error: connect/(resolve: Host not found (authoritative) [asio.netdb:1])