Building Automation Knowledge Base

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.  

Issue Modbus integration to Schneider Electric's PM1200 Power Meter Product Line TAC IA Series Environment I/A Series R2 Modbus Async (asynchronous) Integration Cause Requires the correct settings / configuration for Modbus integration to PM1200 power meter Resolution In WorkPlace Pro, open the UNC station and make changes to the following settings to integrate to the PM1200 power meter via Modbus Async (asynchronous). In the ModbusAsyncService properties, 'Comm' tab, ensure that the COM port settings matches the communications settings in the power meter. In the ModbusAsyncService properties, 'General' > 'Config' tab, change the floatByteOrder to 'order_1_0_3_2'. In the ModbusGenericAI object, the dataType should be set as 'Float'. dataAddress > addressFormat should be set as 'Modbus'. Use the register address as per the PM1200 documentation. Refer to the following documentation for details. PM1000 Series Power Meters Users Guide Modbus basics

Issue Drayton Theta II ES Optimiser and EC Compensator datasheets and technical documentation Environment Drayton Cause Datasheets Resolution Drayton Theta II ES Optimiser Datasheets Drayton Theta II EC Compensator Datasheets For sensor information see What is the resistance for the DOC, DRC, DSC and DLC sensors for a Drayton Theta II EC

Issue Use the block DI to monitor an IO module, and generate an alarm when it is offline. But the above-mentioned function cannot be realized. Product Line TAC Vista Environment Menta Xenta 301, 302, 401 Xenta I/O Modules Cause If there is a configuration error in block DI, the right alarm cannot be generated. It is necessary to check and correct the configuration error. Resolution Create and configure the block DI and Alarm block according to the following procedure, then the IO module status can be monitored. When it is offline, an alarm will occur in the alarm window in TAC Workstation.   1. Create a block DI. (See the Figure 1) Figure 1 2. Edit the block DI and input DI identifier such as the monitored module name, Status_411 in instance. (See the Figure 2)           Figure 2 3. Click BIND in Edit window, select the Online Device in BIND TO column, and input the IO module number in DEVICE ADDRESS. (See the Figure 3)               Figure 3 4. The module number can be found in IO Expansion and Wall Module Table of DEVICE SPECIFICATION in Menta Options toolbar. In the under instance picture, the M1 module, TAC Xenta 411, its device address is 1; the M2 module, TAC Xenta 421A, its device address is 2; and so on, the M5’s device address is 5. (See the Figure 4)       Figure 4 5. After creating and configuring the block DI, the block Alarm should be created. (See the Figure 5)                Figure 5 6. Then connect the block DI and Alarm. When the IO module is online, the DI value is generally 1. So the block NOT must be used. (See the Figure 6)         Figure 6   You can also reference Monitor the online status of a base unit's associated I/O modules.

Issue What HID Corporate 1000 card formats are supported by Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Controller Security Expert Smart Card Reader Cause Information about HID Corporate 1000 card formats is needed to configure the card readers correctly. The existing documentation does not mention this. Resolution HID Corporate 1000 35-bit format has been validated with Security Expert. To use this go to Expanders | Reader Expanders | Reader 1 and set the Reader 1 Format setting to HID Corp 1000 as shown below. Other HID Corporate 1000 formats may work however they have not been validated. If the format specification is known, it is possible to program the cards in a custom format. As an example, below are the custom format settings used for the HID Corporate 1000 48-bit format cards. Go to the Custom Reader Format tab of your controller and enter the following values. HID Corporate 1000 48-bit format 1 HID Corporate 1000 48-bit format 2 If the format is different from the above two examples or is not known, please provide support with the site code, card number and raw data output for Any Bit RAW card reads from at least three different cards to help determine the format. Refer to article Show raw card data of a badged card in Security Expert for further details on this.

Issue When the EWS interface is created, the Status show "online". However, after clicking on the Hardware > EcoStruxure Web Service > SSLite, the Status will go offline. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 and above SmartStruxure Lite 2.7 and above EcoStruxure Web Services Cause Make sure the SOAP Endpoint field says "ews" and not "EWS". Lua program is a case sensitive program. Resolution Change the SOAP Endpoint field to "ews". For firmware version support in EWS, see Firmware versions to support EcoStruxure Web Services (EWS) in SmartStruxure Lite MPM Controllers.

Issue Workstation Log on failure. Difficulties with Login, port settings, and Server localhost: 80 8080 443 444 and other ports Product Line EcoStruxure Building Operation Environment StruxureWare 1.2.x.xxx and higher StruxureWare Building Operation Device Administrator StruxureWare Building Operation License Administrator StruxureWare Building Operation Enterprise Server StruxureWare Building Operation Workstation Cause Logging into Workstation, since I have changed my HTTP and HTTPS port setting to avoid conflict, and error is produced when the login fails: Resolution Beginning with StruxureWare Building Operation 1.2 and forward, Workstation uses the HTTPS as the default protocol (to make communication safer).  Below is the Software Administrator screen capture. Notice HTTPS is using port 450 in this example rather than default 443 since that port is used by another program on the computer.    Now when logging into Workstation, change the Localhost to that HTTPS port number. In this case, it is Localhost:450 Note: Remember, Server field in the Login screen shot above is for the AS or ES you want to connect to. To connect to an AS, plug in directly with ethernet cable (see Ethernet port is AutoSensing (No Crossover Cable required)), and put in IP address of AS.

Issue Unable to connect to the ENC using its IP address. The ENC Ethernet port LED's appear to indicate normal operation. Product Line TAC IA Series Environment I/A Series Enterprise Network Controller Cause The ENC DHCP function was enabled by mistake on a system that does not have a DHCP server. The ENC when booted up will try to get an IP address from a DHCP server which does not exist and the ENC may not have a valid IP address. Resolution Connect to the ENC via its serial shell and perform the following procedure. Refer to Serial connection to I/A Series G3 ENC serial system shell using Windows HyperTerminal for details on connecting to the ENC serial shell. 1. Connect to the ENC serial shell using Windows HyperTerminal. Allow the ENC to boot up completely and you should see output messages similar to the following.   JACE 4/5 IPL Version 6.40 ECC to stop Autobooting on-board nand james startup version 6.41 launching devc waiting for /dev/ser1 creating symlink for /dev/serconsole Welcome to QNX Neutrino 6.4 on the ppc824x(james) starting /ffs0 filesystem ETFS_FS_2048 fs-etfs-jace2048: Truncating fid 0x2f from 337920 to 316718 bytes fs-etfs-jace2048: Truncating fid 0x64 from 5488640 to 13 bytes fs-etfs-jace2048: Truncating fid 0x1ce from 4096 to 0 bytes i2c: Using 100Mhz freq divider Press ESC to choose alternate boot options... continuing boot... ----------------------TCP/IP Network Status------------------------------ en0: flags=80008843 mtu 1500 address: 00:20:96:08:ee:06 media: Ethernet none status: no carrier inet 10.184.111.66 netmask 0xffffff00 broadcast 10.184.111.255 inet6 fe80::220:96ff:fe08:ee06%en0 prefixlen 64 scopeid 0x2 ------------------------------------------------------------------------- bad battery detected, A/C power test will not function MESSAGE [12:38:25 19-Jun-2013] [tid=1] niagarad: starting, baja_home=/niagara MESSAGE [12:38:25 19-Jun-2013] [tid=1] webserver: web server started [tid = 4] MESSAGE [12:38:25 19-Jun-2013] [tid=1] app registry: station registry starting MESSAGE [12:38:25 19-Jun-2013] [tid=7] engine watchdog: station TEST0817_TIM watchdog thread started [tid = 8] MESSAGE [12:38:25 19-Jun-2013] [tid=7] station: station TEST0817_TIM starting login: tac Password: [2J [H J404 System Shell ------------------------------------------------------------------------- hostid: Qnx-J404-0000-15C8-14F9 serial number: 584966 build version: 2.5.25 build date: built on 2011-04-04 16:47:24 system time: Wed Jun 19 12:38:43 STD 2013 niagara daemon port: 3011 en0: inet 10.184.111.66 netmask 0xffffff00 broadcast 10.184.111.255 inet6 fe80::220:96ff:fe08:ee06%en0 prefixlen 64 scopeid 0x2 ------------------------------------------------------------------------- 1. Update System Time 2. Update Network Settings 3. Ping Host 4. Enable/Disable Ftp 5. Enable/Disable Telnet 6. Update Platform Account 7. Reboot L. Logout   2. Select option 2 for update the network settings. 3. Press 'enter' (enter leaves the field at the original setting) for each field until the 'IP address (clear to use DHCP)' field. 4. Type in the required IP address here and press enter. This will disable the ENC DHCP function. 5. Key in the subnet mask at the next line and select 'n' when prompted to use IPv6. 6. Press enter until you are prompted to save the changes.      [2J [HJACE Network Configuration Utility Enter new value, '.' to clear the field or '' to keep existing value Hostname : Domain <> : Primary DNS Server <> : Secondary DNS Server <> : Route <192.168.10.1> : Primary IPv6 DNS Server <> : Secondary IPv6 DNS Server <> : IPv6 Route <> : NET1 Ethernet interface IP address (clear to use DHCP) <> : 192.168.1.141 Subnet mask <> : 255.255.255.0 Enable IPv6 addressing on this adapter? (Y/n) : n Confirm new configuration Hostname : localhost Domain : Default Gateway : 192.168.10.1 Primary DNS : Secondary DNS : Default IPv6 Gateway : Primary IPv6 DNS : Secondary IPv6 DNS : NET1 settings: IP Address : 192.168.1.141 Subnet Mask : 255.255.255.0 IPv6 Addressing disabled Save these settings? (Y/n) : y    7. Reboot the ENC and connect to the ENC using Workbench. 

Issue Checklist to be used as a basis for Maintenance visits. Product Line Andover Continuum Environment Continuum Hardware Continuum Software Cause Having a checklist available for routine maintenance will help with service calls to ensure Continuum sites continue to run smoothly over the life of the installation. Resolution There is no official maintenance checklist but some of the things you might want to consider checking on a regular basis are the items below. Continuum Analyzer Run the tests which check the database for known issues and provides a results file. See How to run Continuum Analyzer and get a report.   Review Windows Event Logs Check the Application and System Event logs for Continuum or SQL related errors. See Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes.   Check the size of the ContinuumDB The Database can't be more than 2GB in MSDE, 4GB in SQL Express, and the size of available space on the drive if using full SQL Server. Continuum will always run better when the database is kept trim, as the database size grows, Continuum transactions may start to slow down. If general system slowness is observed then check the database size and SQL Server resources first.   Truncate/trim event tables in ContinuumDB Especially the ExtendedLog table which can grow very rapidly if not kept in check. See Set up a Continuum system to do automatic log truncation to save database space.   Check that the Continuum Workstation is patched and up to date Periodically service packs and hotfixes are released for different versions of Continuum to resolve identified issues. Consult The Exchange Download Center for the current updates. Service Packs | Hotfixes   Check that Controller Firmware is up to date Check that the Controller firmware versions are supported for your version of Continuum and that they are up to date. Same as service packs for Continuum, new firmware builds are released as issues are identified and resolved. You can find supported firmware for each version of Continuum in the Compatibility Matrix. See Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation. And new firmware updates are available on Exchange Extranet.   Check battery charges On controllers that have them, check that the battery for holding up the active RAM still has a charge. How to check -> Battery life in Andover Continuum controllers that have onboard batteries Replacement batteries -> Replacement batteries for the various Continuum controllers   Run the Continuum Errors listviews to see if there are any recurring errors that may need to be investigated.   Most Importantly - Backup the ContinuumDB before leaving site! Backup and restore instructions for a single-user system are below but these also apply to full SQL Server using Management Studio. Steps 1 and 2 in the article below apply to backing up a ContinuumDB. See Move / Backup / Restore a database on a Single User SQL2005 Express system.

Issue There are 31 different Parser Errors that can result from a Menta direct download to a programmable controller. Product Line TAC Vista Environment Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Causes vary by error code.  See details below and any links to additional information. Resolution No. Name Comment 0 PARSER_OK   1 PARSER_CREATE_OBJ_ERROR Seen immediately on an attempt to download directly.  Subsequent attempts result in "Download Failed."  Resetting the device caused the error to come back.  See in the error in COD window that its showing 0,0 coordinate pairs and underlying information.  The error's not in the Menta code itself.  No spaces allowed in the Program Specification -- a change from earlier versions.  May render your device unusable after attempting to download -- correct files won't download either. 2 PARSER_ALLOCATE_FLASH_ERROR   3 PARSER_IOMOD_SAVE_ERROR   4 PARSER_VERSION_ERROR   5 PARSER_APPNAME_ERROR   6 PARSER_ABBREV_ERROR   7 PARSER_TYPE_ERROR   8 PARSER_SOURCEFILE_ERROR   9 PARSER_SIGNAL_ERROR Error 9 has to do with the signal list (ESP-file) there all the public signals are transferred from Menta into the GraphOP tool by a sort of a long list. Normally, if you just make the application in Menta, this should not be any problem, however search and replace on signal names could give you headache. 10 PARSER_ALARMTEXT_ERROR Seems to download and fails on resetting device.  Had a case where this occurred when the application was too large due to generation of an OP tree where there wasn't one before.  Check memory. 11 PARSER_TIMESCHEDULE_ERROR   12 PARSER_IOMOD_ERROR   13 PARSER_IO_ERROR The terminal may not exist in this unit type.  Could also include situations where the same terminal reference is used in multiple references (this could be on the Xenta or the IO module). Typically caused by copy/paste. Reference to unsupported I/O Error in COD file - Error:13 for more information. 14 PARSER_CYCLETIME_ERROR   15 PARSER_CODE_ERROR Constants table has scientific notation, PVR blocks have scientific notation, Expression block attempting to use scientific notation, application size too large PARSER_CODE_ERROR Error in COD file - Error:15 for more information. 16 PARSER_DST_ERROR   17 PARSER_CHECKSUM_ERROR   18 PARSER_EOF_ERROR   19 PARSER_SNVT_ERROR   20 PARSER_SNVT_CRC_ERROR   21 PARSER_AUTHOR_ERROR   22 PARSER_BLUEPRINT_ERROR   23 PARSER_NO_BPR_FILE   24 PARSER_TLOG_RAM_ERROR   25 PARSER_TLOG_FLASH_ERROR   26 PARSER_TLOG_TO_MANY   27 PARSER_TLOG_ERROR_IN_DEF   28 PARSER_TOLG_PARSE_ERROR   29 PARSER_IMAGE_TOO_BIG   30 PARSER_RESET_BEFORE_PARSED   31 PARSER_SELF_DESTRUCTION_PERFORMED  

Issue "No Answer" when plugging in an operator panel (OP) to a Xenta 300/400/280. Product Line TAC Vista Environment Xenta OP Xenta Programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause There are several adjustable parameters on the Xenta OP that put it into different modes of communication/user preferences. This is a comprehensive list of all of those that might affect connectivity in different situations. If the controller is NOT commissioned, the red LED is blinking. The controller will not talk to the OP until commissioned. The OP will only talk to controllers on its same Domain ID. For troubleshooting connectivity to a Xenta 100 series ASC, see Use a Xenta OP with a Xenta 100 controller. Resolution Is the TAC Xenta controller commissioned? If the controller is NOT commissioned, the red LED is blinking. The controller will not talk to the OP until commissioned. Commission the controller from Lonmaker if using an LNS network (to download to the controller from the system plug-in first) Download and commission from TAC Vista if using a classic network. What mode is the OP in? Press the "escape" and "enter" buttons at the same time to get to the "OP service menu," scroll down to "OP-mode." Usually the OP should be in MAN mode (unless installing it in Lonmaker). Is the OP talking on the same Domain as the controllers? Check what domain being used in Lonmaker or TAC Vista. Go to the OP service menu, OP LON address (dom0), change the domain to match the setting in Lonmaker/TAC Vista.