Issue After installing a new Stand Alone Continuum system or upgrading it to use SQL Server 2005 Express (SQL Express) it is found that the ExtendedLog table is not being purged. (truncate delete purge) The tables fill up, resulting in a large Continuum database that can cause the system to slow down as it reaches its 4GB limit. Product Line Andover Continuum Environment Continuum Stand Alone v1.82 and above. Continuum Stand Alone system that has been upgraded from v1.81 or below. SQL Server 2005 Express Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Before Continuum v1.81, our Database engine for Continuum was MSDE. It used SQL Server Agent service to run maintenance tasks on the ContinuumDB. SQL Server 2005 Express does not have this SQL Server Agent and the scheduled maintenance tasks are added as Windows scheduled tasks during the creation of a new Continuum Database. "SQL Agent is a SQL Server service that is used to automatically schedule job execution for SQL Server. It is typically used to schedule the execution of DTS packages or to perform system maintenance tasks like database backups. While MSDE includes the SQL Agent service, SQL Server 2005 Express does not. However, you can use the Windows built-in Task Scheduler to schedule jobs for SQL Server 2005 Express. You can use Task Scheduler in combination with the downloadable DTS runtime to automatically schedule the execution of DTS packages. Likewise, you can use Task Scheduler in combination with the SQL Server 2005 Express command-line SQLCMD tool to regularly execute SQL Server 2005 Express system maintenance jobs like database backups and other database access jobs." See full article on this at http://technet.microsoft.com/en-us/library/cc966393.aspx The key here is that the scheduled tasks are added during the creation of a new Continuum Database. When upgrading Continuum you would typically install overtop the existing installation; upgrading your existing Continuum Database, which does not create the Windows scheduled tasks required to schedule events tables and ExtendedLog table to be truncated on a regular basis. Resolution Check Purge interval First thing to do is to confirm that your Extended Log Purge Interval has actually been set properly, by default this is set to 0 which disables automatic purging. Right-click your Continuum icon and select General Preferences. On line 10 - Extended Log Purge Interval, set this to the number of days you want to keep in your database. (typically 30 days) Once this is set, the next time the scheduled task runs it will truncate your table back to the number of days you have selected. If this was not set properly this may be all that is required. If it still does not purge and tasks have not been created then continue on with the below steps. Creating Scheduled Truncation Tasks Create a new Continuum database, at the end of this creation after closing the Database Initialization window, the scheduled tasks are created under Start -> Accessories -> System Tools -> Scheduled tasks. To create these scheduled tasks and associated scripts you will need to delete the DB, create a new one, and then restore your backed up database overtop. To do this follow the below steps: Shut down all Continuum Cyberstations. IMPORTANT: Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and, if not already installed, where to get Management Studio from) Use SQL Management Studio Express and logon with the SA account. Browse to the Databases folder, right-click the ContinuumDB and select Delete. This will delete the ContinuumDB from the server and the associated .Mdf and .Ldf files from the harddrive. Open up Database Initialization. Select Stand Alone. Click on the Create New database radio button (bottom right) which opens up the needed fields. Confirm the Database name is ContinuumDB. Ensure the User Login ID is set to Andover97. Ensure the User Password is set to (not disclosed due to public access). Ensure the path is correct for the DB File location. Enter in the SQL Server's SA password. Enter the Windows username and password that has local administrator privileges. (IMPORTANT: Make sure that your Windows user has a valid username and password; the scheduled tasks will not be created if the Windows user does not have a password) Click Continue (This creates the two files ContinuumDev.mdf and ContinuumLog.ldf in the DB File Location) Click Close to close Database Initialization, this is the point at which the scheduled tasks and associated scripts are automatically created. Using SQL Management Studio, now restore the backed up database. Restore the backup over the top of the ContinuumDB on your new system: Right click on ContinuumDB -> Tasks -> Restore -> Database. Select "From device:" and add your Database file, making sure to tick the Restore checkbox to select the source. Next, go to the Options page and select "Overwrite the existing database" and press the "OK" button. Change the db owner with the below query using the sp_changedbowner stored procedure. Select "New Query" and copy the query text shown below. Run the query. use ContinuumDB go sp_changedbowner 'Andover97' go Now confirm that your Extended Log Purge Interval is set properly, by default this is set to 0 which disables automatic purging. Right-click your Continuum icon and select General Preferences. On line 10 - Extended Log Purge Interval, set this to the number of days you want to keep in your database. (typically 30 days) Once this is set, the next time the scheduled task runs it will truncate your table back to the number of days you have selected.

Issue How to combine multiple Continuum DBs into one DB Product Line Andover Continuum Environment Continuum Cyberstation Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause Multiple Continuum site databases need to be combined into a single site database Resolution Guideline for combining Multiple sites to one Database Executing this procedure requires a technician who thoroughly understands Continuum and how it works with SQL Server. This procedure does not encompass BACnet controllers. There is a multitude of decisions related to efficiencies and site preferences that are not documented here. The following procedure is intended for use as a guideline for combining multiple databases. This work must be done offline on a development database and validated on a test bench before Note:Before proceeding with this procedure you must do the following. Backup the Continuum database in SQL. Backup all the files and folder structure under New Graphic Files. Note that these files may be on the SQL Server or elsewhere on a mapped drive. Back all Cyberstation Profiles. Steps 1 – 11 must be done before any of the site exports are done. Preparation All sites must have the same revision software and CX firmware. NO EXCEPTIONS! Make sure that all the Alarm Enrollments and Event Notifications have unique names between all sites as these will wind up together in a single database. Make sure that all the Graphics in the Root directory have unique names between all sites. Make sure each Schedules in the Root directory has a unique name across all sites. Make sure each Custom ListViews in the Root directory has a unique name across all sites. Make sure each Groups in the Root directory has a unique name across all sites. Make sure each Reports in the Root directory has a unique name across all sites. Once steps 1-5 are completed, export each class in the root individually. Import files from step 6 into the new site The Local Site name on all the sites that will be combined must be named LocalSite. All workstations must have unique names and ACC IDs between the sites. All CX, ACX and BCX controllers must have unique names and ACC IDs between the sites. Note: The safest way to do steps 9 & 10 is to create a new controller in offline mode with the changed ID, then drag and drop copy from the original controller to the new controller. Panels, reports, and programs then must be edited to bind to the new controller. Another way to merge the panel, reports, and programs that are in the root is to copy all the panels, programs, and reports to their corresponding controller then export the controller. Doing this will keep all the bindings linked. Then once the controller is imported into the merged database they can be copied back up to the root. All Commports on all controllers and workstations must be named Comm1, Comm2, etc… Each site must have the default “ACC” user and password. All graphic files (.pin) under the New Graphic Files folder must have unique names between the sites. Merging the databases Install a standard multi-user Continuum system being sure to size the database big enough to accept all the other databases combined into one database.  After a clean installation is done, shut down the new workstation and the SQL server. Copy the empty database files to an area where they won’t get corrupted. Do a complete site export from each of the sites that will be combined. Back up all the Graphic files (.Pin) files from the site so that they can be transferred to the new server. Copy all the backed up Graphic files (.Pin) from each site onto a New Graphics Files folder in the location of choice. Note these files can reside on the SQL server or elsewhere on a mapped drive. Import each of the site text exports from the old systems into the new system. After each import check to make sure that each import went cleanly. Check all the Graphics, Programs, Alarm Enrollments, and Event Notifications to make sure that all the links were made during the import process.

Issue After upgrading, it now asks for the security key when launching Continuum. Product Line Andover Continuum Environment Continuum Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Continuum stand-alone is not working in Demo mode after upgrading. Resolution Completely uninstall Continuum and re-install using the following steps. Warning: Incorrectly editing the registry may severely damage your system. At the very least, you should back up your current settings and any valued data on the computer before making changes to the registry. Go to Control Panel > Add or Remove Programs. Remove Continuum. Reboot the PC. Remove EPI Builder Run-Time. Reboot the PC. Remove Sentinel System Driver Installer if installed. Reboot the PC. Remove the Continuum entries in the registry using Regedit. Start > Run > regedit Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Andover Controls. Select the "Andover Controls" key, right-click and select "Export" to backup the reg key. Select the "Andover Controls" key, right-click and select "Delete" to delete the reg key. Reboot PC. Install Continuum without a security key attached to the PC.  You should now be able to start Continuum in stand-alone demo mode.

Issue Software installation problems with Windows 7 OS and above Configuration problems also known as UAC / User Account Control These problems occur when you receive an error message stating that you do not have the correct administrative rights to continue. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows 7 Windows 8 8.1 Windows 10 Server 2012 Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Windows 7 and above user administrator privilege settings (UAC) Resolution The solution to this issue is to turn off the user admin settings before the software is installed by following these instructions: Go to Start > Control Panel. Set the view to "small icons" to show all Control Panel icons Click on "User Accounts." Make sure that the account used for installing the software is a full admin user. On this page, click on "Change User Account Control settings", a slider bar that starts with "Never notify" up to "Always notify" by default will be set to "Notify me only when programs try to make changes to my computer" Set it to "Never notify." This will disable all the admin blocks that pop up in installing and configuring software Once set, restart the PC and then continue with your software installation and configuration Once all is installed and working, the feature may be turned back on if required. Additional requirements for Windows server 2012 and Windows 10. Please note: this process may open the "Windows 10 Firewall up" For Windows Server 2012 and Windows 10, additional steps are required to disable User Account Control. Although the slider bar can be set to “Never Notify”, the User Account Control does not disable completely. The User Account Control can be disabled for any user by setting the system registry value “EnableLUA” to zero in the system registry under the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”. A Windows registration file has been included in the Continuum 2.01 release in order to expedite these additional steps. Or the attached file EnableLUA.zip can be used, unzip and execute.  Supplement: Using the right click "run as administrator" instead of this is not the same. The right click will only run that .exe as an administrator and not the whole install/configuration package, i.e. SQL2005 manager will fail to run if you do not do as instructed above. You will always get an error stating that you do not have permission to run this program.  Alternate Windows 10 Admin. to User privilege for I/Net Seven:   Go to this path: C:\Program Files (x86)\ Inet Seven 1) Rename and move to a new folder these files.       A) INetIoSrv.exe.manifest       B) INetW.exe.manifest       C) If there is a file equalization client, then there is INetEqzMerge.exe.manifest to do this change on as well.  2) Change the DbCreate by doing this:       Another problem for non-admin users will be logging into and using DbCreate. A work-around for that would be to create a new login into the SQL database that could be shared among all DbCreate users and would provide the necessary rights.       Alternate Windows 7 Admin to User privilege for I/Net Seven:  See the attached Document and Manifest Files  

Issue Getting error inserting a row in the database when refreshing a personnel template. Product Line Andover Continuum Environment CyberStation Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause AreaLink table contains NULL instead of zero in the ClearanceLevel column. Resolution WARNING: Unless knowing exactly what you are doing, deleting entries from your database can cause irreversible harm to your database and can potential cause corruption. Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and if not already installed, where to get Management Studio from) Run the following query: Update AreaLink Set ClearanceLevel = 0 where ClearanceLevel is null

Issue How to install / add WebClient to existing SU installation of Continuum. Environment Continuum WebClient Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Existing Continuum SU Cyberstation installed and site is being upgraded with WebClient support. Resolution Perform the following steps to install WebClient on your Single-User installation. Backup the ContinuumDB, Graphics files, and Menus to a safe location. (For detailed steps on how to backup / restore your ContinuumDB see here.) Upgrade security key to allow WebClient. (from supplied serialized upgrade code from Repairs) Uninstall Continuum. Install WebClient from scratch following the Planning and Installation Guide. (IIS then WebClient) Restore your ContinuumDB, graphics files and Menus. Test

Issue There may be cases when the personnel distribution table in the ContinuumDB becomes corrupted and must be truncated. Product Line Andover Continuum Environment CyberStation Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Table corruption issues. Resolution WARNING: Unless knowing exactly what you are doing, deleting entries from your database can cause irreversible harm to your database and can potential cause corruption. Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and if not already installed, where to get Management Studio from) Should an issue arise in Continuum that requires a cleanup of the PersonnelDistribution table in the Continuum database follow this procedure to truncate the table and re-populate it. Make a backup of the Continuum database as a precaution. Close ALL CyberStation workstations. In SQL Management Studio execute the following query. truncate table PersonnelDistribution Once the table is truncated it must be re-populated by one of the following methods... If the total number of personnel objects is reasonably small (in the hundreds) launch Continuum and bring a list view of all the personnel objects, select all then right click and perform a 'Send to controller' OR In SQL Management Studio Invoke the stored SQL procedure that initializes the PersonnelDistribution table using the query dt_DIST_Init_Personnel_Dist_Table IMPORTANT: Truncating the PersonnelDistribution table will remove all pending personnel distribution including personnel deletions; controllers could potentially continue to allow access to doors for the deleted personnel until reloaded. Conversely, removing a pending personnel distribution could potentially cause a person to be denied access at a door until a distribution is performed to the controller.

Issue In some situations, when doing a learn on the CX/BCX controller, the learn process aborts and an error prompt pops up, "Can not learn this controller, it contains an unknown model number." Product Line Andover Continuum Environment Cyberstation CX/BCX I2/B3 Warning COMPLEX PROCEDURE REQUIRED.The resolution of this article has many complex steps that may result in unforeseen results if not performed correctly. If you are at all unfamiliar with the requirements, please contact Product Support Services for assistance. Cause Learn process has been executed more than once and at least one has not completed. Some controllers that reside in the CX/BCX have not been cleared and have a duplicate infinetID with some controller in the database. Reloading the CX/BCX controller will indicate which controller has the duplicate InfinetID. Resolution It is recommended to create I2/B3 controllers manually (not by learn) to avoid this problem. If this problem happens: Open the BCX/CX controller and click "reset" Reload BCX/CX controller, from the distribution properties window to find out which controller has the duplicated InfinetID Go to the Continuum Explorer, right click the i2/B3 controller which has the duplicated InfinetID and then select "send to text file" Open the text file, change the infinetID for this controller to another number that does not exist in the database. Delete the i2/B3 controller which has the duplicated ID and import the text file. Reload the CX/BCX controller, there will be no more error. Do learn again on the commport of BCX/CX controller, that should execute successfully. For any other installation issues that also result in this error, please refer to Unknown model number error when learning I2/b3 device

Issue How can duplicate Handle errors be fixed? Product Line Andover Continuum Environment All versions of Continuum CX, i2 and infinet Controllers Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause An SQL database gives every object a unique handle that is used internally to reference that object. If Continuum requests a value from an Input point that has handle 1234, but that controller has handle 1234 for example as a TimeDate point, then problems will ensue. Every object in the DB has a unique handle. This includes all classes: points, programs, graphics, reports, schedules, etc. Duplicate handles can be caused on sites where engineers use multiple databases during commissioning on new panels (maybe a Single User on their laptop), It can also be caused by importing dump files with handles created from other databases, or just from database corruption on the server from failures etc. It can also be caused by the use of an Infinity LSX280 see Handle mismatch issues. Resolution Usually reloading the controller will re-sync the controller and all of its object handles back to the site database. If the DB has become corrupted, run the analyzer and try to fixup (Clean) any issues You may even have to manually delete the offending objects, running the Import Export Fixup utility (See How to run the Import/Export Fixup Utility) Follow this with a controller reload Worst case would be to revert to a backup DB if it is found to be corrupt. To avoid issues altogether, it is best to engineer a project all from a single DB and take care when importing dump files.

Issue Large data base log file causes Continuum to run very slow and/or crash. Environment SU CyberStation MS SQL Express Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause When Continuum starts and attempts to connect to the DB it takes too long due to the size of the log file (14GB in the case covered by this article) Resolution Shrink the database. Go to http://technet.microsoft.com/en-us/library/ms190757.aspx for steps from Microsoft to shrink the database files.

Issue How to setup automatic table truncation on Single-User SQL Express systems. Product Line Andover Continuum Environment Continuum Cyberstation Single-User SQL Express SQL Server 2005 Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Only the ExtendedLog table is automatically truncated on an Single-User SQL Express Continuum system. The other tables that can fill up quickly and need to be truncated regularly are not catered for (accessevent, activityevent, alarmevent, and errorevent). Resolution IMPORTANT: Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and, if not already installed, where to get Management Studio from) Use the attached file SQLExpress to add table truncations.zip, to configure your Single-User SQL Express system to automatically truncate these tables when it does the ExtendedLog truncation. After downloading the file, follow the steps below. There are three files in the archive, these need to be copied to your Continuum folder on your Single-User system running SQLExpress as the database engine. LogTruncate.SQL This file is the SQL script that performs the truncation of the four tables (accessevent, activityevent, alarmevent, and errorevent) to the number of days you specify - I have selected 90 days as my default but you can change this to whatever you require for each table. CS_LogTruncate_OneOff.bat This batch file will run the LogTruncate.sql script once when manually executed. You will need to change the server name "PC3" to whatever your PC's name actually is on your system. CS_Hrly - with LogTruncat.bat This is the batch file that will be renamed and replace the existing "CS_Hrly.bat" file currently located in your Continuum folder. This is the same as your current file except it has added the LogTruncate.sql script so that this will now be executed every hour along with the rest. Backup "CS_Hrly.bat" file in Continuum folder by renaming the file to something like "CS_Hrly ORIGINAL.bat". Rename "CS_Hrly - with LogTruncat.bat" to "CS_Hrly.bat", copy into (overtop the existing file if you haven't renamed it) the Continuum folder, and change the server name "PC3" to your PC's name. This should now execute this table truncation script along with the other database maintenance scripts every hour.

Issue After time settings have been confirmed as per "The time on the workstation is less than the time of one or more controller log entries"., some ExtendedLog points are not being gathered. The below time synchronization errors are seen in the Errors Listview. Extended logging time synchronization problem. The time on the workstation is less than the time of one or more controller log entries. Product Line Andover Continuum Environment Continuum Cyberstation Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Due to the incorrect time settings previously configured, the controllers may have log events that occur in the future (as far as the Workstation gathering the logs is concerned). Resolution Reload the controller that has the ExtendedLog points showing this error, this will clear out the local log entries and allow the Workstation to gather new log entries.

Issue Procedure for converting a bCX9640 to a CX9680 (NC2) Product Line Andover Continuum Environment CyberStation bCX9640 CX9680 (NC2) Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Documentation Resolution This article provides some guidelines for converting a bCX9640 to a CX9680 in the field. As of version 1.94 CyberStation does not automatically convert a bCX9640 to a CX9680, such conversion while complex and error prone can be done manually.   DISCLAIMER: Be aware that due to the differences between the two models not everything can be converted; certain items may have to be re-created from scratch in the new CX9680 controller. DIFFERENCES BETWEEN BCX9640 AND CX9680   Feature bCX9640 CX9680 1 System Variables 47 65 2 Comm Ports 2 4 3 IO Expansion Modules IOU Modules 4 Infinet 1 2 5 Access Control No Yes 6 UPS Support No Yes 7 Display Module Support Yes No   Procedure: Make sure you have a recent backup of the SQL ContinuumDB as a precaution. From CyberStation send the bCX including children to a text file, the dump file can be later used for reference. Take note of the bCX9640’s name, AccNetID and network settings. Put the CyberStation in offline edit mode and delete the bCX9640 then create the CX9680 using the exact Name, ACCNetId and network settings as the deleted bCX. After creating the new controller object it will come online, at this point you are still communicating with the bCX9640 hardware. In the ‘Send to Database’ options make sure to select ‘Save attached objects and controllers’ then select the new controller in the Continuum explorer and perform a ‘Sent to database’, depending on how many Infinet devices you have this make take a while. When the send to database operation has completed you are ready to remove the bCX9680 hardware and connect the CX9680 hardware. After disconnecting the bCX from the network commission the CX9680 hardware with the same AccNetID and network settings as the bCX it is replacing. When the new hardware comes online reload it from Continuum making sure you don’t reload the Infinet devices (Reload attached objects but not attached controllers)   At this point you have converted the bCX9640 to a CX9680, the next steps in the process is fixing the items that do not convert properly due to the differences between the two controllers. LCD Display Configuration If the bCX has an display module attached all configuration related to the display module must be removed as the CX9680 does not support it. Fixing IO If the bCX had IO then appropriate IOU modules must be configured in the CX9680. In some cases points may have to be moved to a different IOU. For example if you were using a xPBD4 (which has both inputs and outputs) then you’ll have to put the inputs and outputs on different IOU modules as there is not an IOU module that is the equivalent of the xPBD4. Fixing References Any references in programs/functions to objects that do not exist in the CX9680 must be manually removed/fixed. For example the CX9680 does not have some system variables supported in the bCX such as all the system variables related to the display module (ACCLCDBeeper etc) Other items that need partial or complete manual fixing include… Alarms, links will convert ok, but references to Graphics, Program, Video may be have to be re-assigned. Extended logging   Use the dump file created on step #2 for reference when manually re-entering lost configuration.   Article as a document: Procedure For Converting a bCX9640 to a CX9680

Issue Active Event Viewer contents and column headers are blank.   Product Line Andover Continuum Environment CyberStation Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Windows registry corruption. Resolution Method #1 Close Continuum and use Windows System Restore to put the system back at a point where the Event Viewer were fine. Method #2 NOTE: Any customization previously done to the event viewers such as column name changes etc  will be lost when this method is used Shut down CyberStation then backup the Windows registry as a precaution Edit the Windows registry and delete HKEY_CURRENT_USER\Software\Andover Controls\Continuum\Access Event View Start CyberStation and open the event viewer which recreates the entry in the registry using default values.

Issue Time synchronisation is often an issue on large BMS installations. A central time signal is normally required to make sure all controllers, terminals or workstations have the correct time. If there is no internet connection available then the time has to be synchronised from a central source. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Sigma Continuum Vista SmartStruxure Windows XP Windows 7 Server 2003 Server 2008 R2 Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause No internet connection available to synchronise the system time. Resolution Important The methods below contain steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. If using Windows XP, please use the following link - http://support.microsoft.com/kb/314054 If using Server or Windows 7 OS, please use the following link - http://support.microsoft.com/kb/816042 This has been tested for Time updates to an AS by simply using the PC IP address as the primary NTP Time Server. If the firewall is turned on you also need to make sure UDP 123 is open. Please note that Windows will add a dispersion to the time that may cause issues with time synchronization, please see Automation Servers ignore time sync message sent from Windows NTP server that uses local internal clock for details.

Issue Access Event Viewer running in a CyberStation other than the primary access server works initially but after some period of time stops displaying access events. Product Line Andover Continuum Environment CyberStation MSMQ Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Product support has identified several scenarios that can result in Cyberstations other than the primary not showing events in the Live Event Viewer. The commonality with all these cases is that the Primary Access Server(PAS) will always show the events, so before using any of the solutions specified below make sure that is ONLY workstations other than the PAS that are not displaying events in their Live Event Viewer   NOTE also, that we are referring strictly to the Live Event Viewer in this article so it is assumed events are showing in a list view including the Access Events tab that shows events in the door's editor.   CAUSE #1 (Primary failed over to Secondary then back to Primary) In systems configured with a Primary and secondary Access Server (SAS), it has been found that after a failover to the SAS due to the PAS going offline, event viewers in other workstations continue to show events UNTIL the PAS WS returns online and resumes its role of PAS at which point all workstations (other than the PAS) stop displaying events in their Live Event Viewers.   CAUSE #2 (MSMQ issue reported and fixed by Microsoft) Continuum running under MS Windows 7, Vista or MS Windows Server 2008 (including R2) Access event viewers at Cyberstations other than the PAS do not show events. Alarms acknowledged at one CyberStation would remain unacknowledged in the other CyberStations.  Please see MSMQ issue causes Alarms and Access Event delivery problems between CyberStations for more information.   ISSUE #3 MSMQ CleanupInterval setting is too short. Resolution SOLUTION #1 First, make sure the ControllerStatus notification object is configured to send the offline alarm to all the Workstations in question. Second, put a PE program in the SAS to serve as a monitor to let the Live Event Viewer know when the PAS has returned online, this is accomplished by referencing an object from the PAS  SAMPLE PE POGRAM SOLUTION #2  (MSMQ issue reported and fixed by Microsoft) Click MSMQ issue causes Alarms and Access Event delivery problems between CyberStations for more information.   SOLUTION #3 In the Windows registry add the key \SOFTWARE\Microsoft\MSMQ\Parameters\CleanupInterval The recommended setting is 3600000 which is the number of milliseconds in an hour   For additional information about the CleanupIntervalKey, see the following article from Microsoft: http://msdn.microsoft.com/en-us/library/ms703235(VS.85).aspx

Issue Sample programs for carpark access control. Environment Continuum Access Control Carpark Access Carspace Counting Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause Want sample code on how to provide Carpark Access Control. Resolution It is possible to do car park control with Continuum Controllers. There are a number of different ways to do this depending on the sites specific requirements. PSS doesn't provide programming for specific projects but we can provide generic examples. *** Note: This sample code is provided as-is to be used as a sample only.   *** To start off, a very simple solution could be:   To have three Areas defined, Outside, CommonCarPark, and EmployeeCarpark. You then create Door objects for the Entry Readers at the entrance to CommonCarPark and EmployeeCarpark. Use a PE Program to Monitor the CommonEntry Entry Reader for ValidAccess and set a pre-alarm flag (Numeric). Have an AlarmEnrollment attached to the pre-alarm flag and set for a specific amount of time (3 minutes). Have another PE Program that monitors the EmployeeEntry Entry Reader for ValidAccess and then re-sets the pre-alarm flag stopping the alarm from being sent. You could use this sample program, with some modifications, to provide you with this functionality. This is a very simple way of doing it that doesn't take into account having more than one car coming in at the same time though...you could expand on this to include using arrays to store the details of the Personnel that have badged and then have a timer associated with that specific Personnel, set both values into an Array and then have another program monitor that Array and compare the time they entered against the current time...if the difference was more than your alarm time then raise an alarm. When that Personnel badges at the EmployeeEntry Reader you remove their entry from the Array. A sample on how to do this is here. This one is a bit more complex than the previous example but it should give some ideas to start with to mold into a solution. There is a WS program as well as a controller program. The controller program does all of the carpark control which uses arrays to store the number of car spaces currently available for each department group (company/tenant) and allows of disallows new cars from that dept depending on available slots. This solution required both a roller door and a gate inside the roller door to create a "mantrap" for the desired control but the same principle could be applied in a simpler design. The WS program was used to provide a solution to the tenants locking themselves out of the carpark when they didn't badge out properly. It uses an object to search though all Personnel to find a specific card number and then resets that Personnel's current Area so they can badge at the anti-passback enabled Door. From memory, this part of it didn't work as well as the carpark access. The code is good just the method of searching through all Personnel was prone to locking up. Depending on the number of Personnel and size of Database it can take a longtime to do the search ... and the program can time out and go to disabled. So there was human intervention needed at various times.  

Issue Workstations are no longer logging all points configured for Extended Logging. Lots of these errors seen in the Errors Listview and ACCtrace. "Unable to find Extended Log records to download. This can occur when a log is added to a point through offline editing and the change is never sent to the controller." Product Line Andover Continuum Environment Continuum Cyberstation SQL Server Management Studio Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause What has probably occurred is that in the database the point is set for extended logging but in the controller this same value is not set. It happens when the controller recovers from flash and the database stored in flash didn't have the extended log points configured or it was offline edited. This could also be due to a corrupt entry in the ExtendedLogReservation table that is stopping new points from being assigned. Resolution After the troubleshooting steps in Getting error Unable to find Extended Log records to download have been followed but were unable to resolve the problem, truncating the ExtendedLogReservation table and then rebuilding it did resolve the problem in a number of situations. Please note that this is a brute force approach that requires truncating a table using an SQL query. I want to stress that even after following the below steps to re-enable logging, each affected controller should be reloaded at some point to ensure that it has the most recent up to date information. The steps below are a quicker method of getting the logging start working right away without having to wait to reload each individual controller. The best method to disable and then re-enable the Extended Logging on the points that have it configured is to use individual Listviews filtered to show them. One of Numerics, Inputs, and Outputs. The only change required, and this is a critical one, is to change the "Live Data Refresh Rate" to 0 for each of those three Listviews. This will ensure that the view is not refreshed automatically unless we do this ourselves. See image below for details. After importing the three ListViews, follow the below steps to toggle the ExtLogEnable values for all Numerics that were currently setup to trend. Run the imported listviews, Export the results to CSV files, (do this as a backup so there is a record of what points are currently configured). Edit the listviews to disable live refresh, see attached image for exact details of what to change. [** Important **] Shut down all Cyberstations and backup the ContinuumDB. Go back and confirm that step 4 above has been done. Truncate the entire ExtendedLogReservation table and rebuild it. In SQL Management Studio, run the below query to truncate the table. truncate table ContinuumDB.dbo.ExtendedLogReservation   Start up the Cyberstation Set Workstation to Offline (workstation icon in task tray) Run each of the three Listviews, select Edit->select all, select Edit-> set attribute, set the ExtLogEnable attribute to False, Wait for the changes to take effect on all, you can see when this is done (and it may take awhile) by the tasks in the Distribution Properties window. Then select all again and set the attribute back to True, wait for this to complete. Now when you start up the Workstations you should see that the ExtendedLogReservation table gets populated and slowly start to see that some of the Workstations get assigned logs to start logging. You can see which entries are assigned to a Workstation by the value of ReservingWSLo. This will be set to 0 if no Workstation has been assigned to gather the point yet or it will assigned to the IdLo value of the Workstation that has picked it up.  

Issue Unable to enable or disable Enhanced Alarm Logging or Enhanced Alarm Delivery flags in Database Initialization. The Enhanced Alarm Logging flag goes back to what it was set to before making the change and the Enhanced Alarm Delivery flag is greyed out and uneditable. Product Line Andover Continuum Environment Continuum Database Initialization Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause The owner of the ContinuumDB is set to something other than the default andover97. In this specific case it was set to SA. The SA user was unable to write these changes to the database hence why the settings kept reverting back. To compound the issue it was found that an andover97 user had been created under the Security folder in the ContinuumDB, this then blocked attempts to change the owner to the correct andover97 user. Resolution Backup the ContinuumDB before making any changes. See Move / Backup / Restore a database on a Single User SQL2005 Express system. Attempt to change the db owner with the below query using the sp_changedbowner stored procedure. Select "New Query" and copy the query text shown below. Run the query. USE [ContinuumDB] GO sp_changedbowner 'andover97' GO If this produces an error "The proposed new database owner is already a user or aliased in the database" then see Unable to change the ContinuumDB database owner using the stored procedure sp_changedbowner for instructions on how to drop the incorrect user so we can use the correct one. After successfully dropping the user from the ContinuumDB, re-run the query in step 2 above to change the database owner to andover97.   After successfully setting andover97 to the database owner you should now be able to toggle the Enhanced Alarm Logging and Enhanced Alarm Delivery options in Database Initialization. If you want these enabled; toggle them both off, update the database, toggle them both on, update the database again. This will ensure they have been enabled properly. Note: The definitive check to see if the Enhanced Alarm logging and Enhanced alarm delivery are both enabled is by checking the dbo.ACCDBVersion table in the SQL database using SQL Server Management Studio (or Express). New Alarm Logging and New Alarm Delivery should both be set to 1.

Issue 1. Cyberstation PC Windows Application Event Logs showing SQL errors about being unable to allocate space for each of the event tables. Similar to the below errors. Could not allocate space for object 'dbo.AlarmEvent'.'PK_AlarmEvent' in database 'ContinuumDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Could not allocate space for object 'dbo.ExtendedLogReservation'.'IDX_EXTENDEDLOGRESERVATION' in database 'ContinuumDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. 2. Controllers are online but unable to modify existing objects or create new ones. In addition; all events were not being logged to the database. This was seen by reviewing the AlarmEvent, ActivityEvent, AccessEvent, AlarmEvent, and ExtendedLog tables not having any new events being recorded at all. reviewing the distribution properties after performing tasks in Continuum showed no entries at all. Normally, user events initiated from the Workstation are shown in the distribution properties window as they occur. Product Line Andover Continuum Environment Continuum Cyberstation SQL Server Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Cause 1. One of the Database files is set to not grow with Autogrowth set to none. This stops any new data from being able to be entered into the database. One example of this is when the ContinuumDev file was modified by the end-user to inhibit its growth by changing this setting to none. Check all of the following databases files (both the DEV and LOG file) to ensure that they are all set to either autogrowth or to an adequate restricted value so that they are able to write new entries. ContinuumDB MSDB TempDB   2. The disk where the database resides does not have enough available disk space. Resolution 1. Change this database file growth setting to "by 10MB, unrestricted growth" or to an adequate restricted value. Use SQL Server Management Studio Express, see Move / Backup / Restore a database on a Single User SQL2005 Express system on where to get this if it is not already installed on your SQL Server. It is highly recommended to backup the ContinuumDB before attempting any changes to the database, steps on how to do this are in the above article. Start up SQL Server Management Studio, or in my example, Management Studio Express. Log in with your SQL SA password or windows administrator. Expand the server tree, expand the Databases tree. Right-click on ContinuumDB and select "Properties" from the menu; this will show the Database Properties window. Select the Files tab on the RH side of this window and you are now where you need to be to check the Autogrowth setting.   2. If the problem is due to disk out of space your options are; a) Make room on the disk, b) Shrink the ContinuumDB,  c) Install a larger disk in the machine.