ConfigurationService.GetChildren(EnvironmentManager.Instance.CurrentSite.ServerId, "/RuleFolder") --> throws exception

MIP
, ,
21

Thank you for the suggestion. We already planed to do that.

Would you happen to have any API call or solution (sql query) to get those rules which have removed devices? Would be nice if we could list them.

22

Sorry, the only supported way is to use the methods which fails the way you have described. It is not supported to read the configuration db and the table [Surveillance].[dbo].[Rules] directly.

23

Sorry, this used to be supported but is no longer supported. It is neither supported nor recommended to apply a newer VideoOS.Platform dll to an older environment (Management Client, Smart Client, Event Server).

To indicate to the end-user that there might be rules that have not been maintained and include removed devices is the best advise I can give.

24

Does this mean that changing the dll-s is not suggested? What do you suggest as a solution? How can we support our clients with your API on versions 2023 R1, R2 and R3? The problem is that we don’t have anything which supports us finding which rules are bad because the exception does not provide this information.

Unfortunatly we still have a client where we could not find which rule is the problematic. They are still waiting for your fix.

25

This is news to us and might change our perception of this. You have a setup (at a customer) where you cannot see any rules with ‘unknown device’ or ‘deleted device’ and experience this issue?

If you can tell us details we would be interested in investigating this.

26

Hi,

Our client has a lot of rules and we could not find the “unknow device”.

My question is: are you going to provide a new Videoos.Platform SDK? If we build our plugin with the new SDK will you be handling the rules containing “unknown device” correctly (as before 2023 R1) or at least throwing an exception with some details which are the “bad” rules?

27

@Bo Ellegård Andersen (Milestone Systems)​

Would you happen to have answears to my last questions? We need to figure out something because our solution still fails with the SDK.

Best regards,

Attila

28

I am so sorry, thank you for the reminder, I hope to have a reply soon..

29

Milestone Development is now in the process of, for each of the versions 2023 R1 to R3, building a VideoOS.Platform.dll with fix.

30

Thank you for the update.

31

There is a fix for 2023R3 - https://supportcommunity.milestonesys.com/KBRedir?art=000056000&lang=en_US

32

Hi @Bo Ellegård Andersen (Milestone Systems)​

Unfortunatly we could reproduce the issue with the above described steps even after installing the cumulative patch installers.

  1. add resource

  2. add rule

  3. remore resource

  4. call ConfigurationService.GetChildren(EnvironmentManager.Instance.CurrentSite.ServerId, “/RuleFolder”) → this will throw an exception, the text message will still be “Unknown error”.

Can you let me know when will you fix the problem?

33

re 4. Where do you call?

If this is a Smart Client that the patch is here. https://supportcommunity.milestonesys.com/s/article/XProtect-Smart-Client-2023-R3-cumulative-patch-installers?language=en_US

34

We call it from the management client.

35

I am sorry, you are correct, the fix doesn’t work for me either. I will ask Milestone Development to investigate.

36

Hi @Bo Ellegård Andersen (Milestone Systems)​

Do you have any update on this?

37

The fix did work for me, I had a failed test but that was a mistaken test.

I was meaning to ask you: When you test your MC Plugin after applying the fix, do you get the same exception? If different please let us see the exception and stack trace.

Sorry for leaving you waiting on this update, I can see I made a mistake..