About W_Ratschmeier

Microsoft Event Logging, when an error occurs, the system administrator or Integrator must determine what caused the error. The operator can then use the event log to help determine what conditions caused the error and identify the context in which it occurred.   Step-by-step guide Starting Event Viewer The procedure for starting Event Viewer depends on your starting point, e.g. windows key + R type in ”eventvwr.msc” hit enter. Selecting Computers With the decent administrative access, you can select any computer in your network to view that Microsoft system event logs. To select computers in Event Viewer: In the top of the console tree, right-click Event Viewer (local), and then click Connect to another computer. Enter FQDN/NetBIOS name or browser to the regarding machine Adjusting Event Viewer Settings In the console tree, right-click the appropriate log file, and then click Properties. Click the General tab. Saving Event Logs In the console tree, right-click the appropriate log file, and then click Save Log File As. Navigate to the subfolder in which you want to save the file, type a name for the file, click the file type, and then click Save. Clearing Event Logs In the console tree, right-click the appropriate log file, and then click clear all Events. You are prompted for whether you want to save the log to a file before clearing it. Click “Yes” to save a log and clear all events. If you click No, the log is not saved, but all events are cleared from the selected Event log. If you click Cancel, the request to clear the log is canceled. Viewing Event Details In the console tree, right-click the appropriate log file. A list of events in the log file is displayed in the details pane of Event Viewer. Click a specific event in the details pane to display the Event Properties dialog box and details about the event. Filtering Events In the console tree, right-click the appropriate log file, and then click Properties. Click the Filter tab. Type the appropriate information that you would like to filter. Finding Events In the console tree, right-click the appropriate log file. On the View menu, click Find. Type the appropriate information that you would like to find in the dialog box, and then click Find Next.   Event Types: Event type Description Error An event that indicates a significant problem such as loss of data or loss of functionality. For example, if a service fails to load during startup, an Error event is logged. Warning An event that is not necessarily significant, but may indicate a possible future problem. For example, when disk space is low, a Warning event is logged. If an application can recover from an event without loss of functionality or data, it can generally classify the event as a Warning event. Information An event that describes the successful operation of an application, driver, or service. For example, when a network driver loads successfully, it may be appropriate to log an Information event. Note that it is generally inappropriate for a desktop application to log an event each time it starts. Success Audit An event that records an audited security access attempt that is successful. For example, a user's successful attempt to log on to the system is logged as a Success Audit event. Failure Audit An event that records an audited security access attempt that fails. For example, if a user tries to access a network drive and fails, the attempt is logged as a Failure Audit event.   The events themselves are what we’re trying to see, of course, and their usefulness can range from really specific and obvious things that you can fix easily to the totally undefined messages that don’t make any sense and you can’t find any information on your preferred search engine. example: The regular fields on the display contain: Log Name – while in older versions of Windows everything got dumped into the Application or System log, in the more modern editions there are dozens or hundreds of different logs to choose from. Each Windows component will most likely have its own log. Source – this is the name of the software that generates the log event. The name usually doesn’t directly match with a filename, of course, but it is a representation of which component did it. Event ID – the all-important Event ID can actually be a little confusing. If you were to Google for “event ID 122” that you see in the next screenshot, you wouldn’t end up with very useful information unless you also include the Source, or application name. This is because every application can define their own unique Event IDs. Level – This tells you how severe the event is – Information just tells you that something has changed or a component has started, or something has completed. Warning tells you that something might be going wrong, but it isn’t all that important yet. Error tells you that something happened that shouldn’t have happened, but isn’t always the end of the world. Critical, on the other hand, means something is broken somewhere, and the component that triggered this event has probably crashed. User – this field tells you whether it was a system component or your user account that was running the process that caused the error. This can be helpful when looking through things. OpCode – this field theoretically tells you what activity the application or component was doing when the event was triggered. In practice, however, it will almost always say “Info” and is pretty useless. Computer – on your home desktop, this will usually just be your PC’s name, but in the IT world, you can actually forward events from one computer or server to another computer. You can also connect Event Viewer to another PC or server. Task Category – this field is not always used, but it ends up basically being an informational field that tells you a bit more information about the event. Keywords – this field is not usually used, and generally contains useless information. As a rule of thumb (common way of doing), you should try searching by the general description, or the Event ID and the source, or a combination of those values. Just remember that the Event ID is unique for each application. So there is a lot of overlap and you can’t just search for “Event ID 122” only. This is because users might find the list is too large and too general, your specific search aspect might not fit your issue. ... View more

 Find attached the French version of this article!   Related Products: IP cameras, Configuration Manager, BVMS Configuration Client   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.   General information: Syslog feature is implemented in all IP BOSCH Products. The BOSCH IP cameras as network devices can continuously send system messages via Syslog to a Syslog server software. This function should first be activated and configured. Once configured syslog will allow a continuous monitoring information even throughout a complete IP camera power cycle (reboot) as the camera starts connecting to the syslog server IP as soon it is getting back online. Syslog can be useful for analyzing issues that are unpredictable and difficult to reproduce.   3 rd party tools as Syslog server: There are many different monitoring tools available on the market. Examples of some easy tools to start working with can be e.g.: PRTG NETWORK MONITOR from PAESSLER Kiwi Syslog Server EventLog Analyzer from ManageEngine   Step-by-step guide   Example configuration for KIWI syslog free edition to receive and save the syslog send by the camera: Syslog server software must be installed on PC/Workstation that is on the same IP-network as the camera/encoder. One should check the size of the log file per a day and be sure there is enough storage capacity. 1. Enable the logging of the Kiwi software. Access "Setup/Rules/Default/Actions/Log to file", check the box for “Log to file”, then browse to the path where the log files can be saved.   2. Add the IP address of the camera(s) to "Setup/Inputs". Click on the address box, type in the address of the camera, click “Add”, then “OK”. (The Free Edition can log a maximum of 5 cameras.)   3. This point should be done after the camera is configured to send the syslog data. Open the Kiwi software and select “Manage” then Click on “Start the Syslogd service”. Log information should start to scroll in the Syslog main window. How fast or often messages appear depend on which debug command was provided by Tech support   Configure the camera to send the syslog data The configuration can be done via the Web Interface of the camera, Bosch Configuration Manager (stand-alone configuration software) or BVMS Configuration Client software (part of BVMS management system). The layout of the above 3 interfaces is very similar. The following steps and screenshots are done for Configuration Manager. 1. Ensure that the Date/Time of the Syslog PC, camera(s), and recording system are synchronized (as close as possible) 2. Enable the Time Stamping and ensure that it is set for milliseconds. a. NOTE: The time stamp is important for troubleshooting. 3. Navigate to Configuration Tab “Network/Advanced/Syslog”. Enter the IP address of the Syslog Sever PC/Workstation and click the “Save” icon.   4. Navigate to Configuration Tab  “Service/Logging”, then Debug Logging. At the Even Logging text box the debug command that was provided to you by Bosch support team.   If no debug command was provided, use: syslog_dbg. Click on the “Save” icon.   Collecting the logs Once the issue appears, note the date and time, collect and provide the maintenance.log from the camera and the syslog saved at the of the Syslog Sever PC/Workstation.  How to collect logs from your Bosch IP Camera/Encoder? ... View more

Possible causes and solution(s)   Causes   In all VRM installation packages the required .NET framework package is included in the VRM installation routine. As Microsoft Operating Systems are expected to get and have the latest security updates applied before installing any new software component like VRM (Video Recording Manger) or VSG (Video Streaming Gateway), the installer will successfully finish the installation routine. The same is valid for BOSCH DIVAR IP product range:  The DIVAR IP Appliance installer contains Microsoft update packages available from Microsoft at the time BOSCH creates the Appliance installer. But all Microsoft Updates release after the Appliance installer release date are not included in the BOSCH package. It is therefore recommended to check for Microsoft updates whenever a Bosch DIVAR IP Appliance installer is installed.   Solution   For VRM (Video Recording Manager) stand-alone Systems and Servers with VSG (Video Streaming Gateway) installed, it is also strongly recommended to check for Microsoft OS updates before the VRM Master Installer is installed/updated. Note: In case an error code 5100 is shown during the VRM Software installation, please ensure that all Microsoft updates for the used Operating Systems are installed and run the BOSCH Software installer after that once again. For more details Microsoft provides more informaiton here: https://blogs.msdn.microsoft.com/astebner/2008/10/13/net-framework-setup-verification-tool-users-gui... ... View more

Possible causes and solution(s)   Causes Transparant data transmission at a Encoder VideoJet Multi 4000 or VIP-X16-XF-E stops / does not work any longer in case of a power outage and restart of the device.   Diagnosis   When e.g. controlling a Bosch Autodome 7000 and PTZ via Transparent Data not working after reboot of the encoder, this is caused by an issue in the released firmware. It doesn't matter if it is Firmware 6.30.0047 or 6.30.0059. As a power outage should happen not too often the solution below is offered to fix this.   Solution   The solution is via a workaround using an ATSL script in the encoder to re-set the COM port baud-rate upon a reboot/restart of the encoder (which should in normal practice not happen to often). Please add the following scripts to the Alarm Task Editor tab either via CM or Web interface. //The 1st line set the board rate, 2nd line sets the port type RS232 = 1 or RS485/422 = 2 RcpCommand setCOMBaudrate := { Command("rcp.xml?command=0x027e&type=T_DWORD&direction=WRITE&protocol=TCP&payload=9600&num=1") }; RcpCommand setCOMMode := {Command("rcp.xml?command=0x0208&type=T_OCTET&direction=WRITE&protocol=TCP&num=1&payload=2")}; if (true) then setCOMBaudrate, setCOMMode;   If the device has a password set then 2 additional perimeters need to be added UserName() and Password(""). RcpCommand <name of RCP command> := { Command("Bla Bal Bla") UserName(Service) Password("enter the service level password here") };   There will be no further release or fix provided by BOSCH status of 2019-03-19 as the ATSL script resolves this. ... View more

Status February 25, 2017 BOSCH offers and confirms that since February 2017 the firmware version 3.180.05-1562 can be used with the LSI MegaRAID Controller. In case there are newer versions supported and recommended with BOSCH DIVAR IP this will be announced in cooperation with the Product Management. For DIVAR IP units (e.g. DIVAR IP 6000) BOSCH BT Security & Safety Systems offers an firmware update for the internal MegaRADI Controller. It could happen that in the Megaraid Software the user can see the following: potential non-optimal configuration due, PD commissioned as Emergency Spare error.    Firmware *** Firmware file Name: smc[xxxx].rom *** Utility: StorCLI.efi The firmware *.rom files are available inside the attached ZIP files: This Firmware Version is subject of change. Any new version must be announce by BOSCH PRM responsible for DIVAR IP via the BT-ST/ETP-MKP2 organization and BOSCH support at BT-ASA here in the BOSCH Knowledge Base.  FW 3.180.x not applicable for the R1 "DIP 60xx" HW   Here we provide the steps to update a DIVAR IP system:   Step-by-step guide Two methods to flash MegaRAID firmware 1. StorCLI Utility 2. MegaRAID Storage Management Utility   1. Using StorCLI under UEFI 1) Boot from USB key and use following command or run SMC[xxxx].nsh file. fs0:\>storcli.efi /c0 download file=smc[xxxx].rom ex) MegaRAID firmware flash via StorCLI utility   ex) MegaRAID firmware flash via batch file (smc[xxxx].nsh file include above command)   2) Reboot the system and check firmware version in controller OPROM banner during boot and in MSM   2. Using MegaRAID Storage Manager utility under OS   1) Open MSM, Right click on Supermicro MegaRAID controller to be updated and click Update Controller Firmware 2) Click Browse to search for new firmware   3) Select the new MegaRAID controller firmware 4) Click OK to continue   5) Check the “Confirm” box and click OK to continue   *** Wait for around 1~2 minutes to complete 6) Click OK once firmware update completed   7) Reboot the system and check firmware version in controller OPROM banner during boot. At the section Revision you can see version 3.180.05-1562   8.) Check firmware version using MSM in OS When selecting the "Supermicro SMC 2208 (Bus1, Dev 0) device you can see on the right the "Firmware Version" = 3.180.05-1562   ... View more