Building Automation Knowledge Base

Issue While Continuum controllers and EcoStruxure controllers do not utilize Power over Ethernet (POE), can plugging in a Continuum or EcoStruxure controller into a POE switch damage either the POE port or the controller? Product Line Andover Continuum, EcoStruxure Building Operation Environment PoE Ethernet Cause Controllers must be installed on a subnet served by a POE switch. Resolution According to the IEEE standard, a POE switch shall determine if the connected device is POE capable before turning on the power. The detection if a connected unit is POE capable is done by measuring the resistance between the pair #2 - #3 and pairs #1 - #4. On a POE capable unit the resistance is 25kohm, with some tolerance. If it is lower or higher it is not considered to be POE capable. As there are no Continuum or EcoStruxure ethernet controllers that apply a 25K ohm load, a properly functioning switch port will not enable PoE power and the device will not be damaged. Find information on the PoE standard in the Fundamentals of Power Over Internet (PoE) PDF

Issue Is BAS2800+ compatible with Windows Vista or Windows 7 or higher? Product Line Satchwell BAS2800+ Environment Windows Vista Windows 7 Windows 8 Windows 10 Cause What Windows version can BAS2800+ version 2.9 and 2.10 run? Resolution Officially BAS2800+ version 2.9/10 has only been tested on and therefore is only officially supported on Windows NT, Windows 2000,Windows XP and Windows 2003 Server it has not undergone any official testing in Windows Vista or Windows 7. If BAS2800+ software is to be installed on a Windows Vista or higher, the customer should be warned that BAS2800+ has not been tested under that environment. Any issues identified would be their responsibility, Schneider Electric would not accept any liability for any issues encountered. It may be possible to run BAS2800+ using Windows 7 XP mode, however this is also not tested or supported, the best option would be to downgrade the computer to Windows XP. It should also be noted that BAS2800+ was discontinued in 2008 and no further effort will be made to update or test the product against newer operating systems.

Issue CX level controller was once online and now appears as offline Product Line Andover Continuum Environment Continuum Netcontroller CX ACX BCX Cause From time to time issues will be reported that controllers are offline at the IP level. Resolution Troubleshooting steps to perform:   From one of the existing sites Cyberstations perform a ping of the controller. If there are responses, verify that the response is from the controller and not another device. Verification of the response can be done via Wireshark capture if the CX appears to be responding. If there are responses to the ping, then attempt to open up the web-configuration page for second generation controllers. Verify the site’s Cyberstation is online itself. (Right-Click/edit the workstation and view the Comm Status. It will be either Online or Offline.) With CyberStation installed on technician’s laptop with the same version as the site version. Plug an Ethernet cable into the same hub the controller is plugged into. Connect to the site database with the local laptop's CyberStation and start Continuum. Check the controller in Continuum Explorer to see if it shows offline to the local laptop's CyberStation. If the controller is online to the local laptop's Cyberstation, then it is clearly a site network issue. At that point we will need to make sure all the IP address info is correct; there is no port blocking, subnet masks, gateways etc… Standard network troubleshooting. If the controller shows offline to the local laptop's CyberStation, then look at the CPU lights on the controller for activity. Watch the link light, CPU, IO bus lights if there is IO modules, etc… If those look abnormal and you have a smart phone it will be worthwhile to try and get a video of them to send into support for review. If there is no link light then try disconnecting the Ethernet cable from the NETWORK SWITCH and plug it back in to check if it brings the controller back online. If that does not bring the controller back online try disconnecting the Ethernet cable from the CONTROLLER and then immediately put it back and check if the controller comes back online. If all of the above fail then the next step will be to power cycle the controller to try and bring it back online. If communications cannot be established, contact support and open up a case for additional troubleshooting to determine if the controller needs to be sent to repair. If communications is restored and further investigation is required, please retrieve the following information and open a case with support for review. Controller error log Controller offline listview exported to CSV A Wireshark LAN capture at the controller level with peak traffic occurring Additional information may be requested including a controller core dump. This is a very intensive process. Support will supply the Core Dump Utility if needed.   Please click HERE for a copy of these instructions in PDF format.

Issue What kind of preparation must be done prior to upgrading a Continuum LAN system? Environment Continuum Cyberstation SQL Server Cause Continuum Upgrade Resolution Study the Continuum Compatibility Matrix and the Continuum Video Compatibility Matrix.   Plan the upgrade of supporting software applications and hardware using the Continuum compatibility matrix as your guide.  .Net versions and SQL versions must be compatible with the final version of Continuum before you begin the upgrade process.  Older CX controllers (with firmware <= 1.500029) use a different algorithm for defining handles so they should be up-rev’d prior to the upgrade process.   For all other controller the controller firmware can be upgraded after the front end systems upgrade has been completed.    The upgrade process presents an opportunity to make an assessment of all computer hardware that is currently being used in order to make recommendations for upgrading hardware.  This is especially important with respect to the Continuum Database server.   Selecting the right server is a process that involves determining the customer’s needs and defining the systems requirements.  This is an engineering decision that is beyond the scope of Product Support Services.  The customers IT department will likely be involved in this process also.  When are adding a new database server, it may be advantageous to build your Continuum server and prepare the Continuum database off-site. Completing a Continuum LAN system upgrade is a complex process and not something that you can accomplish simply by following a step list. It is crucial that an engineer who is experienced with the Continuum LAN upgrade process on site to direct the upgrade.  This is both to ensure that the upgrade process is handled correctly and to mentor technicians who will be involved in future upgrades on LAN systems.

Issue Since both products -- Xenta programmables and the UNC 520 -- speak LON protocol, there is some assumption that integration should be seamless.  In the case of ASCs, this is true, but Xenta programmable controllers use some forms of proprietary communication that can complicate the integration. Product Line TAC IA Series, TAC Vista Environment Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B UNC-520 Niagara Tridium Cause Xenta programmables use proprietary communications for three main purposes: To communicate their online status between group members and group masters To communicate between a base unit and associated I/O modules To pass proprietary TAC Network Variables between two programmable controllers In a UNC-520, the first function would be taken over by the new network manager (Local Lon Device).  However, the second two must use Group Bindings set through a Vista compatible network management tool like LonMaker or NL220.  If the controllers are commissioned into the UNC-520, that communication will be broken and I/O modules will go offline and no network variables will pass. Resolution  It is possible to engineer a TAC Vista network as usual, using an LNS management tool to create group bindings to facilitate proprietary communications.  A UNC-520, set to non-network management mode could then be implemented on top. However, any attempt to commission the devices into the UNC-520 network will break that proprietary communication.  To prevent this scenario from occurring, the simplest method is: Do not use proprietary TAC Network Variables to pass data between controllers. Use only SNVTs which will be available to a third party LON network manager like the UNC-520 Make no SNVT bindings in a temporary LonMaker or NL220 database.  Let the UNC-520 handle all network management duties. Do not define Xenta I/O modules in the Menta Device Specification. Use only Xenta 421A, 422A, 451A and 452A I/O modules.  These have the capability to act as stand-alone LON nodes. Define the modules as LON nodes, configure them using Configuring inputs on Xenta 421A or 451A when using the controller as a stand alone Lonworks node. Bind to the inputs and outputs of the I/O modules in the UNC-520.

Issue Need to edit StruxureWare Building Operation Reports Product Line EcoStruxure Building Operation Environment SmartStruxure Report Server Report Builder 3.0 Cause Users wish to directly edit or create customized versions of existing reports. Resolution Open Microsoft Report Builder In the Menu, Select Options Change the database path to "http://localhost/reportserver_SQLEXPRESS' Where localhost is changed to the PC name or IP address and SQLEXPRESS is changed to the installed instance of SQL Click OK You can now open existing files on the server and save new files directly to the Reports Server. You must Synchronize the StruxureWare Reports Interface for newly published reports to be available from the StruxureWare Interface.

Issue Memory and System Memory in the AS Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause What is the definition of the two different memory types shown in the AS? It is not clearly defined in the documentation. In various places, one can see Memory and System Memory, or even add a column to show.  Resolution For the AS, System Memory is the RAM used by the AS Linux OS. The rest of the memory is what is being used for the processes, such as programs, trends, etc. Memory is the amount of memory consumed by the AS (nsp_servers application), system memory is that used by the Linux OS, however there is much debate about how this is calculated and allocated, so too much should not be read into this, it is there primarily for developers.

Issue Direct Connect Xenta 527-NPR or 527 Web Server through I/NET Environment I/NET site Cause Direct Connect a Xenta 527-NPR or 527 Web Server through I/NET Resolution Are you using a Xenta 527-NPR or 527 Web Server and want to direct connect to it through I/NET and not having any luck? There are a couple of things that you need to set up in the unit for serial communication to I/NET through Port A (RS 232). The Xenta 527 NPR is set at factory default (RS232 Port A). The following steps should get you through this: Start I/Net and create a profile for the NPR (Net Plus Router) in I/O Server, then make this active. Verify that you have the correct cable to hook up from the serial port of the PC to Port A (RS 232) on the unit. (L1: RJ45 to RJ45 part # 0-073-0817). Connect them together. At this time you will need to start X Builder, if you don’t have it already, then you need to download it from the Exchange Extranet. The path is TAC Vista > Engineering Tools > TAC XBuilder > TAC XBuilder 1.5 (or latest revision). Download this to the PC. Start XBuilder through Programs > TAC > TAC Tool > XBuilder. Once started, select File\ New Project\(Project Name)\Location (default)\Project Template (select 527 Project), call it 527 NPR or whatever makes sense to you. At the settings Editor, just hit the OK button. Once the Editor comes up, in the Network frame, expand the TAC_Xenta_527. Right Click on the RS232-485A selection, click on Add then select I/NET. If you click on the TAC_Xenta_527, you will see all the settings that you have originally set up through Hyper Terminal or you can put those in at this time. Now select the Generate Icon or press F10 to generate the file. In the bottom of your project you would see a message that says Xbuilder – 0 error(s), 0 warning (s). This indicates that your project is now complete without errors. Now select the Rocket Ship Icon or press F11 to transfer the file to the unit. Once completed, restart or cycle power on the 527. Go to I/Net\Edit\Host Computer\Network Configuration and your 527 will show up in the Link Summary. At this time you can save the link, penetrate it and save the controllers etc. the old fashioned way. At this time you should be able to work on your system through a direct connect on a Xenta 527 NPR/Webserver unit.

Issue Problems receiving emails from Xenta 511/527 Product Line TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause Some email servers have been found to filter UTF-7 character encoding as spam. The Xenta products require this encoding to support Swedish characters, but this can be configured by manually editing some files. Resolution Use an FTP program (Internet Explorer) to connect to the Xenta you are trying to change and download the \sys\langstring.cfg file. Edit the file and modify the following lines to replace all instances of 7 with an 8: ALARM_CODE_1= =?utf-7?Q? ALARM_CODE_3=charset=UNICODE-1-1-UTF-7 Upload the edited file back to the Xenta device Cycle power The device will now use UTF-8 character encoding which is more commonly used in the United States. For more troubleshooting tips, see Troubleshooting sending emails from a Xenta Server.

Issue When launching a Access Expert on a Premise install, an error "Unable to retrieve license. Please notify your Keep service provider" when trying to log on to the instance. Product Line Access Expert Environment Access Expert Wondows 7, SQL 2012 SQl 2014 Cause Keep does not have access to the database for license information. Resolution Install SQL Studio and give NT AUTHORITY\SYSTEM sysadmin rights. The following captures shows where to go to enable this in SQL. Connect to SQL, go to the Security Folder and expand it, select the Logins Folder and expand that then select the NT Authority When the tab opens select the Server Roles, then check the box for sysadmin.

Issue Generating a Xbuilder project results in the error message "The size of the generated project is xxxx KB, which exceeds the maximum size 8192 KB". Environment Xbuilder 5.x.x Cause The generated project size exceeds the maximum limit due to the following reasons: The project contents made up of graphic pages, inserted networks (LON, I/NET, etc), large images (BMP, GIF, etc), or imported files in the UserTargetImage directory cause the project to exceed the limit. The option "Send Project backup file to target device" is checked and this causes pushes the project size over the limit. Resolution Generate the Xbuilder project to see how far above the limit the project currently is. Open the Project\Settings and uncheck the "Send Project backup file to target device" and regenerate the project to see the difference in file size. If the size difference is significant then check for large files in the project directory that should not be sent to the device such as project or device documentation files such as PDFs. Remove these files from the Xbuilder project directory and generate the project again.  Search the Xbuilder project directory for the largest size files such as graphic pages and try to find way to reduce the size by converting background image formats that will result in smaller file sizes. Example convert BMP file to PNG or JPG format.

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 A third party BACnet system is able to host  values from a SmartStruxure Lite MPM but an MPM does not seem able to host values from another BACnet system or device. Environment BACnet MPM-VA MPM-UN MPM-GW Cause SmartStruxure Lite Managers have full BACnet server capabilities, however BACnet client functionality is not native to the MPM and is currently only available through Lua programming. Resolution Integrating SmartStruxure Lite™ Managers with third-party BACnet server devices requires a BACnet client script. A sample script (download here) can be used to perform read and write operations to other devices via BACnet IP, however, a few tips and limitations must be taken into consideration before deployment on site. NOTE1: The delay at the beginning of the script (if scl.sysclock() > 90 then) must not be removed or modified. Otherwise, the MPM will keep rebooting endlessly and would require restoring its factory defaults before gaining access to Building Expert again. NOTE2 : The more points used in the script, The higher the MPMs CPU% Usage will be and the less responsive the MPM will be. Therefore, it is recommended to only read/write the necessary points and not all the points on the third party devices. Also, if some points are more important that others, the polling time can be increased to 60 seconds for example.   NOTE3: The more objects you have on the MPM, the less room you have for BACnet points. PGs, Trends and Events consume a substantial amount of CPU Usage so it is important to keep an eye on it as you add more points in the script.   NOTE4 : Run the script every 5 seconds or more if possible   Limitations: - Reading/Writing to Multi State Values (MSV) is not supported

Issue The Enterprise Server enters a restart loop filling the hard drive with crash dump (dmp) files Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause This happens due to corrupt backup sets from AS being present. To make a quick check if this is the issue, rename the following folder replacing x.x with the version you have installed. C:\ProgramData\Schneider Electric StruxureWare\Building Operation x.x\Enterprise Server\db_backup\ASArchives If the ES starts after that, identify the faulty backup sets as described below. Resolution Browse to the AS backup folder (see above in "Cause") Detect backup sets not looking correct e.g. having a size of 0 KB Delete these backup sets   From version 1.7.0 and forward, these backup sets are automatically removed

Issue BACnet Input shows "Out of Service". When attempting to set a value or remove the out of service flag an error is seen. "An attempt has been made to write to a BACnet property with a value that is outside the range of values defined for the property." Environment bCX4040 b3 Controllers Cause An xP Module attached to the Controller was malfunctioning and the inputs on this board were not functioning. Resolution Powering everything down, re-seating the xP Module board and powering the Controller back up resolved the problem.

Issue After setting up an SSC controller, it does not come online even after multiple Resets and putting it into DFU Mode. Product Line Access Expert Environment Access Expert Windows Server 2012 Cause The device was previously set up, maybe at the office. Now, when taken out to site, it shows that it already exists on another instance. Resolution Open up the initial instance that it was set up on Right click and Delete the device Open up the new instance that it will be current on If already created, then communication should start automatically Once online, program accordingly

Issue Can't get the a Sigma laptop to communicate with a Sigma controller via the RS-232 connection (Diagnostic Port SK1). Environment Sigma RS-232 Communications Serial Communications Local Communications Service port Cause Configuration error Resolution Use the following check list to confirm correct configuration. On the main Sigma server Create a service server in the main server and ensure the Att.set files are downloaded to the controllers On the laptop Set the C:\Sigma\Data\Sigma.ini file entry RS232 = 1 Set the C:\Sigma\Data\Sigma.ini file entry Commport=1, Baudrate=9600 (Note: ensure the BAS Integrator is not enabled as it also set for Comm port 1 by default) Set the laptop server number the same as service server number in item 1 above (System Setup -General - Server Details). Restart the laptop Sigma server If you are using Sigma 4.05 build 3.42.34 then you need a Hotfix to enable the Sigma serial communications.  Click here for Hotfix 3.42.46.  Later Sigma releases do not require a hotfix. Confirm the RS232 cable wiring is correct and not broken.

Issue How can the AS-P be used as an LPA interface? Product Line EcoStruxure Building Operation. Environment Building Operation Automation Server Premium. Cause Working with Loytec LPA in  Building Operation and needing a remote interface for connectivity. Resolution To configure the AS-P as an interface in Loytec LonWorks Protocol Analyzer (LPA), follow the steps below: Ensure that you have the Loytec LonWorks Protocol Analyzer (LPA) software installed and licensed. Activate the AS-P as an LPA interface: Access the Loytec LonWorks Protocol Analyzer (LPA) software. Locate the settings or configuration section. Enable the option to "Activate AS-P as LPA" to designate the AS-P device as the interface. Add AS-P as a remote network interface in LPA: Within the Loytec LonWorks Protocol Analyzer (LPA) software, navigate to the network interface settings. Look for the option to "Add AS-P as Remote Network Interface" and select it. Keep in mind that by using the AS-P as the LPA interface, you will only be able to capture and analyze the traffic addressed to or from the AS-P device itself. Network traffic between other devices on the LonWorks network may not be captured using this configuration.   It's important to have the Loytec LonWorks Protocol Analyzer (LPA) software installed and properly licensed to perform these steps.  

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 When doing a LonMaker resynchronization, the operation fails on a certain subsystem or when doing a commission on a controller in Lonmaker an error is displayed: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102) Environment LonMaker 3.X Cause If re-commissioning or downloading and commissioning a controller in LonMaker fails or times out, this issue may crop up. LonMaker assigns the desired neuron ID to a temporary device while performing either of these commands, and if the operation fails, that temporary device will get stuck in the database with the same neuron ID as the controller the user was working on. A successful resynchronization will bring this "phantom device" to light where it can be deleted, but if it is the resynch that is failing, the steps below detail how to remove a neuron ID from a device in the LNS database so it can be deleted. Resolution Try to do a resynch command in LonMaker to get the temporary device to show itself on the Visio drawing. If this works, then the temporary device will show up with a randomly generated alpha numeric name on the same page as the controller you were trying the commission or download. After the resynch completes, delete the device from the page and repeat the commission or download. If the resynch operation fails with: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102), continue. Because the temporary device is in the LNS database, but not on the LonMaker Visio drawing, manual manipulation of the LNS database is required to remove this object. This is done with the LNS Object Browser. First, shut down LonMaker, then click START and chose RUN in Windows and type lnsobjectbrowser and click ok. The Startup Preferences are shown. Set the Client/Server Communication to Don’t change and the Local Network Access to Engineering Mode and then click Ok. After choosing settings in the Startup Preferences menu, the LNS Object Browser is displayed. Press F8 to take the object browser out of read only mode. Browse to the following: ObjectServer/Networks/Your_Network_Name/Systems/ Your_Network_Name/Subsystems/All/AppDevices. Note: Double-click to open each object. Within the APPDevices menu you will see the temporary device with the large alpha-numeric name. Double-click this device to get its properties in the right hand window. Double-click on the NeuronId line in the properties pane of this device and manually set the Neuron Id to 000000000000 (12 zeros) and click Ok. Exit out of the LNS Object Browser and re-open the LonMaker database. Perform another resynchronization of the database, and the suspect temporary device should now show up on the LonMaker drawing. Then, delete that device and re-attempt your work on the original controller.

Issue Description of the file types and file extensions in Menta. Environment Menta Vista Lonmaker .AUT, .TLG, .MCB, .COD, .XLG, .ESP, .OPE, .OPC, .ESP, .BIN, .CHR, .COD, .XIF, .MTA, OPDOC.GOP, .SPT, .BIN, OPDOC.SPT, OPDOC.TMP, .BPR. Cause Description of the filetypes in Menta. Resolution The following data files are involved when creating a Menta application for a Xenta 280/300/401 device. .AUT Text file with application program source code and data including graphical block diagram. .TLG The trendlog definition. .MCB Macro block file (Group of blocks). .COD “Machine code” file in ASCII format for downloading to the TAC Xenta controller. .XLG The compiled trendlog definition. .ESP Specification file with public signals, their attributes etc. generated by TAC Menta. This file contains input data to the OP configuration tool. .OPE A file with an empty tree, i.e. an OP tree without a specification file. This is the kind of file that is created when the OP configuration tool is run from the program manager. .OPC A mix of an .OPE and an .ESP file. This file is created by the OP configuration tool when it has been invoked from TAC Menta. .BIN Binary file with OP menu tree data for downloading to the TAC Xenta controller together with the .COD file. .CHR National character set file for downloading to the TAC Xenta controller together with the .COD file. .XIF External interface file containing a standardized description of all network variables/ objects of the application program. The .XIF enables binding and communication with LonWorks nodes from other manufacturers. .MTA Menta project file, which can include all files (all types mentioned above except for .MCB and .OPE) related to a certain application. Once a file (for example .AUT or .OPC) has been inserted (saved) in the project file, it can be extracted (opened) anytime as an .MTA file. The .MTA file can be stored directly in the TAC Vista database. Note: The .MTA file can be stored in the TAC Vista database even though it can not be compiled. An .MTA file which is not compilable will not, of course, be possible to download into a TAC Xenta device. It must be correct and compilable before download is possible. In addition to the files listed above, the following data files are involved in the creation of the .BIN file. These files are placed in a specific directory for temporary files. OPDOC.GOP An ASCII file created by the OP configuration tool when the Generate command is executed. This file is converted to an .SPT file, which in turn is converted to a .BIN file OPDOC.SPT Intermediate ASCII file generated from the.GOP file. OPDOC.TMP Intermediate ASCII file generated from the.GOP file. BPR The Network Neighborhood file, describing the TAC Xenta device’s surrounding network nodes and groups. This information was taken from the TAC Menta Technical Manual.

Warning 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 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.