Issue When polling data from the Modbus IP and RTU X Drivers, how fast can data be retrieved? Product Line Andover Continuum Environment Modbus RTU, Modbus IP X-Drivers bCX1, Netcontroller II, ACX57xx Cause Polling data too fast particularly with the Modbus RTU XDriver can cause the controller Scan time to rapidly rise to excessive levels. Resolution The Modbus RTU X Driver can typically make 2 polls per second. These polls can be for single values or block reads. As this X Driver operates outside the regular controller scanning process, polling too many points or many points that are offline can cause the scan time to rapidly rise. Use a single Plain English program to schedule the polling of all points. See Helpful Modbus register Information for advice on how to handle offline devices. If 2 off Modbus RTU X Drivers are used on the same controller, then again use a single Plain English program to poll across both ports and do not exceed the recommended overall rate of 2 polls per second.  For the Modbus IP X Driver, only one port can be used to load this driver on any controller. It can typically make 8 polls per second for single or block reads. Also see What should be considered when analyzing the performance of a Modbus TCP/IP implementation?on analyzing the performance of the Modbus IP X Driver.  NOTE:  The ability to enable 2 comm ports using Xdrivers can be done, but is not recommended by the Xdriver developers nor supported by PSS. The RTU Xdriver is poll on demand. This type of driver can request a lot of data and starve the CPU on the controller which then makes the polling irregular. If 2 ports are being used then there are typically more devices being added and therefore more points increasing the requests and demand on the controller's CPU. Use one program to control the polling on both ports. Two programs attempting to control the polling asynchronously will cause communication issues.

Issue Error displayed: "Extended logging time synchronization problem. The time on the workstation is less than the time of one or more controller log entries," when Workstation tries to download ExtendedLog data from controllers. Product Line Andover Continuum Environment Continuum Workstation (LAN & SU) NetController (CX99xx , BCX9640, BCX4xxx, ACX57xx) InfinetController (i2xxx & First Generation InfinetControllers) Cause Time setting is different between Workstation and Controllers or the time setting is same but the UTC Offset (Time Zone) is wrongfully set between the WS and the Continuum Network object of the controller. Resolution Set the correct UTC offset (time zone) in all of the below locations: Confirm Cyberstation(s) PC time zone (UTC offset) and Windows regional settings are correct. Confirm the SQL Server PC time zone (GMT settings) and Windows regional settings are correct. In Continuum, the Workstations Device objects Time tab has the correct time zone setting (be aware this is in minutes, ex. GMT+10 = +600 minutes). In Continuum, the Network folder has a setting for the time zone, this needs to be configured to the time zone the controllers are located. If GMT+10 then this gets set to +600. Note: See Configure Time Zone and UTC Offset settings so that time is synchronized across your system for more detail on the various locations for UTC settings and what these are required for. Setup Workstation and Controller Time Synchronization: Synchronize the time on all Workstations to a common source. See instructions in Cyberstation Installation Guide under "Workstation Time Synchronization." Synchronize controller time by creating a Program in one of your Cyberstations (only create on one Cyber). This synchronizes the controllers time to the Workstations time once every hour. There are detailed instructions on this in the Cyberstation Installation Guide (with a sample program) under "Controller Time Synchronization." (Also see Time sync controllers to workstations)

Issue What card readers and technology can be used with Continuum Access Control Systems Product Line Andover Continuum Environment Continuum Cause Need to know what card readers will work with Continuum Access Control Systems Resolution The card reader and card technology is not relevant to the Continuum Controller, as this is used between the card (tag, fob or other) and the reader. This allows the use of the standard technologies available today, including fingerprint and other biometric based access as well as cards, fobs and tags. The signal that comes from the reader must be serial data input type Wiegand or ABA (or Clock & Data) USB, Ethernet, RS485, RS232 inputs are not accepted. NOTES The exact input type and maximum data bits can only be determined by checking the hardware, firmware and Continuum version combination being used. Retina, fingerprint, facial recognition and other biometric based systems that are connected to Continuum Access Controllers will store the biometric information and still be connected via the serial data Wiegand or ABA to the Continuum Controller. The current Continuum access controllers also accept an 8 bit burst for PIN numbers from keypads See Where can I find datasheets, install guides and other information on HID Electronic Access Control products? ABA (or Clock & Data) this was often used with Magnetic Swipe technology which has mostly been phased out Standard Wiegand Formats within Continuum Infinity 37-Bit AC 4+4 32-Bit Wiegand 26-Bit CK 34-Bit G 32-Bit HIDCorp1000 35-Bit - Some restrictions Custom

Issue When starting up the Continuum Workstation an error "SmartHeap library out of memory" error is displayed and Continuum does not startup. Product Line Andover Continuum Environment Continuum Cyberstation Microsoft Windows Cause The PC memory allocated for Cyberstation to use is insufficient for the application and the site's configuration. There are three known items that can require more memory to be required on Workstation startup. EventNotifications. If a very large number of them. The Workstation reads all of them and may require more memory at startup. Workstation Programs. Check in the Workstation for many or large Programs. Objects in the Root of Continuum. The startup of WS can be very long with a large number of objects in the Root. Resolution Verify that the PC being used for the workstation meets the minimum requirements as defined in the Install.pdf document for the specific Cyberstation version being used. If other applications are to be run on the PC then the RAM size should be increased accordingly. If the system StandAlone (Single User) 1.81 or before then verify the database size is below 2Gb, For Version 1.82 and above it can not exceed 4Gb. Verify that you have sufficient available memory you have when seeing the error, using task manager. If the above checks confirm that the basic PC memory is sufficient then the following changes can be made to allow the Cyberstation application further resources, this is often required when a number of Plain English programs are running in a Workstation. Shut down Continuum and set the Virtual Memory size Initial to 2048 and Maximum to 4096. Using Regedit go to the registry key HKEY_CURRENT_USER\Software\Andover Controls\Continuum\Settings and increase the setting for omscachesize to 5000 decimal. For systems where the Workstation is known to have an extremely heavy workload, this number may be increased up to 9000 in decimals. If using the Elevator Control Module add-on, it may be necessary to set the size to 5000. Note: For new Continuum or WebClient Workstations, the omscachesize registry key is not created until after the Workstation has first logged in at least once. If you are adding a Workstation to an existing LAN installation with a large ContinuumDB, then the omscachesize may need to be increased right from the start. One way to do this is to: Create  a new "test" database, see Creating a test database for troubleshooting for more information. Connect this Workstation to that test database so that the correct registry keys are created Change the omscachesize value as described above Restart the PC Reconnect to the original production database and start-up Continuum.

Issue Licenses for MS SQL Server 2008 are becoming difficult to source, is MS SQL Server 2012 going to be supported? Product Line Andover Continuum Environment Continuum Microsoft SQL Server 2008 Microsoft SQL Server 2012 Microsoft SQL Server 2014 Cause As retailers deplete their old stock, it will become harder and harder to obtain licensing for MS SQL Server 2008 which is the most recent version of MS SQL Server that Continuum v1.94 supports. Purchasing SQL Server 2012 licenses to downgrade deployment rights does not seem to be an option with current Microsoft licensing as this option only applies to volume licensing and not retail license packages. (Refer to page 16 of the Licensing Reference Guide from Microsoft here.) Resolution Continuum v1.94 was not qualified with MS SQL Server 2012 at the time of release, this has since been tested and qualified with Service Pack 1 for Continuum v1.94. Please see the Continuum Compatibility Matrix in Software and Firmware compatibility matrix for older versions of the traditional product lines for details of supported environments. To use Microsoft SQL Server 2012 you will need to upgrade your installation to Continuum v1.94 SP1 or higher. You will be able to use MS downgrade rights to downgrade an SQL 2014 license so that SQL 2012 can be installed. See references from Microsoft below. http://www.microsoft.com/licensing/about-licensing/briefs/downgrade-rights.aspx http://www.microsoft.com/licensing/about-licensing/sql2014.aspx For sites using Continuum v1.94 or older that do not wish to upgrade, downgrade deployment rights can be used with volume licenses of MS SQL Server 2012 to deploy an older version of SQL Server (say MS SQL Server 2008 R2 that is currently qualified with the version of Continuum you have). Note: Continuum v1.94 SP1 has been qualified with MS SQL 2012 (SP1) but has not been tested with SQL 2014.

Issue Extended log data not being saved to the database. Error stated that controller should be returned online and reloaded. Product Line Andover Continuum Environment Cyberstation SQL Extended log data Extended logging Error Troubleshooting logs Cause Error is generated indicating a mismatch between the Database and controller. But reloading the point does not always cure the problem. Resolution The error Unable to find Extended Log records to download states that it was added to the point when the controller was off-line. This can often be the case and the controller should be returned online and reloaded. However if this does not resolve the problem there are other extended logging issues that can cause this message: Ensure the system is set to be using Enhanced alarm logging and delivery if the system is V1.5 or above, it should have been configured (in the DB initialisation) to use this. See Alarm Forward and Log settings with enhanced alarm logging causes unnecessary network traffic. Run the Continuum analyser to ensure the database is not corrupt. Fix any issues and reload the controller. The controllers have not been fully reloaded. Ensure that a full reload including all attached controllers has been done and that this does not generate any errors. Ensure software and firmware is compatible for the version you are using, see Compatibility matrix. Also check Operating system versions and .Net versions are correct for the version used. Verify that you have set the same UTC times for the country in the Network, all Workstations and all BACnet controllers. Check that one Workstation has the time synchronisation program running to keep the CX's in sync' (Time sync controllers to workstations). Look at the Continuum error log to make sure you are not getting Extended log time synchronisation errors. Check for network problems; use the Controller offline alarm to verify no controllers go offline. Controller Network problems can stop the objects from saving to the controller which will cause a mismatch between the DB and controller requiring a reload. Ensure the Workstation IP address is a fixed address in the Windows settings and it matches the Workstation IP address in the database, as viewed in Offline Editing. Verify only 1 network card is fitted and enabled in the PC.  

Issue Do IP settings go to defaults when flashing from 4040 to 9640? Product Line Andover Continuum Environment bCX9640 bCX4040 Cause Have a need to flash a controller from bCX4040 to bCX9640 over a remote connection access. Do not want to have to go to the site to reset IP settings.  Resolution Using CyberStation v1.93 a bCX4040 was flashed to a bCX 9640 and it did NOT lose its IP info. Notes: At the end of the upgrade an error was received: “The uprev could not communicate with the specified controller”. From the webpage it was noted that the IP address had not changed and the upgrade was successful. It did not come back online in CyberStation. From the webpage, resetting it still did not bring it back online in CyberStation. Changing the model number in CyberStation to bCX9640 (from bCX4040) to bring it back online was not an option. The flash upgrade had reset the ACCNetID to 1. The 4040 was then deleted (Bacnet side first then Infinity side) and a new 9640 was created. The proper ACCNetID was set up in the webpage and the changes committed. It was then online in CyberStation. Bottom line – IP address never changed. ACCNetID did. The controller never had to be touched during this process so remotely doing this is expected to work. This was only tested using the latest firmware and CyberStation v1.93. Of course, the best way to do this is on the bench not on a live system. Please be aware that the model flash change will cause node count and/or xdriver upgrades to be reset if they were added as post-factory-shipment upgrades (via the Repair Dept) since these upgrade UPD files are model specific. See Node or XDriver Upgrade of BCX Inf (9640) to BCX BACnet (4040) or reverse. Also see Update b3 or i2 OS, changing (converting) a controller, BACnet to Infinet or Infinet to BACnet .

Issue A Door configured with Magstrike status as Door Status re-locks after 2s  even when Door Strike Time is set to 10s. Environment Continuum Access Control Cause The Door output will relock after the Door Strike Time or when the Door is opened. Since you are using the mag lock status as the Door status (not the preferred method), then as soon as the Door is unlocked, the mag lock is de-energized which turns off the Door Status which then relocks the Door 1s later. Resolution You need to monitor the actual physical status of the Door to indicate when it has physically opened and shut. Either that or remove the input from the Door object by setting the Door Status channel to 0. This should allow the Door to stay open the DoorStrikeTime. You can also use a PE program to get around not having a DoorStatus that monitors the actual Door. This post on the Community discusses this and has some good comments about using this type of Door control with the maglock status instead of a true Door Status switch and is worth a read. Below is an example Plain English program that can help monitor the Door for ValidAccess then hold the Door unlocked for the DoorStrikeTime. 1: If Door1 ValidAccess is On then Goto 2 If Door1 ExitRequest is On then Goto 2 2: Door1 = UnLocked If TS > Door1 DoorStrikeTime then Goto 3 ' wait for DoorStrikeTime 3: Door1 = Locked Goto 1

Issue Where to find Continuum SQL schema and table details so a 3rd party can have access to the database. Product Line Andover Continuum Environment Continuum Cause Third party requires access to the database Resolution It is not recommended that third party systems directly access to the Continuum SQL database as the Cyberstation software expects full access to all tables at all times. Should a table be locked or inaccessible to Cyberstation it may cause problems or runtime errors. We do not publish any details on the database tables or a SQL schema as Continuum is used for Security applications it would undermine the security of the product. Also the database does not contain live data, this should always be read directly from the controllers. There are other alternatives that can be used. Use an existing open protocol XDriver e.g. Modbus IP or other open protocol BACnet IP or MS/TP link to the 3rd party system or controllers, could also be linked to StruxureWare Building Operation Export the required data from a Listview, Group or Report for use by a 3rd Party Create a Plain English program to regularly export data to a .CSV or .TXT file, see Automatically export logged data to .CSV files Commission the development of a new Xdriver or other integration; contact UK Technical Services department for a bespoke solution, paul.bates@schneider-electric.com

Issue Continuum running under MS Windows 7, Vista or MS Windows Server 2008 (including R2) Access event viewers at workstations other than the primary access server do not show events. Alarms acknowledged at one CyberStation would remain unacknowledged in the other CyberStations.  Product Line Andover Continuum Environment CyberStation Microsoft Windows 7 Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Cause Problem in Microsoft MSMQ component. MSMQ service might not send or receive messages after you restart a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008. This will cause any Continuum component that uses MSMQ (such as Alarms and Access Events) to fail. Microsoft has issued a hot fix for this MSMQ problem. Resolution Use the following command prompt test to verify the problem netstat -ano | findstr 1801 The command tests whether MSMQ is listening for messages. For example, Continuum WS 'A' is the primary access server (PAS) with an Event Viewer 'EV' up,  a second Continuum WS 'B'  is also displaying the same EV. If MSMQ is functioning normally you should see the following. 1. is the IP address of WS 'B' that has established a link to WS 'A'  2. is the IP address of WS 'A', the PAS in this case. 2560 is the listening MSMQ process PID  You can clearly see that there is a MSMQ process (2560) in WS 'B' LISTENING on port 1801 If there is no MSMQ process listening the output of the command will show the loopback or localhost IP address 127.0.0.1 and you have to install the following Microsoft hotfix: Package: ----------------------------------------------------------- ----------------------------------------------------------- See Microsoft KB Article Number: 2554746   ** In very rare occasions, removing MSMQ and adding MSMQ again to the PC is required. ** Once it is re-installed, please refer to Access event viewers running in a workstation other than the Primary Access Server stop displaying events to set the MSMQ CleanupInterval setting to one hour in the primary access server.

Issue How do I run Continuum Analyzer and get a report Product Line Andover Continuum Environment Continuum 1.7 onwards Cause The Continuum Analyzer is designed to provide installers and troubleshooters with a point of reference for discovering problem areas within their installations.  The software is proactive in that it enables you to 'clean' orphaned and mismatched objects from the database, thereby recovering from a minimal amount of database corruption.  Continuum Analyzer also performs a system information check and provides full reporting on all aspects of the installation, as well as alerts regarding deficiencies. Resolution Always ensure the site database backed up before Continuum Analyzer is used to "Clean" the database. Go to - Start - All Programs - Continuum - Continuum Analyzer Type in User Name and Password (usually andover97 and (not disclosed due to public access)) for the Continuum DB or you can use the system admin user name and password. Click on the version "System Tests", then "Run Wizards" There should be zero failed. Then "Generate Report". To save click on top left disk icon and save as .html file If there are any failures, then ensure the database has been saved before a "Clean" is performed There was a bug in some Analyzer versions that caused a ghost alarm on the AlarmInfo test, also see Continuum Analyzer Failure for Continuum 1.92 & 1.93

Issue The Save to Flash exclamation point (bang) shows on a Controller object. Hovering over the icon, a tooltip comes up indicating that the controller 'requires flash backup'. However when performing a backup to flash, a result comes back that the 'controller doesn't need flash backup' and the exclamation icon remains. Re-loading the controller and performing a send to database have no effect. Product Line Andover Continuum Environment Continuum Controllers Cause The ObjectStatus attribute of the controller, or an object in the controller, may be fixed on and falsely reporting a save to flash is required when one is not. Resolution Toggle the ObjectStatus attribute by forcing it to a value of zero: In Continuum Explorer, find the controllers that have bangs on them Browse in these controllers and see if there are any objects with bangs on them. Run a Default Class Listview on those objects that show bangs In the listview, select the object(s) that are affected, right-click and SetAttribute for the ObjectStatus attribute to 0. This will reset the bang until it gets set when the flash again needs to be updated.. Also, refer to Save to Flash yellow exclamation point remains after valid save to flash.

Issue Need to prevent passback in a Continuum access control system. Product Line Andover Continuum Environment Continuum Access Control Cause Access control users may try to "passback" their card in order to have another user enter an area. Resolution The way that anti-passback works in Continuum is that all the Door's entering into an Area that require the feature need to be setup for anti-passback. This then means that any one granted access at any of the Door's is then denied access at the other Door's into that same Area until they have badged out. There are two variations on the anti-passback implementation: Strict anti-passback. This restricts the same card from being used to enter the same Area until that Personnel badges out into an exit Area. It also ensures that the person's current area is adjacent to the area he/she is trying to access so if the system has the person's current area as OUTSIDE and the person tailgates into the premises and then badges at an internal door she will be denied access due to anti-passback violation. Relaxed anti-passback. This also restricts the same card from being used to enter the same Area but will allow access if the Personnel is in any different Area. As long as the Personnel is not currently in the Area they want to enter then they will be allowed in. (See Anti-passback enforcement on area re-entry only)   How to setup To setup anti-passback you will need to have at least two Areas created. One you want to restrict access to and another where they will be coming from. Next, you will need to configure the Door objects entering these Areas for both Entry and Exit. Make sure to define both of these Areas otherwise the anti-passback options will not be selectable. (See Anti-Passback Protection option is not available) Then go to the Entry Options and/or Exit Options tabs and tick "Anti-Passback Protection". This will provide strict anti-passback unless relaxed is enable by the next step. You can enable relaxed anti-passback by ticking the "Allow Entry on an Anti-Passback Violation" option. There is also an option for timed anti-passback, which if ticked, allows access on anti-passback after the "Timed Anti-Passback" time has lapsed.   Possible Solutions When Exit Readers Not Available You do need to have exit readers as well as entry readers to be able to configure and use anti-passback. To restrict access to an Area we need to know the current Area that each Personnel is in, we can only do this with Exit readers. This may not mean having to install exit readers at every entry reader though, there a couple of possibilities. First though, you will need to setup dummy exit readers in the Door objects you want to have anti-passback enabled. This will allow you to access the anti-passback function. The main problem will be that after entering the Area successfully, that same user will not be able to enter again unless they are shown to have exited that Area. There a number of possibilities on how to provide this: Install a single "badge out" reader at the exits for Personnel to badge out before exiting through free egress doors. This reader will be tied to a Door object with an exit area attached. Timed anti-passback could be used with a large enough window to deter tail-gating but still allow the cardholder to exit then enter again normally throughout the day. Could use the "allow access on anti-passback violation" option to monitor (and potentially trigger an alarm at the entry point) to note the violation for latter analysis but still allow the Personnel through.

Issue Does Continuum support Outlook 2007 and Outlook 2010 as the client for emailing alarms? Product Line Andover Continuum Environment Continuum Cyberstation (v1.93 and above) Microsoft Outlook 2007 (32-bit) Microsoft Outlook 2010 (32-bit) Cause Sending out alarms as emails using Microsoft Outlook. Resolution Outlook 2007(32-bit) and Outlook 2010(32-bit) have been tested by QA with Continuum for emailing of alarms. This is mentioned in the Cyberstation Installation guide. Outlook Express does not work and is not supported. MS Outlook/Exchange 64-bit is not supported across all versions.  For specific information on how to set up emailing of alarms on your Cyberstation please refer to the Continuum Help available on your Continuum Cyberstation or see Creating an EventNotification Email and Page Distribution List. Note: Outlook 2013 and above has not been tested by SQA, but reports from the field are that it does work. In the new versions of Outlook, they have changed the name of the "Personal Distribution List" to the new name of "New Contact Group" Please see How to create a distribution list from your contacts in Outlook for info on how to set up these groups,

Issue General questions and best practices for RS-485 protocol including cable length and terminating resistors Product Line Andover Continuum, EcoStruxure Building Operation Environment MSTP Cause Understanding best practices for installing, cabling, and terminating RS-485 networks can avoid a lot of problems with communication and hours of troubleshooting communication problems. Resolution MS/TP MS/TP stands for Master Slave Token Passing. Each device on the link is considered the master when it has the token. If it does not have immediate need to use the token, it is required to pass the token along to the next device. This is the token passing part. All devices on the link which do not currently have the token are regarded as slaves, and are expected to listen to any messages the current master may have for it. Because all devices take turns being master, the link is effectively peer to peer. Electrically, MS/TP adheres to standard RS-485, physically wired using two-conductor shielded twisted pair cable. RS-485 Cable Specifications Cables used to form the RS-485 network should conform to the following specifications: Wire Size: 22-24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 100-120 Velocity of propagation: 78% Capacitance: <12.5 pF/ft between conductors and <22 pF/ft between the conductor connected to ground and the next conductor. Topology Daisy chain bus topology. Star topology can be achieved using Infilink/B-Link repeaters. Maximum Cable Length Cable lengths of up to 4000 ft (1220m) daisy chained from controller to controller on one arm of a star are supported. After 4000 ft (1220m), a signal repeater (b-Link) is required to add more nodes to the network or further extend the cabling. Using a b-Link fiber repeater allows you to extend the length of RS-485 with fiber optic cable, recommended for running cable between buildings and through noisy environments. Maximum Number of Devices TAC's MS/TP RS-485 supports a maximum of 127 nodes overall. Each controller represents a single node on the network. RS-485 Termination The MS/TP field bus requires a 120 ohm terminator resistor at both ends of a daisy chain segment. The following diagram illustrates the connection of the terminator: Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue Internet Explorer on Windows Server 2008 (R2) gets "Incorrect User or Password, please try again" or "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" when logon to the Webclient server. Product Line Andover Continuum Environment Webclient 2.0 Windows Server 2008 / 2008R2 Internet Explorer 9, 10, 11 Cause Internet Explorer security issue and the compatibility issue. Resolution Change the setting of the IE 11 on Server2008 as below: When Webclient logon from IE gets error "Incorrect User or Password, please try again": Set the Webclient server a Trusted site : From IE menu, select Tools -> Internet Options -> Security tab -> select the Trusted sites and click the Sites button -> add the Webclient to the Trusted Sites list. When Webclient logon from IE gets error "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" : Set the Compatibility View: From IE menu, select Tools -> Cmpatibility View settings -> add the Webclient name or IP address to the Compatibility View list. Also refer to:  Do we support 64-bit Internet Explorer for use with WebClient? HTTP Error 500.21 Internal Server Error logging into WebClient. or ASP.NET setup custom has stopped working when trying to register .NET 2 using aspnet_regiis.exe Invalid user name or password dialog when logging into webclient with acc that works in Continuum Error: "Unable to load the .Net control for this page." when trying to open a schedule or trend log in WebClient

Issue Where can I find standard Plain English programs for common HVAC and security applications? Product Line Andover Continuum Environment Continuum Plain English Cause Schneider Product Support Services does not issue sample Plain English code.  Resolution There are a number of PE programs available on the Buildings Business Community. Plain English programmers can post samples of their code that may fit your application. Buildings Business Communities: Area 360 Documents

Issue Common card vendors, types and formats commonly used by Continuum Product Line Andover Continuum Environment Continuum HID Indala Corporate 1000 Cause There is a wide range of card formats available. It's necessary to understand the most commonly used options for Continuum. Resolution Credential Card Format H50932 - Schneider Corporate 1000(35) Format A10202 - Andover 37-bit Wiegand Format 4041X (ASP-ANDINF) - Andover 37-bit Indala Format 40045 (ASP-CSI) - CSI Indala Format Indala Reader Format (FP3511A, FP3521A) 10723 (ASP-ANDINF-1L) - Andover 37-bit Indala Format 1009X (ASP-CSI-2L) - CSI Indala Format 10022 (ASP 26-bit Wiegand-1L) - 26-bit Indala Format HID MultiCLASS Reader (9xx Series) 4041X (ASP-ANDINF) - Andover 37-bit Indalat Format For additional  information on other HID formats, see the following article: Which HID card formats are supported by Continuum?

Issue Find New BACnet Device fails to find BACnet devices Product Line Andover Continuum Environment Continuum CyberStation Cause Third Party BACnet software may interfere with the CyberStation Bacnet Find process. NOTE: There are other reasons that bacnet devices may not be found not covered within this document. See: Cannot find new BACnet devices. Could not learn in a new 3rd Party BACnet device Bacnet 3rd party controller will not respond to Find New Bacnet Devices (Who-Is/I-Am) Resolution Stop the BACnet service in Administrative Tools\ Services. One example would be Cimetrics service Bacstac Protocol Once the BACnet devices have been found the BACnet service can be restarted, although it may be best to uninstall any non-Continuum bacnet software from a CyberStation

Issue Check Windows Add/Remove programs and see if MSXML 6 SP2 is installed.  Installation of MSXML 6 Service Pack 2 (KB954459) failed because a higher version already exists on the machine. To proceed, uninstall the higher version and then run MSXML 6 Service Pack 2 (KB954459) Setup again. Product Line Andover Continuum Environment XP SP3 SQL Express 2005 XML Cause When SQL Server Setup tries to install MSXML 6.0 SP2, it detects that the version of MSXML 6.0 that is described in Knowledge Base article 954459 is already installed on the computer. Therefore, the validation process indicates that the current version of MSXML 6.0 should not be replaced. This stops the installation of both MSXML 6.0 and SQL Server 2005. Resolution See Microsoft's Support KB article for more information. MS offers a work around to this issue in their KB article as follows: Download MSMXL fix from the following Microsoft website: http://download.microsoft.com/download/E/3/F/E3F51FFB-505D-480E-9F67-0DD3A9680DEE/MSXMLFix.EXE Extract the fix, and then copy the MSXML6.MSP file and the MSXML_FIX.VBS file to the same folder. Run cscript MSXML_FIX.VBS. Once the fix is run, try installing SQL Express again. For alternative solutions see Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.) and Error when installing SQL 2005 Express on a machine that had previously had MSDE installed