Hello,
using SDK 2023 R2
XProtect professional+ 2023 R2
When we give addhardware via SDK getting error : unable to connect to the recording server while setting up the hardware milestone
Please suggest where to look for exact cause.
Thanks,
Vega
Can you add the same hardware using the Management Client (MC) or does that fail the same way?
In MC in System Dashboard- Current Tasks, on the recording server do you see any hanging tasks?
When you get the error is the hardware added?
Two possibilities:
- The hardware is added and the error happens even though it is in fact added.
- The hardware is not added so the error given is correctly signaling this.
Tip; in MC do a refresh and see if the camera is present for both.
Has the camera been added and removed previously?
If you are using your own integration, please test with the Adding Cameras Using Configuration API sample using the newest MIP SDK NuGet and see if the issue is the same using it.
Yes, we can add using MC.
- The hardware is added, but the error still occurs even though it is in fact added. - Correct, we see hardware is added and in a disabled state. But immediately get SDK return as error: unable to connect to the recording server while setting up the hardware milestone
Has the camera been added and removed previously? - Yes
Tested with ConfigAddCameras using the latest NuGet 26.1.19408.1 , mipsdk-samples-component-main\mipsdk-samples-component-main\ConfigAddCameras still getting the same error.
Clarification needed: This is the error you see while adding hardware, or do you see the same error again if you afterwards try to find the camera in the configuration in MIP SDK? Please explain this to me in detail.
It might be possible to develop a workaround where you after having this error try to read the camera again and if that works then enable it and continues doing the originally planned operations.
I have an idea that there should be something in the Recording Server’s debug logs at C:\ProgramData\Milestone\XProtect Recording Server\Logs that indicate an error at the time the add was tried, but it is only a guess.
Do you ever see this issue in a newer version of XProtect? Note that 2023 R2 in the Milestone product lifecycle is “Limited availability” which means that only operation-critical issue will be fixed.
The error is only while adding, now even after we get error, we continue and check added hardwares , if added we continue.
We developed workaround as suggested.
Now MoveHardware is failing with error like - VMO60261: Could not move the hardware.
The target recording server is in failover mode or not connected.
Thanks,
Vega
In this situation: Does it matter if the move hardware operation is done using MIP SDK method or you do the operation using the Management Client?
Yes, failing in both
Adding to the case - site is https
As mentioned, XProtect 2023 R2 is currently in a “Limited Availability” lifecycle phase. This means that only operation-critical issues are addressed.
Because of this lifecycle status, Milestone Support is unfortunately not able to go into deeper investigation