Who rated this article

Possible causes and solution(s)

In August 2018 (10-08-2018) the VRM version 03.71.0029 was released.

The Video Recording Manager 03.71.0029 is fully supported with BVMS 8.0 and Product Management of BVMS and VRM recommend to use this VRM version instead of the former Release version of VRM 03.70.0056.

Changes / Bug Fixes:

One of the main bugfix reasons to use VRM 03.71.0029 is a fix in regards to correct display and replay of recorded clips in continuous and alarm recording mode. This fix is listed on page 2 of the Release Letter.

For Troubleshooting and support reasons it is essential to double-check a reported gap in recording and to analyze on Level 2 and Level 3 support side what circumstanced could lead to a video gap.
See in the following chapter what kind of data a trained BOSCH partner, Installer or Video expert should provide to the BOSCH Technical Support to advise on next steps. The data described here below can and should be collected before the software VRM is changed and updated to a later version.
Note: Video Recording Manager version 03.71.0029 is not the latest available version of VRM, but in combination with other 3rd party implementation or usage of special BOSCH VMS software version (e.g. BVMS 8.0) this VRM version 03.71.0029 may be required.

VRM logging to collect for in depth expert troubleshooting

In certain situations and troubleshooting scenarios extended logfiles might be required. The BOSCH Level 1 and BOSCH Level 2 team will assist all users on how to collect these data and cooperate with the BOSCH Level 3 Support where needed.

1. Backup the configuration of BVMS and VRM (BVMS elements and VRM config.xml file)
   
   
2. Enable debug logging of the VRM
   Depending on the used Configuration Software the debug logging need to be enabled to get an extended logging information. In case a gap in recording happened in the past it is anyhow helpful to enable the debug logging for a defined time for future incidents. To analyze the already occured video recording gap the available VRM logging must be collected.
   
   
   
   
3. Depending on 32-Bit or 64-Bit version of the VRM software, the loggings are found in the "primary" or "secondary" sub-directory structure. Such for
       ...\Bosch\Video Recording Manager\VRM Server  
   folder at your VRM server to find a similar directory view like shown in the screenshot here below:
   
   

    

4. Inside the directory "log" the standard logging data of the VRM are found and need to be collected.
   
   

    

   
   In addition to the standard logfiles of the relevant day, the debug logging from a defined time period need to be provided in case debug logging was enabled prior to an incident.
   
   
5. Here the "debug" logfiles are found:
   
   

    

   The debug loggins are saved in a special directory "debug".
   
   
6. The Spanhistory logging does provide details of the storage usage. It describes which internal "storage block" was used. It describes the IP of the target, the LUN and the block used for a recording. The Spanhistory of the day where the recording was done and shows issues (e.g. the video reocriding gap), the related spanhistory logfiles is required.
   
   
7. As seen in an earlier screenshot above the VRM configuration file is found in the directory:
       ...\Bosch\Video Recording Manager\VRM Server\primaryAll versions of the config.xml need to be provided to the Technical Support.