Building Automation Knowledge Base

Issue TAC Xenta Server webpage does not work smoothly. A typical example is when you try to change a value. The small dialog that should pop up to change a value might pop up and immediately disappear. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment TAC Xenta Severs Xenta 511, 527, 701, 711, 721, 731, 913 TAC Vista 5 Webstation Cause Using unsupported version of Java may cause various issues. For example, Xenta server webpage does not display smoothly, time schedule does not show up or can not be edited, etc. Resolution Below is the Java compatibility matrix of TAC Vista 5.   5.1.9 5.1.8 5.1.7 5.1.6 5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0 Java 1.5 update 06               X X X X X X X Java 1.6 update 11           X X               Java 1.6 update 17            X 1                 Java 1.6 update 20 X X X X X                   Java 1.7 update 51 X                           1  TAC Xenta Server 5XX/7XX/913 SP1. Log into The Exchange and then click here to download the full Vista Compatibility Matrix. To uninstall an unsupported version of Java and install the supported version, refer to Xenta Server webpage automatically logs out while waiting for Java to load.

Issue Receive "Initialization error" when trying to start I/NET with SQL 2008 When we installing SQL Server 2008 Standard for I/NET Filemaster, what are the main components we should include? When editing / adding a new I/NET Configuration Profile the Database Server section is blank DBCreate does not start.  Appears in task Manager but no user interface is shown. Within DBCreate the restore option is grayed out Product Line TAC INET Environment I/NET Seven 2.4x Microsoft Windows Server 2003, Windows XP, Windows Vista, and Windows 7 families of operating systems. (both 32 and 64 bit) Microsoft SQL 2008 Standard or Express Editions Microsoft SQL 2008 R2 Standard or Express Editions Cause I/NET must have the SQL 2005 Backward compatibility file installed.  If this is not installed I/NET will not locate the SQL Server and hence will issue an “initialization failure” error.  This is can also be identified in either the DBCreate or I/NET Configuration application editors which will show no entries in their "Database Server" settings. The document also details information that is necessary for a Standard or Express editions of SQL 2008 / SQL 2008 R2. Resolution Follow the instructions below extracted from the document called "SQL2008 Expr Install Inst.pdf".  This document is found on I/NET Seven CD under the 'SQLExpress' folder.  For SQL 2008 R2 installations refer to the following document SQL2008 R2 Expr Install.pdf, also found in this same folder .  Installing SQL Server 2005 Backward Compatibility SQL Server 2005 backward compatibility must be installed for SQL 2008. To install SQL Server 2005 Backward Compatibility Navigate to the SQLBcm directory on the TAC I/NET Seven installation CD. Launch the SQLServer2005_BC.msi file. Follow the prompts on each screen and accept all defaults. After the install check the SQL Server Services SQL Server Browser is RUNNING SQL Server (MSSQLSERVER) is RUNNING Check the SQL Server Network Configuration Protocols Enable Named Pipes Enable TCP/IP Completing the Installation Proceed with the installation of TAC I/NET Seven on your PC. For installation instructions, refer to TCON298, TAC I/NET Seven Getting Started. Note: Run Inetcfg.exe before starting TAC I/NET Seven for the first time. This is necessary to attach TAC I/NET Seven to the database and avoid an “Initialization failure” error. Note: Before file equalization will operate, the system must be rebooted or the INETEQZMERGE service must be manually started.   Also refer to Installing I/NET 2.42 or higher and Vista 5.1.7 or higher on a 64-bit operating system for additional details on installing I/NET with SQL 2008 R2.

Issue If the STR 350 plug-in is missing, then the STR 350/351 setup needs to be performed manually in NL220, LonMaker, TAC Vista Workstation, or TAC Menta. Product Line TAC Vista Environment TAC Vista 5.1.4, TAC Vista 5.1.5 Windows 7, Server 2008 Cause Not all plug-ins in the TAC ToolPack can run on Windows 7 or Windows 2008. Read details in TAC ToolPack plug-ins are not showing up. Resolution If the STR 350 plug-in is missing, then the STR 350/351 setup needs to be performed manually in NL220, LonMaker, TAC Vista Workstation, or TAC Menta. NL220 STR 350/351 setup steps are shown below: Use the STR 350 device template to create a new node on the channel. Note: the device template is located at C:\LonWorks\import\TAC\IO Modules (Default location) Double click on the STR 350/351 device and make necessary changes to any signal under “NVs” tab. TAC Workstation STR 350/351 setup steps are shown below: Expand the tree structure in the left panel. Select the desired signal to change in the right panel. If a STR 350/351 is connected to a programmable controller (Xenta 280/300/400), then the STR 350/351 can be added in the Menta file similar to an IO module. Setup steps are shown below: Under “Options/Device Specification” select “Add STR Module…" Under “Type” Select “STR350/351” and Under “Bit(s)”, choose the desired bit(s). Note: hover over each bit, there is a short description about the selected bit. If a STR 350/351 is connected to a Xenta Server (Xenta 7XX), then the STR 350/351 can be added in the Xbuilder project similar to an IO module. Setup steps are shown below: In Network panel,  under “LON", right click and select “Add IO Module->STR35X". Right click on the STR35X model just added, and select "Configure". A configuration pop up window will be displayed.  Make any desired changes. Note: Neuron ID can be manually typed in the Xbuilder or get from service pin in the Workstation. If choose to service pin, need to create and commission a LNS network in Workstation. Save and download the project. Below is a table of each bit in nciOption1 and nciOption2 and its brief description. nciOption1: Bit 0, 1: Fan type 00: No fan (Default) 10: On/Off fan 01: 2 speed fan 11: 3 speed fan Bit 2: Fan auto state 0: Not allowed (Default) 1: Allowed Bit 3: Fan off state 0: Not allowed (Default) 1: Allowed Bit 4: Fan speed 1 0: Not allowed (Default) 1: Allowed (On/Off fan type needs to be activated) Bit 5: Fan speed 2 0: Not allowed (Default) 1: Allowed (2 speed fan type needs to be activated) Bit 6: Fan speed 3 0: Not allowed (Default) 1: Allowed (3 speed fan type needs to be activated) Bit 7, 8 ,9: Not used   Bit 10: Temperature presentation 0: °C (Default) 1: °F Bit 11: Temp. normally displayed 0: Setpoint temperature (Default) 1: Room temperature Bit 12: Setpoint temp. presentation 0: Absolute temperature (Default) 1: Offset temperature Bit 13: Bypass button usage 0: Bypass (Default) 1: On/Off Bit 14: Not used   Bit 15: Supported protocols 0: Standard LonTalk protocol only 1: Standard LonTalk protocol and TAC proprietary protocol (Default) nciOption2: Bit 0, 1: Sunblind - Switch 1 00: On/Off (Default) 10: Up/Down 01: On/Off/Up/Down 11: Not used Bit 2, 3: Sunblind - Switch 2 00: On/Off (Default) 10: Up/Down 01: On/Off/Up/Down 11: Not used Bit 4: Light - Switch 1 0: Disable (Default) 1: Enable Bit 5: Light - Switch 2 0: Disable (Default) 1: Enable Bit 6, 7, 8: Local sensor 000: None (Default) 100: CO 2 010: RH 001: Occupancy Bit 9: CO 2 /RH value 0: Hidden (Default) 1: Display Bit 10-15: Not used  

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

Issue Can the red crosses (that indicate that a signal is offline) in Vista or SmartStruxure Workstation/Webstation be disabled? Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure TGML Graphics (Workstation, Webstation) Vista TGML Graphics (Workstation 5.X, Webstation 5.X) Cause When a signal which is bound to an object in a TGML graphic is offline, this is indicated by a red cross when viewing the graphic in Vista or SmartStruxure Workstation or Webstation. Resolution This can easily be disabled in TGML by adding a script to the OnSignalChange event: function signal(evt){   evt.preventDefault(); }  Note, this script will only disable the red X when a point is offline. This does not address any issue that might cause points to be offline. A short video is available on this process, to review, please see SmartStruxure - Graphics - Removing Red Crosses.mp4.

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

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 An Energy Expert system is being moved to a new server and/or the virtual image is being upgraded. The historical records held in the SQL database of the Power Monitoring Expert (PME) system need to be backed up and properly restored on to the new server. Product Line EcoStruxure Building Operation Environment EcoStruxure Energy Expert (formally Power Manager) Power Monitoring Expert (PME) Enterprise Server Cause The system administrator has deemed it necessary to upgrade the Windows server that the Energy Expert system is installed on for security and/or resource reasons. Resolution It is important to remember that an Energy Expert installation is really just two Schneider Electric offers, EcoStruxure Building Operation and Power Monitoring Expert, installed together and set up to pass information back and forth. This means that appropriate steps must be followed for each system to backup the historical data and properly restore it on the new server. For more detail regarding how the system is laid out, please see the Difference between EcoStruxure Energy Expert (Power Manager) and Power Monitoring Expert (PME). Steps to move an Energy Expert database Backup the Power Monitoring Expert (PME) SQL database, dashboards and reports. The Configuration Manager tool available on the Exchange can be used to back all of these items up automatically. Run the tool on the existing server and it will create a zip file to be used later on when restoring to the new server. See Migrating a PME 8.0 System to a New Server for more information. The Schneider Electric Technical FAQs website also contains many other helpful troubleshooting articles for PME including different versions of the product. Return the Energy Expert license(s) from the Floating License manager in order to move them to the new server. For more information see Video: Licensing Guide for Power Monitoring Expert (PME) 8.x and 7.2.x and ENM 8.3.x. If moving the Enterprise Server, make a historical backup of the EcoStruxure Building Operation (EBO) ES from the existing server. See Backup of StruxureWare/EcoStruxure Building Operation AS and ES for more information. If the Enterprise Server and other EBO licenses are installed on the existing server, then they may need to be returned as well so they can be moved to the new server. See Removing a Local License or Returning a Network License for more information. Next the ETL project files must be retrieved and saved so they can be moved to the new server (if using architecture 1 in the Energy Expert offer). Go to the file location below and save all ETL project files that are needed on the new server. C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs If moving the Enterprise Server, install the EBO software on the new server, rehost the EBO licenses, and restore the EBO server backup(s). See Restoring the EcoStruxure BMS Server for more information. Install the Energy Expert software (the software includes PME, ETL and the integration utility). The information on how to download the Energy Expert software can be found on the Exchange. Once the software has been installed, the Energy Expert license can be hosted to the new server in the Floating License manager. Next, install the PME Configuration Manager tool on the new server. The zip file from step 1 can be loaded using this tool to restore the SQL database, PME dashboards and PME reports. Add the previously saved ETL project files to the same location on the new server C:\Program Files > Schneider Electric > ETL X.X (SBO to PME) > Jobs Since the server has changed, the configuration settings must be updated in the ETL projects to reflect the new server name. The settings in the EWS interface on the EBO server will also need to be updated as well. Note: It may be easier to delete the existing EWS interface in EBO and then use the integration utility to create a new XML import file to simply rebuild the interface.

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment Windows 7 computer WorkPlace Tech Tool software version 5.7 or later Cause The WinPcap driver, used in WorkPlace Tech BACnet communications was configured to start on demand and the WPT module that is attempting to start WinPcap does not have the necessary Windows security rights.  Resolution NOTE 1:  Before using this procedure, please verify that the issue noted in WorkPlace Commissioning Tool UDP Port: "A critical error occurred in the communication server rtmonitor.exe" has been corrected, if present, and did not solve the problem. NOTE 2: If the computer is running Windows 7-64 bit, replace the following references to "Program Files" with "Program Files (x86)". To correct this issue, perform the following steps. Open Windows Explorer, i.e., "My Computer" or "Computer" from the Windows Start menu or computer desktop. Open the folder "C:\Program Files\WorkPlace Tech" For each of the following program files listed here, in turn: RTMonitor.exe, WPCT.exe, WPFB.exe and WPTech.exe Right click on the program name, Select Properties from the pop-up menu, Select the "Compatibility" tab. In the Compatibility display, click the button [Change settings for all users]. Locate "Privilege Level" section of the displayed window and check the box "Run this program as an administrator". (See snapshot below) Click the [OK] button to save the settings for all users. The window will close. You will see that the Privilege Level option is no longer selectable. Click the [OK] button to save the compatibility settings.   After setting the privilege option for each of the four programs in the Workplace Tech folder, repeat the same setting change for the Microsoft Visio program itself, VISIO.EXE. Depending on the version you are using, it will be located in the C:\Program Files\Microsoft Office\OfficeXX folder where xx is 14, i.e., Office14, for Visio 2010, 12, i.e., Office12, for Visio 2007 or 11, i.e., Office11, for Visio 2003. After setting these options, the computer should be shut down and restarted before using the WorkPlace Tech Tool software.  

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

Issue Necessary steps to successfully install a "Stand Alone" versions of the Vista suite where a full Vista installation is not required. Product Line TAC Vista Environment Menta XBuilder Graphic Editor TGML MTA XBP Cause Sometimes a site may not require a full Vista package but will require the ability to edit associated Vista programs. This is the proper way to install only a portion of the Vista Software Suite. Resolution Create a account to the Download Center. Download the needed "stand alone" programs of the desired version, download here: Menta XBuilder Graphic Editor Download a matching version of the "stand alone" License Server, download here. Execute the downloaded programs on the host PC Order appropriate licenses using following program part numbers to validate the software (links to iPortal) Menta 000882401 XBuilder 000882411 Graphic Editor 000882221 (For an existing site requiring an upgrade from older Vista IV or Vista 5.0) Menta Upgrade Pricing 000883401 XBuilder Upgrade Pricing 000883411 Graphic Editor Upgrade Pricing 000883221 An Entitlement will be mailed which must first be Hosted to the PC. This is performed on the schneider-electric.flexnetoperations.com website by following How to Host a Vista Site License. License the Software on the License Server (Stand-alone Licensing for Vista 5 Applications)

Issue Additional information for creating Lonworks networks in ES, not covered by the StruxureWare Technical Guide. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 SP1 Cause Additional information for creating Lonworks networks in ES, not covered by the StruxureWare Technical Guide. Resolution Setup of the NIC852 network interface for the ES is covered in the StruxureWare Building Operation Technical Reference Guide, chapter 37.9 L-IP router setup is covered in the StruxureWare Building Operation Technical Reference Guide, chapter 37.10   Here are some additional points not covered in the Reference Guide: To use the NIC852 as a network interface for the ES, you must configure the Loytec LConfig software to run as a service.  See Not able to get Service pin from LON devices connected with Loytec NIC from ES for more details. The L-IPs must be used in Smart Switch mode in StruxureWare.  There are two Smart Switch modes: 1.  Smart Switch Mode 2.  Smart Switch mode with No Subnet Broadcast Flooding. Only use the first of these modes.  This should be the default, out of the box.  See the L-IP User Manual for details of the DIP switch positions for each mode. The ES version 1.3 can host up to 100 Xenta devices + 100 LON devices in total. These can be divided across 5 logical networks (different domains). It is possible to have multiple L-IPs in the same network if needed - but the limit of 100+100 is per ES, not per network or L-IP. Loytec recommend that in Smart Switch mode an IP channel should have no more than 10 L-IPs and packet rates no more than 500 packets/s. If additional Xenta/LON devices are needed you can add them to one or more AS, below the ES. Observe the standard Lonworks guidelines when creating your network topology e.g. maximum number of devices per network segment, maximum length of runs for the chosen cable type.  Group your devices so that network traffic across channels is minimized. StruxureWare is unaware of your physical network topology - it just sees it as one big channel.  It will reserve a different subnet for each Xenta group you create, starting at subnet 253, but each Lonworks device you create will just be assigned the next available subnet/node address, starting at subnet 254 node 1.  This means that devices with the same subnet address will most likely appear on multiple physical channels. The Loytec L-IP in Smart Switch Mode can still provide effective routing in this situation as it builds its routing table based on the physical location of subnet/node addresses, not just subnets.  Other manufacturers' routers, even in learning mode, may not be so forgiving.

Issue Getting the error "The RPC server is unavailable" when attempting to write to a Vista Database.  This error can also be shown in the plug-ins output pain as "Error: Failed to access object xxxxxxxxxx." Product Line TAC Vista Environment TAC Vista System Plug-in Cause Incorrect DCOM or Firewall settings. This often occurs when installing a new system or restoring an existing Vista Database to a new PC. Computer is running out of memory. Resolution If it is cause due to computer memory shortage, please restart the TAC Vista Server. If the restart does not solve the issue, please follow the steps below. Install the DCOM utility located in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. or manually set the DCOM settings as instructed in the TAC Software Installation Unzip and execute the utility. If the problem persists and Vista Server is not on the local machine, ensure there is not a Firewall preventing a connection. If steps above does not resolve the issue, please reinstall TAC Vista software.

Issue What are the intervals for Trends when using StruxureWare Building Operations Product Line EcoStruxure Building Operation Environment Enterprise Server or Automation Server Cause Questions regarding what the interval in time is for trending Resolution Intervals can be in Days, Hours, Minutes, Seconds, and Milliseconds. . Trend logs can be of different types and used for different purposes. All logs in StruxureWare use circular storage. The interval trend log collects data at a specific time interval. Each logged value is stored as a record in the trend log. Use this trend log when the logging interval is less than 1 hour. You create interval trend logs using WorkStation or WebStation. In WorkStation, you configure the properties of the interval trend log to meet the specific needs of your site. The interval trend log does not record the values between the intervals. An interval log checks the monitored value at each interval and records the new value if it differs from the previously recorded value by more than the delta. Delta is the difference between the current variable value and the last log value. To log a variable according to the time interval, use a delta of zero. You use an extended trend log to transfer records from a trend log. An extended trend log can be connected to a trend log or connected in a series to another extended trend log. Only one extended trend log can be connected to a trend log. You create and configure extended trend logs using WorkStation. The extended trend log is often saved on a higher server level with more storage capacity than the server of an ordinary trend log. This extra storage capacity enables the server to store more records before it overwrites old ones. The extended trend log can be viewed in a trend log list or a trend chart. Trend log lists and records can be exported in two different formats: CSV (Comma separated values) is a standard file format for digital storage of data structured in a table of lists form. The CSV format can be used by Excel and in databases such as SQL. XML (Extensible Markup Language) is a standard file format for structured data and can be use with a lot of different tools. One last suggestion is the number of records, depending on how many records you want to store is important. For example: a single one minute interval Trend Log, and for 66 day, that would be 99,792 records. The maximum is 100,000 on an AS, so take this into account when configuring. This is why Extended Trend Logging is important. Check out Maximum number using StruxureWare Building Operation (Scalability and Capacity) for information on trends and extended trendlogs.

Issue During the installation of Workstation on a PC that didn't previously had any SmartStruxure software installed, you can get the message: "Failed to install XXXX redist, error: 3010" Product Line EcoStruxure Building Operation Environment Workstation Cause One of the build in Microsoft Visual C++ Redistributeable (VCRedist) installers (2008, 2010, 2012) is failing for some reason. Resolution Restart the PC and start the installer again Note: There is a similar issue but with error 1603, if you get this please see Getting the error "Failed to install XXXX redist, error: 1603" during installation.

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 While upgrading a database from 1.7.1 to 1.8.1 that has already been prepared, the upgrade log states that a MAP file is missing (similar to one shown below), and the upgrade is cancelled and reports "Database upgrade failed!" MAP file is required for upgrading the type public.lon2.devicetemplates.pidxxxxxxxxxxxxxxxx but none could be found Product Line EcoStruxure Building Operation Environment Upgrade LonWorks Pre-upgrade add-on Observed in version 1.7.1 and 1.7.2 Cause At some point in a previous version of StruxureWare Building Operation, the import of a device template has gone wrong in the sense, that the XIF has been imported and parsed correctly, but stored incorrectly. That means that we have cases where the actual content of the XIF stored in the database, can either be another completely different XIF, or even in some cases just random files. The issue can be verified by performing a "Content Analysis" using the "SBO xbk Analyzer" version 1.0.9 and above. You'll get a message like this: Error in XIF file: Mismatching program ID (SBO: 90001347000604A0 - XIF: 90:00:13:47:00:06:04:3C) This means that Building Operation has a device template with PID 90:00:13:47:00:06:04:A0 but that the actual file this device template points to is 90:00:13:47:00:06:04:3C Resolution A hotfix has been produced to allow replacing the wrong XIF with the correct one. With the following procedure you can manually fix the issue if you don't have the hotfix: Firstly ensure you have run the Pre-Lonworks upgrade configuration and try the upgrade again. Check if the template is in use by searching the specific template while logged in directly to the server Once the device has been identified, proceed with the following steps: Record Neuron ID(s) - this is required since the Export Process does not retain this information. Export device(s) If you have multiple devices you can Export the folder containing these devices, it is not critical to export the devices individually. Delete device(s) remembering to keep references. Import latest XIF for device From WorkStation select: File > LonWorks > Device Template Browse in the correct XIF. Import exported device(s) in step 2 Commission device(s) Run the Pre-Lonworks upgrade configuration The database should now successfully upgrade.

Issue If the Xenta Server IP address is unknown or lost, how can the user retrieve or reset the IP address? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Once the Xenta Server IP address is lost, the user has to use a serial connection cable to connect the Xenta Server to the HyperTerminal in order to retrieve the IP address. The serial cable is a RS-232 to RJ10 cable which can be purchase from Schneider Electric order entry (Part number: 00730920). For some reason, if the cable need to be home made, please follow the steps below to connect correct pins. Note: some third party IP search/scan software can be used to search all IP addresses in a range. User can also use this type of software to retrieve Xenta Server’s IP addresses. Resolution Xenta Server serial cable guide: Connect RJ10 pin 1 to RS232 pin 2. Connect RJ10 pin 2 to RS232 pin 3. Connect RJ10 pin 4 to RS232 pin 5. Connect RS232 pin 1, 6, 4 together. Refer to IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for how to set up HyperTerminal in order to retrieve/setup Xenta Server IP address.

Issue Where to find a statement of discontinued products if needed. Product Line Andover Continuum Environment Obsoleted Continuum Controllers DCX250 DCX 250, Netcontroller CX9000, CX9400 Infinity products Cause Which products are no longer available? Resolution The following link details all products that were discontinued in 2007/ 2008: 2007/ 2008 Discontinued Products Also the DCX250 was obsoleted in 2011 see Product Announcement Discontinuation of Infinity 01-0008-300 (DCX 250) Also see Display options now the DCX250 is no longer available for DCX250 alternatives.  Search for all discontinuation announcements on The Exchange.

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 TAC Vista stopped trending or cannot read trend value. SQL reaches 4GB or 10GB limitation (depending on version, Vista 5.0.1 - Vista 5.1.6 supports up to 4 GB and Vista 5.1.7 and newer support up to 10 GB) $queues folder keep growing Product Line TAC Vista Environment TAC Vista 5 Logging errors SQL data Log full, shrink Cause The SQL 2005 Express version that come with Vista 5.0.1-5.1.6 has a 4GB limitation and the SQL 2008 Express version that comes with Vista 5.1.7 and newer has a 10GB limit. Once the SQL database reaches this limitation, Vista will not be able to read/write data from/into the SQL database. To fix this issue, the SQL database needs to be purged and a new SQL database needs to be created, or the SQL server needs to be upgraded. Once the SQL database is full, log data will be stored in the $queues folder wanting to be written into the SQL database. If the $queues folder gets too big that even creating a new SQL database with the same size limitations will not allow the Vista Server to run then data in the $queues folder will need to be removed or an upgrade to a version of SQL with larger size limits will need to be performed. Resolution Note: In deciding which resolution below will be most appropriate, consideration should be given to how quickly the SQL database is growing and how long it took to fill up initially. When the SQL database fills up it is a perfect time to carefully look at the various trends and alarms that consume space in the database and consider what if anything might reasonably be removed. Also, note Vista 5.1.7 and newer include SQL Express 2008 which has a 10 GB storage limit. This is 2.5 times greater than the SQL Express 2005 version that was included with earlier versions of Vista 5 and is a free upgrade from any Vista 5.1.X versions.   Please find the scenario that matches your issue and read the resolution section accordingly.   Scenario A Scenario B Scenario C Scenario D Data in "$queues" folder Not needed Needed Not needed Needed Data in SQL Db Not needed Not needed Needed Needed NOTE:  Administrator rights on the computer and to the SQL database is required in all scenarios in order to resolve this issue. In order to prevent the same issue occurring again, a log backup should be performed regularly.  Refer to Performing database maintenance with Vista 4.5.0 for additional information. Additionally, consideration should be given to whether an upgrade to full version of SQL should be installed to best suit the needs of the system.   Scenario A: Data in the $queues folder and SQL database are not needed. In this scenario, empty the $queues folder and create a new SQL database is the resolution. Please follow the steps below: Empty $queues folder Go to database folder. Its path can also be found in TAC Vista Server Setup (start->all programs/Schneider Electric/TAC Vista Server5.X.X. For TAC Vista 5.1.3 and prior, go to start->all programs/TAC/TAC Vista Server5.X.X instead).  Under “Vista Database” tab, the path is listed in the “Database folder path” textbox.   Delete everything in the $queues/insertevents folder (NOTE: don’t delete the folder). Delete everything in the $queues/insertlogvalues folder (NOTE: don’t delete the folder).   Delete taclogdata. Go to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data (default path). Delete “taclogdata.mdf” (default name, or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name). Delete “taclogdata_log.LDF “ (default name,  or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name).   Open “Server Setup” (start->all programs/Schneider Electric/TAC Vista Server5.1.X. For TAC Vista 5.1.3 and prior, go to start->all programs/TAC/TAC Vista Server5.X.X instead) and select “SQL Server” tab. Under “SQL configuration”, choose “Custom”.   Under “Custom connect using”, make a new name to “Log database name” (example:  change “taclogdata” to “taclogdata2”). NOTE: DO NOT change the user name and password.   Click Apply Click “OK” for “TAC Vista integrated SQL backup/restore function will not be available in custom configuration”.   Click yes at the prompt that says “No log database was found on SQL Server. Create and configure a log database?"   Click OK. Issue should be resolved at this point.   Scenario B: Data in the $queues folder is needed, but SQL database is not needed. If $queues folder is too big, need to upgrade to a full version of SQL database in this scenario.  $queues folder can be found inside the Vista database folder (refer to Scenario A step 1 for how to find the $queue folder). If $queues folder’s size is not too big do the following: Leave everything in the $queues folder. Data will be written into SQL database automatically after a new SQL database is established. NOTE: depends on the size of the $queues folder, it may take hours to transfer all data from the $queues folder into the SQL database.   Follow Scenario A steps 2-3 to purge the SQL database and create a new one. Issue should be resolved at this point.   Scenario C: Data in the $queues folder is not needed, but SQL database is needed. If the SQL database is needed, it can be removed from the Microsoft SQL Express folder and stored somewhere else. However, an upgraded version of SQL server is needed in order to view the old SQL database.  If the Vista version is <5.1.7Please follow the steps below: Follow Scenario A step 1 to empty the $queues folder.   Move taclogdata Go to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data (default path). Move “taclogdata.mdf” out of the folder to somewhere else (for example: Desktop). NOTE: taclogdata is the default name, or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name. Move “taclogdata_log.LDF “out of the folder to somewhere else (for example: Desktop). NOTE: taclogdata is the default name, or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name.   Follow Scenario A step 3 to create a new SQL database. Issue should be solved at this point.   Scenario 😧 Data in the $queues folder and SQL database are both needed. If the SQL database is needed, it can be removed from the Microsoft SQL Express folder and stored somewhere else. However, an upgraded version of SQL server is needed in order to view the old SQL database. Versions of Vista between 5.0.1 and 5.1.6 (which include SQL Express 2005) can be upgraded to Vista 5.1.7 or newer (which use SQL Express 2008).  This will upgrade from a 4 GB database size limit to a 10 GB limit and is a free upgrade for and version of Vista 5.1. (Note that it is a paid upgrade from Vista 5.0.X.) In scenarios where SQL Express 2008 is already being used and is full or where 10 GB will not be an adequate upgrade for SQL Express 2005 then a full version of SQL Server will need to be purchased and installed. If $queues folder is too large, it will be necessary to upgrade to a full version of SQL server in this scenario.  $queues folder can be found inside the Vista database folder (refer to Scenario A step 1 for how to find the $queue folder). If $queues folder’s size is not too big do the following: Leave everything in the $queues folder. Data will be written into SQL database automatically after a new SQL database is established. NOTE: Depending on the size of the $queues folder, it may take hours to transfer all data from the $queues folder into the SQL database.   Follow Scenario A steps 2-3 to purge the SQL database and create a new one. Issue should be resolved at this point.

Issue After installed I/NET, DBCreate will never pop up to create a new database, which will cause I/NET never launches. Backup and Restore button are greyed out when opening DBCreate, which also will cause I/NET fails to launch. When restoring database, an error will show up, saying that version is incompatible with this server. When restoring the database, an access deny error will show up. Unable to create a backup of an I/NET Seven Database using DBCreate, gets a backup failed error. When restoring I/NET database backup from another server in DBcreate, it shows an error: Error dropping PRIMARY KEY 'PK_DvrServers': Could not allocate space for object 'sys.sysserefs'.'clust' in database 'InetDb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause SQL default instance is not created correctly. SQL2005 BCM is not installed correctly if SQL2008 is used, or there is a database version mismatch for I/NET. This is usually caused by restoring new SQL database to old version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Windows permissions are not enough to do the restoring Functionality of the host pc and the database seems to be inconsistent. If the database size limit is reached, I/NET database will fail to update. The backup of the database will be fine, but when trying to restore onto another computer, it will also fail. Resolution If you are using I/NET 2.4x, and already have a named SQL instance on the computer (for example, TAC Vista 5.1.7 or higher has been installed, with a named instance installed called TACVista), I/NET may fail to recognize it, while also fail to create a default instance. Similar kind of warning will pop up during the I/NET installation: Under this condition, use your current SQL server installer or browse to /SQLExpress folder of I/NET installation CD, to manually create a new default instance. You can refer to the guide within the /SQLExpress folder about how to create it. As long as the default instance is created, DBCreate will pop up immediately and a new database can be created. If 64 bit Operation System is used, refer to Installing I/NET Seven on a 64-bit operating system for the detailed guide. Also refer to Installation guidelines for installing I/NET and Vista on the same PC for more details about installing I/NET and TAC Vista on one computer. If SQL 2008 or SQL 2008 R2 is used, be sure to follow the correct steps about how to install them: I/NET Seven with SQL 2008: I/NET Seven with SQL 2008 Installing I/NET Seven on a 64-bit operating system: Installing I/NET Seven 2.42 or higher on a 64-bit operating system If SQL 2008 is installed correctly, please refer to Data Base maintenance before performing an upgradeto perform a forced upgrade for the database. Refer to Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate: Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate Refer to DBCreate backup access denied using Windows Server 2008 R2 Standard and Microsoft SQL 2008 R2: DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2. Refer to Unable to Create a backup in DBCreate: Unable to Create a backup in DBCreate. Refer to Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached: Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached.

Issue Cannot get the Site license to run after downloading and installing it. Product Line TAC Vista Environment Vista 5.X LMTOOLS Cause TAC Vista 5 license needs to be recognized by the licensing server (FLEXnet License Server). Sometimes, license needs to be set up manually using the LMTOOLS software. Resolution Please follow the steps below to manually read the site license. Stop and close TAC Vista Server, Workstation, etc.   Generate the License file at schneider-electric.flexnetoperations.com and insert the .lic file into C:/Program Files/Schneider Electric/License Files folder (default path, for TAC Vista 5.1.3 and prior, the default path should be C:/Program Files/TAC/License Files) .   Open the LMTOOLS utility from the Start menu: All Programs/Schneider Electric/TAC Tools 5.x.x/LMTOOLS (for TAC Vista 5.1.3 and prior, use path: All Programs/TAC/TAC Tools 5xx/LMTOOLS).   Under "Service/License File" tab, make sure the "Configuration using Services" choice is selected and "TAC License Server" choice is highlighted.       Under "Config Services Tab", ensure the path to licenses file is correct (C:/Program Files/Schneider Electric/License Files, by default). Browse to the folder if necessary by using the "Browse" function. Make sure "Start Server at Power Up" and "Use Service" choices are checked.   Under "Start/Stop/Reread" tab, check "Force Server Shutdown" box. In order click, "Stop Server" (wait a few seconds, there will be no message when the server stops), "Start Server", "ReRead License File". You should receive a message stating the ReRead License File Completed.   Start any TAC application other than Vista Server (for example: TAC Menta). You will be prompted to "Specify the License Server System" or "Specify the License File". Select "Specify the License Server System" and enter the computer name preceded by an "@" symbol. If the License Server resides on the local machine, type "@localhost". Note: In more recent versions of License Server, the "@" symbol is optional. If in doubt, putting it in will work with all versions. If you are NOT prompted to "Specify a License Server" in Step 7, Please follow the instructions in Switching from the Demo license to the site License in Vista 5.1.7 or older. At this point the License should read correctly and the licensed Vista products should execute. If the license continues to fail, reboot the computer and try to open a Vista product again (for example: TAC Menta). If the license if still failing, please verify the above steps again before contacting Product Support. For additional information about the LMTOOLS software. Please go to What options are NOT supported by Signal XP?.