Possible Communication Issue between BVMS 8.0 and VRM 3.7x in case .NET version too old

[#1]

Possible causes and solution(s)

• Causes

Possible Communication Issue between BVMS 8.0 Central Server and Video Recording Manager (VRM) 3.7x with BVMS 8.0 installed on different Servers.

Problem Identification

Communication can get interrupted and configuraiton might fail if the below desribed actions are not performed. If your system is affected or not is described here as follows:

• There can be authentication issues between the BVMS Central Server and the Video Recording Manager in case they are installed on different Servers.
• It is possible to see reports at the BVMS 8.x system alarms that VRM reports wrong version
• Please check in the VRM debug logging if the following logline indications can be found

CONFIG;DEBUG;SENDING XPATH /SYSTEM/DEVICES/DEVICE as well as HAS NO CONFIGURED NODE, SET TO CONFIGURED

CONFIG;INTERNAL;/SYSTEM/DEVICES CHANGED IN CONFIG. DEVICEID= [DEVICE IP]\0;SYSINFO;INTERNAL;LINE 1 HAS NO CONFIGURED NODE, SET TO CONFIGURED

• Solution

In general please keep in mind, that it is strongly recommended to use VRM 3.71.00xx with BVMS 8.0.
Do not use any older VRM version like 03.71.0022. The 03.71.0029 and Release letter is available at the BOSCH DownloadStore (status update 2018-10-26).

• https://downloadstore.boschsecurity.com/FILES/Setup_VRM_03.71.0029_win32.zip

Release Letter:

• https://downloadstore.boschsecurity.com/FILES/Bosch_Releaseletter_VRM_3.71.0029.pdf
  

At the VRM system / server, please check and ensure that the following Microsoft software packages are pre-installed:

• .NET framework 4.6.2 or higher
• Redistributables for Visual Studio 2015
  

In case one component is missing, please perform the following steps:

1. Download the missing Microsoft components. Note: When using BVMS 8.0 the VRM is typically a 32-Bit VRM software. Therefore the 32-Bit Microsoft packages are needed.
   Component that was seen as missing is the
   >>   “Visual C++ Redistributable for Visual Studio 2015” 
             https://www.microsoft.com/en-US/download/details.aspx?id=4814
   Please choose the 32-Bit version of that when using with 32-Bit VRM
   and the
   >>  .NET framework 4.6.2 or higher (NDP462-KB3151800-x86-x64-AllOS-ENU.exe)
         https://www.microsoft.com/en-US/download/details.aspx?id=53344
   
2. Stop the VRM (rms.exe) service in Windows services 
3. Install those components with Administrator rights at the VRM server
   Reboot the server after installation of the Microsoft components
4. Check if the VRM service is running and if needed Re-Start the VRM (rms.exe) service
5. Check that the combination of messages are not longer seen in the VRM debug logging

The VRM package is enhanced and users should no longer run into this issue with VRM 3.81 and newer versions.

Please be aware that BVMS releases are tested with certain VRM versions. This still can offer to install a newer VRM than originally rolled-out in the BVMS overall installer.

For all VRM versions 3.7x and below 3.81 it is needed to add this packages.