C CURE 9000 Version 2.20 Patch 4 R2

Transcription

1 C CURE 9000 Version 2.20 Patch 4 R2 C CURE 9000 Version 2.20 Patch 4 R2 Release Notes September 2014 This Release Notes file provides important information for installing C CURE 9000 Version 2.20 Patch 4 R2, for both server and client machines. (In case of discrepancy, the information in this document supersedes the information in any document referenced herein.) NOTE: This patch is not supported for Unified systems with C CURE 9000 version 2.20 and victor Unified Client version 4.3. This patch is supported for Unified systems with C CURE 9000 version 2.20 and victor Unified Client version 4.4. If you are currently using VideoEdge integration ( ) and/or HDVR Integration ( ), you will need to obtain and install the following versions of these integrations after installing Patch 4 R2. VideoEdge integration ( ) HDVR Integration ( ) Please read this file before installing the product. Contents 1. Patch CD Contents 2. New System Variable: Auto Increment Site Code 3. Installing the Patch 4. Uninstalling the Patch 5. SPARs Fixed Patch #4 SPARS Patch #3 SPARS Patch #2 SPARS Patch #1 SPARS 1. Patch CD Contents This patch CD includes the Patch 4 R2 installation program, the version 2.20 Language Pack, the C CURE 9000 Web Client for 2.20 Patch 4, and a new version of CrossFire (version ). This patch installs a new version of the ADSDK (4.4). 2. New System Variable: Auto Increment Issue Code Patch 1 introduced a new System Variable for Personnel: Auto Increment Issue Code. This option is used to increment the Personnel Credential Issue Code when a Magnetic Card Format replacement badge is printed. RN R2 1

2 When this system variable is set to True, and Print Badge on the Personnel Badging tab is used to print a replacement badge with a magnetic card format that includes an Issue Code, C CURE 9000 automatically increments the Issue Code for the Personnel record, as long as the current Issue Code value is less than the maximum value allowed by the Card Format. (If the Issue Code value is at the maximum value, the Issue Code value is reset to zero.) If a new credential is created and printed, or an existing credential s Card Number is modified, the Issue Code is not incremented. When this system variable is False, the Issue Code is not incremented. 3. Installing the Patch NOTE: You should have the original C CURE 9000 V2.20 and Patch 2 or Patch 3 media available during installation, in case Windows prompts you to insert it to continue. C CURE 9000 V2.20 Patch 2 must be properly installed for this patch to install and run properly. NOTE: If you have previously installed C CURE 9000 V2.20 Patch 4, you must uninstall it prior to installing C CURE 9000 V2.20 Patch 4 R2. If you are currently using the VideoEdge integration ( ) and/or HDVR Integration ( ), you will need to upgrade these integrations to the newest versions after installing Patch 4 R2. NOTE: If you uninstall Patch 4 R2, you will need to uninstall VideoEdge integration ( ) and/or HDVR Integration ( ) and revert to the previous version(s). Therefore it is important that you have the install programs for the previous integration version(s) available before you install Patch 4 R2, in case you decide to uninstall Patch 4 R2. On the C CURE 9000 Server: 1. Perform a System Backup from Options & Tools. 2. Log out and exit the Administration application on the server and all clients. 3. Log out and exit the C CURE 9000 Monitoring Station application on the server and all clients. 4. On the server machine, use the Server Management application to stop the CrossFire Service and the Server Component Framework, and then exit the application. 5. In Administrative Tools>Services, stop the following services Software House AutoUpdate Installer Software House AutoUpdate Service TycoESS 6. Install the C CURE 9000 patch by double clicking on update.exe on the root of the patch CD. 7. Follow the installation instructions on screen to complete C CURE 9000 patch install. On the C CURE 9000 Client: 1. In Administrative Tools>Services, stop the following services Software House AutoUpdate Installer Software House AutoUpdate Service 2. Install the C CURE 9000 patch by double-clicking on update.exe on the root of the patch CD. 3. Follow the installation instructions onscreen to complete C CURE 9000 patch install. 2 RN R2

3 4. Uninstalling the Patch If you uninstall C CURE Patch 4 R2, your system will revert to the previously installed Patch. You do not need to uninstall ADSDK 4.4, but if you have installed updated versions of VideoEdge and HDVR integrations, you will need to uninstall these integrations and re-install the version you were using previously. To Uninstall C CURE Patch 4 R2: 1. Perform a System Backup from Options & Tools. 2. Close the C CURE 9000 Administration application. 3. Close the C CURE 9000 Monitoring Station application. 4. In the Server Configuration application, stop the CrossFire Framework Service and the CrossFire Server Component Framework, then close the application. 5. In Administrative Tools>Services, stop the following services Software House AutoUpdate Installer Software House AutoUpdate Service TycoESS 6. Click Start>Control Panel>Programs and Features. 7. Click View Installed Updates. 8. Select C CURE 9000 V2.20 Patch 4 and click Uninstall. 5. SPARS Fixed This patch includes the following SPAR fixes. Patch #4 R2 SPARS Version 2.20 Patch 4 now installs with the correct database connection strings for a system using a remote SQL database. Patch #4 SPARS Card Numbers with 18 or more digits no longer cause SystemTrace.log error messages, and now work correctly with the Disable by Inactivity feature An upgrade of a version 2.02 system with Bidirectional Inputs and Groups defined no longer causes the istar driver to fail to start because the Group is not recognized The istar driver no longer displays an unhandled exception during fast firmware download An error no longer occurs when setting the Activation and Expiration date/times for a Custom Clearance on a non-us English system using a localized Date/Time format. RN R2 3

4 An unhandled exception that caused the CrossFire Framework Service to stop has been corrected The backup of an Audit Log Volume on a MAS no longer returns a Backup failed to backup volume error Play Sound actions now work correctly after the upgrade to version 2.20 of a SAS or MAS The Event Action Address field now provides better support for special characters that are valid in an address After migration from C CURE 800 to C CURE 9000 version 2.20 Patch 2, apc8x doors no longer show an incorrect locked status Inputs on apc no longer show a status of Unknown while still functioning normally istar controllers no longer show a status of Unknown while still functioning normally and A new System Variable (System Operations>Observe Class Level Privilege for Excel Export) has been added to allow the Export to Excel capability to be controlled by Privilege. The System Variable is a Boolean with the default value of FALSE. If the System Variable is FALSE, the Export view contents to Excel function is Enabled. If the System Variable is TRUE, the system enables or disables the Export view contents to Excel function based on the Operator s class level Privilege for the object type contained in the Dynamic View. If the Operator is restricted from exporting the objects in the view, the button is disabled Auto Increment for a new Personnel record now works correctly when using a Personnel Template that contains a User-defined field of type Identity Patch install for a system using a SQL server name or alias separated by comma before the port number now works correctly After installing C CURE 2.20 Patch 3 and starting the Intellex driver, the Windows Event viewer Application Log no longer displays Find Collection errors. 4 RN R2

5 and After installing C CURE Patch 3, Events that are triggered are now correctly showing the Event causes, and no exception errors occur Printing a badge no longer causes a disabled Credential to occasionally become re-enabled and Updated OpenSSL from 1.0.1c to 1.0.1g to resolve OpenSSL TLS Heartbeat Critical Vulnerability The CrossFire Server Component Framework Service no longer disconnects from the istar driver as a result of the driver returning a null value You can now batch print and encode MIFARE cards at the same time with a Fargo DTC4500e printer. Patch #3 Critical Update 2 SPAR You can now successfully grace a global person while connected to the MAS, using a custom Privilege with full Global and SAS access. Patch #3 Critical Update 1 SPAR Updates OpenSSL from 1.0.1c to 1.0.1g. This update eliminates the Heartbleed vulnerability. Patch #3 SPARS A PersonnelObject SetupClearancePair exception: Object reference not set to an instance of an object errror message no longer appears when the istar driver restarts When an Event runs a Report in an Enterprise system, the message Error: [RunReportCommand] Object Report Result cannot be created in Global partition no longer occurs An unhandled exception no longer occurs when running C CURE 9000 version 2.20, Patch 1 with victor Unified Client version An exception caused by incorrect byte values in an Intrusion Zone activity Message from an istar controller no longer occurs. RN R2 5

6 The apc driver now correctly handles Personnel records when the system variable Allow activation after expiration is set to True A change to a SAS Operator s Privileges while the SAS Operator is logged in is now correctly updated on the MAS A change of the server name in the Client Configuration program now correctly updates the Windows registry entry used by the C CURE 9000 installation program during a repair operation. Note that the Administration Station must be run with Administrator rights if UAC is enabled, or this change to the registry will not be saved Operator Privilege changes on a SAS now synchronize correctly to the MAS If you configure a Card Format using the Card Only CHUID, check the "Show Position Offsets- - apc only" check box, and configure an OFFSET for one of the fields (i.e., the Facility Code field), you are no longer prevented from applying an Extended CHUID card format to istar readers and Viewing the Credential Dynamic View from the MAS no longer causes the error: Failed to enable constraints to appear , , and C CURE Mobile readers now can connect without error to the C CURE 9000 server, after installing C CURE 9000 version 2.20 Patch Data Import of a Clearance when a Clearance item property was changed in the import file (example: Door1 was edited in XML to Door2 ) no longer causes a problem for the istar driver Imported Personnel records now have associated Credential Inactivity records created, so that disable by inactivity works correctly for these credentials The Video Framework no longer causes an unhandled exception with third party video drivers Event Viewer Event times no longer change when you close and re-open the Monitoring Station. 6 RN R2

7 Fast Personnel Download to an istar controller in an Enterprise configuration now correctly downloads all Personnel (specifically, local Personnel from a SAS, promoted to be Global Personnel, are now correctly downloaded TIF images larger than 3.0 MB no longer cause an unhandled exception in the CrossFire Framework Service right after startup CCURE ID now correctly sets the Parity bit when programming a SmartFrame smart card for standard Wiegand26 format with Even and Odd parity In an Enterprise configuration, after upgrading a SAS to C CURE 9000 version 2.20 Patch 2, apc panels now download all Personnel data correctly A SQL lockdown that affected the apc driver no longer occurs CrossFire no longer fails to start correctly on systems with more than 62 core processors Scheduled Events downloaded to an istar controller now correctly respect Holidays An unhandled exception that caused the CrossFire Framework Service to stop has been corrected Intellex Video Popup views in the Monitoring Station no longer display as blank A condition that caused istar controllers on a SAS with version 2.20 Patch 2 Critical Update 5 installed to continuously perform fast Personnel download has been corrected Activating a C CURE 9000 Event no longer causes a memory problem in victor that could eventually stop the CrossFire Framework Service Credential Inactivity now correctly synchronizes after the conversion of a standalone server to a SAS A problem that caused a previous cardholder s name to display in the Journal as the new cardholder s name was resolved. RN R2 7

8 In an Enterprise, when a local Personnel record is made Global, a Credential Inactivity record is created on the MAS, so that disable by inactivity works correctly for these credentials Duplicate causes that cannot be cancelled no longer appear in the Cause list for Events. Patch #2 Critical Update 5 SPAR On a SAS, scheduled Events downloaded to an istar controller now correctly respect Holidays. Patch #2 Critical Update 4 SPARS C CURE Mobile readers now can connect without error to the C CURE 9000 server, after installing C CURE 9000 version 2.20 Patch The status message webserver not found no longer appears when you click Load server config on a CCURE Mobile reader, after installing C CURE 9000 version 2.20 Patch 2. Patch #2 Critical Update 3 SPARS In an Enterprise configuration, after upgrading a SAS to C CURE 9000 version 2.20 Patch 2, apc panels now download all Personnel data correctly A SQL lockdown that affected the apc driver no longer occurs An unhandled exception that caused the CrossFire Framework Service to stop has been corrected. Patch #2 Critical Update 2 SPAR Fast Personnel Download to an istar controller in an Enterprise configuration now correctly downloads all Personnel (specifically, local Personnel from a SAS, promoted to be Global Personnel, are now correctly downloaded. Patch #2 Critical Update 1 SPARS Operator Privilege changes on a SAS now synchronize correctly to the MAS. 8 RN R2

9 If you configure a Card Format using the Card Only CHUID, check the "Show Position Offsets- - apc only" check box, and configure an OFFSET for one of the fields (i.e., the Facility Code field), you are no longer prevented from applying an Extended CHUID card format to istar readers. Patch #2 SPARS An issue that caused some Journal Replay and Audit Log Server Date or Message date times to be incorrect in some time zones has been corrected A condition that caused the Activity Viewer to display the wrong Personnel record when you freeze the view after 1000 messages, and click on an Activity message, has been corrected Pre-defined CHUID formats for "PIV I CHUID Format", "PIV II CHUID Format" and "Full FASC-N CHUID Format" are being removed from the C CURE 9000 database because they are causing the istar driver to treat all records as if they have an 80-Character CHUID Reports printed in PDF format via an Event no longer display a disclaimer that states that the document was printed using an evaluation version of ActiveReports The SEND action on Door triggers associated with a Schedule no longer executes when the Schedule is inactive An issue that prevents changing an Operator from Local to Global in an Enterprise Architecture has been corrected The Area Status tab Personnel Count now correctly updates dynamically when Occupancy for Areas is enabled. Also, the Personnel Count now correctly updates dynamically when you select Display Occupancy Personnel Group from the Area Dynamic View context menu Corrected an issue that caused the upgrade from C CURE 9000 version 2.10 R2 to version 2.20 to not add a runtime setting to SoftwareHouse.CrossFire.Server.exe.config and Corrected an issue that caused synchronization errors to occur for Global Schedules in an Enterprise system Swipe and Show now supports a configurable refresh setting. You can add a setting to the Monitoring Station configuration file: RN R2 9

10 Tyco\CCURE Client\SoftwareHouse.NextGen.Client.MonitoringStation.exe.config) to change the refresh from the default value of 1 second (1000 milliseconds) to another value, with a minimum value of 50 milliseconds. The following lines would set the refresh rate to 0.5 seconds (500 milliseconds): <appsettings> <add key="swipeupdateinterval" value="500"/> </appsettings> A FileNotFoundException error (cannot find Microsoft.SqlServer.Smo) that occurred when installing 2.20 Patch 1 on a C CURE 9000 server that uses Remote SQL has been corrected Creating a CHUID with a card number length 20 digits and assigning the CHUID to a card holder no longer causes system trace errors when you import Personnel records A delay (or a timeout message) that occurs when you click Limited Previous Doors or Complete Previous Doors on the Personnel Previous Doors tab has been corrected Query results are no longer affected if you edit a Personnel record while the Query is being processed; previously, the Personnel record being edited was incorrectly added to the Query results apc controllers on systems upgraded from version 2.02 to version 2.20 are now assigned the correct Time Zone Auto Import on the MAS no longer experiences failures when re-importing Personnel records that reside in a SAS partition A Limited Privilege with Data Import Edit permission no longer incorrectly prevents an Operator from using the Personnel Mapping Tool, Field Mapping Tool, or Custom Stylesheets in Data Import Corrected an issue that caused some Activity Viewer rows to be missed, or to be blank, after toggling the Freeze Timeout button, when there are over 1000 rows of Activity in the Monitoring Station Activity Viewer An issue that caused Reports that previously ran correctly to time out after version 2.20 Patch 1 was installed has been corrected. 10 RN R2

11 Corrected an issue that caused synchronization errors to occur for Global Schedules in an Enterprise system An error that occurs when starting the victor client on a unified C CURE and victor 4.4 system after the C CURE Language Pack is installed has been corrected Image and signature capture date fields on the Personnel Images now display the correct time and date The CrossFire Framework Service no longer stops when an Operator on a unified system acknowledges an event while there is a high rate of input activity apc controllers no longer perform an unnecessary full download when recovering from Comm Fail An Operator with limited Privilege on a Partitioned unified system (with C CURE 9000 and victor 4.4) can now view doors, controllers, readers, and inputs correctly in the Monitoring and Administration Stations. Patch #1 Critical Update 1 SPAR apc controllers no longer perform an unnecessary full download when recovering from Comm Fail. Patch #1 SPARS A problem that caused long delays to occur when processing alarm responses after upgrading to version 2.10 has been mitigated by adding an IntrusionZoneUpdateTimePeriod parameter to the istar Driver, and changing the way queued updates are processed A problem that caused long delays to occur when processing alarm responses after upgrading to version 2.10 has been mitigated by removing unnecessary AcknowledgeStatus messages from the update queue This SPAR provides the functionality that uses the new Personnel system variable Auto Increment Site Code to increment the Personnel Credentials tab field Issue Code for a credential when Print Badge (on the Personnel Badging tab) is used to print a replacement badge. For more information, see New System Variable: Auto Increment Site Code. RN R2 11

12 92361 A problem that caused the Application Layout editor to not display newly added tabs correctly, when ten or more tabs were added before saving the layout, has been corrected. All tabs that were added when saved will now be visible. With this correction, if you add 10 new tabs to an Application Layout and save the Layout, when you subsequently open the layout, all 10 tabs will be displayed. Existing tabs that were added prior to this correction will now be visible, but may not appear in the order desired, and may need to be edited or deleted Corrected a problem that caused a local SAS Event to intermittently not appear on the Monitoring Station of a MAS client after the SAS CrossFire services have been stopped and restarted A problem that caused istar panel problems when SQL was unavailable during start up of an integration driver has been corrected by shutting down the istar driver until SQL is available again A problem that caused an istar panel to experience Comm Fail when downloading a large number of Personnel Groups for an Area with occupancy restrictions has been corrected A problem that allowed an istar Door to be added to three Areas (rather than only two Areas) has been corrected A problem that caused CHUID Format errors when attempting to add a credential to a card holder has been corrected A problem that caused an error message box ( No room available to display rows ) to appear if the Monitoring Station window is resized to be too small to display new activities has been corrected A problem that caused Card Reject Events not to end after the specified Minimum Activation Time expired has been corrected A problem that caused Video and Map popup Event actions to not display unless send state changes to Monitoring Station was enabled in the Event has been corrected A problem that caused Card Reject Events not to end after the specified Minimum Activation Time expired has been corrected. 12 RN R2

13 96885 A problem that caused Video and Map popup Event actions to not display unless send state changes to Monitoring Station was enabled in the Event has been corrected. Patch #0 Critical Update 1 SPARS A problem that caused long delays to occur when processing alarm responses after upgrading to version 2.10 has been mitigated by adding an IntrusionZoneUpdateTimePeriod parameter to the istar Driver, and changing the way queued updates are processed A problem that caused long delays to occur when processing alarm responses after upgrading to version 2.10 has been mitigated by removing unnecessary AcknowledgeStatus messages from the update queue. End of Release Notes The trademarks, logos, and service marks displayed on this document are registered in the United States [or other countries]. Any misuse of the trademarks is strictly prohibited and Tyco Security Products will aggressively enforce its intellectual property rights to the fullest extent of the law, including pursuit of criminal prosecution wherever necessary. All trademarks not owned by Tyco Security Products are the property of their respective owners, and are used with permission or allowed under applicable laws. Product offerings and specifications are subject to change without notice. Actual products may vary from photos. Not all products include all features. Availability varies by region; contact your sales representative Tyco Security Products. All rights reserved. RN R2 13