We have a plugin developed for exaopc communication using local user and received alarm on the Milestone system.
The plugin is functional since 2016 and developed as per Milestone recommended environment.
However, we have recently experienced the plugin alarm is failure with the MIP based developed plugin Milestone XProtect Corporate 2024 R1.
Issue : The plugin was working with the local user.
As of now , it is not working with the local user account and hence not receiving alarms on the milestone.
We are partnered with the Milestone and trust the support that our business will not be impacted due to changes on the latest version.
The existing plugin should be supported as a backward compatibility .
Kindly need your urgent assistance as customer is behind us for the plugin .
Please share the workaround solution for the existing plugin .
Manny Nicodemus
Senior Telecom Engineer
Yokogawa
Plugins should be forward compatible unless in the rare cases where there is a breaking change. Breaking changes would be mentioned in the release notes. https://doc.developer.milestonesys.com/html/
To me it sounds, from your description, like it could be an issue that the user you are using and the role it belongs to might not have the necessary permissions. Please double-check this. As an experiment try to put the user into the Administrator’s role and observe if it makes a difference.
If that is not it, I need you to elaborate on the issue. What does the plugin do exactly? What is the setup? What SDK methods are used? What is the error? Errors mentioned in the logs? Where does the plugin run (Smart Client, Event Server, Management Client)? What do you observe troubleshooting or debugging?
Hi @Bo Ellegård Andersen (Milestone Systems),
Thank you for your reply.
We created this plugin since 2017 and have been successfully using it since then until we started facing the issues.
On the server side, part of the plugin runs in the Event Server. However, to enable the plugin to communicate with the source (which is an OPC DA server), we have to configure the Event Server to run with a local account (even in a domain environment) to work around DCOM limitations.
We were able to do that successfully until recently. There seems to be some security changes from Milestone that prevents this scenario. We have already tried the procedure to change the server account but it doesn’t help.
We need your support to enable us to continue using the local account for the event server since we need to resolve and demonstrate urgently to our customer. In the long term, we need to identify a workable solution with the new security model from Milestone.
Hi @Bo Ellegård Andersen (Milestone Systems) ,
Can you please update on above request?
If your issue is that the Event Server is changed in which users the service can run as I don’t think it is a SDK issue, in that case you might be better helped asking the Support Community -https://supportcommunity.milestonesys.com
Please include what happens when you try to change the server account, if that is what is not working.
If it is down to the SDK please see my questions above.
Note. It seems to me, if you need to run as a certain user towards the XProtect Vms and/or your OPC, that you have implemented a plugin is a bad design choice, a separate service or app seems to be the logical choice then.