Issue The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Product Line TAC Vista Environment LonWorks Network Cause A LonWorks network test and diagnostic tool are needed. Resolution NodeUtil is a Windows console application that can be used with Echelon’s family of network interfaces (including the PCLTA-20, PCLTA-21, PCC-10, i.LON® 10, i.LON 100, i.LON 600, Loytec Devices, SmartServer, SLTA-10, U10, and U20 network interfaces) to diagnose and configure LonWorks® network interfaces, routers, and devices. NodeUtil is a test and diagnostic tool - it is not a network management tool.  It will not assign destination addresses or bind network variables. Nor will it format LonMark® interoperable device information. This tool can be used in the following conditions: The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Other network test and diagnostic need This software can be downloaded at http://www.echelon.com/support/downloads/detail.aspx?partNum=153-0373-01A The username and password are needed. This site is opened to the public for registration, so everyone can obtain it. Once you are logged in by default "Recommended Downloads" will be selected. Select "Development Tools" instead to locate the NodeUtil software.

Issue Connecting a serial cable to a Xenta 5/7/9xx controller Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Xenta Servers have a service portal for use with HyperTerminal with a serial connection to the RS-232B port. Resolution Connect a serial cable, Programming Serial Kit, part no. 0-073-0920-0, between the PC and the RS232 port B on the TAC Xenta.  For more information about the cable see Cable Guide OFL-3972. Go to Start/All Programs/Accessories/Communications/HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. NOTE: Product support has also witnessed strange behavior with serial connections when certain laptops were not plugged into a power source or the Xenta Server was not grounded. If connection problems persist after the connection setting above are verified, make sure the Hyperterminal PC is plugged into a 120 vac power source.

Issue BACnet device can't be discovered but instead shows up under the 'Unconfigured devices' in the server's hardware folder. Product Line EcoStruxure Building Operation Environment WorkStation Enterprise Server - ES Automation Server - AS Cause A BACnet device name must be unique. Devices with duplicate BACnet names can't be discovered. In the screen shot below a device by the name AbesbCX already exists under Network1, when performing a device discovery on Network1 a second device with the same name is found, Since StruxureWare already has a device with the same name it adds the device to the list of unconfigurable devices. NOTE: “The <<N>> means the device was discovered on a directly connected network (such as the local IP network, or a directly connected MSTP bus).  The 2 indicates it was “port” 2, (port numbers are really an internal detail) The server's Trace Log shows the following information, which includes the device's ID. The entry gives the reason as duplicate device name. Resolution 1.8.1 and above BACnet device name duplication is allowed, the duplicates will still land in the unconfigured folder and the system alarm will be generated BUT you can drag the duplicate device from the unconfigured folder to the desired network. When finished, manually delete the device from the unconfigured/non-conformant folder. Alternatively, you can also  warm start the server to force the unconfigured/non-conformant devices list to be updated. Note that the devices with duplicate names will still stay in the unconfigured/non-conformant folder until the name conflict is resolved. 1.7.2 and below A workaround is to create the device manually and specify a BACnet name during the create process. When manually creating the device you need to know the Device ID, you can get the id from the information in the trace log as shown above. SmartStruxure will send a message to the device to change its name to the specified BACnet name. The entry in the unconfigured devices folder should automatically update after a few minutes, you can also re-start the server to force the unconfigured devices list to be updated, the entry for AbesBCX should be gone now that the devices has been manually configured.

Issue When running TAC Vista in a Network environment, there are several ways of setting up the license system. Sometimes, TAC Vista nodes (Vista users) "steal" license modules for each other. Environment Vista in network Flexnet license Cause When various TAC Vista systems are pointed to the same license server, one server can take or "steal" e.g. an OPC Client license which another server should use. Resolution For a complete explanation about the license system and how to setup the system and control licenses, refer to this video. A useful tool to use is the Options file, with the .opt file extension. Located in the License files folder, its easily monitored in a text editor, and could be used for Reserving or Excluding license modules for other TAC Vista nodes. Other features available for the Options file can be found in the Flexnet Licensing End User Guide. 1: Make a file called taclic.opt and place it in the same directory as the license files. 2: Edit the file with notepad and make the reservations you need. The syntax for each line in the file is "command amount feature HOST host". The feature names can be seen in the license files. Here is an example on how to reserve an OPC Client license for a PC called "BMS_SERVER_1" RESERVE 1 Vista.Server.OPCClient HOST BMS_SERVER_1 3: Restart the license server.

Issue Every item shown in the Objects window of the TGML editor can be considered a Node. In the figure shown below, this relatively simple TGML page has 14 nodes. Nodes are hierarchical with parent and children nodes. One important concept when scripting in TGML is finding the desired node. Examples of this are: Changing the color of a rectangle when a bound signal is offline Writing a new value to a text box every time the database value updates Opening a new page when the user left clicks on a component Product Line EcoStruxure Building Operation, TAC Vista Environment StruxureWare Building Operation TAC Vista TGML Graphics Editor Cause Within a script, there are two functions that will pinpoint a specific node, but have very different applications. These are: getTarget() getCurrentTarget() An example function of how to use these functions is: function click(evt){ target = evt.getTarget(); } Resolution getTarget() - returns where an event is coming from getCurrentTarget() - returns the parent of the script Both examples below chart the differences between the two functions using the screen capture below. If the bind object in the figure above changes its value, here is what getTarget() and getCurrentTarget() would each return if they were a part of each script (A, B, C). Script getTarget() getCurrentTarget() A Bind Component B Bind Rectangle C Bind Bind If the user clicks on the rectangle in the figure above, here is what getTarget() and getCurrentTarget() would each return if they were a part of each script (A, B, C). Script getTarget() getCurrentTarget() A Rectangle Component B Rectangle Rectangle C N/A N/A Also check out the JavaScript Essentials - Programs and Statements Quick-Help video on the Exchange.

Issue How to change the STR-150 temperature display, setpoint adjustment range, etc. Product Line TAC Vista Environment STR-150 STR Sensor Cause The communication between the STR-150 and the TAC Xenta 121/122 device is one way, space temperature and setpoints are sent from the sensor to the controller. Therefore some STR-150 functions (for example, the setpoint adjustment) can not be configured though Zbuilder, but needs to be done manually in the STR 150 device. Resolution Buttons on the thermostat: Increase Button Decrease Button Bypass button Fan button Wrench symbol   Steps of changing the STR-150 configuration are listed below: Enter Configuration: Push the fan and bypass button simultaneously for 2 seconds to enter P0 In P0, hold down the bypass button and push the fan button three times to enter configuration mode. NOTE: the wrench symbol is lit when the STR-150 is in configuration mode.   In configuration mode: Press the fan button repeatedly until reaches desired parameters (refer to the configuration table below). NOTE: the two digits farthest to the left on the display show the parameters, while the two digits farthest to the right show the value Use increase button or decrease button to change the value.   Exit configuration mode: Push the fan and bypass button simultaneously for 2 seconds. Or, the timeout will exit configuration mode if idle.   Configuration Options: Parameter Function Value/Range Default value P0 Software Version - - P1 °C or °F temperature display 1=°C, 2=°F 1=°C P2 Reference temperature (Reftemp) 15-30°C / 60-90°F 22°C / 72°F P3 Setpoint or room temp. 1=Setpt, 2=Room 1=Setpt P4 Timeout 5-90 seconds 10 seconds P5 Fan Settings 0=No fan 1=On/Off fan 2=Two-speed fan 3=Three-speed fan 3=Three-speed fan P6 Room temperature and setpoint display resolution 0.1 or 0.5 °C 0.2 or 1.0 °F 0.5 °C or 0.2 °F P7 Max adjustable setpoint span above or below Reftemp (P2). +/- 0 - +/- 5°C +/- 0 - +/- 10°F +/- 3° or +/- 6°F P8 Bypass button and occupancy indication When = 2, no bypass command is sent  to the controller 1= Symbol on, off Or flashing 2=Symbol always off Default 1=on, off Or flashing P9 Setpoint as Absolute or Offset value 1=Absolute 2=Offset 1=Absolute   Click here to read STR-150 user's manual.

Issue While attempting to activate a purchased license, the entitlement ID shows that it is valid, but there is no available licenses that can be activated, or less available than listed on the entitlement certificate. The entitlement ID or certificate is lost. Unable to return the license in order to activate it on another PC Getting "This Operation is not applicable for Trusted Fulfillments" Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause In order to activate a SmartStruxure license, it must be available and unused. If a license is already in use, it needs to be returned before it can be activated. Note that all handling of licenses are to be carried out using the License Administrator. Licenses are not returned or rehosted as it was done for TAC Vista. Resolution Refer to WebHelp article #6687 for instructions on how to return a license If you are unable activate a license because you don't have the entitlement ID or certificate, note the activation ID before you return the license, and send that to Product Support Services in order to get the associated entitlement ID Launch the License Administrator Go to the Diagnostics tab and click the refresh icon in the top left corner. The entry in the list that is labeled Entitlement ID is actually the Activation ID. In the case that the computer has crashed or you are unable to successfully return the license on your own, contact Product Support Services providing the following details: A copy of the entitlement certificate The site name An elaborate explanation of why you are not able to return the license yourself

Issue How to change the IP address of the Automation Server and ensure proper communication. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Building Operation Device Administrator Building Operation Workstation Cause At times the IP address information for an Automation Server must be changed after being added to an Enterprise Server to accommodate changes in IP network design, correction of incorrect data, or any other reason. Changing the IP address needs to be done in the proper method to avoid artifacts and confusion after the change. Resolution To avoid complications, follow this process to modify the IP address of an Automation Server that is already communicating with an Enterprise Server. In the Building Operation Device Administrator connect the AS controller via USB or IP.  WebHelp Topic Connect to SmartX Servers Right-click on the AS and select Network Settings Modify the IP address settings to the new values Additionally, this can be changed through PuTTY with the "setip" command. Power Cycle the Automation Server (If a power cycle is not completed the AS will still have invalid data for network settings despite the physical network interface running with the new settings) Start Building Operation Workstation and log in to the Enterprise Server Select the Enterprise Server and open the Communication Tab Highlight the Automation Server that needs to be changed and modify the address field for the IP address of the device. (The Communications settings tab is enabled by selecting the Show/Hide tick icon). Click the Save button The Enterprise Server should now automatically establish communication with the AS, but if you want to speed this process you can right-click the Enterprise Server and select the "Advanced\Repair Server Communication" option. IMPORTANT: As of 1.41 if the IP address is changed on a server that is configured with a BACnet interface, the IP address and possibly the broadcast address of the IP Network under the BACnet interface must be updated manually. (see below)

Issue Requirements / specifications on cables used in a LonWorks network Environment LonWorks Cable Wire Guide LonMark Cause There are special requirements on cables used for LonWorks networks between Lon devices. Resolution LonMark organisation is recommending cables according to their specification. An example of this is the Belden LonWorks cable guide. Also, Echelon has a Wiring Guideline and Users Guide.

Issue Interfacing M-Bus meters to Modbus. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell Sigma Environment Sigma IC3-Modbus Mbus Modbus Kampstrup Heat Meter Multical 601 Cause Multical 601 M-Bus meters are required to be interfaced with the BMS. Resolution A M-Bus/Modbus converter (RS-485, RS-232 or TCP) and configuration software are required. The converter  and software are available from SyxthSense or similar suppliers. Using the converter and software setup the M-Bus/Modbus system without the BMS system connected. The M-Bus/Modbus converter will automatically assign the M-Bus registers as Modbus registers. From the software note the tables and registers used. Create the Modbus registers as required for the BMS system used. For Sigma - Create the gateway.txt, connect and configure the IC3-Modbus. A sample of the gateway.txt can be downloaded here: MultiCal Modbus Gateway.zip. For further M-Bus information see M-Bus Protocol Information. 

Issue How to create custom reports in Building Operation WebReports Product Line EcoStruxure Building Operation Environment Building Operation WebReports up to version 3.2.  Note: WebReports is no longer included in Building Operation 2022 and above. Cause Custom reports are typically created by modifying another report and then saving these changes. Typically used are the factory-supplied reports as the base for a new report then enter the filtering criteria that are required to be used in the new report. Assign a unique name to the custom report and save the new report as a dashboard or prompted report.  There may be a need to create a report not based on any of the standard reports provided in these Report Packs, this article covers this process. Resolution To create a non-factory-supplied report within WebReports it is necessary to use an editor.  Since WebReports use Microsoft Reporting Services it is recommended to download the Microsoft SQL Server 2008 R2 Report Builder 3.0 or MS MSQL Server 2012 Report Builder.  This is a free tool provided by Microsoft that provides an intuitive report authoring environment for business and power users. This download provides a stand-alone installer for Report Builder 3.0.  Please note that Product Support does NOT provide support for Report Builder.  After downloading and installing the Report Builder application, the steps are as follows:  Each of these steps is also located on the Building Management System WebHelp site, a link for each of these steps is provided for additional reference and guidance. Start Report Builder and create a new blank report, see Creating a Basic Report for the steps.  After Creating the report create a data source that connects this report to StruxureWareReportsDB, see Creating a Data Source for these steps Then create the Data set, so add to the report which tables, views, stored procedures, and fields from the StruxureWareReportsDB are required to use in your report, see Creating a Dataset for these steps. This data can then be added to the custom report as required.  See Setting Up a Report for an example of setting up a report. See Adding an Image to a Report  on how to add images to the report  The new report now must be deployed to the Reports Server where it can be accessible to WebReports. To complete this procedure use SQL Server Reporting Services Report Manager. See Deploying a New Report to the Reports Server to view these steps in detail.  Finally, the report must be synchronized in WebReports to be deployed and therefore appear in the WebReports Reports Tree. Use WebReports with a Web browser to complete this procedure.  See Synchronizing WebReports with a New Report for the steps to complete this. Once all these steps have been completed successfully the new Report should be visible in the tree - the placement of these reports will depend on where they have been uploaded in step 5 above.  See the image below:

Issue Error Codes: Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1631 E 04/05/2012 10:55:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1632 E 04/05/2012 10:57:30.00 0x00001c0b 0x04dd8500 0x02124e26 0x0000640b 0x00000000  Error Code Meaning: GLB_ELOG_DUP_START Product Line Andover Continuum Environment Continuum Site with BCX Controllers and an Error Log Cause Crash of BCX and log reveals: Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1629 E 04/05/2012 10:51:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000 Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1630 E 04/05/2012 10:53:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1631 E 04/05/2012 10:55:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1632 E 04/05/2012 10:57:30.00 0x00001c0b 0x04dd8500 0x02124e26 0x0000640b 0x00000000  Error Code Meaning: GLB_ELOG_DUP_START Resolution It is in the range of “Global System errors” that is usually not good, either faulty controller or need reloading of the O/S. Cold start and update O/S with the latest version supported by the Cyberstation version. Then run it on a test rig with different ID and see if it still crashes, if so will need to be repaired or replaced.

Issue Documentation for KLR-E AC Room Controllers / Thermostats Environment AC Room Controllers Thermostats Cause Documentation for KLR-E type thermostats. Resolution KLR-E Thermostats are manufactured by EBERLE (Invensys) and available from Schneider Electric in Europe. Click here to download KLR-E documentation in French Click here to download KLR-E documentation in English/German

Issue One of the following error messages are displayed. Internal server error Server already part of a system Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation Server Cause Version Mismatch: The Automation Server is either not the same version as the Enterprise Server or it is still connected to a different Enterprise Server. If the Automation Server is still connected to another Enterprise Server then it must be detached before it can be added underneath a new Enterprise Server. User Permissions: In some instances, the User Permissions "System Address" is not added to the user account that is attempting to add the server.    Resolution If you are given an error that states "Domain: Internal Server Error" then you need to download the same version of firmware to the AS that is installed on the ES. Resolution #1: Detach the Automation Server Log in to the Automation Server.   In the system tree pane, right-click on the automation server and go to Advanced > Detach server.   The Disconnect Automation Server window will open; click yes.   The Automation Server is now detached and can be added to an Enterprise Server. Resolution #2: Verify User Permissions Check a current backup using the SBO xbk Analyzer and verify the number of servers listed under Reports>Servers Log on using the default admin account and see if these servers exist. Detach the server(s), as described above. If the secondary user still requires permission to add and see ALL servers: Go to the user and select the Permissions tab Ensure the ES path is selected Click on the Add System button (identified with the arrow) Enable all options to allow read/write, create etc.  Save these changes and log off and back on with this user to see the changes. This user should now be able to add/see ALL servers.

Issue When restoring a Continuum database the process fails with a Cannot show requested dialog error message. Index was outside the bounds of the array. Product Line Andover Continuum Environment Continuum Cyberstation Microsoft SQL Server Microsoft SQL Server Management Studio Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause The version of SQL Server Management Studio is not compatible with the Microsoft SQL Server version. In this example the error occurred when attempting to use SQL Server Management Studio for SQL Server 2005 Express to restore a database on an SQL Server 2012 Express server. Resolution Uninstall the incompatible version of SQL Server Management Studio and then install a compatible version. The database can then be restored.

Issue Problems installing Continuum Continuum will not install correctly SQL Express will not install correctly Product Line Andover Continuum Environment Continuum Cause Cyberstation fails to install or run correctly Resolution Continuum Cyberstation can normally be installed very quickly (usually less than half an hour) on a normal windows installation that fits within the Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation, this would include SQL for a stand alone (Single User) installation. The Continuum Cyberstation uses many Windows components and services, and runs many executable files and batch files within its normal operation. We do not have a published list of services that Continuum requires to run since requirements vary depending on the site configuration. We obviously use Active Directory and .NET, RPC, MSMQ, SMNP, and all DCE services. SQL Server Management Studio Express is a free down from Microsoft and is an excellent tool for checking the SQL install Up to v1.94sp1 SQL2005 https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-2017 v2.0 and beyond SQL2012 https://www.microsoft.com/en-us/download/details.aspx?id=35579 There are a few items that can interfere with the smooth installation or running of a Continuum Cyberstation Ensure the workstation PC is within the Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation for the version being installed, especially Windows service packs and .NET framework versions. Ensure the minimum requirement for the workstation PC, is observed, as stated in the Cyberstation installation guide. Ensure the recommended requirement is observed, if the Cyberstation will be used for video or other more intense operations.  Local administrator accounts are required for some version of installation with passwords set. See How to create a local administrator log on in Windows. Automatic updates. See the individual installation guides, however, it is normally wise or even mandatory (depending on Continuum version) to leave them off, as updates include service packs and .NET framework updates that would take the installation off the Compatibility Matrix and could compromise the installation. There have also been other updates that have caused issues. See 5 below. MSXML6 Update SQL Express install fails on MSXML 6 Firewall & Anti virus issues. These should be disabled during installation. Issues with starting Continuum after new installation (Anti-Virus and Firewalls) Error when starting Continuum 1.9: Cannot find acc video recording service Access denied errors when installing Continuum or Webclient Crash of ACCDataServices on start up or running Continuum Another example of antivirus interfering with Continuum install is getting Microsoft Visual V++ error when opening a pin point graphic, when the install is completed with AV "webRoot" enabled.  SQL2005 Express (1.82SA onwards) When creating the sa password ensure the password is tested in notepad before typing in Database Initialisation, as if the keyboard is not set up correctly, you may be using an illegal character (eg " rather than @, in this case you will need to uninstall SQL, before re-installing via Database Initialisation) Custom Windows Images - Some Windows Images installed on new PCs include modifications that interfere with the Cyberstation installation, always use a clean MS Windows if possible, as this avoid such issues. HP Protect Tools - MFC error on Continuum startup or Continuum won't start on HP PC IT tampered Windows & domains. It is important to install Continuum with local Administrator rights as item 3, above, beware of PCs locked down by IT departments, the installation can be slow and difficult Error 1001, windows event log full. Error 1001 when installing Cyberstation or Webclient Problems with MSMQ (MicroSoft Message Queue) can cause install problems MSMQ errors and Continuum fails to start MSMQ error starting Continuum. "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ." MSMQ error message: "Appears to be a problem with configuration of system please check to make sure you have MSMQ correctly installed" Trying to install CyberStation 1.9x.  It completes but then pops up 6 errors saying "Access denied" "Access Denied" messages during a CyberStation 1.9x installation Microsoft Update issues see Windows updates and Continuum Continuum Version 1.93 Fails to install. IssueReceive AccDataservice errors on startup. Continuum Version 1.93 Fails to install For Windows 7 installs see Disabling administrator rights messages in Windows 7 OS and above (Also known as UAC / User Account Control) If you see a Continuum install Error -  "Error, unable to open documentation list \misc\doclist.txt" then you are running the incorrect "setup.exe", you should install using the one in the Cyberstation root directory, not the one in the Continuum sub-directory. It has be found that Microsoft "Strong" passwords are required not only for the SQL sa password but also for Andover97 password, see Password requirements for Andover97 SQL Login for details For a v1.82 Stand Alone and beyond, if the install admin user has no password, it has been seen that the tasks (CS_Minute, CS_Distn and CS_hrly) are not always created, see Getting AccDataServices error with AlmUtil.dll error when closing Continuum If a Continuum re-install, on a LAN CyberStation is required (were some part or program has broken) then uninstall Continuum, then re-install. A workstation initialization may be required. Deleting the Continuum directory and clearing out Continuum from the registry may also be required (check for any local held graphics, .mnu files, etc. before deleting the Continuum directory) Seeing "Can not change directory to Continuum" see Cannot change directory to Continuum error during installation of Cyberstation Re-Installing Continuum is sometimes required, for example, an automatic update to the Antivirus software has been seen to stop listviews from working. The only way around this was to uninstall Continuum then re-install it. There are different levels to uninstalling possible, 1.Simple uninstall. 2. Uninstalled followed by removing the Continuum Directory and other .ini files. 3. Uninstalled followed by removing the Continuum Directory and other .ini files, followed by cleaning of the registry.  In a few more recent cases where Controllers will not come online (after testing for other errors) or where persistent MSMQ errors cannot be resolved, a complete re-install of the OS may be required to ensure a "clean" Windows OS is available. Uninstalling some Continuum required programs can cause issues, especially SQL. see Problem uninstalling software. The following method has been seen to work: Stop service, uninstall, delete folders, run CCleaner (or Revo) and clean registry, reboot, run CCleaner (or Revo) and clean registry, reboot, re-install SQL Shared Memory errors seen with 32b systems and v2.0SP1, see "Shared Memory" error on startup of Continuum

Issue How do I locate the consolidated patch files (modules) for the I/A Series G3 maintenance builds (3.6.406, 3.7.106, 3.8.37).  Please note:  I/A Series G3 maintenance builds (3.6.407, 3.7.108, and 3.8.41) are now available for download from the Schneider Electric Buildings Download Center and include all updates for the previous builds. Product Line TAC IA Series Environment I/A Series G3 maintenance builds - 3.6.406, 3.7.106, and 3.8.37 Cause Various issues have been resolved in I/A Series G3 however it is difficult to locate the modules individually. Resolution Please note:  New I/A Series G3 maintenance builds (3.6.407, 3.7.108, and 3.8.41) are now available for download from the Schneider Electric Buildings Download Center.  The new builds already include the consolidated patches listed below. Below the latest consolidated patch files for I/A Series G3 maintenance builds 3.6.406, 3.7.106, 3.8.37 are listed.  The files contain updated modules and a set of release notes.  The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric Buildings Download Center and enter Consolidated_Patches in the search area or the filename of the zip shown below.  Modules listed in bold have been modified or added since the previous patch. Note: This article will be updated with information to newer patch files as they become available for release. Consolidated_Patches_3.6.406_SE_05272015.zip  ...  Click here for Release Notes alarm 3.6.406.3 bacnet 3.6.406.3 baja 3.6.406.10 bajaui 3.6.406.3 control 3.6.406.1 docMbus 3.6.406.5 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 kitLon 3.6.406.1 lonworks 3.6.406.5 mbus 3.6.406.5 modbusCore 3.6.406.3 modbusSlave 3.6.406.2 modbusTcp 3.6.406.2 modbusTcpSlave 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 obixDriver 3.6.406.1 opc 3.6.406.1 pdf 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 report 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.9 workbench 3.6.406.3 Consolidated_Patches_3.7.106_SE_07242015.zip   ...  Click here for Release Notes alarm 3.7.106.7 alarmOrion 3.7.106.2 bacnet 3.7.106.15 baja 3.7.106.10 bajaScript 3.7.106.1 bajaui 3.7.106.5 control 3.7.106.1 docMbus 3.7.106.5 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.2 hx 3.7.106.2 kitControl 3.7.106.1 kitLon 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.5 mbus 3.7.106.5 mobile 3.7.106.1 modbusCore 3.7.106.3 modbusSlave 3.7.106.2 modbusTcp 3.7.106.2 modbusTcpSlave 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 opc 3.7.106.2 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.3 seriesTransform 3.7.106.7 smartTableHx 3.7.106.1 snmp 3.7.106.4 weather 3.7.106.1 web 3.7.106.17 workbench 3.7.106.5       Consolidated_Patches_3.8.37_SE_07242015.zip   ...  Click here for Release Notes alarm 3.8.38.5 bacnet 3.8.38.11 baja 3.8.38.10 bajaui 3.8.38.3 control 3.8.38.1 docMbus 3.8.38.5 driver 3.8.38.1 email 3.8.39 gx 3.8.38.1 history 3.8.38.2 hx 3.8.38.3 kitControl 3.8.38.1 kitLon 3.8.38.1 kitPx 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.5 mbus 3.8.38.5 modbusCore 3.8.38.3 modbusSlave 3.8.38.2 modbusTcp 3.8.38.2 modbusTcpSlave 3.8.38.2 nDriver 3.8.38.1 niagaraDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.9 provisioningNiagara 3.8.38.1 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.3 smartTableHx 3.8.38.1 snmp 3.8.38.4 web 3.8.38.11 workbench 3.8.38.5 zwave 3.8.38.1   ********* Previous Release History ********* Consolidated_Patches_3.6.406_SE_09112014.zip  ...  Click here for Release Notes alarm 3.6.406.2 bacnet 3.6.406.3 baja 3.6.406.7 bajaui 3.6.406.2 control 3.6.406.1 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 lonworks 3.6.406.3 modbusTcp 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.6 workbench 3.6.406.2 Consolidated_Patches_3.6.406_SE_11112014.zip  ...  Click here for Release Notes alarm 3.6.406.3 bacnet 3.6.406.3 baja 3.6.406.7 bajaui 3.6.406.2 control 3.6.406.1 driver 3.6.406.1 fox 3.6.406.2 gx 3.6.406.1 lonworks 3.6.406.3 modbusTcp 3.6.406.2 ndedicatedMicros 3.6.406.3 niagaraDriver 3.6.406.3 obix 3.6.406.1 provisioningNiagara 3.6.406.1 raster 3.6.406.1 schedule 3.6.406.1 snmp 3.6.406.1 weather 3.6.406.1 web 3.6.406.6 workbench 3.6.406.2   Consolidated_Patches_3.7.106_SE_09112014.zip   ...  Click here for Release Notes alarm 3.7.106.5 alarmOrion 3.7.106.2 bacnet 3.7.106.13 baja 3.7.106.5 bajaui 3.7.106.4 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 kitControl 3.7.106.1 lonworks 3.7.106.3 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.1 obix 3.7.106.2 obixDriver 3.7.106.4 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.2 weather 3.7.106.1 web 3.7.106.14 workbench 3.7.106.4 Consolidated_Patches_3.7.106_SE_11112014.zip   ...  Click here for Release Notes alarm 3.7.106.6 alarmOrion 3.7.106.2 bacnet 3.7.106.13 baja 3.7.106.5 bajaui 3.7.106.4 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 kitControl 3.7.106.1 lonworks 3.7.106.3 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.1 obix 3.7.106.2 obixDriver 3.7.106.4 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.2 weather 3.7.106.1 web 3.7.106.14 workbench 3.7.106.4 Consolidated_Patches_3.7.106_SE_01222015.zip   ...  Click here for Release Notes alarm 3.7.106.6 alarmOrion 3.7.106.2 bacnet 3.7.106.14 baja 3.7.106.8 bajaui 3.7.106.5 control 3.7.106.1 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.1 hx 3.7.106.2 kitControl 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.3 mbus 3.7.106.4 modbusCore 3.7.106.1 modbusTcp 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 snmp 3.7.106.3 weather 3.7.106.1 web 3.7.106.16 workbench 3.7.106.5   Consolidated_Patches_3.7.106_SE_05272015.zip   ...  Click here for Release Notes alarm 3.7.106.7 alarmOrion 3.7.106.2 bacnet 3.7.106.15 baja 3.7.106.9 bajaScript 3.7.106.1 bajaui 3.7.106.5 control 3.7.106.1 docMbus 3.7.106.5 driver 3.7.106.1 fox 3.7.106.3 gx 3.7.106.2 history 3.7.106.2 hx 3.7.106.2 kitControl 3.7.106.1 kitLon 3.7.106.1 kitPxGraphics 1.0.16 lonworks 3.7.106.5 mbus 3.7.106.5 mobile 3.7.106.1 modbusCore 3.7.106.3 modbusSlave 3.7.106.2 modbusTcp 3.7.106.2 modbusTcpSlave 3.7.106.2 ndedicatedMicros 3.7.106.3 niagaraDriver 3.7.106.5 niagaraLexiconZhcn 3.7.106.6 niagaraVirtual 3.7.106.3 obix 3.7.106.2 obixDriver 3.7.106.5 opc 3.7.106.2 pdf 3.7.106.1 platWifi 3.7.106.1 provisioningNiagara 3.7.106.2 raster 3.7.106.1 report 3.7.106.2 schedule 3.7.106.2 seriesTransform 3.7.106.7 smartTableHx 3.7.106.1 snmp 3.7.106.4 weather 3.7.106.1 web 3.7.106.17 workbench 3.7.106.5         Consolidated_Patches_3.8.37_SE_09112014.zip   ...  Click here for Release Notes alarm 3.8.38.2 bacnet 3.8.38.3 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.6 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1     Consolidated_Patches_3.8.37_SE_10012014.zip   ...  Click here for Release Notes alarm 3.8.38.2 bacnet 3.8.38.3 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1       Consolidated_Patches_3.8.37_SE_11112014.zip   ...  Click here for Release Notes alarm 3.8.38.4 bacnet 3.8.38.6 baja 3.8.38.2 bajaui 3.8.38.1 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 kitControl 3.8.38.1 lonworks 3.8.38.3 modbusTcp 3.8.38.2 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.2 web 3.8.38.3 workbench 3.8.38.1 zwave 3.8.38.1     Consolidated_Patches_3.8.37_SE_01222015.zip   ...  Click here for Release Notes alarm 3.8.38.4 bacnet 3.8.38.9 baja 3.8.38.6 bajaui 3.8.38.2 control 3.8.38.1 driver 3.8.38.1 gx 3.8.38.1 hx 3.8.38.3 kitControl 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.3 mbus 3.8.38.4 modbusCore 3.8.38.1 modbusTcp 3.8.38.2 nDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.8 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.1 snmp 3.8.38.3 web 3.8.38.7 workbench 3.8.38.2 zwave 3.8.38.1 Consolidated_Patches_3.8.37_SE_05272015.zip   ...  Click here for Release Notes alarm 3.8.38.5 bacnet 3.8.38.11 baja 3.8.38.9 bajaui 3.8.38.3 control 3.8.38.1 docMbus 3.8.38.5 driver 3.8.38.1 email 3.8.38.1 gx 3.8.38.1 history 3.8.38.2 hx 3.8.38.3 kitControl 3.8.38.1 kitLon 3.8.38.1 kitPx 3.8.38.1 kitPxGraphics 1.0.16 lonworks 3.8.38.5 mbus 3.8.38.5 modbusCore 3.8.38.3 modbusSlave 3.8.38.2 modbusTcp 3.8.38.2 modbusTcpSlave 3.8.38.2 nDriver 3.8.38.1 niagaraDriver 3.8.38.1 niagaraVirtual 3.8.38.2 obixDriver 38.38.1 platMstp 3.8.38.9 provisioningNiagara 3.8.38.1 raster 3.8.38.1 report 3.8.38.1 schedule 3.8.38.2 smartTableHx 3.8.38.1 snmp 3.8.38.4 web 3.8.38.10 workbench 3.8.38.4 zwave 3.8.38.1 bajaui 3.8.38.2 bajaui 3.8.38.2 baja 3.8.38.6 baja 3.8.38.6               obixDriver 3.7.106.4 alarm 3.7.106.5 alarm 3.7.106.5 alarmOrion 3.7.106.2 hx 3.8.38.3 hx 3.8.38.3 hx 3.8.38.3   gx 3.8.38.1 gx 3.8.38.1 gx 3.8.38.1   hx 3.8.38.3   kitLon 3.8.38.1 kitLon 3.8.38.1   nDriver 3.8.38.1   nDriver 3.8.38.1

Issue Satchwell ALE series Linear Actuator requires replacement. Product Line Field Devices Environment Satchwell ALE series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  Actuator type :- ALE series.  Cause Obsolescence of Satchwell ALE series Linear Actuator. Resolution Replace Satchwell ALE series Linear Actuator with Schneider Electric M800 Linear Actuator and Linkage Kit :-   Linkage kit to mount a M800 actuator to a Satchwell valve (MZ,MZF, VZ, VZF, VSF and MJF) = L2SV Replace ALE Actuator with M800 + L2SV combined part number 880-0650-000 Replace ALE with Auxilary Switch kit with M800-S2 + L2SV combined part number 880-0651-000 Just linkage kit = 880-0124-000 Just M800 = 880-0310-030 N.B.  Should the Satchwell ALE series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :-  S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000)   Particular care should be taken when selecting an Schneider Electric Forta M800 Actuator to replace an existing Satchwell ALE series Actuator. The Schneider Electric Forta M800 Actuator may be used to replace an existing Satchwell ALE series Actuator but it should be noted that where an existing Satchwell ALE series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) will also be required. (e.g. Schneider Electric Transformer Type TR60)   Where an existing Satchwell ALE series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALE series Actuator (9.5VA) only.   In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) (e.g. Schneider Electric Transformer Type TR60) Details of the Schneider Electric M800 Actuator may be viewed here Details of the Schneider Electric TR60 Transformer may be viewed here

Issue BACnet proxy points and BACnet devices are configured to use COV subscriptions however points are listed as Polled when added to database. Product Line TAC IA Series Environment Niagara G3 all version, ENC-520, ENC-410 Cause The "Use Cov" property is set to false in the BACnetNetwork Default Tuning Policy. The "Use Cov" property default is "False." If set to "True," and the assigned proxy points are under a BacnetDevice that supports the Subscribe COV service, any necessary updates (Niagara proxy subscriptions) are attempted using BACnet COV subscriptions to the device. If the subscription attempt succeeds, the "Read Status" property of the point's BacnetProxyExt displays "COV." If the subscription attempt for a proxy point fails, normal polling is used and the "Read Status" property shows "Polled." Resolution The "Use Cov" property must be set to true for COV subscription to function. It’s a good idea to create a separate tuning policy for BACnet COV subscriptions. Creating a new Tuning Policy Expand Tuning Policies under the BACnetNetwork Right-clicking an existing policy, then choosing "Duplicate" in the shortcut menu. "Name" it as desired. Open the tuning policy you just created Set "Use Cov" to true and save. Assigning the new tuning policy to the proxy points under the BACnetDevice that is configured for COV subscriptions. Expand the Points folder of the BACnet Device Double-click on the proxy point you wish to configure to use Cov Click on the drop down menu next to Tuning Policy Name and select the tuning policy you created. Save. Configuring the BACnetDevice to use COV Open the BACnetDevice under the BACnetNetwork Set the "Use Cov" property to True. Note: Typically, you create multiple tuning policies in the BACnetNetwork—especially if you have multiple BACnet network ports enabled. This allows you to reference different tuning policies from BACnet proxy points under different networks (often with vastly different performance capabilities). For example, points under a BACnet MSTP network would likely use different tuning policies than those under a BACnet IP network. Reference the "About BACnet Tuning Policies" section of the Niagara AX-3.x BACnet Guide document for additional information.  

Issue Datacard ID Works gives an ODBC error. Examples shown below: Microsoft SQL Server Login Connection failed: SQLState: '01000' SQL Server Error: 53 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). Connection failed: SQLState: '08001' SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. Data Source Error Data source name not found and no default driver specified State:IM002,Native:0,Origin:[Microsoft][ODBC Driver Manager] Product Line TAC INET Environment I/NET Seven all versions Datacard ID Works video badging software Cause The "IDWorksView" driver uses a ODBC Connection to allow the ID Works Software to communicate to the I/NET SQL Database. If for some reason this ODBC gets corrupted, you will get an error anytime you try to run the ID Works software. Resolution Go to Start > Control Panel > Administrative Tools Select Data Sources (ODBC) Select the System DSN tab Highlight Seven ODBC SQL Server in the list and hit the Configure button Make sure the settings are as follows: Name: Seven ODBC Description: ODBC Connection for I/NET Seven Server: (local) Hit Next Before you actually login to this window, choose the Client Configuration button and make sure these settings are correct. Network libraries: TCP/IP Connection parameters: Dynamically determine port Note that the InetThirdParty password changed in I/NET Seven rev 2.4X to PassInetDb3p_SE. If you try to use this in this process it will fail on you. Instead of using the InetThirdParty and the password here, use the Username and Password that you use for the DbCreateEditor. Then select the Next button. Verify the settings below, then hit Next: Change the default database to: InetDb Verify the settings below, then hit Finish Perform translation for character data