MIPSDK 2018r2 component integration samples not displaying video

MIP
, , , ,
1

Upgraded MIP SDK to 2018r2 and the sample applications give me a can’t connect to camera (reconnecting to camera) message. The 2018r1 samples still work. The 2018r2 component integration samples build and run, they just don’t show any video live or playback.

2

Sounds like you have run out of license on the server side - do you connect to same VMS install?

Does Smart Client show vide?

3

Smart Client 2018r2 was also installed and it works fine. All software connects to same VMS. If it is a license issue, why does MIPSDK 2018r1 still work?​ I believe we are operating on a temporary license of some sort.

4

Smart Client of different versions can connect to any VMS version. But what version is your VMS.

If you have a “Cant connect to toolkit” message - you might be missing a DLL in your solution.

5

VMS is 2017 version. We are using the VideoViewer sample application to debug this problem. It will connect to the VMS and allow you to select a camera, but the camera will not display video. It will only say “lost connection to camera… Reconnecting”. It doesn’t display live or playback video. This is true with both the 64-bit and 32-bit versions of the MIPSDK.​

6

There are 2 messages that are similar, when the client is unable to connect to the recorder, and when the recorder is unable to connect to the camera.

Also, if you have missed copying one of the WPF player DLLs from the BIN folder - you can get a message like this.

I suggest you try copying all files from the BIN folder to the sample executable folder, and try take a look into the MIP log to see if any error messages are logged.

7

Thanks for the quick response. For 64-bit, the Visual studio solution for the sample applications copies the necessary DLL​’s from the MIPSDK/bin folder. For 32-bit we copy all the files from the MIPSDK/bin folder. This is the same process we use for the 2017r2 version which works fine. Are you talking about client side logs or server side?

8

Client side log, under the ProgramData\MIPSDK folder.

But we found at one point that some DLLs were missing in the bat file, that is why I suggest to copy all files - just to check.