SC EndPoint communications not working

frediano.dicarlo · July 11, 2025, 9:05am

I have a plugin that, among other features, displays a list of client endpoints on the network (SC, MC, and Standalone).

While MC and Standalone work correctly, the SC doesn’t respond at all to the related messages.

I started both a MC and SC on the same machine and the situation is the following: the MC sends the Login message when it starts and then responds to the “Who Are Online” request, while the SC shows no sign of life.

Below is the MIP Log of the plugin that builds the list of EndPoints:

2025-07-10 17:39:15.159+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)  Login da: Nome: "b430042" | Tipo: Administration | Host: STAZ-12280 | IP: 172.19.51.206 | ID: 54ec16ae-bb89-449f-af37-51936533b99d
2025-07-10 17:39:15.159+02:00 [   358] INFO       - ### Cruscotto.Background.StatusMonitorServer.SendUpdateEndPointMessage (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)  Aggiornamento Stato EndPoint: 11
2025-07-10 17:39:15.161+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.EndPointTableChangedHandler (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)  Notifica aggiornamento Tabella EndPoint
2025-07-10 17:39:15.162+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.SendWhoAreOnlineMessage (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)  Richiesta Broadcast: "Who Are Online"
2025-07-10 17:39:15.175+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.WhoAreOnlineResponseHandler (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)  Risposta a richiesta "Who Are Online": 13 EndPoint
2025-07-10 17:39:15.176+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "COMGE\MILEsvc  (192.168.197.166)" | Tipo: Service | Host: VM-MILEMNGMTP01 | IP: 192.168.197.166 | ID: 4dd2775e-7d3e-4e38-98be-9720de5c3fe8
2025-07-10 17:39:15.176+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "" | Tipo: SmartClient | Host: VM-MILEMNGMTP02 | IP: fe80::e135:c15b:3c1f:b734%14 | ID: e964349a-d6eb-449e-9a6c-fc4cfb2e9f15
2025-07-10 17:39:15.176+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "milesvc  (192.168.197.167)" | Tipo: Standalone | Host: VM-MILEMNGMTP02 | IP: fe80::e135:c15b:3c1f:b734%14 | ID: 7cfb42c6-5858-405c-8bf1-97dd276ff5fc
2025-07-10 17:39:15.176+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "b664129  (172.19.63.30)" | Tipo: SmartClient | Host: STAZ-21440 | IP: 172.19.63.30 | ID: b19d39cd-4c0e-4841-82bc-d26d409a7048
2025-07-10 17:39:15.176+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "b365068  (172.19.53.76)" | Tipo: Administration | Host: STAZ-21446 | IP: 172.19.53.76 | ID: bae19545-1a94-47d1-b64e-3414312e579e
2025-07-10 17:39:15.177+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "b365068  (172.19.53.76)" | Tipo: SmartClient | Host: STAZ-21446 | IP: 172.19.53.76 | ID: b16b1956-40a9-4cc5-9a4e-f2e94ff5e3a2
2025-07-10 17:39:15.177+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "milesvc  (192.168.197.187)" | Tipo: Standalone | Host: VM-MILEBRDGP01 | IP: 192.168.197.187 | ID: fa292fe7-da4e-4bb6-aaa4-40ff0d56d026
2025-07-10 17:39:15.177+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "milesvc  (192.168.197.187)" | Tipo: Standalone | Host: VM-MILEBRDGP01 | IP: 192.168.197.187 | ID: 258fcfed-a9f5-406e-b97d-55c8b5bd6537
2025-07-10 17:39:15.177+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "milesvc  (192.168.197.166)" | Tipo: Standalone | Host: VM-MILEMNGMTP01 | IP: 192.168.197.166 | ID: b02db23b-ca2c-4dc0-b8c1-f0129c65a4f1
2025-07-10 17:39:15.178+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "COMGE\MILEsvc  (192.168.197.167)" | Tipo: Service | Host: VM-MILEMNGMTP02 | IP: fe80::e135:c15b:3c1f:b734%14 | ID: 5cebb91b-ebca-467c-a9ba-b3261d0b5e00
2025-07-10 17:39:15.178+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "" | Tipo: SmartClient | Host: STAZ-21441 | IP: 172.19.51.44 | ID: 410b6332-2ef7-4fed-8185-f0b1fd7527ce
2025-07-10 17:39:15.178+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "b430042  (172.19.51.206)" | Tipo: Administration | Host: STAZ-12280 | IP: 172.19.51.206 | ID: 54ec16ae-bb89-449f-af37-51936533b99d
2025-07-10 17:39:15.178+02:00 [   358] INFO       - ### Cruscotto.ClientMessenger.LogEndPoint (Service 5cebb91b-ebca-467c-a9ba-b3261d0b5e00)     - Nome: "b430042  (172.19.58.34)" | Tipo: SmartClient | Host: STAZ-21445 | IP: 172.19.58.34 | ID: 29f2aa7d-703d-440a-baaa-26490bb40751

First row is MC login message while row 17 the answer of MC to Who Are Online request.

No message from SC are present.

What can I do to help you troubleshoot the problem?

Regards,

Frediano

Bo_Ellegard_Andersen · July 14, 2025, 5:59am

The Chat sample uses the WhoAreOnlineRequest, if you test with the unaltered Chat sample does it work for you? - https://doc.developer.milestonesys.com/html/index.html?base=samples/pluginsamples/chat/readme.html&tree=tree_1.html

There might be information, errors perhaps, in the Event Server logs with clues as to what is wrong. Look in both [C:\ProgramData\Milestone\XProtect](file:C:/ProgramData/Milestone/XProtect) Event Server\logs and [C:\ProgramData\Milestone\XProtect](file:C:/ProgramData/Milestone/XProtect) Event Server\logs\MIPLogs .

frediano.dicarlo · July 15, 2025, 12:22pm

Corporate 2023R3

This is network pc with clients without any plugin. IP addr is 172.19.51.206 and User b430042

This is server pc with Chat plugin, ip addr is 192.168.197.167, same user

as you can see there are the 2 clients with Chat plugin and a MC with some User (ip 172.19.58.34) and ONLY MC from previous image … SC is not communicating login

Any error in ES log files.

Frediano

Bo_Ellegard_Andersen · July 16, 2025, 6:36am

If you on the Smart Client (IP…206) do a Help ->About, can you verify that the Chat plugin is loaded?

If it is loaded please try to enable logging and see if you find anything in the SC logs (ClientLog or MIPLog).

How to enable Smart Client logging in 2020 R3 and newer

Go to Settings (gear icon in the upper right corner of the window).
Go to the Advanced tab.
Switch Logging (for technical support) to Enabled.

frediano.dicarlo · July 17, 2025, 8:51am

NO, on .206 the 2 client have no plugin

Frediano

Rik · July 23, 2025, 12:34pm

Hello Frediano,

I am sorry for the delayed reply. I have tested this issue, and I think I could reproduce the issue on XProtect 2025 R2. Milestone development will start an investigation.

0053X00000GSbIcQAL · August 6, 2025, 8:58am

Hello Frediano,

I have been looking into this issue and found that it is by design that Smart Clients are not broadcasting to the event server when they logged in. This is to lessen the strain on the event server when not needed.

The solution will require a Smart Client plugin using the MessageCommunication. If you already use plugins that does any message communication then you will not need to implement one yourself, but if some or all your Smart Clients are plugin free, then you need a small plugin that starts the MessageCommunicationManager and followed by calling Get() on the MessageCommunicationManager.

This will make the Smart Client broadcast to the event server that it is online for message communication.