We developed a plug-in integration using a 2018 SDK. The Configuration API is used extensively in the background plug-in. Specifically in the code that adds cameras, which is actually based off of the ‘ConfigAddCameras’ sample in the MIPSDK.
Unfortunately we learned our client still has XProtect Corporate 2014 7.0d and of course our plug-in doesn’t work. I’m tasked with trying to make it work. Before I continue to sink more time into this, I wanted to first check if this is even possible as I see that the Config API was introduced in 2014, but extended in 2016.
Currently, the error I’m stopped at according to the logs is:
`Error ConfigurationApiItemWrapper ConfigAPI GetItem(): The server doesn’t support the specified path Parameter name: path`
The `server doesn’t support the specified path` actually comes up several times in the logs
Thank you
The sample was introduced in 2018R1, so from then on and in newer versions it will work.
The error you get means that the item (path) is not supported, so it is the expected error message for suing something that is not supported in the older VMS.
Ideally the exception would have listed the path, because that would have told you what it is that is not supported.
Perhaps you can single-step debug and find what is the last call when the exception happens.
If you do this, let me know, I might be able to say more based on that information.
If you run the Config API Client sample against the old VMS, it should work, and it should simply put forward the items and methods that are supported. The sample does use strongly typed classes, and is therefore harder to follow and understand. But to the question whether it is at all possible; please test with the Config API Client sample, if you can add a camera in that sample it is possible..
Thanks for the info. I do have a follow up. We decided to skip the automatic camera addition functionality for now and focus on getting our client side plugin working, which uses messages that the background plugin listen for. The messages aren’t being registered however and the exception is still happening.
I tried to debug step by step but was unable to locate the cause. Eventually, I completely removed all plugins from the MIPPlugins folder, and the exception was still happening when I check the MIP logs.
Do I need to try and use an older SDK version? I know you always suggest using the latest SDK, so we’re using 2019R1 SDK with Corporate 2014. Could that be causing the exception?
So your plugin which does not do any Configuration API operation still causes this message in the logs?
(Error ConfigurationApiItemWrapper ConfigAPI GetItem()
Please verify, your plugin does not use VideoOS.Platfrom.SDK.dll and the only referenced (Milestone) dll is the VideoOS.Platform.dll?
In which environment(s) does your plugin run? (Event Server, Smart Client, Management Client?)
The VMS is XProtect 2014, if your plugin runs in one of the clients, which version is the client?
If you remove all plugins, restart the Event Server, do not run any MIP SDK based standalone application and you still see the exception, then we might have a mystery. The question about MIP SDK version becomes irrelevant if you have nothing running or loaded.
I can only think of the Mobile Server that could potentially use the MIP SDK logs.
Please clarify or double-check, do you see the error even if no app or plugin is in play?