What to do if the VRM cannot be reached from BVMS Configuration Client?

Question

Answer

This behavior could occur due to the corrupted or empty configuration files. Restoring a valid backup (config.xml.bak.1) could be a resolution of the connectivity problem.

First, check whether the config.xml and config.xml.bak have 0kb. If this is the case, then proceed further with the steps below:

IP Verification: Check if the IP addresses of both the VRM and the associated unit are correctly set and matched.
File Restoration Procedure:
- Stop the VRM services.
  - Be sure that the config.xml.bak.1 is intact and correctly sized.
  - Backup all existing configuration files to a separate location.
  - Rename the corrupted config.xml to avoid overwriting.
  - Rename config.xml.bak.1 to config.xml.
Restart the VRM services

Upon reopening the BVMS Configuration Client:

The VRM should become reachable.
Camera recording should be resumed.