C•CURE 9000 Version 3.

00 Release Note

October 2024 Document Number: 8200-2102-26

Revision: F Build number: C•CURE 3.00.586.586

www.swhouse.com
Contents
Installation media contents .......................................................................................................................................4
New features .............................................................................................................................................................4
Button for the conversion of iSTAR Ultra to Ultra G2 On the iSTAR Ultra editor .................................................4
Amazon Web Services (AWS) Relational Database Services (RDS) database support .....................................4
C•CURE Portal security updates ..........................................................................................................................4
C•CURE ID security updates ................................................................................................................................4
Email template customization ...............................................................................................................................4
Personnel group assignment through XML import ...............................................................................................5
Query enhancements ...........................................................................................................................................5
Encryption passphrase changes ..........................................................................................................................5
Client load impact and metrics in CrossFire Server .............................................................................................5
Pushing load impact information into the system trace log ..............................................................................5
Configure initial size and autogrowth settings for Unified Journal databases ......................................................5
Supported operating systems, database management systems (DBMS), and SQL collations ...............................5
Supported browser and mobile operating systems ..................................................................................................7
Redundancy and disaster recovery ..........................................................................................................................8
C•CURE 9000 considerations and known limitations ...............................................................................................8
Installation and upgrade issues ............................................................................................................................8
Enterprise considerations and known limitations .....................................................................................................9
Installation and upgrade issues ............................................................................................................................9
Application layouts on MAS ............................................................................................................................... 10
Editing Global Operators ................................................................................................................................... 10
Importing considerations.................................................................................................................................... 10
C•CURE Portal considerations and known limitations .......................................................................................... 10
Single sign on (SSO) support in C•CURE Portal ............................................................................................... 10
Notification hyperlinks from emails .................................................................................................................... 10
Compatibility of third-party hardware ..................................................................................................................... 10
Compatibility of third-party software ...................................................................................................................... 12
Firmware Versions for Tyco Security Products Controllers ................................................................................... 13
Enhancements ....................................................................................................................................................... 14
Issues fixed ............................................................................................................................................................ 14
Upgrading to v3.00 ................................................................................................................................................ 15
Upgrade troubleshooting ....................................................................................................................................... 16
C•CURE and victor server databases may expand during upgrade ................................................................. 16
Upgrade may freeze with Out-of-Disk Space error ........................................................................................... 16
Post-upgrade steps for C•CURE 9000 v3.00 System on custom (non-default) path ........................................ 16
Exported objects into external XML documents ................................................................................................ 16
SDK Connected Program drivers ...................................................................................................................... 16
Installation troubleshooting .................................................................................................................................... 16

2
 Enable Microsoft Media Foundation Server ...................................................................................................... 16
SQL privileges for local system account in a Workgroup .................................................................................. 17
Server requirements failure message during installation on Windows servers ................................................. 17
Installation completes on a computer with a name that is longer than 15 characters, but Clients do not connect
........................................................................................................................................................................... 17
Services and server components manual start ................................................................................................. 17
victor Temporary License Expiration and C•CURE 9000 Licensed Video Drivers ............................................ 17
Installing C•CURE Go Web Service and C•CURE 9000 Legacy Web Client ....................................................... 17
IP address requirements for C•CURE Go install ............................................................................................... 17
IIS version prerequisite for C•CURE Go Install ................................................................................................. 17
Installing Language Pack for C•CURE Go and C•CURE 9000 Web Client ...................................................... 17
C•CURE Go Web Service installation not supported on MAS .......................................................................... 18
End of release note ................................................................................................................................................ 18

3
Installation media contents
The installation media includes C•CURE 9000 from Software House and victor from American Dynamics. These
combine for Unified deployments. The installation media also includes supporting services and integration
drivers.

Contents:
• C•CURE 9000 Install components (victor Application Server and C•CURE 9000 Client).
• EULA.rtf – End User License Agreement.
• HostIDUtil.exe – HostID Application.
• RN-CC-v3.00-8200-2102-26-B.pdf – the C•CURE 9000 version 3.00 (v3.00) release note file. Check
the Software House website for the latest revision of the C•CURE 9000 v3.00 release note file.
• RN-CC-WEB-v3.00-8200-2102-37-A.pdf– the C•CURE 9000 v3.00 C•CURE web-based client release
note file.
• Unified Quick Start Guide.pdf - the Unified Installer Quick Start Guide.
• C•CURE Quick Start Guide.pdf –the C•CURE Quick Start Guide.
• victor Quick Start Guide.pdf – the victor Quick Start Guide.
• Setup.exe – Executable to launch the installation dashboard.
• Certificates folder containing security certificate files.
• Bin folder containing supporting installers and support files for C•CURE 9000 and victor products.
Installers should be installed through the installation dashboard, not through individual install files.
• Manuals folder containing the documentation of Software House software and hardware products.
• Integrations folder containing installers and support files for DSC and Galaxy Intrusion integration
software.
• Prerequisites folder containing prerequisite software requirements for C•CURE 9000 and victor.

NOTE: The Intellex, Video Edge, and HDVR/Exacq video drivers are included with this v3.00 release.

New features
The following features are new in C•CURE 9000 v3.00.

Button for the conversion of iSTAR Ultra to Ultra G2 On the iSTAR Ultra editor

Operators with the Convert Board privilege can access a conversion button, Convert to Ultra G2. The Convert to
Ultra G2 button is hidden for newer iSTAR Ultra and iSTAR Ultra G2 controllers.

Amazon Web Services (AWS) Relational Database Services (RDS) database support

Cloud deployment of your Microsoft SQL Server database is now supported through AWS RDS. With AWS RDS,
you can set up, authenticate, operate, and scale your SQL server in the cloud with assistance from your cloud
provider.

For more information, refer to the C•CURE Amazon Relational Database Services Quick Start Guide.

NOTE: AWS RDS is the only RDS that is currently supported by C•CURE 9000.

C•CURE Portal security updates

C•CURE Portal has moved to the Angular web framework, which offers increased security and usability for the
Visitor Management Portal, Reception Portal, and Access Management Workflow.

C•CURE ID security updates

EV1 and EV2 cards now support the encoding of up to five applications simultaneously. If one application is
hacked, you can roll the key and move to the next application.

Email template customization

An HTML editor is now provided in the Visitor Management Portal and Access Management Workflow to
supplement the existing plain text editor. Additionally, a preview tab has been added to verify modified scripts.

4
Personnel group assignment through XML import
Assign and remove personnel from personnel groups by importing an XML file with the <GroupsChanged> and
<GroupsAll> keywords.

Query enhancements
The new IN GROUP operator has been added to Journal and Audit Log queries for selecting single groups. If
you select a group, the query returns all the journal records that have an object referenced as the member of the
group.

Encryption passphrase changes

On the Encryption tab in the Server Configuration application, you can change the passphrase which is specified
when the system is first installed. If you do not have the existing passphrase, C•CURE Customer Support can
provide a one-time key that you can use to change the passphrase.

Analytics alarms for exacqVision, VideoEdge, and Illustra integrations

Support for analytics alarms has been added in the exacqVision, VideoEdge, and Illustra integrations.

Client load impact and metrics in CrossFire Server

In the Server Configuration Application, CrossFire now keeps a continuously updated table of the calls in the
previous hour for each session that is connected to CrossFire.

Pushing load impact information into the system trace log

1. In the Server Configuration Application, click the Diagnostics tab.
2. On the Metrics tab, open the Client Metrics dropdown menu.
3. Click the TraceSession button.
4. To view the load information and metrics in the system trace log, click the Trace tab.

Configure initial size and autogrowth settings for Unified Journal databases
To improve performance, four new system variables have been added to the Unified Journal database so you
can set the initial size and autogrowth settings:

• Initial Size for Journal Datafile

• Initial Size for Journal Logfile
• Automatic Growth Size for Journal Datafile
• Automatic Growth Size for Journal Logfile

Changing these variables prevents log files from growing excessively and increasing the virtual log file (VLF)
count.

Disable person PIN failure system variable

This new system variable can be set to automatically disable a personnel card if several PIN attempts are
incorrect. The minimum value for disabling a personnel card is 2 incorrect PIN attempts and the default value is
3 incorrect PIN attempts. If the value is set to 0 the system variable is disabled.

Supported operating systems, database management systems (DBMS), and SQL

collations
The operating systems, DBMSs, and SQL collations that are supported in C•CURE v3.00 are listed in Table 1,
Table 2, and Table 3.

NOTE: See the C•CURE 9000 Windows Compatibility Update Note on the Software House website for more
information on the compatibility of monthly Windows system updates with C•CURE 9000 systems.

Table 1: Microsoft operating systems for Server and Client

Server Series L/M/N/Satellite application server Supported Version
(SAS)
Windows 10 Professional* 64-bit
Windows 10 Enterprise* 64-bit

5
 Windows 11 Professional 64-bit
Windows 11 Enterprise 64-bit
Windows Server 2016 Standard 64-bit
Windows Server 2016 Datacenter 64-bit
Windows Server 2019 Standard 64-bit
Windows Server 2019 Datacenter 64-bit
Windows Server 2022 Standard 64-bit
Windows Server 2022 Datacenter 64-bit
Server Series P/Q/R/R+/S/S+/T/SAS Supported Version
Windows 10 Professional* 64-bit
Windows 10 Enterprise* 64-bit
Windows 11 Professional 64-bit
Windows 11 Enterprise 64-bit
Windows Server 2016 Standard 64-bit
Windows Server 2016 Datacenter 64-bit
Windows Server 2019 Standard 64-bit
Windows Server 2019 Datacenter 64-bit
Windows Server 2022 Standard 64-bit
Windows Server 2022 Datacenter 64-bit
Master application server (MAS) Supported Version
Windows Server 2016 Standard 64-bit
Windows Server 2016 Datacenter 64-bit
Windows Server 2019 Standard 64-bit
Windows Server 2019 Datacenter 64-bit
Windows Server 2022 Standard 64-bit
Windows Server 2022 Datacenter 64-bit
Client Supported Version
Windows 10 Professional* 64-bit
Windows 10 Enterprise* 64-bit
Windows 11 Professional 64-bit
Windows 11 Enterprise 64-bit
Windows Server 2016 Standard 64-bit
Windows Server 2016 Datacenter 64-bit
Windows Server 2019 Standard 64-bit
Windows Server 2019 Datacenter 64-bit
Windows Server 2022 Standard 64-bit
Windows Server 2022 Datacenter 64-bit

*NOTE: Windows 10 must be v1809 or higher. Ensure that Microsoft Windows Media Foundation Server is
enabled in your Windows environment.

Table 2: Microsoft DBMS

Server Series L/M/N/SAS Supported Version
SQL Server 2016 Express SP1 or higher (64-bit)
SQL Server 2016 Standard SP1 or higher (64-bit)
SQL Server 2016 Enterprise SP1 or higher (64-bit)
SQL Server 2017 Express* All Service Packs (64-bit)
SQL Server 2017 Standard All Service Packs (64-bit)
SQL Server 2017 Enterprise All Service Packs (64-bit)
SQL Server 2019 Express All Service Packs (64-bit)
SQL Server 2019 Standard All Service Packs (64-bit)
SQL Server 2019 Enterprise All Service Packs (64-bit)
Server Series Standalone P/Q/R/R+/S/S+/T Supported Version
SQL Server 2016 Standard SP1 or higher (64-bit)
SQL Server 2016 Enterprise SP1 or higher (64-bit)
SQL Server 2017 Standard All Service Packs (64-bit)
6
 SQL Server 2017 Enterprise All Service Packs (64-bit)
SQL Server 2019 Standard All Service Packs (64-bit)
SQL Server 2019 Enterprise All Service Packs (64-bit)
SAS Server Series P/Q/R/R+/S/S+/T Supported Version
SQL Server 2016 Standard SP1 or higher (64-bit)
SQL Server 2016 Enterprise SP1 or higher (64-bit)
SQL Server 2017 Standard SP1 or later (64-bit)
SQL Server 2017 Enterprise All Service Packs (64-bit)
SQL Server 2019 Standard All Service Packs (64-bit)
SQL Server 2019 Enterprise All Service Packs (64-bit)
MAS Server Supported Version
SQL Server 2016 Standard SP1 or higher (64-bit)
SQL Server 2016 Enterprise SP1 or higher (64-bit)
SQL Server 2017 Standard All Service Packs (64-bit)
SQL Server 2017 Enterprise All Service Packs (64-bit)
SQL Server 2019 Standard All Service Packs (64-bit)
SQL Server 2019 Enterprise All Service Packs (64-bit)

*NOTE: SQL Server 2017 Express supports C•CURE v2.80 to v3.00 upgrades on SiteServer. SQL Server 2017
Express is supported on C•CURE 9000 Series-P.

Table 3: SQL Server collations

Windows Locale Default Collation
Arabic (Saudi Arabia) Arabic_CI_AS
Chinese (PRC) Chinese_PRC_CI_AS
Chinese (Taiwan) Chinese_Taiwan_Stroke_CI_AS
Czech (Czech Republic) Czech_CI_AS
Danish (Denmark) Danish_Norwegian_CI_AS
Dutch (Netherlands) Latin1_General_CI_AS
English (United Kingdom) Latin1_General_CI_AS
English (United States) SQL_Latin1_General_CP1_CI_AS
French (France) French_CI_AS
German (Germany) Latin1_General_CI_AS
Greek (Greece) SQL_Latin1_General_CI_AS
Hungarian (Hungary) Hungarian_CI_AS
Italian (Italy) Latin1_General_CI_AS
Japanese (Japan) Latin1_General_CI_AI
Korean (Korea Dictionary Sort) Korean_Wansung_CI_AS
Polish (Poland) Polish_CI_AS
Portuguese (Brazil) Latin1_General_CI_AS
Russian (Russia) Cyrillic_General_CI_AS
Spanish (Spain) Modern_Spanish_CI_AS
Swedish (Sweden) Finnish_Swedish_CI_AS
Turkish (Turkey) Turkish_CI_AS

Supported browser and mobile operating systems

Table 4 shows the supported browsers and mobile operated systems that are supported for C•CURE v3.00.

Table 4: Browser and mobile operating systems

Internet Information Services (IIS) versions
IIS Web Server v8 or later
C•CURE Go
Android v7 or later
iOS iOS 13 or later

7
 C•CURE Go Reader
Android v7 or later
C•CURE 9000 web-based client
Microsoft Edge (Chromium-based) v83 or later
Google Chrome v83 or later
Mozilla Firefox v77 or later
Apple Safari Supported
C•CURE Portal Visitor and Access Management
Microsoft Edge (Chromium-based) v83 or higher v83 or higher
Google Chrome v83 or higher v83 or later
Mozilla Firefox v77 or higher v77 or later
Apple Safari Supported
Visitor Kiosk App (iOS) Supported
C•CURE Kiosk
Android Not Supported
iOS iPad only

Redundancy and disaster recovery

Table 5 shows the redundancy and disaster support software that is supported for C•CURE v3.00.

Table 5: Redundancy and disaster recovery software

Versions v2.80 v2.90 v3.00
Stratus everRun Enterprise 7.4.2 7.7 7.7.0-283
Stratus everRun Extend Supported Supported 18.2.0.5683

NOTE: Only the latest available versions of Stratus everRun MX and Enterprise are qualified on each C•CURE
9000 release. Stratus everRun MX and Enterprise will be qualified on C•CURE 9000 v3.00 SP1.

C•CURE 9000 considerations and known limitations

Installation and upgrade issues
Consider the following issues before installing C•CURE 9000 v3.00.

• Cybersecurity issues with Innometriks tunnel configuration for High Assurance services
Due to cybersecurity concerns, the stunnel configuration for High Assurance services has been removed
from the C•CURE 9000 v3.00 installation. The Innometriks High Assurance Services installer now
updates the stunnel configuration during the High Assurance installation process.

If you have installed previous versions of C•CURE 9000 and Innometriks High Assurance, you must
choose from one of the following options:
o Back up the stunnel configuration file, upgrade C•CURE to v3.00, then restore the stunnel
configuration file.
o Uninstall the High Assurance services, upgrade C•CURE to v3.00, then reinstall the High
Assurance services.

• OpenSSL .dll files issues

If the Innometriks integration is installed and you upgrade C•CURE 9000 to v3.00, the installer
downgrades the OpenSSL .dll files. To resolve the issue, upgrade C•CURE 9000 to v3.00, then reinstall
or repair the Innometriks integration.
• Manually uninstalling FreeSWITCH when upgrading from Unified C•CURE v2.80 to v3.00
If you use the remote client, FreeSWITCH is not automatically uninstalled when upgrading from Unified
C•CURE v2.80 to v3.00. If the installer detects an old version of FreeSWITCH on your client, an error

8
 message displays. To continue the installation, you must manually uninstall FreeSWITCH from Windows
Apps and Features.

If you use victor Application Server, FreeSWITCH is automatically uninstalled during the upgrade.

Enterprise considerations and known limitations

Installation and upgrade issues
If you use Enterprise, consider the following issues before installing C•CURE v3.00.

• Using SQL Server Express with SAS L/M/N upgrades

SQL Server Express is supported for upgrades of SAS Series L/M/N but for best performance, use SQL
Server Standard/Enterprise with C•CURE 9000 v3.00. SQL Server 2017 Express supports C•CURE
v2.80 to v3.00 upgrades on SiteServer. For more information, see the datasheet for the applicable SQL
Server versions compatible with C•CURE 9000 v3.00.

• Upgrading SiteServer appliances to C•CURE v3.00

SiteServer appliances cannot upgrade to C•CURE v3.00 using the current C•CURE v3.00 installation
image. SiteServer appliances can only be upgraded to C•CURE v3.00 using a SiteServer-specific
upgrade image.

• SAS and licensing

You cannot convert a SAS to standalone by changing the license after initially installing and licensing it
as a SAS.

• Relation between SAS and its MAS

You cannot point an existing SAS to a different MAS. You must back up the MAS before adding each
new SAS in case you have to revert the enterprise to the setup before the SAS was added.

• Upgrading MAS before its SAS

You must upgrade the MAS before you upgrade the SAS systems to the same version. If you upgrade
your SAS systems first, the SAS systems must be restarted again after upgrading the MAS.

• Synchronizing Journal before upgrading from v2.30/2.30 R2/2.50 to v3.00

Prior to upgrading your MAS and SAS systems from v2.30/2.30 R2/2.50 to v3.00, verify that any
scheduled Journal Synchronization from SAS to MAS has been completed.
Caution: Close the ‘CrossFire Server Component Framework Service’ prior to performing this last
synchronization. If you do not synchronize before upgrading to v3.00, unsynchronized journal messages
from v2.20/2.30/2.30 R2 never sync to the MAS. For more information about the Application Server
Synchronization tab, see Chapters 4 and 10 in the C•CURE 9000 Enterprise Architecture Guide.

• Upgrading SAS while server is not configured or running correctly may fail
Do not upgrade a SAS when the server is non-functioning as the upgrade may fail. Run a repair, and
ensure the repair is successful before performing the upgrade.

• Converting a standalone C•CURE 9000 system with User Defined Fields (UDFs) to a v3.00 SAS
You cannot automatically convert a C•CURE 9000 system with UDFs to a SAS. For detailed instructions,
see Chapter 2 of the C•CURE 9000 Standalone to SAS Migration Utility User Guide.

• Upgrading Enterprise system with SAS that used to be a Standalone C•CURE 9000 system to v3.00
If you are upgrading an Enterprise System with a SAS that used to be a Standalone system to v3.00,
you may need to do the following after the SAS is upgraded and fully running:
Stop and then re-start any running Administration/Monitoring Station applications connected to the MAS.
This allows the application to access certain Enterprise functions, such as Synchronization Conflict
Views.

9
 • Uninstalling MAS with Server Management Application open causes error
Make sure that the Server Management Application is closed before uninstalling a MAS. If you uninstall
a MAS without closing the Server Management Application, a message is displayed asking you to close
the Server Management Application. The uninstall will complete unsuccessfully and displays a fatal error
message.

Application layouts on MAS

Do not edit the three pre-defined Application Layouts on the MAS: Default View 1, Default View 2, and Default
Application Layout. Create, and assign, a new MAS Application Layout to all Operators to avoid the need to edit
pre-defined layouts.

Editing Global Operators

Do not edit Global Operators if you are logged into the system as a Local Operator, because Application Layouts
do not save correctly.

Importing considerations
For performance reasons, imports must be done on the server that owns that Object’s partition.
Example:
Import global data on the MAS and import local data on the SAS that owns it.
• Very large imports can cause the MAS performance to significantly degrade when synching with the
SAS. Importing personnel records with attached documents or images can use significant amounts of
memory during replication. Software House recommends you keep imports down to a total of 400 MB,
including both Image and Document data.
Example:
• 3000 personnel with 500 KB Documents for each personnel record = 1.5 GB of memory to process.

C•CURE Portal considerations and known limitations

If you use C•CURE Portal, consider the following issues before installing C•CURE v3.00.

Single sign on (SSO) support in C•CURE Portal

C•CURE Portal does not support SSO on v3.00.

Notification hyperlinks from emails

Before opening any hyperlinks from a C•CURE Portal notification email to the C•CURE Portal website, you must
log on to the C•CURE Portal system for the authentication to work correctly.

Compatibility of third-party hardware

Table 6 shows some of the third-party hardware products that are compatible with C•CURE 9000 v3.00.

Table 6: Third-party hardware compatibility table

Equipment type Vendor model Model Latest supported
version
Digital Video American Dynamics Intellex 5.4
Management System
VideoEdge 6.0

HDVR 1.7, 2.1, 2.2

Exacq exacqVision 22.09, 22.12

Wireless Readers / Schlage AD-30x / 40x AD.A.130

Locks
NDE/LE

Assa Abloy Aperio Hub Hub 6.6.32718

10
Signature Capture Topaz T-S261-B 3.0.3

T-S751-B

Topaz USB T-S261-HSB 4.4.0

T-S751-HSB

PenWare 100 PW100 4.5.0

USB Badging Cameras Video Associates Val Cam 6.1.76.00

VA-3 USB 6.1.76.00

Videology 2x USB 9.0

TWAIN 2.1.18

All brands WIA-compliant (non-TWAIN)

ID Scanners Acuant ScanShell R2/R3 SDK 10.11.04

SnapShell Passport SDK 10.11.04

Gemalto AT-9000-UV 5.2.80

QS1000

IP Cameras AXIS 2400/2401 2.33

Badging Printers Fargo HDP 5000 3.5.4

HDP 6600 01.00.0013

DCT 4500E 2.1.0.3.2

Magic Card 600 2.00

Pronto 2.00

Rio Pro 2.00

DYMO 450 Series

Brother 820-WiFi Printer

QL-820NWB Wi-Fi

VC-500W Wi-Fi

Primera LX500C No Wi-Fi

Smart Card Device SCM Microsystems SDI010 5.21

Readers HID HID-USB-5421

11
 5127

Identive 4701F

Innometriks Cheetah 5.2.6

Cheetah SE 2.0.2

Rhino 5.2.6

Compatibility of third-party software

Table 7 shows some of the third-party software products that are compatible with C•CURE 9000 version 3.00.

Table 7: Third-party software compatibility table

Company Product Latest supported version

Data Dynamics Active Reports 6.2.3681

American Dynamics Intellex API 5.02.32.45

Flexera FLEXNet Publisher 11.10.1

LEAD Technologies LEADTOOLS 14.5.0.68

Infragistics Infragistics 17.2

Microsoft Application Request Routing 3.0 (6.0.2900.5512)

Database Providers 3.1
DirectX June 2010 4.9.0.904
Redistributable
.NET Framework 4.8.1

NOTE: For some C•CURE

products, .NET Framework 3.5
Service Pack 1 must be installed
on the system. If necessary, the
Dashboard prompts you to
install the service pack.
.NET Core 3.1
ProviderServices 2.1
SQL Server 15

12
 SQL Server 2017 Feature Pack 14.0.1000.169
Sync Framework 2.1
Windows Installer 4.5

MFC Runtime 9.0 SP1, 10.0 SP1, 11.0, 12.0,

14.0
Visual Studio C++ 2012 11.0.61030.0
Redistributable
Visual Studio C++ 2019 14.25.28508.3
Redistributable
Sequiter Inc CodeBase 6.5

Stratus everRun MX 7.5.1.1

everRyn Enterprise 7.5.1.1

Stunnel Stunnel 5.42

The OpenSSL Project OpenSSL 1.0.2L

Apache CouchDB 3.2.0

Node.js Node.js 14.19.0

AXIS Media Control 7.4.1.0

Firmware Versions for Tyco Security Products Controllers

The following table shows the firmware versions related to C•CURE 9000 v3.00.

Note: apC firmware cannot be flashed. You must physically replace firmware chips. However, apC Lite and apC
8x firmware can be flash upgraded.

Table 8: Firmware for Tyco Security Products controllers

Component Latest supported version
iSTAR Classic 4.4.C
iSTAR Pro 5.2.F.19831.i2
iSTAR Edge 6.2.8.20232.i4
iSTAR Edge G2 6.8.9.24214.i7
iSTAR eX 6.2.8.20232.i3
iSTAR Ultra 6.8.9.24214.i5
iSTAR Ultra G2 6.8.9.24214.i8
iSTAR Ultra SE 6.8.9.24214.i8
ISTAR Ultra LT 6.8.9.24214.i6
apC 7.7ZF
apC/8x 8.7ZF
13
 apC \L (apC Lite) 10.7ZF
iSTAR Configuration Utility 6.8.6.22959
IP-ACM / IP-ACM 2 6.8.9.24214

Enhancements
The following table shows enhancements for C•CURE 9000 v.3.00.

Table 9: Enhancements
Category Issue Fix description
number
C•CURE ID 745283 HID physical access solutions (PACs) can be read from HID SEOS
cards with the Omnikey 5127 CK mini encoder, within HID Fargo
HDP6600 badging printing.
767647 EV1 and EV2 cards now support the encoding of up to five
applications simultaneously.
Enterprise 728612 When an application server in an Enterprise environment is moved
to another machine with a different hostname, obsolete DBQueue
entries are removed.
777441 If the SAS and service account is different to the current user, a
pop-up message warns that the SAS service account must be an
operator in the MAS database.
Installation and 728735 Performance improvements for client session disposal during
upgrade installation.
745146 You can use quotation marks and equals signs in passwords.
iSTAR Driver 745720 The method of enabling Intrusion Zone tracing has been simplified.
Instead of editing the iSTAR Driver configuration file, you can edit
an iSTAR Driver system variable,
IntrusionZoneUpdateTimePeriod.

Maps 732878 For clarity, the label of the Map Name field has changed to Legacy
Map Field.

Issues fixed
The following table shows defects and issues that are fixed in C•CURE 9000 v.3.00.

Table 10: Issues fixed

Category Issue Fix description
number
Administration and 728733 In a Monitoring Station attached to a MAS, you can clear SAS-
Monitoring Stations based events that need clearing checked, as expected.
729193 When using a custom Personnel view, images display as
expected.
729313 An issue where you cannot edit the Personnel Quick Search
system variable if two or more customer labels have the same
value is resolved.
733101 An issue where large UDF fields cause system start-up to slow
down is resolved.
745836 An issue with adding iSTAR Ultra controllers, where the Password
field does not appear if the screen resolution is low, is resolved.
Active templates 728532 Performance issues caused by active template privileges are
resolved.
Badging and badge 729356 Badge layouts assigned to personnel appear when saving a
layouts Credential on a new record, as expected.

14
 Category Issue Fix description
number
C•CURE Portal 728728 An issue where new visitor registration fails if a personnel UDF
type is set to Date is resolved.
Credentials 728536 Operators without edit privileges for Credentials can print badges,
as expected.
Cybersecurity 739567 An SQL vulnerability is resolved.
Enterprise 728724 Performance issues with the MAS sync queue in Enterprise
systems are resolved.
Events 728730 An issue where report attachments are missing from emails is
resolved.
Import and export 728621 An issue where lightweight directory access protocol (LDAP)
referrals fail is resolved.
Installation and 757484 Upgrades from Enterprise v2.70 SP3 to higher versions no longer
upgrade fail because of a script execution error.
iSTAR Driver 728742 With P2000 controllers, manual actions no longer interfere with
iSTAR driver startup.
728732 Conflicts between Daylight Savings Time time zones are resolved.
728738 An issue with excessively long system startup for iSTAR Driver is
resolved.
Journal 728809 An issue where the SASinator tool does not process older unified
journals or SWHSystemJournal is resolved. Operators without the
GLOBAL ALL privilege can perform a journal replay of card swipe
statuses that are older than the time that the SASinator was run,
as expected.
Operators and 728736 Performance issues with privilege fetches are resolved.
privileges
Personnel 728731 An issue where operators erroneously receive a custom clearance
duplication error message while saving an existing record is
resolved.
Readers 728523 After a request to exit (RTE), the door lock relay is reactivated for
doors with the status Door open to long, as expected.
774310 An issue where reader modules (RMs) cannot communicate with
the iSTAR Edge G2 controller after using the Edge to Edge G2
conversion tool is resolved.
779258 An issue with iSTAR IP ACM readers becoming unresponsive after
After Hours is enabled is resolved.
728734 Performance issues with session creation are resolved.
Video 728729 An issue with the Verint Video Management Software integration,
where the email option in the video pop-up player fails with no
error message, is resolved.
Visitor management 775302 An issue where visitor portraits do not appear in email notifications
when the visitor checks in for the first time is resolved.

Upgrading to v3.00
See the C•CURE 9000 Installation and Upgrade Guide for information on upgrading your C•CURE 9000 system.

You can upgrade to C•CURE 9000 v3.00 directly from the following earlier versions:

Table 11: Software version upgrades

Standalone and Enterprise Systems
v2.80 to v3.00
v2.90 to v3.00

15
Be aware that upgrading removes the existing firmware files
(<INSTALLDIR>Tyco\CrossFire\ServerComponents\apC and istar) while adding the new firmware versions. If
you need to keep your existing firmware, save the files elsewhere before you upgrade to v3.00. Otherwise, you
must re-download these files from the Software House web site.

Upgrade troubleshooting
If you are upgrading to v3.00 from an older C•CURE system, you may encounter one the following issues.

C•CURE and victor server databases may expand during upgrade

Ensure you have ample disk space available before upgrading as C•CURE and victor Server application
databases may expand by up to 10 GB.

Upgrade may freeze with Out-of-Disk Space error

During an upgrade, a message may inform you that there is not enough disk space available.
Workaround: Add more disk space on an existing/new drive and run the upgrade again.

Post-upgrade steps for C•CURE 9000 v3.00 System on custom (non-default) path
If you are upgrading a system in a custom (non-default) location, once the upgrade to v3.00 completes, you
must verify that the System Variable paths for Import, Export, and Database Backup are correct.

Exported objects into external XML documents

If you have exported objects into external XML documents from previous versions of C•CURE 9000, you may
not be able to re-import them directly into C•CURE 9000 v3.00. Object definitions in the database can change
from version to version, so the import may fail, or the imported object may not work correctly in C•CURE 9000
v3.0.

Workaround: If you have any valuable XML documents generated by Data Export in a prior version of C•CURE
9000, you should do the following prior to upgrading C•CURE 9000 to v3.00:
1. Re-Import the XML documents.
2. Upgrade to v3.00.
3. Export the Objects again.

SDK Connected Program drivers

SDK Connected Program drivers and C•CURE 9000 upgrade

BEFORE UPGRADING C•CURE 9000: If you licensed any of the SDK Connected Program drivers with a
previous release, check the Software House web site (Home>Support>“Software House Connected“>
Compatibility Matrix http://www.swhouse.com/support/SWH_Connected_Compatibility_Matrix.aspx) to confirm
that your integration is compatible with v3.00 before you upgrade.
Contact the distributor of the Connected Program driver to get your C•CURE 9000 v3.00 compatible driver.
NOTE: Client Auto-Update does not update clients with new versions of a Connected Program Driver product.
You must perform Client updates for these products manually at each client.

Uninstalling SDK Connected Program drivers

If you have a Connected Program Integration from a previous release that you do not intend to upgrade and
wish to uninstall, you must uninstall it before you upgrade your C•CURE 9000 to v3.00. If you upgrade to
v3.00 and then try to uninstall, the uninstall may fail.

Installation troubleshooting
If you are installing C•CURE v3.00 for the first time, you may encounter the following issues.

Enable Microsoft Media Foundation Server

Ensure that Microsoft Windows Media Foundation Server is enabled in your Windows environment before
installing C•CURE 9000 v3.00. For more information on enabling this feature, check your Windows help
documentation.

16
SQL privileges for local system account in a Workgroup
If you are installing C•CURE 9000 on a Workgroup system that already has SQL Server 2014/2016 Express/Full
installed, you must assign the SQL Sysadmin privilege to the Windows account local system. If you do not do
this, the CrossFire Services do not start.

Server requirements failure message during installation on Windows servers

If IIS Extension files are not installed on your server system, the Installer reports that IIS is not installed. You
can safely continue installing and install the IIS Extension Files after the C•CURE 9000 install is complete.

Installation completes on a computer with a name that is longer than 15 characters, but Clients do not
connect
If you install C•CURE 9000 on a computer with a name longer than 15 characters, the following error message
displays: The NetBIOS name is limited to 15 characters. You can continue the install, but the system name
will be truncated. Consequently, Clients will be unable to log on to C•CURE 9000.
Workaround: Change the computer name to match the 15-character truncated version.

Services and server components manual start

After installing C•CURE 9000 v3.00, you must run the Server Configuration Application (Start>All
Programs>Tyco>Server Configuration Application) one time to start the CrossFire Framework and CrossFire
Server Component Framework Services. You cannot access C•CURE 9000 functions until you start these
services.

You also need to enable and start the Extension Service (Hardware Driver) for each type of controller, video, or
network component to be used on the server. The Extension Services [Drivers] are not automatically started by
default because enabling drivers for devices that are not used can affect system performance. In addition,
starting them automatically would trigger a download for apC and iSTAR controllers. You can view the status of
these drivers from Windows Services, but should not configure them to start automatically from there; startup is
managed by the CrossFire Server Component Framework Service.

For more information, see the C•CURE 9000 v3.00 Installation and Upgrade Guide.

victor Temporary License Expiration and C•CURE 9000 Licensed Video Drivers
If you install a C•CURE 9000 + victor Unified system but do not obtain a permanent license for victor, C•CURE
9000 Video drivers may stop working when the victor temporary license expires.
Workaround:
1. Either obtain a permanent victor license or remove the victor temporary license.
2. Edit, disable, and then save each Video Server on the C•CURE 9000 Administration Station.
3. Edit, enable, and save each Video Server to restore the connection with each server.

Installing C•CURE Go Web Service and C•CURE 9000 Legacy Web Client
If you are installing C•CURE Go Web Service or C•CURE 9000 Legacy Web Client, be aware of the following
considerations.

IP address requirements for C•CURE Go install

Install the C•CURE Go Web Service application either on a system with a fixed IP address or on a system that
cannot switch from one IP address to another by a simple reboot. Since C•CURE Go has no way of knowing that
the IP address has changed, it cannot distinguish a server IP address change from the service on the server
stopping or the server being shut down.

IIS version prerequisite for C•CURE Go Install

An error is displayed on the C•CURE Go Web Service installation screen, not on the final prerequisite review
screen, if the IIS version for the C•CURE Go Web Service is incorrect.

Installing Language Pack for C•CURE Go and C•CURE 9000 Web Client
Install C•CURE Go Web Service and the C•CURE 9000 web-based client on a machine with C•CURE 9000
client and the C•CURE language pack to ensure that C•CURE Go and C•CURE 9000 web-based client are
translated.
17
C•CURE Go Web Service installation not supported on MAS
C•CURE 9000 MAS systems running as IIS servers are not licensed for, and do not support, C•CURE Go Web
Service.

End of release note

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 Johnson Controls 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 Johnson Controls 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.

© 2024 Johnson Controls. All Rights Reserved.

18