About Central_Support

Possible causes and solution(s)   System structure: BVMS Server Windows Server 2022 Standard 21H2 with BVMS version 11.1.1   Symptoms   OPC server is installed on the BVMS server OPC client software is installed (the client used in this article is Softing OPC Toolbox Demo Client), and the user can connect to OPC server that is running on BVMS server, but the user cannot send any command from 3rd party OPC client to BVMS system, for example changing the status of virtual inputs. There are no events coming from OPC to BVMS and the OPC client is not present in the list for third party integrations with BVMS (see details: Which are the components that establish a connection between BVMS& 3rd party management system? )   Solution   The correct steps to follow are to be found within this article and taking in consideration the below: 1. Register the OPC service again Register the BVMS OPC Server (run the following tool as Administrator: <Program directory>\Bosch\VMS\bin\RegisterBvmsOpcServer.exe ). Confirm the password for the mgts-service user configured above 2. Export the OPC configuration from BVMS again 3. Delete the file - C:\Program Files\Bosch\VMS\AppData\Bosch.Vms.BISProxy.settings.cxml 4. Start the Softing OPC Client    5. The correct view should be as below (be sure that your server’s name didn’t have strange symbols before the actual name or you didn’t you edit the following file in your previous attempt somehow - Bosch.VMS.BISProxy.dll.config😞   6. To see if the connection is established, check if you receive in Softing Client events from BVMS (first configure an event, for example VI, then toggle it with - C:\Program Files\Bosch\VMS\bin\VirtualInputsTest.exe and see if you receive the event in the Softing Client)   7. If everything is as expected till this step, then you can send via CMD the command for toggling the Virtual Inputs. ... View more

Question   Why is the error in the pink box when accessing the VCA Tasks & Metadata Generation (Configuration Manager)?   Answer   One of the reason for this error when trying to access the VCA Tasks/ Metadata Generation could be generated because of the configured tasks which exceeded the Script Size limit (limit=2000 bytes) and metadata cannot be read. Therefore, please check the below article to find more information regarding this topic and make sure that the configured script does not exceed 2000 bytes: How to create the VCA fields for multiple presets in Configuration Manager?    If you lower the Script Size limit and this error persists, get in contact with the Central Technical Support team for a detailed investigation and provide them with your findings including the following: Detailed problem description Logs, diagnostics, Print Screens with the issue and videos ... View more

Scenario: Integrating and configuring the Adam 6051 units with alarm buttons into BVMS installation. An alarm button is connected to the Adam unit and when this input is activated (close or open), a full screen camera image shows on the display. The display is always logged in the Operator Client for live camera view on the DIVAR IP 7000 AIO. The Adam 6051 unit is seated in the same data cabinet, and all devices plugged in the same network switch with no VLANS - a basic network configuration. There are not used any decoders to switch any of the camera views.   Step-by-step guide   1. BVMS configuration - Adding the ADAM module Once logged in to BVMS Configuration Client, navigate to Devices > Other Devices > Right click on "I/O Modules" and you can either scan for the ADAM module, or add it manually using the IP address and specifying the type.   2. Once added, you will see tabs for the ADAM module, Inputs, and Relays. If you added an ADAM-6050, you will have a total of 12 inputs and 6 relays that you can use within the system. Each of the relays and/or inputs used for this configuration should have a unique name so that they can be easily identified later. 3. Afterwards, configure the desired state in the Events tab.    4. Configure the Alarm afterwards. Please note that the Priority will have to be maximum 9 in order to trigger the full screen action. Otherwise, you will receive the alarm in Operator Client, but the cameo will not display the camera's image in full screen.    Note If the alarm events have the same priority set (e.g. 1), the 1 st  triggered alarm will have to be accepted or lower priority alarm can be displayed.   In the attached video there is a screen recording of the behavior seen on the Monitor. The relays are closed. Relay 2 was first triggered, and the Alarm event displayed the configured camera full screen on the monitor, afterwards Relay 1 was triggered and the camera configured for that Alarm is displayed over the previous one. ... View more

Question   Does the log4j pose a risk when Microsoft SQL server is installed with BVMS installation package?   Answer   We have identified that the vulnerable Log4j 1.2.17 component is installed as part of the setup of Microsoft SQL Server 2019 on Windows, all editions. The vulnerable component is not actively used or called by the SQL Server or by the BVMS. This means that the vulnerabilities are not exploitable unless you install some additional components that refer to the vulnerable component. Therefore, there is no risk of exploitation within the SQL Server or BVMS environment. There is a security information published: here → this security information gives exact details on how to mitigate this and how to achieve that the vulnerable log4j component gets removed by installing that cumulative patch from Microsoft latest version of the patch: Download Microsoft® SQL Server® 2019 Latest Cumulative Update from Official Microsoft Download Center https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2019/cumulativeupdate25 BVMS is not using log4j, and neither is the SQL server in the way we use it. (only to use the MS SQL Server installer "as is" and it installs the log4j binaries) Additionally, BVMS does not install Java runtime, and in absence of that, the log4j does not pose a risk. Therefore, this is similar to the statement for CVE-2021-44228 that BVMS is not affected CVE-2021-44228 not affected BT productsR8.indd (boschsecurity.com) In response to CVE-2021-44228 Microsoft advised (https://msrc.microsoft.com/blog/2021/12/microsofts-response-to-cve-2021-44228-apache-log4j2/#sql-server-on-windows---all-editions) to a user who enables Java to “upgrade to the latest version or remove the Java Archives (JARs) that require the dependency”.   Is the end customers install Java runtime by themselves (or any other 3rd party software that installs Java) and use 3rd party software that makes use of the log4j from SQL Server DTS folder, then it becomes more challenging as in this case the customer may create vulnerable PC configuration (that might in turn endanger BVMS or any other software on target PC/network). This cannot be prevented by us and it is responsibility of the end customer to ensure vendor provided patches are also installed in timely manner.    Nice to know: Subscribe to this article and stay up to date with the latest published Security Advisories related to Bosch products: Bosch Security Advisories - PSIRT (Product Security Incident Response Team) ... View more

Possible causes and solution(s)   Symptoms   We have received reports that some customers are having issues with Intelligent tracking when it’s enabled manually or via script. This is seen in scenarios when the user does not want to have intelligent tracking on all the time because of compounding alarms or other environmental variables. We found that there was a change in the way intelligent tracking worked after CPP 7.3 firmware v7.62.0005. With these changes if an object triggered an alarm that turned on intelligent tracking, the camera would not track the object. It would wait for another object to trigger an alarm to track it.   Solution   Currently, there are 2 workarounds to get the desired behavior with CPP7.3 firmware:   1. Using a duplicate alarm with a debounce timer:   Example First task may be used to turn on autotracker (mode: auto) //@Task T:2 V:0 I:2 "Crossing line 2" { //[1.a=(s1:1);1.b=2;1.h=32;11.a=o:20.0;] Event #32:={CrossedLine#1} ; external Event #2 := {Event #32 !before(0,20.0) Event #32 where first.oid == second.oid}; //@} And second Task will be most properly triggered by the same object may be followed by the autotracker //@Task T:2 V:0 I:3 "Crossing line 3" Unknown macro: { //[1.a=(s1} ; //@} 2. Use the VCA task editor to remove triggers from the VCA task:   Example //@Task T:1 V:0 I:1 "Object in field 1" { //[1.a=(s1:1);1.b=1;] external ObjectState #1 := InsideField #1;  external Event #1 := OnSet ObjectState #1;  //@} ... View more