Issue Are the current Veeder Root Xdrivers compatible with the TLS450 and TLS2P console? Environment Xdriver Cause The current Xdrivers are compatible with the Veeder-Root TLS350 Console. Are the current Veeder-Root Xdrivers compatible with the TLS450 and TLS2P console? Resolution No. The current 1st and 2nd Generation Continuum compatible xDriver for Veeder-Root TSL300/350/350R is not compatible with the TLS450 or TLS2P. For the current Xdriver see Leak Detection Systems Drivers on The Exchange  Download Center.  

Issue Valve Datasheet & Catalogue Actuator Datasheet & Catalogue Sensor Datasheet & Catalogue Field Device Datasheet & Catalogue Peripheral Datasheet & Catalogue HVAC Control Devices Selection Tool Environment Actuator Valve Sensor Field Device Peripheral HVAC Control Device Selection Tool Cause Need for valve and actuator information. Need for sensor information. Resolution For European and American Field Device and Valve datasheets/technical publications and catalogues click here to go to the website and select which range that is required. Or the EMEA  sensor catalogue  or the valve and actuator catalogues can be download from the Download Center For the Sensor selection tool click here. For the Heat Meter selection tool click here. For the Cross Reference selection tool click here. 

Issue SmartStruxure with BACnet interface, points from BACnet devices are displayed in a graphic, list view etc, initially everything works fine and the point's value updates normally but after sometime of operation (days or weeks) the value stops updating. Value maybe shown as 0.00 or ... or with a green circle or red X that indicates a bad variable. Environment Automation Server Enterprise Server BACnet interface B3 Third party BACnet devices Cause Software defect in version 1.3 (including SP1) and below. Resolution Please note that if 1.3 SP1 has not been applied it MUST be applied before installing the hot fix. Contact Technical Support to obtain hot fix 1.3.0.11403 Provide site details Apply the hotfix

Issue End connection kits needs to be ordered separately, specified depending on application Product Line Field Devices Environment VZ219E VZ319E VZ419E VZ219C VZ319C VZ419C Cause The end connection kits needs to be ordered separately.  Resolution 1 (one) kit / port  on valve is required, i.e. a VZ219 needs 2 kits, and VZ419 needs 4 kits. See data sheet for details.  

Issue VTState value displays 204 before the phone is answered. When a message is played the VTState goes directly to 301 when it should wait until the message has completed.   Environment I/O Module Continuum CyberStation CX9900 CX9680 Cause The cause of the problem is unknown, but flashing the firmware will typically resolve the issue. Resolution Flash upgrade VT-1 IO to most recent firmware. If the most current firmware is already installed, reflash the unit with the same version firmware. Buildings Business Extranet Software

Issue On a 7718 controller, why do none of the discrete outputs provide 24vdc when energized? Product Line TAC INET Environment I/NET site Cause Using the 7718 controller, why do none of the discrete outputs provide 24vdc when energized Resolution Verify that fuse F9 is not open. (TCON106)

Issue How to configure an exception mode of a TAC Xenta 121 device to use terminal load as the activation input. Environment TAC Xenta 121-HP TAC Xenta 121-FC ZBuilder Cause To use Terminal Load in an Exception mode both the version of ZBuilder as well as the version of the system program of the TAC Xenta 121 device must be taken into consideration.  Resolution TerminalLoad used as input to Exception mode in Xenta 121 ZBuilder version Firmware <1.14 Firmware 1.14 Firmware > 1.23 < 5.1.3 No Yes 1 No 5.1.3 No Yes 1 Yes 2 5.1.4 No Yes 1 Yes 2 5.1.5 or later No Yes 1 Yes 1 Only exception modes 7 and 8 can be used for this; this is done by selecting Space Temp as the activation input for the exception mode and also setting nciAppOption2.bit12 manually in the device (in Vista Workstation this point is Applic.UCPTappOptions2.bit12). These steps are described in TPA-MALR-09-0003.00. 2 Only exception modes 7 and 8 can be used for this; the activation input can be correctly set as Terminal Load in the exception mode in ZBuilder.

Issue Using an End-User Dongle to license XBuilder or Menta when Vista Server is not installed Environment Vista 5.1.7 and older XBuilder Windows XP Menta Cause License may not be able to install due to previous license file conflicts. Resolution Install or re-install the TAC License Program found on Exchange Select Start>All Programs>Schneider Electric>TAC Tools>LMTools (or Start>All Programs>TAC>TAC Tools>LMTools Click on the Start/Stop/Reread Tab Click on "Start Server" Click on "ReRead License File" Close LMTools and Start XBuilder If the option is available, it is preferred to host the license to a MAC address instead of a dongle ID.

Issue Setting up a Xenta 121-HP to properly control a heat pump that has an internal reversing valve control, separate termination blocks for heating and cooling, and an isolation valve. Typically a unit with this configuration is designed to operate with a standalone thermostat that will signal a cooling call or heating call separately depending on the setpoint. A manufacturer in which this specific situation has been documented in the past has been McQuay heat pumps. Product Line TAC Vista Environment ZBuilder LonMaker NL220 Vista Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Cause If the 121-HP is configured in ZBuilder without a reversing valve but still has an isolation valve, it causes the isolation valve to close in certain situations. As seen in the screen capture below, when the reversing valve is unchecked, ZBuilder activates the "Compressor operation" setting box. The choices are either for the compressor to operate in cooling mode or heating mode. If cooling mode is selected then the 121-HP will close the isolation valve in heating mode and vice versa. Resolution There are two options that can be used to allow the 121-HP to control this specific kind of heat pump setup. Turn the 121-HP into a 121-FC Note: Using this method will completely change the controller and all bindings will be lost. It is suggested that the controllers be labeled 121-FC to help minimize future confusion. This method does not allow for a time delay between the isolation valve opening and the compressor command. Instead each goes off of different terminal load levels. Download the latest NXE-APB files for the 121-FC off of the Exchange Extranet. Then download the 121-FC APB file into the controller. Reference Downloading new NXE or APB files using Lonmaker for LonMaker and Downloading new NXE or APB files using NL220 for NL220 download help. Once the 121-HP has been converted into a 121-FC, set the template up with the following settings. Cooling set to On/off Primary heating set to On/of Fan set to On/off The final setting is to create a point that can be used as the isolation valve. Go to the Configuration tab > Free I/O > Function input and activate aux pump function. Underneath the activation, check aux pump active in heating mode and aux pump active in cooling mode. This aux pump feature will turn on whenever there is a terminal load and turn off in the deadband. Use a Relay with Traditional Heat Pump Setup In order to accommodate this type of setup, the following items and settings need to be in place. A relay needs to be installed off of the 121-HP The ZBuilder template needs to be configured in a typical heat pump configuration with a reversing valve present, isolation valve, and a single point dedicated to the heating/cooling compressor command. Under the configuration tab > Application > Valve configuration > Reversing valve, it should be set to a closed contact in heating mode The wiring diagram below is how the unit needs to be wired up to run properly. In this example K1 is the fan command, K2 is the reversing valve command, K3 is the heating/cooling compressor command, and K4 is the isolation valve command.

Issue Using I/NET2000, Can a site change a filemaster setting? Environment I/NET2000 Cause Using I/NET2000, can a site change a filemaster setting? Resolution Not, without difficulty. Setting a pc as a filemaster makes irreversible changes in software. We, in tech support have not found a way to reverse them, short of uninstalling Inet, deleting the root directory, and removing registry entries. Then reload Inet software. See pages 1-12 through 1-14 of TCON 237, Technical Reference Guide for a discussion of filemaster functioning.

Issue Using I/NET Audible Alarms with Remote Clients No audible alarms with Remote Client configuration Product Line TAC INET Environment I/NET Seven Software 2.42 and newer I/NET Remote Client or Remote Client with I/O Server Cause The functionality was changed with the following TrackRecord 5940 fix in I/NET 2.42: Alarms in a Remote Client do not get an audible alarm Only clients configured as "Remote Client w/IO" are capable of routing alarms/events to the server. The masking on clients configured as "Remote Client" will not cause alarms/events to be routed to the server. On these clients, you can use the masking to get audible alarms with no danger of getting duplicate alarms.   Resolution To receive and activate audible alarms on a Remote Client, set the Distribution Group and Masking of the alarm point within AMT.   Note: This setting is only the case for I/NET 2.42 and above.  If this is setting is made in earlier versions of I/NET, it will cause alarms / events / trends to be routed to the server and possibly can cause duplicate events / trends to be sent to the server.  The following information is noted in TCON300: "Limitations to TAC I/NET Seven on Remote Clients   Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features:   Network functions                 Automatic DPU restore                 Archiving                 Dial after edit   Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed." "Limitations to TAC I/NET Seven on Remote Clients" Remote clients configured as “Remote client w/IO” have access to TAC I/NET Seven’s full functionality. Remote clients configured as "Remote client" do not have access to the following areas of TAC I/NET Seven features: Network function Automatic DPU restore Archiving Dial after edit Additionally, for any client configured as a “Remote client”, the mask settings in the AMT Configuration editor and Host Configuration editor are ignored. Only the mask settings on the server or on the client configured as “Remote client w/IO” will control what messages are received in AMT and what data is stored for trends. You can, however, use unique filter settings at each remote client to control what AMT messages are displayed."  

Issue Dumping or reloading a NetController using HyperTerminal. Environment Windows HyperTerminal CX9900 CX9400 CX9200 Command Terminal Configuration Guide Infinity and Continuum Window Interface Cause Not known cause. Resolution Click here for instructions on using HyperTerminal to dump or reload controller.  For full details on using the Window interface as used on Infinity and 1st Generation Continuum controllers, you can download the Command Terminal Reference Guide.

Issue Unable to successfully use Gmail SMTP server to send out alarms via email from I/A Series G3.  Various errors can be seen in the console output. Some of the errors are indicated below but they may not be limited to these. Error: BOutgoingAccount could not dequeue persistent email: 550 The address is not valid java.lang.Exception: Valid CryptoService not found Environment Enterprise Network Server / Enterprise Network Controller I/A Series G3 version 3.5 and above I/A Series G3 maintenance builds version 3.4.55 and above Cause Improper configuration of the EmailService's OutgoingAccount and missing CryptoService in the station. Resolution Procedure and properties settings required when using the Gmail SMTP Server: Add the EmailService and CryptoService to the station's Services folder. If emails are to be sent from an ENC, ensure that the email and crypto modules (and their dependencies) are installed into the ENC. Add the OutgoingAccount to the EmailService. In the OutgoingAccount properties, configure the properties indicated below. Leave other properties as their default settings. Hostname: smtp.gmail.com Port: 465 (this is the TCP port SMTP over SSL uses) Account: example@gmail.com Password: Your Gmail account password Enabled: true Use Ssl: true (Gmail requires SSL) Transport: SMTP Use Authentication: true (Gmail requires authentication when sending out emails) You can test the functionality by right-clicking on the EmailService and selecting 'Actions' > 'Send' to send out an email. If you are still having an issue with authentication, it may need to allow less secure apps to access your Gmail account. Refer to https://support.google.com/accounts/answer/6010255?hl=en for details.  Notes: CryptoService enables the SSL feature in the G3 station. The crypto module is included in the installation of I/A Series G3 version 3.6 but it was not included in earlier versions. You can download the crypto modules for earlier versions of G3 (crypto 3.4.64 / crypto 3.5.34) from The Exchange Download Center. Ensure that the station is licensed for crypto. You can look into your license file to check. Below is an example taken from a demo license. feature expiration="2012-03-31" name="crypto" parts="ENS-DEMO" ssl="true"

Issue Understanding how to check the firmware version of the USB-485-I/NET adapter and upgrade it to the latest version. Product Line TAC I/NET, EcoStruxure Building Operation Environment Building Operation I/NET USB-485 I/F Building Operation Automation Server Building Operation Automation Server Premium Cause If the firmware version of an I/Net USB interface is at an older firmware version then it may need to be updated. Please check the Exchange website for the latest firmware version Note: If the USB adapter is not at least at firmware version 1.02 then the system may experience communication issues in which I/Net values are not updating in EcoStruxure Building Operation or Automation Servers may be dropping offline.  In some cases, the Enterprise Server can lock up due to the older firmware in the I/Net USB adapter. Resolution To download the latest "USB-485-Inet Firmware Update Utility" click here. To Verify the Current Adapter Firmware Version in EBO 2.0 and Higher Right click the I/Net Interface is the System Tree of WorkStation and choose Properties. Down towards the bottom of the Basic tab you will find the Firmware Version.   To Verify the Current Adapter Firmware Version in SBO 1.9 and Lower Connect the USB Interface to a laptop with the USB cable that is attached to the AS-P. Do not hold the pushbutton in on the USB Interface. Run the firmware executable. Press Enter. It will display: "Found USB Device on COMX" and will display the hardware version, software version, and the firmware date. It will then say, "Press Enter to begin the upgrade.  Note: Pressing Enter here will only repeat the hardware and firmware versions. The process to Upgrade the Adapter Firmware Note: If the I/Net USB adapter is already plugged into the laptop from checking the firmware version as described above, then to start the upgrade process USB cable will need to be unplugged from the laptop. Then follow the steps below. While holding down the pushbutton of the I/Net USB adapter, unplug the adapter's USB cable from the AS/AS-P and plug it into your laptop. After it is plugged into the laptop, release the pushbutton.  You will see that the LEDs on the interface are not flashing. On the laptop, run the firmware executable. After the command window opens, press Enter to start the update process. It should display "Unprogrammed device located" followed by "Device programmed successfully". Next, it will say "Found USB Device on COMX" and show the hardware version, firmware version, and the firmware date. Press Esc to close the command window.  The firmware upgrade is now complete. Note: Some laptops will not recognize the USB Interface and will not assign it a Com port.  If this is the case you will still be able to upgrade the firmware.  But instead of giving the Com port the and the firmware version after the upgrade is complete, it will show "Unable to find USB Device".   Also, you would not be able to check the firmware version prior to upgrading as mentioned above.  To correct this you must install the 7801 Tap.inf driver.  Click here to download the 7801 Tap.inf drivers. To install the 7801 Tap.inf drivers: Connect the USB Interface to a laptop with the USB cable that is attached to the AS-P. Go into Device Manager and find the I/Net USB Interface.  It will have an error because of no driver. Right-click on it and choose to Update Driver Software... Select Browse my computer for driver software and browse to the 7801 Tap.inf file. Then follow the instructions above.

Issue Is a controller reload required when upgrading from v1.74 to v1.93 or 1.94 to 2.02? Environment CyberStation v1.74,1.93 1.94 and 2.02 NetControllers, Infinet controllers Cause We will be performing an upgrade on a site from v1.74 to v1.93. or  v1.94 to 2.02 Do we need to reload every network controller? Resolution In this case it is not a requirement of the CyberStation upgrade that dictates if a controller reload will be required. However, in order to keep the CyberStation and controller versions compatible, a flash upgrade of some controllers may be required. (Refer to Continuum Software and Firmware Compatibility Matrix)  The process of doing a flash upgrade usually requires a reload and is generally a good idea. There are some cases where a minor version upgrade (for only a bug fix, for example) in a controller with a valid flash backup will not require a reload because the controller will reload itself automatically from flash. Even if you think a reload is not required make sure you edit a few objects in the controller after the flash upgrade. If you get an error that the object cannot be found, reload the controller and then do a flash backup. Additionally, a planned "outage"  is a good opportunity to reload a controller that may not have been reloaded in a while. It would be better to know right after the upgrade if there is a problem, than to find out after you leave the site. The Infinet controllers typically do not need to be reloaded - but make sure you test a few infinet controller alarms on all upgraded network level controllers.  

Issue Upgrading an AS results in an empty database. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 StruxureWare Building Operation 1.1.0.362 to 1.2.0.767  Cause When upgrading the database, the Enterprise Server (ES) upgrades without error, but when upgrading the AS, the result is an empty database. Resolution StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 The problem is caused by the initial engineering of the system being carried out on an old AS that was not LON or BACnet specific, copying into new hardware at R1.0 then when upgraded to R1.1 the upgrade fails due to the wrong type of AS being used (LON or BACnet). This practice is not common place and rather rare. When the trace log is examined, they find that the upgrade fails due to the fact that an illegal object type is attempted to be created – a BACnet interface. This is not legal in an AS-L. The reason that this occurs is that the backup file is from an AS-L that had been restored from a 1.0 AS-B backup file. Check New Release or Upgrade StruxureWare Building Operation Site Software. The issue you face could possibly be a procedural one and this article clearly defines the steps. StruxureWare Building Operation 1.1.0.362 to 1.2.0.767 The solution is identifying problems with a period, space, or other character in names. Placing a period at the end of a name or accidentally having a space at the end is suggesting something is following or further action. If using BACnet, please see the note below. Problems with bindings which were still in tact when values were removed also are a potential issue and not properly removed.    Work Around: Backup AS Upgrade PC to 1.2 Open Device Administrator Upgrade AS to 1.2 DO NOT close Device Administrator Open StruxureWare Workstation Log into AS If Database is Blank go back to Web Browser Connect to AS Log in In the top right hand corner of the screen select Setting>Device Configuration Select the Server Log tab Click “Get all log files” Once downloaded, open “trace” using Notepad Click Edit>Find Type the word “nsp.csc.UpgradeManager ERROR:” The error lines run from date stamp to date stamp so isolate the line beginning with the year and ending with the next instance of the year. Here is an example: 2012-08-29 16:39:32.990 [32] nsp.csc.UpgradeManager ERROR:    Error Parsing Dump Objects:  RecoverableException: source/Path.cppy) ) Error: Invalid_Path (0x10001), module Coml(11), moduleCode 0, dispString "Heatsink Temp.", techString "Path& Path::Append(const UTF8String& name)"  The “dispString “_______”” section of this line will give you the object name that contains an illegal character. Downgrade the AS back to 1.1 Locate the dispString object and change the name so that it does not contain any illegal characters. This is typically a name ending in a period. NOTE: when the rename dialogue pops up, it will indicate that an illegal character is present to confirm you are modifying the right object. Backup the AS Re-Upgrade the AS to 1.2 If the upgrade fails, repeat steps 9-20 or call product support. Be prepared to provide a Db backup at 1.1 as well as the trace file from the 1.2 failed upgrade. BACnet Note: A BACnet device including an object name "East Duct Max." is no longer valid because of the illegal character at the end of the name. Before upgrading the ES from 1.1 to 1.2, remove any full stops/periods from any object names. "East Duct Max." is changed to "East Duct Max"  Other illegal characters include *°?|/"<> or ~ and an object cannot begin or end with a white space or period. Select TPA-SBO-12-0008.00 - ES upgraded from 1.1 to 1.2 loses database to review this TPA.

Issue Upgrading a Xenta 102-AX to v 2.16 Product Line TAC Vista Environment Xenta 102-AX LonMaker NL220 Cause Firmware upgrade Resolution The following instructions will describe the firmware upgrade process for three different LNS environments: LonMaker 3.1, LonMaker Turbo 3.2, and NL220. The NXE, APB, and XIF files for upgrading the 102-AX are now available on The Exchange Download Center. Preparation   Always remember to make backups before beginning this process. Record the Neuron IDs for all Xenta 102-AXs that will be receiving the upgrade. If you do not record the Neuron IDs ahead of time, you will have to press the service pin on every controller being upgraded. A list of all Neuron IDs can be obtained in one of the following ways: Through TAC Vista Server Open TAC Vista Server Click on Reports > LonWorks Networks, Survey   This process will open a .txt document which lists all controller names and Neuron IDs in the Vista database. Through Echelon LNS Utilities Navigate to Start > Programs > Echelon LNS Utilities > LNS Report Generator Select the LNS Network   Hit Generate   This will generate a .csv file in the designated location with controller names and Neuron IDs. This can be viewed using Microsoft Excel. Through NL220 Choose either Subsystem or Channel view Depending on the view, right click either on the Subsystem or the Channel Select Print > Print list of nodes Select Export   Choose desired file format Hit OK If changes have been made to the configurations of the 102-AXs through any means other than the LNS plug-in (I/STAT, M/STAT, Vista Workstation) these parameters will first need to be uploaded to the LNS database. If this step is skipped, then any configurations made this way will be erased during the upgrade. In LonMaker 3.1 Right click on a device Select Resynch CPs... Repeat for each 102-AX In LonMaker Turbo 3.2 Right click on a device Select Commissioning > Resynch CPs... Repeat for each 102-AX In NL220 Right click on a device Select Copy configuration values in memory Repeat for each 102-AX Download the NXE and XIF files for version 2.16 from The Exchange Download Center. Please note that during the upgrade process, the 102-AX will not function properly. In a multiple LIP or router database the dummy database can be created on a notebook PC. This allows for a local FT10 connection to the Lon network after the router. The existing network topology is not needed on the dummy database in this case.   Performing the Upgrade in LonMaker 3.1 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch LonMaker Select New Network Set the new network to be Online and Network Attached. Do not register any plug-ins. Add a generic device *Note: The network has to represent the topology of the physical connection to the FT-10 channel Check Commission Device box, hit Next.   Load XIF. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit Next.   Specify channel. Hit Next.   Default Properties selections are okay. Hit Next.   Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you planned to service pin the controller, select Service Pin. You will be prompted at the end of the process to service pin the device.   Check the box for Load Application Image. Browse to the v2.16 NXE downloaded from Exchange Online. Hit Next.   Set the desired state to Online. Set the Source of Configuration Property Values to Current values in device. This is an important step. If you do not set to current values in device, your previous configuration parameters will be erased. Press Finish to begin the download.   Allow approximately 50 seconds for the application image to finish loading. While you wait you will see this window.   To upgrade the next 102-AX, right click on the device and select Replace. Repeat these steps for each 102-AX in the system. Performing the Upgrade in LonMaker Turbo 3.2 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch LonMaker Select New Network Set the new network to be Online and Network Attached. Do not register any plug-ins. Add a generic device Check Commission Device box, specify channel, hit Next.   Load XIF. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit Next.   Default Properties selections are okay. Hit Next.   Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you planned to service pin the controller, select Service Pin. You will be prompted at the end of the process to service pin the device.   Check the boxes for "Load application image" and "Update firmware in device to match application image." Browse to the v2.16 NXE downloaded from Exchange Online. Hit Next.   Set the desired state to Online. Set the Source of Configuration Property (CP) Values to "Application image file." Set the Device Specific CPs to "Preserve device values." This is an important step. If you do not preserve device values, your previous configuration parameters will be erased. Press Finish to begin the download.   Allow approximately 50 seconds for the application image to finish loading. While you wait you will see this window.   To upgrade the next 102-AX, right click on the device and select Commissioning > Replace. Repeat these steps for each 102-AX in the system. Performing the Upgrade in NL220 It is not possible to upgrade a 102-AX in an existing database. To upgrade a 102-AX, a temporary "dummy" database must be created. Launch NL220 Log in and create a New project. Do not register any plug-ins. In SmartChannel, set the new network to be Attached. Under the Device Templates tab, right-click and select New Device Template. Create the New Device Template from interface file. Browse to the downloaded v2.16 XIF file (not the standard XIF, but the v2.16 downloaded from Exchange Online). Hit OK.   On the Channel tab, right-click and select New node on Name the device and choose Create node from a device template. Select the newly created 2.16 device template. Uncheck Set all configurations to manufacturer's default.   Right-click on the new device and select Install (network > commission in newer versions). Set the Neuron ID. If you recorded them in a report previously, manually enter the data here. If you are going to service pin the controller, do it now.   Right-click the device and select Download program. Choose Upgrade system version. You will receive a warning stating that upgrading the system image can leave the device in a bad state and break communication. You should only use this option if you are sure of what you are doing. Confirm, Yes, you want to continue. Configuration download should be set to Keep current configuration on node.     Allow approximately 50 seconds for the application image to finish loading. To upgrade the next 102-AX, right click on the device and select Network > Replace. Repeat these steps for each 102-AX in the system.

Issue Upgrading Vista when using Windows XP Service Pack 2 Environment TAC Vista Server Windows XP SP 2 Cause If you upgrade the version of Vista on a properly working machine you will be required to repeat some of the steps. Resolution TPI C-88-1-F57 indicates the steps needed to make Vista run on a Windows XP SP 2 operating system. However if you upgrade the version of Vista on a properly working machine you will be required to repeat some of these steps. The first step you will need to repeat is the exclusion of Vista Server (TACOS.exe) in the Windows Firewall detailed in step 3 found in section 3 of the TPI. This is due to the fact that the installation of the latest versions of Vista includes the revision in the installation directory. The second step is step 4 found in section 4 of the TPI. The DCOM settings for TACOS must be reconfigured to use default Launch and Activation Permissions. The reason for this is the same as described in section 7 of the TPI when configured Vista Server to run as a service or not.

Issue Upgrading Reports Server from 1.4.1 to 1.5 Environment StruxureWare Building Operation 1.5.0 Windows Server 2008 R2 Reports Server WebReports Enterprise Server Warning Cause Failure to follow upgrade guides may result in data loss. The most likely point of failure seems to be running the Reporting Agent Service on the Reports Server while upgrading the Enterprise Server. The Upgrade will error out if SQL2008 R2 is not upgraded to SP2 or .NET framework is not upgraded to 4.5 at the indicated points. Resolution This resolution process was developed from the System Upgrade Reference Guide and tested on a single PC. Windows Server 2008 R2 at StruxureWare Building Operation 1.4.1 running SQL2008 R2 SP1 and .NET 4.0 upgraded to StruxureWare Building Operation 1.5.0 SQL2008 R2 SP2 and .NET 4.5.  You can find and download all 1.5.0 released software and documentation by searching the Building Download Center for the tag "relsbov1.5" Backup Enterpriser Server, All Automation Servers and Report Server. Store backups on external media. If desired, create a Windows snapshot for a quick return point. Download all StruxureWare Building Operation 1.5 Installation files, SQL2008 R2 Upgrade files and .NET 4.5 installer. Close all StruxureWare applications In the Windows Server Manager, Expand Configuration and Select Services Browse to “StruxureWare Reporting Agent”, right click on it and select stop Open Software Administrator and stop the ES service. Close Software Administrator In the Windows Server Manager - Services section, stop the service “Building Operation 1.4 License Server” Run the .NET 4.5 installer. If prompted to restart, select Restart Later. If the PC restarts on its own, verify that all services listed above are stopped before moving forward. (repeat on all PCs) Run the License Administrator 1.5.0 installer Run the Enterprise Server 1.5.0 installer; select the Upgrade current version option. Note the ports used. Port 80 should not be used for http communication when the ES is installed on the Same PC as the Report Server. If desired install the Project Configuration Server.  Be sure that the HTTP port is not the same as what is used for the Enterprise Server and not port 80 Open Software Administrator and verify that both the Enterprise Server and PCS are running and using different ports Install Workstation. If you are upgrading from 1.4.1 to 1.5 and planning to delay the upgrade of the Automation Servers, you should install Workstation in parallel instead of upgrading Install Device Administrator. If you are upgrading from 1.4.1 to 1.5 and planning to delay the upgrade of the Automation Servers, you should install Workstation in parallel instead of upgrading At this time, upgrade any required Automation Servers. If upgrading from 1.4.0, all AS must be upgraded together. Install any required language packs If required, download and install the SQL2008 R2 upgrade to SP2 : http://www.microsoft.com/en-us/download/details.aspx?id=30437The default file name for the upgrade installer is SQLServer2008R2SP2-KB2630458-x64-ENU.exe In Windows Control Panel, go to Programs and Features Uninstall the “Building Operation Reports Installation” application only. This is the installer application for 1.4 Web Reports Run the Reports Server 1.5.0 installer Browse to C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation Reports Installer Right Click on SE.SBO.WebReports.Installer and select “Run as Administrator” For Setup Type, select “Upgrade both software and database” Fill in site specific information as instructed. For Reporting Agent, be sure to specify the exact Enterprise Server Address and port used. Follow the remaining prompts to install WebReports On completion, log into the StruxureWare WebReports interface and run a few test reports.

Issue When upgrading EcoStruxure Building Operation to version 2.0 or newer, the existing Power Manager software should also be upgraded to EcoStruxure Energy Expert to maintain compatibility Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Power Monitoring Expert (PME) Power Manager 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 proper procedure is required when upgrading from older versions of Power Manager to the latest Energy Expert version. Guidance and best practices are needed for upgrading a PME server from PME 7.2 to PME 9.0. Resolution A Power Manager 1.0 site should be taken to 1.1 first, then upgraded to Energy Expert 2.0 Below are the recommendations for a side-by-side upgrade from PME 7.2 to PME 9.0: On the old server: Run the PME_8.2.iso file to do an in-place upgrade from PME 7.2.3 to PME 8.2 After completing that upgrade, the system will default to using a PME 8.2 trial license Install and run the PME 8.2 CM 2.1.0 Tool which will perform necessary actions for the side-by-side upgrade; we will use it to create a .zip file containing configuration components such as reports, dashboards, diagrams, users, devices, etc. Transfer this .zip file from the CM Tool to the new server On the new server: Run the PME_8.2.iso file to install PME 8.2 (this can be done while the above steps are performed on the old server) After transferring the .zip file from the old server, install and run the PME 8.2 CM 2.1.0 Tool on the new server and have it load the archived data from the .zip file into the program, and then write it to the system (essentially performing a PME 8.2 server to server migration) After that finishes, we can run the PME_9.0.iso file to upgrade from PME 8.2 to PME 9.0 After PME 9.0 is installed, we can activate the PME 9.0 license(s) in the Floating License Manager using the activation ID(s) that were already acquired, then remove the PME 9.0 trial license using License Manager (different from Floating License Manager) Running into issues with the install? Receiving error messages related to PME? Check out the Technical FAQ for a solution to your problem.  Links to relevant documentation and files: Where can I find documentation for Power Monitoring Expert 8.2 (PME 8.2)? Where can I download Power Monitoring Expert 8.2 installation files? Where can I find documentation for Power Monitoring Expert 9.0 (PME 9.0)? Where can I download Power Monitoring Expert 9 installation file? PME 8.2 CM Tool Exchange Community post  PME 9.0 CM Tool Exchange Community link