About Galina

In order to quickly offer a technical solution or to provide a professional advice for the next analysis steps, the technical support specialists need to get some general and basic information. Ticket content should always be in English and provided in a well summarized and structured way in order to be able to provide a quick and appropriate feedback. Not following the guideline will impact the processing time of the ticket.   Related Products: BVMS, Operator Client This article describes the initial information needed to start troubleshooting Operator Client Crash.   General Information   SMA validity How to retrieve the Hardware ID for BVMS and check the Software Maintenance Agreement (SMA) status? BVMS stand alone or appliance Detailed problem description   Symptom specific Information Problem Description   Note down the events that lead to crash Classify the crash reproducible crashes that trigger Windows Error Reporting crashes/ hangs/ freezes that are hard to reproduce, or take long before repeating   Logging Information   Dump file from the crash – refer to the following article How To create BVMS memory dump?  ConfigCollection from the machine where the crashing Operator Client is running. ... View more

Related Products Workstations, Z4G4, Microsoft License Question Is it possible to Activate Windows 10 by phone for Bosch Workstations? Answer With introduction of Windows 10, Microsoft disable the phone license activation for Bosch Workstations. Please perform online activation over internet. ... View more

This article shows how to configure Input Alarm and later search for them in the Event search using Web Interface. There are only 3 different search parameters for Event type search, which are "All", "Motion" and "Alarm". Once can search for any alarms during the set time period and channel and in this way indirectly to filter for Input Alarm (if only Input Alarm triggers Recording for a particular channel). It is not possible to directly narrow the search for particular Alarm type (ex. Input alarm).   Step-by-step guide   1.Configure the Input Alarm. Go to: Settings - Alarm - Input Alarm. Click Enable and Chose the respective Input (from 1 to 16), then click Record Channel and Save.  Note: The other Settings like Buzzer, Display Mon. A can also be configured but is not a must for performing Even Search. Schedule the recording. Settings - Schedule: Chose the days of the week, the time and enable "Alarm" Set the recoding stream. Settings - Storage - Recording: Chose the stream to be recorded.   2. Event Search - Chose the respective Camera (that recorded on Alarm Input) and search for "Alarm" ... View more

Related Products: BVMS / MVS / VSDK Overview: On request from development to provide a dump file from MVS system please follow the steps in the solution section.   Step-by-step guide   Reproduce the issue Download the Microsoft debugger procdump (https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx). The procdump tool is also attaced to the article :How To create BVMS memory dump?  When application is crashing, do not click any buttons on the appeared error window that will change the program state. Run the procdump.exe from the directory where you copied the tool with following command line (Start - cmd): procdump.exe –ma <name of the programm exe> <dump file name>.dmp   In the case of MVS you need to do that for all 4 MVS services: - Bosch.MVS.SourceProvider.BVMS.Service.exe - Bosch.MVS.DataStorage.Service.exe - Bosch.MVS.SourceProvider.MobileCamera.Service.exe - Bosch.MVS.Transcoder.Service.exe ... View more

 Find attached the French version of this article!   This article covers all important aspects of BVMS dump creation - error scenarios and corresponding dump creation methods.   Quick links: BVMS_OC_dump_onException.zip BVMS_DumpTools_V2.zip BVMS_OC_dump_Just-In-Time-Debuger.zip   BVMS dumps are needed to troubleshoot the following types of issues: Application crashes – dump is expected to provide more information about the cause of the crash and its origin. Memory or handle leaks – dump is expected to point to their origins Deadlocks, freezes and hangs – dump is expected to point to their origins   Recommended tool to create BVMS dumps. The recommended tool is Procdump. It is a command line tool which must be started from the command shell. Bosch development team provides couple of .bat files that start Procdump with predefined parameters and cover the most common dump creation cases. The tool as well as the set of .bat files are attached to this article.   Batch files for dump creation The batch file names follow a naming guideline: <Executable>_<Dump use case> where <Executable> is one of: ConfigClient ConfigWizard OperatorClient ManagementServer ArchivePlayer ExceptionTest and <Dump use case> is one of: SingleDump TwoDumps DumpOnException E.g. batch file OperatorClient_SingleDump.bat immediately creates a dump of the Operator Client process, while OperatorClient_TwoDumps.bat creates two dumps of the Operator Client process with a delay of 1 hour between the dumps. OperatorClient_DumpOnException.bat creates a dump of the Operator Client process as soon as it throws an unhandled exception.   Note that also batches for executable "ExceptionTest.exe" are provided. These batches can be used for testing purposes - ExceptionTest.exe is a little test application that simply crashes when being started. There is an additional batch file "ActivatePostmortemDebugging.bat" which registers procdump as Just-In-Time debugger. Calling this batch will ensure that a dump is created when Windows Error Reporting is triggered by a crash. To learn more about the advanced capabilities of the procdump tool, start batches ShowProcdumpHelp.bat and ShowProcdumpHelpSamples.bat. These batches display procdump options and some samples for how to use prodcump.   Error scenarios and corresponding dump creation methods The procdump tool is useful for creating dumps for different problem scenarios: Issues which can be easily reproduced application crashes which trigger windows error reporting memory or handle leaks Issues which are hard to reproduce sporadic application crashes or crashes which do not trigger windows error reporting application sporadically becoming unresponsive (freezes/hangs)   Step-by-step guide   A. Dump creation for reproducible crashes that trigger Windows Error Reporting To create a dump for a reproducible crash, follow these steps: Run the affected application/service (Operator Client, Configuration Client). Note: Management Server Service is running by default. Reproduce the steps that lead to the crash Leave the Windows crash dialog open Run the corresponding batch file for creating a single dump: *_SingleDump.bat. E.g. run OperatorClient_SingleDump.bat to create a single dump of the Operator Client process. Provide support with the resulting .dmp file a description of the steps to reproduce the problem a ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_onException.zip   B. Dump creation for reproducible memory or handle leaks To create a dump for a memory/handle leak, follow these steps:   1.Run the affected application/service (Operator Client, Configuration Client). Note: Management Server Service is running by default. 2. Run the corresponding batch file for creating two dumps: *_TwoDumps.bat. E.g. run OperatorClient_TwoDumps.bat to create two dumps of the Operator Client process. Note that by default, the delay between the two dumps is set to one hour (3600 seconds). Depending on the magnitude of the memory leak, you might want to increase/decrease the delay. To do that, edit file *_TwoDumps.bat: replace value "3600" by a value that fits your needs E.g. a value of "7200" will create two dumps with a delay of two hours. 3. Reproduce the steps that lead to the memory leak. Wait until the second dump was created. 4. Provide support with the resulting two .dmp files a description of the steps to reproduce the memory leak a ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client, as well as additional examples - BVMS_DumpTools_V2.zip   C. Dump creation for crashes/hangs/freezes that are hard to reproduce It is impossible to create a manual dump for sporadic crashes/hangs/freezes or for those cases where a crash does not result in display of a Windows Error Reporting dialog. For these cases, procdump should be registered as just-in-time debugger. To register procdump as just-in-time debugger, follow these steps:   Deactivate the restarting option for Operator Client / Configuration Client (skip this step for BVMS MS issues). To deactivate the restarting option for Operator Client / Configuration Client: edit ..\Bosch\VMS\bin\ConfigClient.exe.config or ..\Bosch\VMS\bin\OperatorClient.exe.config. Navigate to section <appSettings> add a new entry <add key = "DisableExceptionHandling" value="TRUE" />. Run ActivatePostmortemDebugging.bat (run it with administrator rights)   Run the affected application/service (Operator Client, Configuration Client). Note: Management Server Service is running by default. As soon as the issue appears, check whether the dump was created. Provide support with the resulting .dmp file a description of the steps to reproduce the crash a ConfigCollection Note: attached you can find a configured example for this scenario and application Operator Client - BVMS_OC_dump_Just-In-Time-Debuger.zip Note: after collecting the logs, please disable the debugger - delete the Auto and Debugger registry entries (they were created by command in point 2. Run ActivatePostmortemDebugging.bat ) ... View more