XProtect Corporate Integration with C CURE 9000 v2.60 User Manual April 25, 2018 1
Table of Contents 1 Document information... 3 2 Document revision history... 3 3 Version Compatibility... 4 4 Feature Matrix... 4 5 Introduction... 6 6 Component Overview... 6 6.1 Limitations... 6 7 Installation... 7 7.1 Prerequisites... 7 7.1.1 Licenses... 7 7.1.2 Integration Steps... 7 7.2 Server Components Install... 7 7.2.1 Uninstalling Server Components... 10 7.3 Client Components Install... 10 7.3.1 Uninstalling Client Components... 12 7.4 Milestone SDK 3.5b Redistributable Install... 13 8 Configuration... 15 8.1 C CURE Server Configuration:... 15 8.2 Recording Server Configuration... 17 8.2.1 Display Video tree... 19 8.2.2 Create new Video folder... 20 8.2.3 Create new Recording Server... 21 8.2.4 Edit Recording Server properties... 23 8.2.5 Import Milestone Cameras into the C CURE system... 25 8.2.6 Display Cameras connected to Recording Server... 26 8.2.7 Integrate Multiple Milestone Recording Servers... 26 8.2.8 View Live Video from Milestone Camera... 26 8.2.9 Retrieve recorded video from selected camera... 31 8.2.10 Setting up C-Cure event to stream video in Monitoring Station... 34 8.2.11 Associating Milestone Event as Action to C-Cure Event... 39 8.2.12 Associating Milestone Analytic Event as Action to Ccure Event... 44 8.2.13 Full support for all Milestone Camera/Recorder Events... 53 8.3 C CURE Enterprise MAS/SAS Configuration... 62 9 Troubleshooting... 64 9.1 General troubleshooting of XPCO integration with C CURE 9000... 64 9.2 Troubleshooting Milestone XProtect VMS Video Driver... 65 9.3 Additional Logs... 65 9.4 Troubleshooting Event Acknowledgment in CCure... 65 2
1 Document information Project Name Milestone Software House Integration User Manual Document Version 2.7 2 Document revision history Rev Date Author Summary of changes 2012 Jan12 SR Initial Version 1.21 2012 Oct 22 2013 Nov 1 2013 Nov 7 SR SR SR Support C-Cure v2.10 Support v2.10r2 and trigger Milestone Events Support v2.20 2015 Apr 8 JFM Support v2.30 2015 Oct 23 JFM Support v2.40, Added support for all milestone camera and recorder events + custom events 2016 Dec 15 JFM Support v2.50 2017 May 31 JFM Added support for Analytic events 2017 Sep 11 SRB Added support to acknowledge milestone alarms automatically 2017 Oct 19 SRB Support v2.60 2017 Dec 12 SRB Added new troubleshooting subsection 2017 Dec 19 SRB Updated Compatibility, Limitations and Feature Matrix sections + updated installation snapshots 2018 Feb 15 SRB Updated all screenshots 2018 Apr 25 SRB Enterprise support + Version compatibility 2018 May 17 BHA Support v2.70 3
3 Version Compatibility The Milestone XProtect Integration with C CURE 9000 has been tested with Milestone XProtect Corporate (XPCO) and C CURE 9000 according to the following table. C CURE 9000 XPCO 2017 R1 XPCO 2017 R2 XPCO 2017 R3 XPCO 2018 R1 CCure Enterprise MAS/SAS Support 2.20 U U U U U 2.30 S T S S S 2.40 S T S S S 2.50 S T S S S 2.60 T T T T T 2.70 S S S T S T: [Tested]. Fully tested and supported. S: [Supported] Tests were done to make sure the integration is compatible. U: [Unsupported]. Integration exists but is no longer supported (no bug fixes and no new features). 4 Feature Matrix Video Feature Mark an X where comply Special Notes C CURE Min. version supported Live Video X 2.30 Text Overlay Not Supported - Pre-recorded Video X 2.30 Playback Status X 2.30 Export To AVI Not supported - Time Synchronization X 2.30 Record Start (On Only Journal Entry Record starts only on motion 2.30 Demand) is guaranteed. Recording may or may not be available. as set up in Milestone system Frame Rate Adjustment Not Supported Will be setup in Milestone - Record Stop (On Not Supported Record stops on timeout as - Demand) set up in Milestone Server PTZ (Domes only) X 2.30 4
Video Alarms X Video loss, Motion, 2.30 Recording events in this version Video Tour X 2.30 Video View Up To 16 X 2.30 Cameras Presets & Patterns X (Only Presets) (Patterns not supported) 2.30 View Live & Recorded Video from multiple cameras via Popup in single window PTZ Presets & Presets based on event, alarm input Replay Up To 4 Cameras for same Time Interval Toggle Video Window Size from 1x to 4x Display Up To 4 Live Video Windows based on Event Original Recorded Video Cannot be Altered Playback and Recorded Video in one window Partially supported. Allowed in Live View Supported (Only Presets) For playback multiple popup single view windows can be called up 5 2.30 (Patterns not supported) 2.30 Not Supported Playback from 1 camera only - with single command X 2.30 X Use Views for this 2.30 X 2.30 Not Supported - Bi-directional Actions X 2.30 Support for All Camera X 2.30 and Recorder events in C Cure Support for XProtect X 2.30 Custom Events in C Cure Support for XProtect X 2.30 Analytic Events Support for XProtect X 2.30 Alarm acknowledgment CCure Enterprise MAS/SAS X Please see the «Enterprise» section below. 2.60
5 Introduction This document provides instructions to integrate Milestone XProtect Corporate Video Management System with Software House C CURE 9000 Access Control System. The purpose of the integration is to enable users to view live and recorded video from Milestone VMS system from inside the C CURE user interface. The integration will facilitate viewing C CURE data and Milestone video from a single integrated console instead of requiring two consoles, one to view C CURE data and another console to view Milestone video. This integration will provide access to basic features of Milestone VMS inside C CURE system. Note: To access the comprehensive features of the Milestone VMS system, use the standalone Milestone Smart Client application independent of this integration. 6 Component Overview Administration and configuration of the integration is performed from the C CURE Administration Workstation and Server Configuration applications. The solution requires a. Integration server components to be installed on the C CURE Server machine b. Integration client components to be installed on all C CURE Client machines where integration is required c. Milestone SDK 3.5b redistributable to be installed on all client machines where the integrated UI will be viewed Note: Removal of the previous Milestone integration does not remove Milestone objects from Cross Fire database. This integration uses the same Milestone objects from the previous integration. When upgrading, all Milestone video servers and cameras set up with the previous integration will continue to exist. 6.1 Limitations This integration does not support C-Cure Clustering/Redundancy Refer to the user manuals and documentation for C CURE 9000 and Milestone XProtect Corporate for a comprehensive description of the limitations of the respective systems. 6
Milestone XProtect Corporate Video Management System Software House C CURE 9000 Access Control System 7 Installation 7.1 Prerequisites Prior to install the integration, Ensure that C CURE 9000 server and C CURE clients are configured and working normally. Ensure that the Milestone Management Server, Milestone Recording servers and cameras are installed, configured and working normally. Refer to the user manuals and documentation for C CURE 9000 and Milestone XProtect Corporate for a comprehensive description of the installation, configuration and features of the respective systems. 7.1.1 Licenses Obtain integration license from Software House and apply license using the C CURE licensing tool. Obtain integration license from Milestone Systems 7.1.2 Integration Steps The following sections describe the steps needed to install the different parts of the integration: Server components on the C CURE 9000 server machine. Client components on all C CURE 9000 client machines. Milestone SDK 3.5b redistributable on all C CURE 9000 client and server machines. 7.2 Server Components Install Server components are required to be installed on the C CURE 9000 Server. Note: Use Milestone-CCure-v2_60-Integration-v2_6_XXXXX_XX.msi installer for integrating with v2.60. Double-click the Milestone-CCure-v2_60-Integration-v2_6_XXXXX_XX.msi file to start the installation and bring up the Welcome screen. 7
Click Next to bring up the Setup screen. If installation directory is different than the default directory indicated, change the directory suitably. Enable the Server Components feature which is deselected by default. 8
Click Next to continue Click Install to start the installation process. 9
7.2.1 Uninstalling Server Components The Server Components can be uninstalled by running the Milestone-CCure-v2_60- Integration-v2_6_XXXXX_XX.msi installer and selecting the Remove option. 7.3 Client Components Install Install the Client Components on all C-Cure client machines on which milestone video integration is needed. Note: Use Milestone-CCure-v2_60-Integration-v2_6_XXXXX_XX.msi installer for integrating with v2.60. Click Milestone-CCure-v2_60-Integration-v2_6_XXXXX_XX.msi to start installation and bring up the Welcome screen. 10
If installation directory is different than the default directory indicated, change the directory suitably. Click Next to continue. 11
Click Install to start the Installation process. 7.3.1 Uninstalling Client Components The Client Components can be uninstalled by running the Milestone-CCure-v2_60-Integrationv2_6_XXXXX_XX.msi installer and selecting the Remove option. 12
7.4 Milestone SDK 3.5b Redistributable Install Milestone SDK 3.5b redistributable is required to be installed on all C CURE 9000 Client machines that need access to Milestone video. Click Milestone_SDK_3.5_Redistributable_Package.msi to start the installation. Press Next as needed to complete the installation. 13
Click Next to complete installation. 14
8 Configuration 8.1 C CURE Server Configuration: Go to Start menu and select All Programs/Software House/C CURE9000/Server Configuration to open the Server Configuration application. Check the status of CrossFire Framework Service and CrossFire Server Component Framework Service in the Services tab. If both services are started as indicated by green status of Running, restart the services one by one by first stopping the service by clicking Stop Service button and then starting the service by clicking Start Service button. If the services are stopped as indicated by red status of Stopped, start the services by clicking on the corresponding Start Service button. Ensure status changes to Running. 15
Click the Database tab. If the Status column indicates INVALID for the Milestone.SwhIntegration.Common.MiSwhVideoObjects item, change the Connection String for this item suitably to point to the correct path to the C CURE Database and restart CrossFire services. Ensure Status indicates VALID. 16
Click the Server Components tab. Under Video, note the status for Milestone.SwhIntegration.Server.MiSwhVideoServerComponent. If the Status indicates Stopped, ensure Enabled checkbox is checked, and click Start Service button to start the component. This server component should indicate Status of Running. 8.2 Recording Server Configuration Start the C CURE 9000 Administration application by selecting All Programs/Software House/C CURE 9000/Administration Workstation from the Start menu. 17
18
8.2.1 Display Video tree Select the Video tab in the bottom left corner of screen to display the Video tree. 19
8.2.2 Create new Video folder Select and right click Video at the top left-hand corner of the screen. Select New to start the process of creating a new Video Folder. 20
Enter a Name and Description. Click Save and Close to create the new folder under Video. 8.2.3 Create new Recording Server Select and right click on the newly created folder to display the menu. Mouse over Milestone VMS Recording Server to display the New menu options. Select New to display the Milestone VMS Recording Server screen. 21
Name: Enter the Milestone Recording Server name exactly as it shows up in the Milestone Management Client. Description: Enter a description as needed to indicate details of the Recording Server. Enabled: Check the checkbox to enable this object. 22
Domain: Enter the domain of the Milestone Management Server. User Name: Enter a valid user authorized to access the Milestone System. Password and Re-enter Password: Enter password for the User entered in the above step. IP Address: Enter IP Address of the Milestone Management Server. Click Save and Close at the top left corner of the screen to save the settings. 8.2.4 Edit Recording Server properties Select and right click the newly created Recording Server object to display the context menu. 23
Click Edit to display the settings for Edit. If the settings and credentials are valid and correct, the system will connect to the Milestone Recording server. The Online checkbox will be checked and the Import Cameras button will be enabled as shown below. Note: If the Online checkbox does not show up as checked, edit the settings suitably and click Save and Close to save the correct settings. 24
8.2.5 Import Milestone Cameras into the C CURE system Click on the Import Cameras button. Click Save and Close on the Edit screen to save the imported cameras into the system. 25
8.2.6 Display Cameras connected to Recording Server Select the folder expand arrow to the left of the newly created Recording Server object to display the Milestone cameras imported into the system for the selected Recording Server. 8.2.7 Integrate Multiple Milestone Recording Servers Repeat the steps listed in Create new Recording Server as indicated above for all the Recording Servers that need to be integrated into the C CURE System. 8.2.8 View Live Video from Milestone Camera Select a camera to view video. Right click to display the context menu. 26
Click on View to view the video stream from the selected camera. Click on Popup View to view the video stream from the selected camera in a floating window. 27
28
Floating window: PTZ from live cameras: If the selected camera has PTZ capabilities, the PTZ controls will be displayed above the image window. The PTZ controls can be operated as needed. Presets from live cameras: If the selected Milestone camera has been programmed with Presets, the Preset list-box will be displayed above the image window. To move the camera to the required Preset, choose the Preset from the dropdown. Caution: Presets created in Milestone system should follow the below naming convention: nn-xxxxxxxxx Where n indicates numeric and X indicates Alpha-numerals. For e.g. 01-Best View, 02-Full Zoom If this Preset naming convention is not followed in Milestone system, Preset lists may get resorted and assigned new indexes when new Presets are added in Milestone system. This may cause C CURE events which are based on indexes to trigger the wrong Preset when the event linked to Preset is triggered. 29
Show overlay : Not supported. This button will be disabled. Take snapshot : Capture screenshot of the live video. The snapshot will be in JPEG format and saved in C:\camera_name\time_date_stampLiveSnapshot.jpg. Record video : Record video option is used to generate a 30 second timestamp and the relevant alarm will be generated in the monitoring station. There is no guarantee that pressing the Record Video button will actually start recording, since Milestone cameras are set up to only record on motion. The camera setting can be changed in the Milestone system to record continuously if needed. From the monitoring station, the user could retrieve the recorded video if available for the noted timestamp by selecting the respective state image. Reconnect camera : Click this button to reconnect to the selected camera. 30
Email snapshot : Click this button to take a snapshot and email it using the SMTP parameters configured in the C CURE environment variables. Click the Email icon to send the message. 8.2.9 Retrieve recorded video from selected camera Click on the green arrow button above the video window to display the Playback screen. To return to the live window, click on the red arrow button 31
The Milestone VMS Camera Playback screen provides the following buttons and combo boxes to perform various operations. Time Range: Specify start time and end time for the video to be retrieved. 32
Click the Get Video button to play back the retrieved video for the selected time range. Play Button: After selecting the time range for playback and the Video is retrieved, you may press the Play button to start playing back the recorded video. Stop Button: When the retrieved video is playing back, you may press the Stop button to stop playing back the recorded video. Play Direction: Select the playback direction needed from the dropdown. Available options are Forward and Backward. Speed: Select the speed of playback as needed form the dropdown. Available options are x0.5, x1, x2, x4, and x8. Browse Mode: Select the Browse Mode as needed from the dropdown. Available options are Current Sequence, Repeat Sequence or Multiple Sequences. Multiple Sequences mode can be chosen to stream the video starting at the requested time and jump to the next available video sequence at the end of the sequence. 33
8.2.10 Setting up C-Cure event to stream video in Monitoring Station In the Administration Workstation, click Configuration tab. Select Event in the dropdown at the top of the screen. Figure 1. Click New to start the Event creation process. 34
Figure 2. 35
Enter Name and Description for the event. Check Enabled checkbox. Check Armed checkbox in the General tab. Select Action tab. Click on Add button. Under Action heading, select Display Viewer in the dropdown. Figure 3. To fill up Type field, click browse button and select Milestone VMS Video Camera. See figure 4. 36
Figure 4. 37
To fill up Object field, click browse button and select the camera that should stream in the video viewer. See figure 5. Figure 5. Click Save and Close to complete Event setup. Associate the newly set up event in the Admin workstation to be triggered as needed. When the set up event is triggered, Video Viewer window will open up in the Monitoring station and stream video from the associated camera. 38
8.2.11 Associating Milestone Event as Action to C-Cure Event Milestone User Defined Events that are setup in Milestone system can be assigned as Action to C-Cure event. When C-Cure events occur, the assigned Milestone User Defined Event will be triggered. The actions assigned to the Milestone User Defined event will then be executed in the Milestone System. Various actions such as emailing snapshot, emailing event video, logging the event, displaying video from selected cameras in Milestone Smart Wall, etc. can be performed in the Milestone system. Open Admin Workstation application and select Configuration Event New to create a new event. Check Enabled and Armed checkboxes in the General tab. 39
Click on Action tab and click Add to add a new action for this event. Select Milestone Event Action from the dropdown under Action. 40
Choose the required Milestone event from the Available Milestone Events dropdown and click on the button to move selected event to the Associated Event box. 41
Click on Save and Close. 42
The alarm setup with Action will show up in the Configuration screen. When C-Cure events occur, the associated Milestone event will be triggered which in turn will trigger actions set up in the Milestone system. 43
8.2.12 Associating Milestone Analytic Event as Action to Ccure Event Milestone Analytic Events that are setup in Milestone system can be assigned as Action to C- Cure event. When C-Cure events occur, the assigned Milestone Analytic Event will be triggered with the configured associated cameras. The actions assigned to the Milestone Analytic event will then be executed in the Milestone System. Various actions such as emailing snapshot, emailing event video, logging the event, displaying video from selected cameras in Milestone Smart Wall, etc. can be performed in the Milestone system. 8.2.12.1 Configure Analytic event in XProtect To use this functionality, you need to configure an analytic event in XProtect. First make sure that the analytic server port is turned on in XProtect Management Client Options Dialog: In the options dialog select the Analytic event tab, verify it is enabled and configured for port 9090 44
Next make sure you have defined analytic events in Milestone Management client. Go under the Rules and Events / Analytics Events in the site navigation tree. Right Click the Analytics events root node in the Analytics Events window and select Add New Name the Analytic event and hit save. 45
Once the analytic event is created, you may want to create an associated alarm with the analytic event as a trigger. Go in Site Navigation/Alarms, right click the Alarm Definitions root node in the Alarms definitions window and select Add New 46
Name the alarm definition, then select Analytics Events from the Triggering Event drop down Select the analytic event to use as a trigger for the alarm from the drop down Select the sources allowed, by pressing the Select button on next to the Sources text box 47
Select every All xxx source, to allow all sources Once selected press OK and save the alarm definition by pressing the save button on management client toolbar on the upper left. 48
8.2.12.2 Configure Analytic event in C-Cure To configure the analytic event in C-Cure you need to already have a C-Cure event that can be used as the cause for triggering the Milestone Camera Action. In this example we have an event called CCureEventTrigger that we will use to test the Milestone Camera Action with. Double click the event in the event list that you want to edit. We can then select the Action tab in the event editor window to add our Milestone Camera Action. Press the add button to add a new action 49
Select the Milestone Camera Action from the drop down The Milestone Camera Action UI will now show on the bottom of the Event Configuration Dialog. In here you can select the Analytic Event from the dropdown and edit the Analytic port on which to send the Analytic event as configured in the previous section. The Selected Analytic Event Name and 50
Event Server IP fields will fill based on the selection on the dropdown. In the case where the dropdown does NOT contain the Analytic event you are trying to fire, you can edit the Analytic Event Name manually as well as the Event Server IP. When events are acknowledged in C-Cure, it is possible to have their associated Milestone alarms acknowledged as well. Automatic alarm acknowledgement is disabled by default but you can enable it using the Auto-acknowledge alarms checkbox. The list of available cameras drop down is based on the cameras discovered at the Event Server IP address. If the Event Server IP is invalid or the XProtect system cannot be reached, the available camera list will be empty. You can only attach cameras from the XProtect system where the Analytic event is defined. So multiple recorders from different XProtect systems cannot share one Analytic event. Multiple recorders from the same XProtect system however, can share the same analytic event. To add/remove selected cameras to/from the Available cameras list, select them in the drop down/associated camera list and press the Add/Remove button. Once you are done with you camera selection, save the event by pressing Save and Close or Save and New bottom at the top of the window. 51
52
8.2.13 Full support for all Milestone Camera/Recorder Events Starting with v2.40 we now support all camera events and recorder events. These will be available under the respective camera or recorder on which you wish to trigger an action into C-Cure. Triggering them is the same as setting any alarm on a camera or recorder, now there are just more of them. Here is a recorder s available events: 53
Here is a camera s available events: 54
Milestone Custom Events into C Cure 9000 It is possible to receive and map Milestone custom events to fire Pulse events into C-Cure. Here is how: 1. Define a custom event in XProtect. 2. Now we need to associate the Milestone custom event with a Custom event slot on either a Recorder or a camera in C-Cure. Open C-Cure Administration Station. Select either a recorder or a camera and double-click. You then select the Milestone Custom Events tab. There are 10 custom event slots per recorder/camera. Each custom event field corresponds to a predefined configurable event on the given recorder and/or camera in C-Cure and it can be mapped to any of the defined custom events in Milestone. So for example below the Canon camera VB-S30D is mapped to my-userdefined-event custom event on its CustomEvent1 slot. The recorder VM-RecServer1 in the next image also has myuserdefined-event triggering the CustomEvent1 slot. 55
56
3. Once this is defined we need to configure what happens when the Custom Event slots are triggered on the given objects, for this we use the Alarms tab of the recorder/camera object. We press the Add button and in the Property field press the... button from there comes a popup window where all the supported events of the recorder/camera objects are listed. Notice the 10 PulseXXXCustomEvent# events these correspond to the custom event slots in the Milestone Custom Events tab. Lets select the PulseDeviceCustomEvent1 slot on the camera and configure it to fire a C-Cure event. 4. Once we select the PulseXXXCustomEvent# from the property field we have to select when and what action happens when we receive this event in C-Cure. This is what the Value and Action fields are for. For Value we check the box meaning we want to fire when the PulseXXXCustomEvent# is received. In the Action drop down we select Activate Event. From the botton Event field we click V button/new 57
58
5. This allows us to create a new event in C-Cure it is also possible to use an existing one by pressing the... button and selecting it from the list. Here is what the new event should look like: 6. Because we want the event to show up in Monitoring station we have to check Send State Changes to Journal and then Send state changes to Monitoring Station. 7. We hit Save and Close and now the screen looks like this, we can now save and close the camera. 59
8. To test the chain of events we can use the Milestone Management Client to trigger the custom event and the Monitoring Station in C-Cure to receive it. 60
9. We get this in the C-Cure Monitoring Station: 61
8.3 C CURE Enterprise MAS/SAS Configuration In a CCure Enterprise setup, the client and server components of the integration must be installed on every CCure server (including the MAS and on every SAS), as described in the Installation section. When the integration is installed on a SAS, it must be configured as a regular CCure installation by following all the steps described in the previous sections. When the integration is installed on a MAS, the following steps must be followed: 1. Make sure both the Client and Server components of the integration are installed on the MAS, as described in the Installation section. 2. Even if we require the server components of the integration to be installed on the MAS, a license to run the server components on the MAS is NOT required. The CCure Server Configuration Application will report the MiSwhVideoServerComponent as being not licensed, which is perfectly normal. This component must be installed, but doesn t need to run on a MAS. 3. For the integration to work correctly on the MAS, some changes must be made to its database. To prepare the MAS database for the integration, open a Windows command prompt at the following path and run the following command: Path: Command: C:\Program Files (x86)\tyco\crossfire\servercomponents MiSwhHost --setupdb 62
Note: When running this command, make sure the currently logged Windows user has access to the MAS database. 4. Close and re-open the CCure Server Configuration Application. The Status column under the Database tab should now indicate VALID, in green, next to the Milestone.SwhIntegration.Common.MiSwhVideoObjects item. 63
9 Troubleshooting 9.1 General troubleshooting of XPCO integration with C CURE 9000 1. Is Milestone System licensed and cameras configured inside Milestone system? Ensure your Milestone system is licensed and all cameras are configured. Ensure you can view Milestone video with Milestone Smart Client. Integration with C-Cure system should only be performed after the standalone Milestone system is configured and running properly. Ensure integration license from Software House is applied Ensure integration licenses from Milestone is applied 2. Milestone VMS Recording Server does not show up for creating the Recording Server object in Admin Workstation: Ensure Milestone.SwhIntegration.Server.MiSwhVideoServerComponent is Enabled and Running in Server Configuration Application under Server Components tab. Ensure Milestone Integration Client Components are installed in the Client machine Ensure Milestone SDK Redistributable is installed in the Client machine 3. Online checkbox is not selected which indicates system is not online in the Milestone VMS Recording Server object edit screen: Ensure Name field has the name of the Milestone Recording Server name exactly as it shows up in the Milestone Management Client. Ensure IP Address field has the IP Address of the Milestone Management Server Ensure Domain field has the Domain value of the Milestone Management Server Ensure correct values are entered for user name and password 4. Import Cameras button is not enabled in the Milestone VMS Recording Server object edit screen: Ensure Cameras are available, configured and streaming video within Milestone System. Milestone Smart Client can be used to verify this. Ensure Online checkbox shows up as selected in the Edit screen which indicates system is online. See previous note about Online checkbox. 5. Milestone Cameras do not show up after clicking Import Cameras. Ensure Save and Close button is clicked after Import Cameras process succeeds. 64
9.2 Troubleshooting Milestone XProtect VMS Video Driver Video Driver Trace logging will be controlled by setting suitable entries in ACVS.Enterprise.Server.Configuration.exe.config file located in C: Program Files (x86) \Tyco\CrossFire or C: Program Files (x86)\software House\SWHSystem\CrossFire in upgraded systems. <appsettings> <add key = TraceViewer.Enable value= true /> <appsettings> Where value can be set to true or false to enable or disable logging respectively. Open Server Configuration Application. Diagnostics tab will now show up. Click on Connect. Several modules will show up. Select MileTraceSwitch and set trace value suitably. Red Error, yellow warning, purple info and Green verbose. Logging messages will now show up. 9.3 Additional Logs Additional logs are also created (and can be configured) under the %ProgramData%\VideoOS folder. A subfolder is created for every CCure process that loads this integration. 9.4 Troubleshooting Event Acknowledgment in CCure When a Ccure event is marked as This event requires acknowledgment, it sometimes become impossible to acknowledge it (the acknowledge button remains disabled in the UI). When this situation occurs, you can follow the steps below: 1. Open the Event Monitoring Screen (from either the Administration Station or the Monitoring station) by right-clicking the event: 65
2. Make sure the event isn t latched (the Unlatch button should be disabled). If it is latched, click the Unlatch button to unlatch it. 3. Also make sure there aren t any Activate Event or Deactivate Event actions in the list on the left. If, like in the snapshot below, there are actions in the list, right click on each one of them and select Cancel from the dropdown until none are left. The Acknowledge button should now be enabled. 66