We have a developed a driver using your framework and it has been working for some time. The device has a camera, mic and metadata. After we upgrade Milestone system this driver is stuck without status in Management client and the driver is not working. Even if we restart the recording server or the computer. To resolve this we need to do a “Replace Hardware” or “Update Hardware”. And after this the normal status is shown and driver is working.
We suspect that this issue was introduced in 2024 R2c. And after we get a warning during installation about “Drivers potentially missing after installation”.
Why does this happen, any way to resolve this without having to use Replace Hardware
I think I have reproduced the same issue in the Milestone test lab using the DemoDriver. We will start an deeper investigation.
Milestone did the investigation and found:
There is an issue upgrading the recording server and using MIP Driver Framework based devices. After the upgrade the device will not start, in order to get the device running in XProtect you will have to do “Update Hardware” (simpler and recommended in comparison with "Replace Hardware).
Milestone has developed a fix which is in final testing and will be included in 2025R2, until that version you will have to use “Update Hardware” towards MIP Driver Framework based devices after an upgrade.
Ok thanks for the responce. Can you confirm in what version this issue was intruduced.
2024R2. Your suspicion was correct, that it was introduced in 2024R2.
Has there been a fix to this? I am on Xprotect Professional+ 20225 R3. I upgraded from 2023. We have a ton of cameras that I am having to do this fix
When you are in this situation you will unfortunately have to do Update Hardware on each device.
A fix is in place that it will not happen in future further upgrading.
We did a renewed test in the Milestone test labs based on your question.
We installed 2023R3, deployed Demo Driver, added the Demo Driver device, with this running we upgraded to 2025R3 and saw no interruption to the device. We think the fix for the upgrade scenario works. Why you have experienced differently is right now a mystery.