GetDevicePresetsCommandHandler exception

MIP
, , ,
1

Hi,

Using 2023 R2 SDK on VMS 2023 R2 Corporate.

We add dynamically camera and issue getdeviceptz command like below:

recserver - recording server object

ServerTask addHardwareServerTask = recserver.AddHardware(cam.sIPAddress, cam.sDriverInfo, cam.sUsername, cam.sPassword);

Hardware hardware = new Hardware(managementServer.ServerId, addHardwareServerTask.Path);

Camera camera = hardware.CameraFolder.Cameras.FirstOrDefault();

ServerTask serverTask = camera.PtzPresetFolder.GetDevicePresets(0);
if (serverTask.Path != null)
    serverTask.GetTask(serverTask.Path);
while (serverTask.State != StateEnum.Error && serverTask.State != StateEnum.Success)
{
    System.Threading.Thread.Sleep(100);
    serverTask.UpdateState();
}
if (serverTask.State == StateEnum.Error)
    throw new Exception(serverTask.ErrorText);
if (serverTask.State == StateEnum.Success)
{
    serverTask.ExecuteDefault();
    String sessionid = serverTask.GetProperty("SessionDataId");
    serverTask = camera.PtzPresetFolder.GetDevicePresets(Convert.ToInt32(sessionid));
    if (serverTask.Path != null)
        serverTask.GetTask(serverTask.Path);
    while (serverTask.State != StateEnum.Error && serverTask.State != StateEnum.Success)
    {
        System.Threading.Thread.Sleep(100);
        serverTask.UpdateState();
    }
    if (serverTask.State == StateEnum.Error)
        throw new Exception(serverTask.ErrorText);
    if (serverTask.State == StateEnum.Success)
    { }
    serverTask.ExecuteDefault();
}

We get exception

AXIS M5013 PTZ Dome Network Camera (192.168.0.114) AXIS M5013 PTZ Dome Network Camera (192.168.0.114) - GetDevicePresetsCommandHandler: Unknown Response type: VideoOS.Common.Integration.Command.ErrorResponse

Thanks,

Vikas

2

If you do the same operation manually in the Management Client, does it succeed or do you get the same error there?

3

It succeeds when done by the Management client.

4

We could reproduce the issue with 2023R2 XPCO and need to talk to Milestone Development regarding the issue, but many developers are out of office due to winter holiday. So, we will get back to you next year. I am sorry for the inconvenience.

5

Milestone Development will start an investigation.

6

We have investigated this issue and have come up with the following solutions:

1: Update Corporate to 2023 R3.

2: Fallback to ConfigurationAPI

VideoOS.Platform.SDK.Environment.Initialize();
VideoOS.Platform.Configuration.Instance.ConfigurationApiManager.UseRestApiWhenAvailable = false;

Make sure the last line is immediately after Initializing the environment at shown above.