Issue PE Programs cause Locks to go into "Inoperable Mode" Environment Continumm version 1.94 and above Cause Personlized PE Program causes the locks to go into an inoperable mode due to the constant polling of the PIM for lock status based on the program characteristics. Resolution To resolve this issue, please follow these steps: Do not use PE Programs to poll lock status it would minimize battery life Disable all PE Programs that are lock specific. Do not use PE Programs for Schlage Integration.

Issue Using PIN only for the Integration and it is not working. Environment Continuum Version 1.94 and above. Cause The X Driver has a limitation on how it functions with PIN only. Resolution To resolve this issue, DO NOT use PIN only as it is not supported by the X-Driver. If the PIN needs to be used then it must be Card and PIN.

Issue Is there any way to mass change any of the bCX / ACX / NC2 settings as configured from the controllers configuration webpage?  Environment ACX57x0 CX9680 bCX9640 bCX4040 CX9702 Cause Settings need to be changed en-mass for a large number of Controllers. In one particular case there were a large number of ACX57xx’s that needed to have the first and second SNMP alarm target PC's IP addresses changed for all controllers. Resolution There is no way to set all of these at once. As with all of the settings on the controller configuration webpage, they will need to be manually changed one at a time by connecting to each individual controllers configuration webpage.

Issue Unable to communicate with Assa Abloy  Hubs Environment Continuum Version 1.94 and above Cause The HUB being used is the wrong version and cannot communicate with the XDriver Resolution To resolve this issue, the following steps need to be observed: Verify that the correct XDriver is on the Continuum Panel Verify that the settings on the Comm Port is correct per the installation manual pg 7 Verify that the Global Config Numeric is set to 1001 Verify that the HUB does not have an M on it (this is for a Mercury Integration) Replace the HUB with a standard one and verify  that communication has been restored

Issue Email alarming is configured correctly but Continuum keeps crashing when alarms are sent as emails. ACCDataServices is the crashing module.   Windows Application log shows two email errors that point to an issue with Outlook. Email, Failed to send email - SendNote in Send function failed. Result is 80070057. Email, Failed to send email -  SubmitMessage failed in CSession::SendNote, Result is 80070057 Environment Continuum Alarming Outlook Cause Outlook account folder is too large and does not have available space for new entries. In this case the folder was 7GB in size with emails going back eight years. Resolution Archive Outlook account folder and truncate to free up space for new emails.  

Issue With the Personnel Import Utility, is it possible to query multiple OU containers? Product Line Andover Continuum Environment Personnel Import Utility (PIU) Cause Need to be able to query multiple OU containers. Similar to below query. Server Name: LDAP://test/DC=test, DC=com (test and com are separate domains) Resolution Unfortunately the query cannot be changed to accommodate this. Different Domains can be specified but it is not possible to go down to the OU level.

Issue Can the Personnel Import Utility update existing Personnel only and not create new Personnel objects if they do not already exist? Environment Personnel Import Utility PIU Cause Need to be able to only modify existing Personnel and not create new ones when performing Personnel import with the PIU. Resolution The way the PIU handles this, to modify existing Personnel or if none exists to create a new one, is "functions as designed". There is no way to stop a new Personnel object from being created when it is unique.

Issue BACnet Input shows "Out of Service". When attempting to set a value or remove the out of service flag an error is seen. "An attempt has been made to write to a BACnet property with a value that is outside the range of values defined for the property." Environment bCX4040 b3 Controllers Cause An xP Module attached to the Controller was malfunctioning and the inputs on this board were not functioning. Resolution Powering everything down, re-seating the xP Module board and powering the Controller back up resolved the problem.

Issue Sites need guidance on how to setup custom ABA cards in Continuum. Environment CyberStation NetController I (CX99xx) NetController II (CX9680) AC1Plus IOU Module ACX57xx Cause The implementation of ABA cards in Continuum access control systems was designed to comply with the ISO 7811 ABA standard for magnetic stripe card. Because of this, the system only reads  one field (the PAN or Primary Account Number) from the ABA card, this field contains a number of up to 19 digits which is used as the card number. Continuum Custom ABA feature provides for maximum flexibility by allowing the 19 digit PAN field on track 2 of the mag stripe to be organized in sub fields such as site code etc. Resolution A summary of the steps to configure Custom ABA cards in Continuum is available through the CyberStation Online Help.  Open the help on the Continuum workstation and search for "Defining a Custom ABA String Format"          

Issue Using a non-default SQL Server port with Continuum. Environment Continuum Workstation SQL Server Cause SQL Server has been changed from the default port setting and  confirgured with a specific static port for incoming SQL connections. Resolution Continuum doesn’t care if the SQL Server is using a default port or not. As long as the Database can be created/updated using the Database Initialization application it will work fine. This has not been tested or qualified but should work fine. After the port is changed, the user should perform the Database Update process to ensure that the connection can be made from Continuum to SQL Server and vice versa. Here’s a Microsoft article on how to change the SQL port. https://support.microsoft.com/en-us/help/823938/how-to-configure-sql-server-to-listen-on-a-specific-port

Issue When the Save statement is used to save objects in a BCX4040 to the database. Steps to reproduce problem: Create an InfinityString object (Test.Str) with a manual array size of 1 in a BCX4040. Create a program in the BCX that sets the value of Test.Str[1] to 'Success' From command line, print the value of Test.Str[1] while the workstation is in OnLine mode. The value should = 'Success' From command line, print the value of Test.Str[1] while the workstation is in Offline mode.  No value should be returned as the value has not been updated in the database. Create a fallthrough/autostart program in the workstation with the following code: FIRSTLINE: Save \TestNet\TestACX\Test.Str -0 Goto StopLine STOPLINE: Stop From command line, print the value of Test.Str[1] while the workstation is in Offline mode.  The value should now = 'Success'.  Expected result: The value returned for Test.Str when the workstation is in Offline mode (Database value) should 'equal the value returned when the workstation is in Online mode (Live Value), i.e. = Success' Actual result: The Offline value of Test.Str[1] does not change and does not equal the value live value. The resulting ACC_Dump_Debug that is produced is found to have no contents. Product Line Andover Continuum Environment Continuum  Plain English Cause The following Plain English code does not accomplish a Save to Database. FIRSTLINE: Save \TestNet\TestACX\Test.Str -0 Goto StopLine The functionality of the Save command is not to perform a "Save to Database" operation. This is a functioning as designed. The Save command, which is equivalent to the Dump command, dumps the contents of the passed-in arguments (i.e. objects) to a file if provided Resolution Workaround: When a manual Save to Database is done on the object, the database value is updated with the current Live value.

Issue After a missing or deleted default list view is re-created using the Continuum database initialization utility; the list view does not contain any columns. Environment Cyberstation Cause This issue is caused by a Continuum defect issue that cannot be corrected at this time. QC#2222. Resolution There are several workarounds that can be used to resolve this issue. 1)      Columns can be manually added back to the list views re-created by the database update option. 2)      The default list views can be reimported from the DefaultListViews.dmp file in the Continuum folder.  This would overwrite all default list views there by losing any customization to existing list views. 3)      Individual list views can be imported from a dump file created from another Continuum Systems to provide pinpointed recovery of certain listviews.

Issue After selecting a photo and trying to save it in the Image Enhancement screen, the error Invalid width/height -11 pops up.   Environment Cyberstation Cause This is caused by the resize box under the capture options being checked and the sizes being set to 0. Resolution This can be resolved by one of the following suggestions below:   Uncheck the resize box under the capture options Set the x: and y: options to something other than 0

Issue Personnel Manager not operating correctly but Personnel Editor is fine Product Line Andover Continuum Environment Seen in Continuum 1.94 Cause Personnel Manager seems to run correctly but the Area names, Assigned and Unassigned data does not show correctly and cannot be modified. Blank spaces at the end of the Area Names or Alias cause the Peronnel data (Assigned and Unassigned Areas) to show incorrectly in Personnel Manager, but all correct in Personnel Editor. Resolution Remove the spaces at the end of the Area Names and Aliases Restart Continuum

Issue On a cold start, the i2 or b3 controller does not retain the configuration stored in flash memory. The controller error log shows a 0x000014fb error.   12     E      01/01/1989 00:02:10.00     0x000014fb     0x0928ab00     0x019085a6    0x1442000c Product Line Andover Continuum Environment Continuum b3 Controller Continuum i2 Controller Cause i2 and b3 controllers must compile the controller configuration prior to backing the configuration up to flash memory.  An invalid configuration will prevent the compilation process from completing, thus preventing the backup process from succeeding.     The most common causes of OMS Backup failures are Plain English programs that contain errors. Input or Outputs that are configured without a channel number.   Resolution Correct any configuration errors.  Initiate a backup of the controller configuration to flash memory. Verify that the backup has been successful.  There should be no 0x000014fb  errors in the controller error log. 

Issue Easy Lobby is compatible with limited Continuum versions Product Line Andover Continuum Environment Continuum Cyberstation Cause The Easy Lobby integration is developed and supported by HID. There has been no further development for integration amongst other revisions. Resolution Easy Lobby is only compatible with Continuum version 1.94 SP1.

Issue Setting up a single user (SQLExpress 2005) v1.93 CyberStation and the SQL Service Manager is not popping up like it should (on the Windows taskbar). Environment Standalone CyberStation SQLExpress 2005 Cause Previous versions of CyberStation had a SQL Service Manager application in the Windows taskbar. When installing a standalone v1.93 CyberStation this application is not there. Resolution SQLExpress 2005 does not install that application. This application is not required to run CyberStation.  If for some reason there is a need to stop SQL Server there is a workaround. Go to Control Panel>>Administrative Tools>>Services. Then scroll down to SQL Server (SQLExpress). You can stop SQLExpress by right-clicking it.