Security: Video

During the troubleshooting process, the Central Technical Support team often needs to run several different loggers to gain a more complete understanding of the problem. This log collection method is useful only when an issue can be reproduced fast, because the logs are overwirtten.

Related Products: BVMS SDK, BVMS    Overview: BVMS Scriptlets can be debugged via logging to a logger file or messaging to the Operator workstation. This article describes how to enable BVMS Scriplet logging. You can log to the Server Script log or the Client Script log. Logs are default send to C:\ProgramData\Bosch\VMS\Log   1.Creating Log files ClientScriptLogger – automatically created Creates file “ClientScriptLog.txt” ServerScriptLogger - automatically created  Creates file “ServerScriptLog.txt”   2.Log information to the log files There are 3 methods to log information: Log Info Log Error Log Debug   Examples: [Scriptlet("59c4d66e-9395-4dcc-8d27-90dc2b7a00c4")] public void DemoLogger() { //use refence:C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 MessageBox.Show("Hello World"); Logger.Info("Hello World script started"); Logger.Error("Hello World script started"); Logger.Debug("Hello World script started"); // Not writing to ClientScriptLog.txt ! }   3.Logging Location - C:\ProgramData\Bosch\VMS\Log. The logs are automatically collected by the BVMS Configuration Collection Tool. 4.Changing the location of the BVMS Scriplet Logging.   Server Scripts : Logging Directory can be found in the file: C:\Program Files (x86)\Bosch\VMS\AppData\Server\CentralServer\BvmsLogCfg.xml and is defined by the ServerScriptLogAppender path: Default: </appender> <appender name="ServerScriptLogAppender" type="Bosch.Vms.Shared.Logging.Imp.RollingFileAppender, Bosch.Vms.Shared.Logging.Imp"> <file value="%CommonApplicationData%\\Bosch\\VMS\\Log\\ServerScriptLog.txt"/>   Client Scripts : Logging Directory can be found in the file: C:\Program Files (x86)\Bosch\VMS\AppData\Client\OpClient\ApplicationWiring\Nvr\LogCfg.xml and is defined by the ClientScriptLogAppender path: Default: </appender> <appender name=“ClientScriptLogAppender" type="Bosch.Vms.Shared.Logging.Imp.RollingFileAppender, Bosch.Vms.Shared.Logging.Imp"> <file value="%CommonApplicationData%\\Bosch\\VMS\\Log\\ClientScriptLog.txt"/>

This article explains how to enable and collect Video SDK Logs for VSDK based applications.

   Find attached the French version of this article!   🕞 This procedure takes in average ~ 10 min to complete   This information may be requested by Central Technical Support Team, as the bundle file is useful for troubleshooting the improper behavior of the unit. The method for collecting the NetApp DSA E2800 support bundle file from SANtricity Storage Manager App is provided below.   Step-by-step guide   Please make sure that you have the SANtricity Storage Manager App installed on your unit. 1. Open the SANtricity Storage Manager App   2. Right click on your DSA E2800 > select "Execute Script..." option    3. Add the following line in the Script Editor:  save storageArray supportData file="c:\supdat.7z" force=true;   4. Go to Tools and select "Verify Syntax"   5. "Syntax check complete" message should be displayed   6. Next, go to Tools and select "Execute Only"   7. To perform this operation, you have to login with your DSA E2800 credentials > click OK > "Working" message will be displayed Note: it may take a while for the next window to appear 8. Select "Add Security Exception" and next "Confirm Security Exception"   9. You will be prompted to enter the credentials again. Fill in the necessary details and click OK   10. The Script will start the execution and the bundle file will be exported.   11. The file will be downloaded in "C:\"     Nice to know:   How to download the support bundle file for DSA E2800 via WEB browser? How to download the support bundle file for DSA E-Series E2700?   You can also see the NetApp Knowledge Base:  How to collect an E-Series support bundle via SANtricity command line interface Note: You should have a NetApp account to access the NetApp KB article above.

This article explains how you can collect VRM logs in different versions of it

The ASUS Inband Tool is the preferred log collection tool, all relevant logs can be gathered from there for ASUS Tech Support. LSI Storage Authority, LSA for short, can be found on the DIP74xx’s Windows desktop. 

With the release of the DIVAR IP all-in-one 7000 gen4 (DIP-74xx), a new tool is available for health monitoring and log gathering, it essentially replaces SuperMicro’s SuperDoctor5; the ASUS Inband Tool. This tool operates as a service on the DIP and provides a webpage with hardware health monitoring options, hardware status details, and hardware information, as well as an option to export logs and run reports.

The internal logs are directly located in the folder C:\ProgramData\Bosch\VMS\Log and then are named like "CameoSdkLog_Instance1.txt.0".  To activate the Cameo SDK logging, the "Init" button has to be pressed after setting the checkbox "Internal logging" and entering an instance name - then logging is activated with the given instance name (e.g. "Instance1").

Learn from this article how to collect RAID Controller Event log, Diagnostics Logs or Server Report of DIP 6000 AIO via LSA for more in-depth troubleshooting, which might be required by Central Technical Support Team.

In this article is explained step by step how to collect System Manager logs from your DIVAR IP all-in-one 4000 & 6000.

This article presents where are the Transcoder Log settings and how to enable them for log collection.  

This article explains what action should be done for DIVAR IP 7000 Gen 3 before collecting IPMI logs

Central Technical Support team may ask you to provide them with the logs from VIDEOJET decoder 7000 (VJD-7513). Follow this article and find out how to do this!

Follow the steps below from this article to collect the configuration data file and the maintenance log file that might be requested by Central Technical Support team for troubleshoot & support purposes.  

This article provides a background information about syslog, tips for 3 rd party Syslog server options and step by step instructions how to configure, activate and collect the syslog.

This article explains the most common way of gathering logs from a SONY camera.

Based on the symptoms of no steaming video, a blank diagnostic log and the message below in the logs, there could be a few possible problems. These would be internal hardware issues.  

Central Support Team may ask you to provide them with the log files and configuration file of Intelligent Insights.This article explains you how and where you can get them.

You can collect Service logs from the unit using two methods. Both methods will save the service logs as a password protected ZIP file ( Example: ServiceLog-XXXXX.zip ).

This article explains you how and where you can get the logs of your camera. The system logs are extremely useful for troubleshooting recurring or obscure problems, as they provide a record of all work performed on the system and may shed light on hard-to-spot interactions between seemingly unrelated symptoms.