Building Automation Knowledge Base

Issue Serial connection to I/A Series R2 UNC VxWorks Target Shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series R2 Universal Network Controllers: UNC-410-1 UNC-410-1-N UNC-520-2 UNC-520-2-N Cause There maybe a need to access the UNC via its serial port if the IP address of the UNC is unknown or for troubleshooting purposes when the UNC's Ethernet port is not functioning. Resolution Hardware required for connection to UNC's RS-232 port: 8-conductor flat silver satin stranded cable with standard male (plug) RJ-45 connectors RJ-45 to DB-9 adapter (part number: UNCC-405) or a socket-to-plug type RJ-45 to DB-25 adapter (part number: UNCC-430) A functioning COM port on a computer A 2-pin jumper for connection to the UNC's "Mode" connector Refer to the Installations Instructions for UNC-520 (page 15) for details on the cable and adapter (applies for both UNC-410 and UNC-520). Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) also refers to these pin outs. Connection to UNC's VxWorks Target Shell using Windows HyperTerminal (for operating systems without HyperTerminal, please refer to Hyperterminal on Microsoft Windows Operating Systems😞 Connect the cable and adapter between the UNC's RS-232 port and the RS-232 COM port used on the computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to UNC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port used on the computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: Hardware Click OK. On the UNC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 17 UNC-520 Installation Instructions for position of the Mode connector (top right corner). With the HyperTerminal session active, remove power from the UNC, let it cycle down, then reapply power. After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... To enter commands to the UNC, press any key to break out of the boot sequence. A prompt similar to the following is shown: [VxWorks Boot]: To determine the IP address / subnet mask of the UNC, do not break the auto-boot sequence as described in step 7. Allow the UNC to finish booting. When the controller stops displaying new messages, press ENTER to reach the command prompt. The prompt is similar to the following: -> Using the scroll bars on the HyperTerminal window, scroll up until the section that begins with the line 'Press any key to stop auto-boot...'. The IP address of the UNC is listed on the line that begins 'inet on ethernet (e)' The IP address is listed (in dotted decimal), followed by a colon, and then the subnet mask (in hexadecimal). Disconnect from the UNC when complete. Press the 'Disconnect' button on the HyperTerminal toolbar. Exit from the HyperTerminal application, selecting to Save if planning to reuse this HyperTerminal setup for future connection to an UNC. Remove the 2-pin jumper from the Mode connector of the UNC. Reboot the UNC by removing the power connector, waiting for all lights to extinguish, and plugging the power connector back in. * If troubleshooting the UNC, send the HyperTerminal start up messages to Product Support for analysis.

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 Communication issues between the Enterprise Server and Automation Servers result in an offline status of the AS. More information is required on how this status is detected.  Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause An AS behaves as if it is online yet shows up as offline in Workstation.  Resolution As of 1.5.0.10001 there is a new model for detecting online / offline servers. Prior to 1.5.0.10001 When a communication error was detected the Automation Server was marked as offline. As of 1.5.0.10001 and Newer An immediate DetectOnline call is scheduled. Only after three failed DetectOnline with an interval of one second we consider the  server to be offline. When offline an alarm is generated.and set the offline status as normal, and also go back to one minute interval for online detection. In 1.5.0.10001 the number of retries and interval is possible to set in server.properties. From 1.6.0 this is configurable from WorkStation. *** Server Communication folder is hidden in more recent versions of SBO See Also: How BACnet b3 controllers are established as being Online / Offline How the communication status of BACnet devices are verified

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 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 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 Unable to login to AS directly when using Domain user. It is possible to login to AS directly with "Local" Domain and to the ES with same Domain. Receive error "Can not continue because server is offline or temporarily unavailable" even though ES is online. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Domain Cause AS is unable to communicate with the ES to properly authenticate the Domain user.  If the ES is picking up a WiFi IP address instead of the LAN IP address, this can be the cause. All other communications can still function correctly with the ES but the issue occurs when the AS tries to connect directly to query the Domain, it will be using the wrong IP address. Resolution Changed the order of NIC''s in Windows so that the Local Area Connection was first, confirmed the ES had the correct IP address, confirmed the AS saw the change, and was then able to login to the AS directly using the Domain user. See How to set the Enterprise Server IP address for details on how to ensure you are using the correct IP address.  Another thing to look out for is that you are using the correct port number for the ES communications as seen from the AS.

Issue Is it possible to run TAC Vista 5.X.X in Windows XP compatibility mode (When TAC Vista Installed on Windows Vista, Windows 7, Server 2003/2008) Product Line TAC Vista Environment TAC Vista 5.X.X Windows XP Windows Vista Windows 7 Windows Server 2003/2008 Cause If TAC Vista 5.x.x is Installed on Windows 7, Windows Vista, or Windows Server 2003/2008, is it possible to run the Vista Workstation on Windows XP using Compatibility mode. Resolution TAC Vista has several other applications that work together with Vista. These applications do not support compatibility mode. Upgrade to Vista 5.1.4 or later which support Windows 7. If the operating system is a 64-bit version, upgrade to Vista 5.1.5 or later. For the compatibility matrix see Software and Firmware compatibility matrix for older versions of the traditional product lines.

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 How and where should sensors be fitted and maintained? Product Line Field Devices Environment Temperature and humidity sensors Cause General advice is required for cleaning and maintaining temperature and humidity sensors. Resolution The most important thing about sensors is to fit them correctly and appropriately during installation as this will reduce the amount of maintenance required. Fit them in locations that are accessible as well as away from dust and dirt to reduce the amount of cleaning required. See Recommended locations for Temperature Sensors, Valves, and Actuators for further advice on sensor location. Check the specific installation instructions for the sensor used and verify they are fitted accordance with this. All sensors should be regularly checked for correct operation as part of a regular building maintenance plan and replaced if they are not operating correctly. Most sensors are sealed units and do not require maintenance, maybe just an occasional dust with a clean cloth to remove surface dust, these include duct and immersion temperature sensors, outdoor sensors and thermostats. Room temperature and humidity sensors usually have vents or gauzes to allow airflow over the elements; these should be regularly dusted and can be cleaned with careful use of a vacuum cleaner or air blower to remove dust or other particles from within the unit. Do not however use equipment that can produce excessive pressures like compressed airlines as this could result in damage to the sensor. If you do need to use cleaning products on the sensors, then first check the materials used on that specific sensor (see datasheet, most sensors use Polycarbonate or ABS plastics) then verify that the cleaning chemicals are safe for use on that type of plastic or metal. Chemical/ material compatibility data is widely available on external websites (e.g. http://www.coleparmer.co.uk/Chemical-Resistance )

Issue Encountered the error 'The Bcpv3 service is not installed under Config/Services' while trying to add a discovered BACnet device to the station database Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server / Workbench Cause The default view of the BacnetNetwork is now the 'Bcp Bacnet Device Manager' instead of the standard I/A Series G3 'Bacnet Device Manager'. This happens when the Distech Controls EC-NET-AX Support Package  v3.0.2.8 (I/A Series G3 support files for Proview) is installed on the computer running the station. Refer to BCP Device Manager showing up with the BACnet Device Manager. The Bcp Bacnet Device Manager is used to discover and add Distech devices. Using it to discover and add I/A Series BACnet controllers will result in the 'The Bcpv3 service is not installed under Config/Services' error. Third party non Distech devices may also exhibit the same symptoms. Resolution Discover and add BACnet devices using the 'Bacnet Device Manager' instead of the 'Bcp Bacnet Device Manager'. The 'Bacnet Device Manager' is now the 2nd view of the BacnetNetwork (right-click on the BacnetNetwork and go to 'Views' > ' Bacnet Device Manager').

Issue The STR-150 Installation Instructions state that the stat wires into D1, X1, and M of the Xenta 100 series controller. However, this is not applicable to the Xenta 121, which does not have a D1 input. Product Line TAC Vista Environment Xenta 121 STR-150 Cause The correct terminal for the mode input from the STR-121 is labeled differently on the Xenta 121 versus all other Xenta 100 series controllers. Resolution Wire the stat as follows: STR-150 Xenta 121 Label Terminal Label Terminal Mode 11 Y1 5 Data 12 X1 7 M 13 M 6   The Purpose of output Y1 The only function that the STR-150 uses Y1 for is to get an effective occupancy signal from the Xenta 121. When the Xenta 121 is occupied, the man symbol will be displayed on the STR-150. If Y1 is already in use then the Status LED can be moved to a K output as explained inIs it possible to use an analog valve on the TAC Xenta 121-FC/HP and still have the effective occupancy active on the STR-150?. In order to activate this feature, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. If this feature is not desired then unselect Hardwired status LED and only wire up X1 and M. The STR-150 will still be able to send the controller the temperature, setpoint, bypass signal, and fan speed.

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 When restoring database, an error will show up, saying that version is incompatible with this server. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause This is usually caused by restoring new SQL database to older version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Microsoft doesn't like to do this. Resolution There is build number matrix for each SQL server version:     RTM (Gold, no SP) SP1 SP2 SP3 SP4 SQL Server 2012 11.00.2100.60 11.00.3000       SQL Server 2008 R2 10.50.1600.1 10.50.2500 10.50.4000     SQL Server 2008 10.00.1600.22 10.00.2531 10.00.4000 10.00.5500   SQL Server 2005 9.00.1399.06 9.00.2047 9.00.3042 9.00.4035 9.00.5000 So check the build number in the error message and download the corresponding version of SQL to restore and be used for I/NET.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.

Issue Xenta Server is offline in Vista and can not be reached via web interface. Product Line TAC Vista Environment Vista 5.1.9 Windows 7 Cause The PC has proxies configured. Resolution Open Internet Explorer Go to Tools > Internet options > Connections > LAN settings Disable "use a proxy server" Related Article: Xenta Servers are offline in Vista, although they can be reached via the web interface

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 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 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 Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Controllers: ENC-410-1 ENC-410-1-N ENC-520-2 ENC-520-2-N Cause There maybe a need to access the ENC via its serial port if the IP address of the ENC is unknown or for troubleshooting purposes when the ENC's Ethernet port is not functioning. Resolution Hardware required for connection to ENC's RS-232 port: 8-conductor flat silver satin stranded cable with standard male (plug) RJ-45 connectors. RJ-45 to DB-9 adapter (part number: UNCC-405) or a socket-to-plug type RJ-45 to DB-25 adapter (part number: UNCC-430). A functioning COM port on your computer. A 2-pin jumper for connection to the ENC's 'Mode' connector. Refer to the Installations Instructions for ENC-410 (pages 10 & 11) or ENC-520 (pages 10 & 11) for details on the cable and adapter.  Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) used for serial integrations to a Niagara R2 UNC or Niagara G3 ENC also refers to these pin outs. Connection to ENC's serial system shell using Windows HyperTerminal (for operating systems without HyperTerminal, please refer to Hyperterminal on Microsoft Windows Operating Systems😞 Connect the cable and adapter between the ENC’s RS-232 port and the RS-232 COM port you are using on your computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to ENC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port you are using on your computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 57600 Data bits: 8 Parity: None Stop bits: 1 Flow control: None Click OK. On the ENC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 7 of the ENC-410 or ENC-520 Installation Instructions for position of the Mode connector. With your HyperTerminal session active and configured to log to a file, remove power from the ENC, let it cycle down, then reapply power.  The easiest way to power cycle the ENC is to unplug the 6-pin power plug from the circuit board, wait 15 seconds and plug it back in.  After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... Do not press any key, wait for the login prompt. If you did press a key to stop auto-boot, select option 1. At the login prompt, enter the platform user name, and at the password prompt, the platform password. The default user name is 'tac' and password is 'niagara'. The system shell menu should now appear. You should able to see the IP address of the ENC now. When finished using the serial system shell, do the following: Remove the 2-pin jumper from the Mode connector of the ENC. From the system shell menu, select the Reboot option. Type 'y' at the 'Are you sure you want to reboot [y/n]' prompt, and press Enter. Shutdown-related text appears in the HyperTerminal window, and then the connection is dropped. Press the Disconnect button on the HyperTerminal tool bar. Exit from the HyperTerminal application, selecting to Save if you wish to reuse this HyperTerminal setup for future connection to an ENC. If you are troubleshooting the ENC, send the HyperTerminal start up messages to Product Support for analysis.

Issue webClient schedules getting error 'request for permission of type' system.security.permissions Product Line Andover Continuum Environment webClient Cause Require to run the Caspol commands. Resolution Run the Caspol commands, here is a batch file that runs these commands without typing them in. Click Here to download the batch file   Rename the caspolwebclient.txt to .bat Run the batch file at each WS that needs to access webclient schedules. Below are the actual commands: The following command will add FullTrust to the Internet_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Internet_Zone -zone InterNet FullTrust -name FullTrust The following command will add FullTrust to the Trusted_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Trusted_Zone -zone Trusted FullTrust -name FullTrust This will result in output like: The operation you are performing will alter security policy. Are you sure you want to perform this operation? (yes/no) Then select Y and you should see: Added union code group with "-zone" membership condition to the Machine level. Success In some configurations, you may need to add the IIS computer into Internet Explorer as a trusted site for each browser. Internet Explorer > Internet Options > Security > Click trusted Sites > Click Sites Type in http://yourservername/webclient and click Add (Ex. http://tacweb/webclient) Deselect the checkbox for Require server verification (https:) for all sites in this zone. Click OK and Ok Close Internet Explorer and access webclient See Removal of MS KB2858725 Dot Net 4.5.1 causes issues with Web Servers IIS Functions if this is for 1.94 SP1 - Uninstalling KB2858725 * It may be necessary to give specific permissions in the registry if you are seeing system.permissions.UIPermission, mscorlib Make a backup of the From Windows, Start> Run> Regedt32.exe Expand the hives(folders) to HKEY_CLASSES_ROOT\CLSID\{00B01B2E-B1FE-33A6-AD40-57DE8358DC7D}\InprocServer32\2.0.0.0 Right Click on 2.0.0.0 and select export, name the file and save. (This file can be used to restore the original settings of this branch)  Right click on this folder again and select permissions, select Users and add Full Control See below for snapshots

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 Downloading a Xenta Programmable controller under a SmartStruxure Automation Server LON channel fails with message: "Application Download Failure." Viewing error details, the Progress view window shows "Wrong device version." Product Line EcoStruxure Building Operation Environment Automation Server LON channel Xenta Programmable Controllers Cause Right click on the Xenta controller in StruxureWare Building Operation Workstation. Go to the Xenta tab. Check the Software version. If this is below 3.6, then the controller's .MOT file is out of date and must be updated. Resolution The controller's software version must be at least 3.6 to be compatible with SmartStruxure. Use the Download Wizard to load an updated .MOT file into the controller. See Download an .MOT file into a Xenta Programmable controller for further instructions.

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.