Access Control plugin disappears from Management Client and Smart Client after creating an Alarm Definition and restarting Event Server (plugin still loads on Event Server)

After restarting event server plugin is not recognized by Milestone management system and Smart client. In the event log, plugin is loaded successfully.

Summary

We have a third-party Access Control Module plugin. It works in Management Client and Smart Client. After we create an Alarm Definition that uses an Access Control event and then restart Event Server, both clients no longer show the plugin or the Access Control system.

Event Server logs show the plugin loaded successfully after the restart. Reinstalling the plugin does not restore it in the clients.

This looks like an Event Server / Access Control web-service / Alarm Definition restore issue, not a failed DLL load.

Environment

  • XProtect Corporate, 2026 r1

If you look at Management Client → License Information, do you see Access Control Doors being licensed? If there is any indication that licensing is blocking the functionality, try activating the license and see if that makes a difference.

If you remove the Alarm Definition again, does the Access Control tab reappear in the Smart Client?

Could you share an example of the Alarm Definition you created?

Also try enabling Smart Client logging and check for any related errors in:


C:\ProgramData\Milestone\XProtect Smart Client\MIPLog.txt

Logging can be enabled in:


Settings → Advanced

PS: I tested this in our lab using the DemoAccessControlPlugin sample with XProtect Corporate 2026 R1 and was unable to reproduce the issue.

Removing the alarm doesn’t make the AC tab appear in smart client. Restarting doesn’t help either. I had to reinstall Milestone.
Here are the logs

I cannot upload MIP log here. It is saying max size reach even though the file is only 16MB

Application.log (4.6 MB)

If you create an Alarm Definition that is not related to Access Control, does the same issue occur after restarting the Event Server?

I see indications that this could be a more general issue and not necessarily related to the Access Control plugin itself. Creating a different type of Alarm Definition could help identify whether the problem is Access Control-specific or more broadly related to Alarm Definitions. Let me know what you observe.

Similar issue happened when restarting event server without creating new alarm.

Thank you for the detailed description.
To get closer to what is triggering the issue, could you help verify the exact conditions?

  1. No Access Control plugin deployed
  • Event Server starts and restarts normally.
  • Alarm definitions continue to work after an additional Event Server restart.
  • No issue observed.
  1. Access Control plugin deployed, but no Access Control system configured
  • Event Server starts and restarts normally.
  • Alarm definitions continue to work after an additional Event Server restart.
  • No issue observed.
  1. Access Control plugin deployed and an Access Control system configured
  • No issue is observed immediately after configuration.
  • After an Event Server restart, the issue appears.
  • Access Control functionality disappears from the clients.
  • Alarm/Event Server related functionality is no longer working as expected.

Could you confirm whether the behavior above accurately describes what you are seeing? If not, please provide any corrections or additional details that may help us better understand the sequence of events.

  1. Access Control plugin deployed, but no Access Control system configured
  • Event Server starts and restarts normally.

  • Alarm definitions continue to work after an additional Event Server restart.

  • No issue observed.

I have installed the Access control plugin. First time I was able to add in Mielstone system and able to see in xprotect smart client. After adding alarm and restarting event server, the access control plugin is not detected by the Milestone system.

Event server is already running. I cannot attach more media. It was saying “I am new user and cannot have more than one media attached.“

I think I found the root cause. It happened after I created alarm and restarted the event server. For the alarm configuration, I used my plugin category as trigger (Access granted) and bind to the all door. It didn’t happen in Milestone 2025 R3 version.

Can you advice me what is the workaround for now.

Thanks for reporting this and for the detailed investigation.

Based on your description, the fact that Alarm Definitions are no longer visible suggests that the Event Server enters a bad state that affects more than just the Access Control plugin itself.

At the moment, the only workaround I can suggest is not creating the Alarm Definition, as that appears to trigger the issue after the Event Server is restarted.

You could also try removing the Access Control plugin and restarting the Event Server. If the plugin is contributing to the condition, this may allow the Event Server to return to normal operation. Of course, this would also mean that the Access Control integration would not be available, but it may help determine whether the rest of the VMS functionality is unaffected.

The behavior you describe is not expected. The Access Control plugin should remain available in both Management Client and Smart Client after the restart.

We are investigating the issue further to better understand the root cause and identify possible mitigation steps. If we discover additional workarounds or relevant findings, I will update this thread.

I uninstalled the plugin but the behavior was still the same. The only workaround was to reinstall the Milestone from scratch.

I am sorry because I do not have a workaround then.
I have created a bug report for Milestone Development, I will await their analysis and the let you know what they find.

It would be interesting for our analysis to know:
Do you see this error on multiple systems? Do you see it in your internal testing as well as with customer installations?

1 Like

It was during development and in one of the customer site.

So two different installations / systems with the same issue, not just a single site that might have its own peculiarities. I will add this fact to the case with Milestone Development. Thank you for clarifying.