Hi Team,
I’m seeing this error for some cameras when I try to edit any of its settings via the Milestone PowerShell module.
From my understanding, it’s caused by the PowerShell cmdlet validating the entire camera setting instead of the one you try to apply, so if any of the defaults are incorrect, then that needs to be fixed before applying any setting.
Usually the error points some direction on what value is incorrect here (and I’m able to get past the error by fixing that setting), but using the config api client, whenever I try to change a camera setting for the problem camera, I’m getting a generic error of “Property definition invalid (jnternal error)”
Anyone have any pointers on trying to find what incorrect setting is causing this on the camera? I compared the settings side by side with a working camera and I don’t see any weird settings that could cause this error (usually it’s some blank values or something along those lines)
Thanks!
Hi @Dylan Mak ,
The only other time I’ve observed this error is when a new/updated device pack driver supplied a default setting value to the management server which did not pass the validation rules associated with the setting. What happens then is the configuration API returns the DeviceDriverSettings object with the streams and their settings, we change a setting and then call “Save()” which ships the whole object back to the management server. At that point the server attempts to validate the object and all it’s properties, fails to validate one of them, and returns a validation error. The exception object normally has a property with a collection of validation errors with a property name and a message like “out of range” or something of that nature.
If you have a camera that is actively giving you grief, and the config api client SDK sample also throws an error when trying to change settings, open a technical support case with us and provide as much information as you can about the problem camera, as well as another camera as identical as possible which doesn’t show the issue.
I would avoid discussing PowerShell / MilestonePSTools with support/dev as the issue is apparent when using the config api client sample which is specifically developed and maintained by the SDK team. Adding powershell to the mix will only risk someone lobbing this back to me and the module and your script are not the source of the problem. When you get a fix and the config api client works consistently, you are more than welcome to come to me with the PowerShe’ll questions if you’re still seeing weird behavior there.
Heres some of what technical support / dev would likely want to see to get to the bottom of this:
SQL backup if possible. If not possible, but a narrow scope of information from SQL can be shared, we can ask dev what data makes the most sense to retrieve and to share the relevant TSQL.
Camera ID, and make/model/firmware for the broken/working units.
Device pack version.
Diagnostic Tool logs from the Management Server and Recording Server.
Understood, will do! Thank you for the pointers.