I have an XProtect Access (ACM) integration for S2 Netbox that I’ve maintained for many years, which does not work with 2025 R3. The plugin loads fine in the Event Server, and all functionality in the Management Client works; you can associate doors and cameras, look at live data on the diagnostic tabs, search cardholders, etc. You can even execute commands, so two-way communication with the plugin and access control system is working. No errors show up in the MIP log. However, when logging into the Smart Client an error is displayed during initialization: “Retrieval of the configuration failed. Server communication error”. If you look in the Event Server log, you get the following message at the same time:
ERROR - AccessControlWebService Unhandled exception in access control web service [get_Item] with message: The given key was not present in the dictionary.
Since everything in the Management Client works, nothing shows up in the MIP log, and this error does not specify what key is missing from which dictionary, I’m a bit stuck on how to figure this out.
Any suggestions? I’d like to release a fixed version of our plugin for 2025R3.
I guess you use Smart Client version 2025R3, same as the version of the XProtect VMS. For our investigation please confirm or mention the version used if not 2025R3.
I am using Smart Client 2025R3, and had installed all publicly available patches. Looks like this one hasn’t been released yet, and it does fix the problem.
I have a couple of questions:
I assume this doesn’t affect all access control integrations? If so can you tell me if I should adjust anything in our code (ie maybe we’re not doing something wrong, but we’re doing something unexpected).
I have a few customers that have upgraded and are waiting for a fix; do you know when this will be released or should I just send them the copy you sent me?
This could be affecting most Access Control integrations. I will asking Milestone Development for information to clarify this.
The fix is an official patch but right now Milestone is experiencing problems updating the Knowledge Base articles normally presenting the new patches. Please share the patch or patch link with your customers.
I was able to identify the root cause of the issue with assistance from Milestone Development. When Milestone introduced grouping of access control units, a bug was inadvertently introduced.
As a workaround, integrators can avoid the problem by setting ParentUnitId = null (not string.Empty) when creating an access control unit that does not have a parent—for example, a controller or a door that is not associated with a controller.
Please note that your customer can apply the available patch, and the permanent fix will be included in the 2026 release, removing the need for patching. Implementing the workaround may still be beneficial; now you have the information needed to decide whether you want to apply it.