Building Automation Knowledge Base

Issue A Continuum Workstation has become corrupted and cannot be re-added Product Line Andover Continuum Environment Continuum Cyberstation / Workstation Continuum Database Initialization SQL Database Cause Workstation will not initialize correctly and Continuum does not start correctly even though database can be seen correctly from the PC Resolution Occasionally a workstation can get corrupted, within Continuum, such that the computer cannot connect as that particular workstation.  A new workstation needs to be created within Continuum using Database Initialization.  Consider the following:  During the initialization process new Workstation Name, Folder Name, Device Node ID, and Network ID are required.  When initializing an IP conflict may occur, requiring a manual change to the computer IP address first. Once created log in using the new Workstation,  copy over any required objects from the old Workstation and then delete the old Workstation. Please refer to How to create a Continuum Cyber Workstation for supporting information  

Issue Checking if a port is open Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution It is possible to check if a port is open in a network by issuing the Telnet command. Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet. If a port is open, a blank screen will be seen after issuing the command: telnet [domainname or ip] [port] where [domainname or ip] is the domain name or IP address of the server being checked [port] is the port number the server application is listening on For example: telnet 192.168.0.20 9001 (to a closed port would display a connect failed message)   telnet 192.168.0.20 9003 (to an open port would display a blank screen)   To exit the Telnet session, type Ctrl + ] and then type "quit".   For how to enable Telnet in Windows 7 please see Enable Telnet Client on a Windows 7 PC

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. Issue How are the pull down lists populated in the Personnel Manager for fields such as Department, Hair Color etc? How to edit/remove entries from those lists. In the screen shot below the site has changed the name of a department from 'Technical Support' to 'Product Support', how to go about removing the old department name from the list. Product Line Andover Continuum Environment Continuum Cyberstation Microsoft SQL Cause Documentation Resolution The 'Department List' is populated from the department column of the Personnel table, the Personnel Manager walks the column and adds to the list any department name string that is not already present on the list. Since the list is dynamically populated from that database, to remove an entry from the list, all instances of personnel objects that have been assigned to that department must be changed until no personnel object remains with a department string equal to the string that we want removed from the list. In cases where only a few personnel objects are assigned to the department string to be removed, we can manually edit those personnel objects and change the department. In many cases the manual approach is not practical due to a large number of personnel objects that will need to be manually modified, in such cases the change can be made directly in the SQL database using the following query. ***** MAKE SURE TO HAVE A FRESH BACKUP OF THE DATABASE BEFORE MAKING ANY CHANGES DIRECTLY IN SQL **** update personnel set department = 'Product Support' where department = 'Technical Support'--------------------------> To rename an entry on the list. update personnel set department = NULL where department = 'ISIS'------------------------------------------------------------> To remove an entry on the list. Note the all personnel assigned to ISIS department will now have a BLANK department

Issue Some things to look for when you get ID 0 errors when doing a Save to Database Product Line Andover Continuum Environment Continuum Database Cause There are several causes such as date and time settings, scan variables, IP addresses, etc. Some troubleshooting steps are listed below based on different possible causes. Resolution Confirm that the date has been set in the controller. Edit the scan system variable and put a description in the description field. Doing this will update the LastChanged attribute of the Scan system variable. Verify that an IP address has been configured in the controller. If you are saving a remote site back that is earlier than revision 1.52 you need to set an IP address in the remote controller. Verify that the CX controller is at least revision 1.5 Verify that the controller is not reset. In some rare cases we saw that you would have a problem if you created the CX controller while offline editing. The correction in this case was to go offline edit, delete the CX in Cyberstation, go online, recreate the CX and then do the save to database. If the controller you are saving back has to go through a firewall and the firewall has blocked the access to the other IP addresses of the other controllers this controller knows about. Port numbers 33487, 33440, and 33456 are blocked in a router. Specifically port number 33456 is used for the save to database functionality. Make sure Firewall programs are not blocking the network connections. Disable any firewall programs before doing a “Send to DB”. Create a debug file (Acc_Dump_Debug.txt). See the Infinity-to-Continuum Upgrade document. Look in the debug file and see where it failed and act accordingly. 

Issue Field Bus controller shows its version number as 0.000000. Learn controllers from comm port is very slow and fails when reloading the controller. Updating the firmware will not fix this problem. Product Line Andover Continuum Environment Cyberstation 1.74 above i2 controllers B3 controllers Cause There are many reasons that will cause the i2 and B3 controllers show their version number as 0.0000000 Wireless network enabled or Multi-Network card enabled on the machine. Database snatched from Flash RAM after power-cycle does not match to the Continuum Database Some controllers with special firmware (Such as B38XX-V with 4.501043) have points referenced by other controllers, this will make the source controller buffer to be full after more than 20 hours Unknown application software installed on the CyberStation PC B-Link fault will also cause this problem Resolution Exit Continuum CyberStation, then ensure only a single network card is enabled Fix the problem caused by database mismatching: Create a new database and bring the master controller online, Do learn from the commport and bring the field controllers online Click the "Reset" button on the Runtime tag after opening the controller editor. Do database initialization and connect the original database to see if the version number is correct or not. If not, skip to item 4. If yes, do SendToController and then BackUpToFlash Update the controllers to the latest version. Rebuild the CyberStation PC. Only have the Windows operating system and Continuum CyberStation installed. Skip over B-Link and connect Field bus to BCX1 comm2 directly to verify B-LINK has some fault, and then replace it with new one, if required

Issue Access denied and/or insufficient access errors reloading CX9680 or ACX2 (5720/5740) The above typically happens following an uprev of the controller FW to a different version. Product Line Andover Continuum Environment CyberStation CX9680 ACX5720 ACX5740 Cause RAM Memory issue due to the difference between the two builds, this problem will be addressed in future releases of the FW A similar warning can be seen if an XDriver is not correctly loaded. (Xdr may be referred to in the Distribution Properties page) Resolution Remove the battery Power down the controller, wait 5 minutes to make sure RAM is fully erased. Power up and reload the controller once it is online. Or reload the XDriver correctly first

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. Issue Procedure for converting a bCX9640 to a CX9680 (NC2) Product Line Andover Continuum Environment CyberStation bCX9640 CX9680 (NC2) 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 In the field it can be advantageous to flash an i2 to a b3 or a b3 to an i2 Product Line Andover Continuum, EcoStruxure Building Operation Environment Infinet controllers BACnet controllers i2xx/i28xx-V b3xx/b28xx-V Cause Flashing controllers in the field can save time Resolution If the controllers are i28xx-V or b38xx-V then these can be flashed back and forth in the field.  Please refer to Update b3 or i2 OS which also contains information on converting a bCX4040 to/from bCX9640 Refer to Conversion of Continuum devices from i2 to b3 and vice-versa in the field for non -V models If the i2/b3 controller is NOT included in the above (any other type of controller) then it cannot be flashed in the field, it will need to be sent to repair to change from an Infinet to BACnet or BACnet to Infinet.  If you attempt to flash this way in the field it can cause the controller to become a non-functioning controller.

Issue How can I streamline badge creation in Security Expert? Product Line EcoExpert Security Expert Environment Security Expert Server Security Expert Client   Cause There is no "Import/Export badge" feature available in Security Expert (unlike in Episuite/Continuum) Resolution This video demonstrates how to streamline badge creation in Security Expert.     Badge templates are normally provided by the customer.  They should be provided in bitmap (.bmp) or portable graphics format (.png) format. JPEG image format does not work well for resizing.     A new template can also be drawn though this is time-consuming.      Blank template from client 1. In Security Expert Client menu, go to Users--> Card Template Editor   Add and name new template, 2. Add blank template as image, go to right side Properties-->Images   Add blank template Adjust image to fit blue outline   3. Add dynamic user fields, go to right side Properties-->User Fields   Add and name fields ONE AT A TIME by dragging out items on to plan (drag one at a time to avoid confusion)     4. Name and place dynamic user fields over-top of blank template layout (Photo, Name, Dept, etc.)   Stretch, Align and Center Fields for uniform finish         5. Save template   6. Preview badge In Security Expert, go to Users--> Users-->Photo tab   Select a user:   Photo ID: Card template(drop-down menu)--> Choose your newly created template Hit the preview button Note: Do not choose Print & Read if no USB card reader is attached; this will cause an error and shut down Security Expert   Print Preview:

Issue When using the Modbus RTU X Driver to communicate to multiple Socomec Diris A20 electric meters it has been found only 2 or 3 devices can be networked together, even using a b-Link to boost the signal does not resolve the issue. Product Line Andover Continuum Environment Modbus RTU X Driver on bCX1 or Netcontroller II B-Link repeaters Cause The Socomec Diris A20 meters require a minimum of 4V RS-485 signal to communicate reliably, but the EIA RS-485 standard only calls for a +/- 1.5 volts signal and the Receiver Input sensitivity should be +/- 200mV. When using a bCX1 with the X Driver on Comm1 you will require a b-Link to provide the RS-232 to RS-485 conversion, although the B-Link fully conforms to the EIA RS-485 standard it does not have the drive levels required by the Socomec products. Resolution To resolve the non standard electrical requirement of the Socomec Diris meters use a Socomec RS-422/ RS-485 Repeater this will output the required electrical levels required by the Diris meters, the Socomec  part reference is 48990120.  Please refer to SOCOMEC Communication accessories or RS-422/485 Repeater Operating Instructions   If a B-Link is to be used each RS-485 output that is used will require a separate Socomec repeater.  

Issue What is required to control command priorities in 3rd party controllers using Plain English? Product Line Andover Continuum Environment Continuum Cyberstation BACnet Controller (BCX, B4920, B3) BACnet command priority Plain English Cause Need to understand how to control command priorities and point values with Continuum workstation programs or controller infinity programs. Resolution Command Priority is a BACnet mechanism to decide the control hierarchy of a point, with 1 being the highest priority and 16 being the lowest.  Consider the following:   Default setting for a workstation program priority level is ManualOperator priority 8 Programs located in the workstation default command priorities can be controlled through Bacnet Preferences Controller InfinityPrograms will need to use the WriteProperty function to set a different priority other than priority 10 To relinquish a priority level use Relinquish(pointname, priority level)   The WriteProperty function is written in the format: WriteProperty (object_name, value, priority, index) object_name  Includes a full pathname, followed by a property name. The object identifier and property identifier are combined as one argument value   This actual value to which the property is set. This is optional.  If it is not present, then the next argument, priority, must be present to perform a Relinquish command.  (See the example in Relinquish.)  priority  The priority  number, ranging from 1 (highest) to 16 (lowest).This is optional.  It applies only to a set commandable property.  For controllers:  If it is not present, priority 10, if applicable, is used.  For CyberStation: The value, based on the priority in the BACnet Preferences dialog, is used.  index  This is optional.  It applies only to an array-type BACnet property.  The index is ignored whenever it is not applicable.   Infinity controller samples: This line will write the value of 22 to priority 10 BACnetDevices\BNet_4444\B3_885\B3Num1 = 22 This line will write the value of 33 to priority level 4 WriteProperty(BACnetDevices\BNet_4444\B3_885\B3Num1, 33 , 4 ) This line will relinquish the value for priority level 4 setting the value back to NULL Relinquish(BACnetDevices\BNet_4444\B3_885\B3Num1 , 4 )

Issue By design, the Continuum system cannot delete personnel objects until all the distributed copies can be first removed from the controller(s). In some cases the distributed copies cannot be removed from the controllers, such as when a controller is permanently offline or has been deleted. Product Line Andover Continuum Environment CyberStation Cause Communication failure between CyberStation and controllers. Resolution Starting in CyberStation version 1.94 a new feature has been added that allows the user to force a delete of personnel objects even if the distributed copies cannot be removed. In CyberStation 'Delay Distribution' dialog, a new button has been added; the button is only enabled when CyberStation is in offline edit mode. Make a backup of the Continuum database as a precaution. Close ALL CyberStation workstations. Put CyberStation in Offline edit mode to enable the 'Clean up failed personnel delete distribution' button Click on the button, the system will provide the following warning Click OK to force all personnel deletions that are pending or have failed distribution to complete; any distributed copies in the controllers will be left orphaned. If offline controller returns online orphan distributed personnel records in controller can be removed by one of the following methods: Cool start the controller.  (For controllers that support access control and backup to flash such as the CX9680, ACX5720, ACX5740 . Note that personnel objects ARE NOT saved to flash memory, the controller requests a personnel distribution from CyberStation on cool start). See Restart modes of the second generation Infinity controllers for more information on cool start. Reload the controller from the CyberStation, this will perform a cold start and re-send all objects to the controller followed by a personnel distribution.

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. Issue How to combine multiple Continuum DBs into one DB Product Line Andover Continuum Environment Continuum Cyberstation 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 CSV file that has been edited with Excel does not import. There is no error given but the import has no effect. Product Line Andover Continuum Environment CyberStation Cause This problem can occur if the application used to edit the CSV file adds hidden characters. Resolution Make sure the file contains ONLY plain text. Use a simple text editor such as Notepad to avoid this issue

Issue After a find new BACnet devices in Continuum or EBO, 3rd party devices may come in and that we do not know the IP address of. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum Cyberstation BACnet Operator Workstation EcoStruxure Building Operation Cause BACnet devices IP addresses in Continuum explorer and EBO are encoded in HEX per BACnet Standard. BACnet IP addresses in BACnet are described as BACcnet MAC address. Resolution 3rd party IP level device is already in the BACnet side of Continuum, the IP address in HEX located as BACnet MAC address. Right-click and edit the third party device and use the BACnet MAC address to decipher. That is the IP address plus the port used to communicate For instance: The BACnet MAC address on the device editor is 0A9F1ACFBAC0 That would be 0A = 10, 9F=159, 1A=26, CF=207  The IP address would be 10.159.26.207 and BAC0 is 47808 on the port.   If you have exported to Excel and need a solution to covert, please reference IP address from BACnet MAC Address (SBO & Continuum)

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue ACX57xx Continuum controller frequently reboots itself, loses configuration and/or stop granting access to doors until reloaded.     In the controller error log frequent and spontaneous re-starts of the controller can be observed without an apparent cause such as power failure for example.     Here is another error log from different controller with same issue, a similar signature can be observed in the following screen shot   Product Line Andover Continuum Environment Continuum ACX 2 Controller Continuum ACX 4 Controller Cause Electrical noise coming from door striker corrupting controller's memory.   Resolution An external Varistor may be installed for Noise Suppression of a Door Strike. Here is a link to a part that may be used for this purpose:   https://www.digikey.com/en/products/detail/bourns-inc./MOV-07D470KTR/13420467?utm_adgroup=General&utm_source=google&utm_medium=cpc&utm_campaign=PMax:%20Smart%20Shopping_Product_Zombie%20SKUS&utm_term=&utm_content=General&gclid=Cj0KCQjwteOaBhDuARIsADBqRei7ZmpR8CRYf12zRH1bfTIK7GHk3NC6XStbVoCBrPizkZvEPDlCaFEaAjLFEALw_wcB    The part should be installed at the Door Strike, from the switched 24VDC terminal to the common 24VDC terminal, like this:  

Issue Pop-up error message displayed when trying to create ContinuumDB on stand-alone system. Unable to get past this to create the database. Error message similar to below: "Microsoft SQL Server 2005 Setup The sa password must meet SQL Server password policy requirement. For strong password guidelines, see Authentication Mode, in SQL Server Books Online."   Product Line Andover Continuum Environment Continuum Stand-alone SQL Express Cause When SQLExpress was installed a "strong" SA password was not defined. Resolution As per Microsoft SQL password policy Strong passwords must meet the following guidelines: The password does not contain the account name of the user. The password is at least eight characters long. The password contains characters from three of the following four categories: Latin uppercase letters (A through Z) Latin lowercase letters (a through z) Base 10 digits (0 through 9) Non-alphanumeric characters such as: exclamation point (!), dollar sign ($), number sign (#), or percent (%). Passwords can be up to 128 characters long. Use passwords that are as long and complex as possible.   To change the SQL password: Download and install management studio express. http://www.microsoft.com/download/en/details.aspx?id=8961 Change SA password so that it now complies as a strong password. Find the SA user under Security\Logins. Change the Password. Run Database Initialization again and create the new database using this new SA password.

Issue A combined keypad reader works with a valid card swipe, but the keypad does not work. The keypad does not allow a valid pin to be entered to engage the door output even though the door, area and personnel objects are setup correctly. This issue could also happen with a keypad only, without the combination reader. Product Line Andover Continuum Environment Keypad Keypad/Reader Combination Cause A keypad or keypad/reader combination can be ordered with the keypad output set to work in a number of different modes.  Continuum requires the output mode to be ordered as follows: Buffer one key add compliment 8 bit message (Dorado) This is also known as 8 bit burst A keypad that has a different configuration than this will not work with Continuum   Resolution 1. Order a keypad or keypad/reader combination with the 8 bit burst output mode set 2. Contact the keypad manufacturer's technical support (Eg. HID), to see if they will send a Configuration Card that allows the output mode to be changed retrospectively in the field.

Issue Project specifications call for there to be no default administrator password in the BMS.  Can the ACC user in Andover Continuum be deleted? Product Line Andover Continuum Environment Administrator password Continuum CyberStation Permissions Cause By default Andover Continuum always creates the ACC administrative user on all system but this is deemed unacceptable by some project specifications. Resolution The Andover Continuum default ACC admin user cannot be deleted, however it can be renamed and its permissions can be removed/amended.  

Issue Removing software from a PC may leave behind unused / old registry entries and folders from the removed software, this in some cases may prevent software re-installation Product Line Andover Continuum,EcoStruxure Building Operation,Satchwell BAS & Sigma,Satchwell MicroNet,TAC INET,TAC Vista Environment All supported Operating Systems Cause This is due to the windows uninstall program not fully removing all elements for the software. Some of this is due to windows thinking the the software may have been removed unintentionally and therefor all the previous settings will still be saved in case of  re-installation. For example, when SQL is uninstalled the program folders that contain the database will remain intact. This may be an issue if, for example, the software is removed due to a problem with the original installation. This is when a complete removal off all components and registry entries may be needed. Resolution The best solution for removing all the unused registry entries is to use a program designed to remove obsolete registry entries and temporary files. Some examples of these are: CCleaner, which will allow you to clean up your PC by removing past installation components. Revo Uninstaller  which is useful for removing redundant folders / files / Registry entries.   It may be useful to use both of these programs to ensure a complete cleanup. Revo Uninstaller can be used to remove unused software and then CCleaner to get rid of all the Temp files etc.  Finally remove the relevant folders from within the windows explorer, Example: C:\Program Files (x86)\Continuum Once done you should then be able to install a fresh clean copy of the application software. This solution is current in all versions of Windows including windows 10