How to Configure SSL for the C•CURE 9000 2.60 Web Client

C•CURE 9000 TAB Article ID: SWH-TAB-000001582 March 31, 2017 BACKGROUND When configuring SSL for the C•CURE 9000 2.60 Web Client, the following message may be displayed during initial setup and testing. This message is misleading because there is no certificate bound to port 443 (used for SSL). SOLUTION •      Open IIS Manager. •      Click on… Continue reading How to Configure SSL for the C•CURE 9000 2.60 Web Client

Badge Designer no Longer Works after Upgrade to C•CURE 9000 2.60

C•CURE 9000 TAB Article ID: SWH-TAB-000001560 BACKGROUND After upgrading to C•CURE 9000 2.60, when launching the Badge Designer (Personnel>Badge Layout), the following message appears “Could not load file or assembly ‘CCUREIDSetup, Version=3.0.0.0,…”. The CCUREIDDesign.exe file should be in both the \Badging and \CCURE Client folders. It is in the \Badging folder but not in the… Continue reading Badge Designer no Longer Works after Upgrade to C•CURE 9000 2.60

iSTAR Ultra Diagnostic Logs

C•CURE 9000 TAB Article ID: SWH-TAB-000001319 BACKGROUND This is the process on how to generate and download the diagnostic log files from an iSTAR Ultra panel. These logs are used to troubleshoot iSTAR Ultra GCM hardware and communication issues. IMPORTANT: Do not attempt to open or modify the file as this can corrupt the log… Continue reading iSTAR Ultra Diagnostic Logs

2.60 C•CURE 9000 Prerequisites Fail to Install

March 15, 2017 BACKGROUND Visual C++ 2017 installs version 14.10, which is considered an upgrade of C++ 2015 version 14.0. Microsoft did this with a new and separate installer. The C•CURE 9000 2.60 installation will fail if MS visual C++ 2017 is installed. Check the installDashboard.log file (located in %temp%). The following entries are verification… Continue reading 2.60 C•CURE 9000 Prerequisites Fail to Install

Upgrading or Installing C•CURE 9000 v2.30R2 may Fail on a System with Non-US Regional Settings

December 8, 2014 BACKGROUND Installing or upgrading to C•CURE 9000 v2.30R2 may fail when using non-US Regional Settings. In the failed upgrade/install “UnifiedServerInstall log” (located in %temp%), there will be an entry similar to  this near the end of the log: DEBUG: Error 2203: Database: D:\bin\bin\es\UnifiedServer.mst. Cannot open database file. System error -2147287037 1: 2203… Continue reading Upgrading or Installing C•CURE 9000 v2.30R2 may Fail on a System with Non-US Regional Settings

Upgrading from C•CURE 9000 v2.30 to v2.30 R2 with Language Pack

October 6, 2014 BACKGROUND If a 2.30 system with Language Pack installed is upgraded to 2.30 R2 in a manner inconsistent with the following upgrade steps, the localized resource files will be overwritten with English resource files. This will cause dynamic views, reports, and queries to be in English. The upgrade should be done in… Continue reading Upgrading from C•CURE 9000 v2.30 to v2.30 R2 with Language Pack

Upgrading to C•CURE 9000 2.50 will Require a New HostID

January 3, 2016 BACKGROUND Starting with C•CURE 9000 2.50, the algorithm that generates the HostID has been updated. As a result, upgrades from a previous version of C•CURE 9000 will require the HostID to be generated with the new version of the HostID Utility.   SOLUTION To avoid interruption with the C•CURE system: Log on… Continue reading Upgrading to C•CURE 9000 2.50 will Require a New HostID

Important Alert Regarding C•CURE Upgrades

March 3, 2016 BACKGROUND The upgrades below will remove files under the “Tyco/CrossFire” folder. The Tyco\CrossFire folder is the default name. Sites may have a different folder name. SOLUTION Before you upgrade, save the contents of the “Tyco\CrossFire” folder and its subfolders to a location outside the folder where C•CURE is installed for safe keeping.… Continue reading Important Alert Regarding C•CURE Upgrades

User-Defined Fields must exist for MAS Upgrade to Work

April, 2012 BACKGROUND: When trying to install an upgrade on the MAS from C•CURE version 2.0 or 2.01 in order to get the system upgraded to C•CURE version 2.02 R2, the system is giving this error message: SOLUTION: The workaround is to define a User-Defined Field (UDF) for both personnel & credential on the MAS:… Continue reading User-Defined Fields must exist for MAS Upgrade to Work

System Variable in C•CURE 9000 for Classic ACM Reset

April 1, 2015 BACKGROUND Early Classic ACMs were prone to “fall asleep” and stop communicating to the readers (both RM & Direct Connect) and I8/R8 boards that were connected to it. Hardware modifications were put into place to rectify the issue, however due to the many revisions of the early Classic ACMs, and the logistics… Continue reading System Variable in C•CURE 9000 for Classic ACM Reset