Issue When you view a Xenta Log through Vista you get estimated values in the Log. Product Line TAC Vista Environment Vista 4.x.x Vista 5.x.x Cause If the site has many Xenta logs in 200,300 or 400 controllers you maybe exceeding the limit for trend uploads to Vista. The maximum limit is 4 uploads of Xenta logs per minute to Vista. If you exceed this value estimated values may appear in the Xenta logs. Here is a link to a white paper description on this topic TAC Xenta Trend Logs Whitepaper Resolution Here are some steps to check if the estimated values are caused from excessive Xenta trend upload.   Calculate the amount of uploads that are occurring in the database. As an example if a Xenta log is set to store information in the controller for 1 hour and upload at 80% full. This equates to 0.8 uploads per hour or 0.013 uploads per minute. If you work out this rate for all the xenta logs in the database you can then calculate how many uploads are occurring per minute. To extract all the Xenta Logs in the Vista database follow these steps also shown in the video. From TAC Vista workstation select View and then Search from the toolbar. select the browse option for the field "Type of devices or objects" Expand the heading labeled Files. Expand the heading labeled Trend Logs under the Files heading. Expand the heading labeled Trend Log Vista under the Trend Log heading Check the Trend Log Xenta box Select OK In the Property value dropdown list select the" Log size byte " option. This is the Xenta Log duration in seconds. Select the search Button The search results now show all the Xenta Logs. You may need to uncheck the "interrupt search if more than 1000 results" to capture all Xenta trends In the Search output Pane right mouse click and select "Additional properties" Expand the list and select "Retrieve at % Full option" The Search results then show all Xenta trends with Xenta Log duration and retrieve % full. Copy this list in Excel and calculate the uploads per minute from this Database. Below is an image showing the data pasted into Excel, displaying the equation to calculate the upload per minute value per log:  If you find your total "uploads per minute" exceed 4 then reducing this may remove the estimated values. Some ways to do this are. Extend the Xenta log storage time in the Xenta device if memory permits. Change the upload percentage to a greater number if it has been decreased below 80%  Increase the Xenta sample rate which will allow for the Xenta storage to be extended as in point 1.

Issue The Following error is displayed when attempting to use webUI: java.lang.ClassNotFoundException: tridium.webuser.ui.WebUserAdminApplet at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source) at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source) at sun.plugin2.applet.Plugin2Manager$AppletExecptionRunnable.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Exception: java.lang.ClassNotFoundException: tridium.webuser.ui.WebUserAdminApplet Product Line TAC IA Series Environment Niagara R2 WorkPlace Pro 532 Cause Some servlets which the browser uses were left out of the webUser-2.301.532.jar files. Resolution The plan is to correct this issue in the next maintenance build release. The workaround is to replace the current webUser-2.301.532.jars with the webUser-2.301.530a jars. Reference How to install an I/A Series R2 JAR File.

Issue Unable to login to Workstation. Getting error "Requested license is not available on the license Server" even though the license for the StruxureWare Enterprise Server is valid. License server does not support this feature (Error code: -18) Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation v1.3/1.4 WorkStation Enterprise Server License Server Cause When using Network Licenses this possibly indicates there was no valid WorkStation license. The Enterprise Server license does not also provide a Workstation license to run Workstation. If using Local Licenses, such as the Evaluation / Demo license and you are attempting to connect to an Enterprise Server from a separate WorkStation, the License server and the demo license file must be installed on both the Enterprise Server and each Workstation since the local license can not be shared between computers. Check Online help for additional detail. Resolution Network License: A new WorkStation license is required to use WorkStation. This would need to be acquired and added to the license Server. The part numbers for these are below. WorkStation software (including editors) Part number Product name Description SXWSWWORK00001 SW-STATION-STD-0 WorkStation Standard, 1 concurrent user license, (no maintenance subscription included) SXWSWWORK00002 SW-STATION-PRO-0 WorkStation Professional, 1 concurrent user license, Professional WorkStation version includes Editor licensing, (includes TGML Graphics editor, Function Block & Script Programming, no maintenance subscription included) Depending on what your requirements are, it may be possible to use the WebStation instead of a dedicated WorkStation for light monitoring duties. There is no part number for WebStation; it is a default feature of the Automation Server and Enterprise Server (with no need for additional licensing) in v1.3. Details on the WebStation and WorkStation can be found at the below links. WorkStation WebStation Local License: If using Local Licenses, such the Evaluation/Demo license and you are attempting to connect to an Enterprise Server from a separate WorkStation, the License server and the demo license file must be installed on both the Enterprise Server and each Workstation since the local license can not be shared between computers. Check Online help for additional detail.

Issue Get error message "OPC communication error" when trying to view Vista OPC server objects in OPC tool. Product Line TAC Vista Environment TAC Vista 5.1.X TAC Vista OPC server 1.6.1 Cause Incorrect version installed or DCOM settings. Resolution Confirm which version of Vista OPC server is installed. Go to control panel\add remove programs and double check that it is version 1.6.1. that is installed. Confirm that OPC server setup account settings aren't being saved. Go to Start\Programs\Schneider Electric\TAC Vista OPC server\Tac OPC Server setup. Under Login to TAC Vista server, change to Login using the following TAC Vista account and fill in the appropriate user details. Click OK and close the dialogue. Re-open the TAC OPC server setup dialogue and see if the account details added in b are still there. If so then there is probably a problem with DCOM settings (see TAC Vista OPC Server Technical Manual). If the option Login using the windows account which is running the TAC Vista OPC server is re-selected TAC Vista OPC server 1.6.0 must first be installed according to OPC server for TAC Vista will not keep the login settings in the TAC Vista OPC Server setup.

Issue Error "Not enough space in RTI device"   Product Line TAC Vista Environment Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause Memory in PSU is corrupt. Resolution Run Dongleutil, a dongle reset utility software. This utility resets the memory in the PSU that is connected to the PC. You need to install the license file again after this operation. This problem is usually seen when Inhouse PSU is used. In TAC Vista version 4.10 and later, it’s no longer necessary to install the engineering file when Inhouse PSU is in use. Just connect the PSU to the PC, and everything should work fine.

Issue Error states: "Ensure that Vista Server is started" when trying to log into TAC Vista Workstation. The server is started. Product Line TAC Vista Environment TAC Vista Workstation 4.2.5, 4.3.0-4.5.0, 5.0.0 and higher Microsoft Windows XP Service Pack 2 Cause Microsoft Windows XP Service Pack 2 has security changes/upgrades from previous service packs.  This affects the DCOM permissions that Vista Server relies on. a variety of other reason could result in an error in DCOM parameters in later operating systems. Resolution Vista 4.2.5 Apply settings described in this TPI to get TAC Vista to work properly. Vista 4.3.0-4.5.0 Apply settings described in this TPI to get TAC Vista to work properly. Vista 5.0.0 and higher Apply settings described in TAC Software Installation Manual available on The Exchange Download Center. This can be done using the DCOM Utility in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. Error Message: Ensure that Vista Server is started lists manual steps to access DCOM.

Issue Error when trying to add exceptions to a schedule is seen when trying to "apply" the changes. Example: Personnel Manager Error saving data Communication Error Exception has been thrown by the target of an invocation. The personnel object was created Product Line Andover Continuum Environment Continuum Cause Too many old exceptions in the schedule. Sometimes RPC (Remote Procedure Call) errors happen on Cyberstation following the above error. Resolution Delete the old exceptions. This must be done manually for infinet schedules. 1.94 NOTE: If this issue is happening for 1.94, there is Hotfix for TPA CONT 12 0002.00 Schedule Exception Errors.zip that has been released for this issue. The V1.94 issue is also detailed in Technical bulletin: TPA-BOST-12-0002.00  

Issue When viewing access events in NetControllers door object, error "ACX database fault".  Environment NetController with AC1 I/O modules NetController II with AC1 I/O modules Cause Error is due to the Door Switch, on a dual-reader door, being wired to the Exit reader I/O module. I/O channels on the Exit reader I/O Module should not be used for Door control. Resolution Rewire the Door Switch to the Entry reader I/O Module. For an example of the correct wiring of a dual-reader door’s Door Switch, please see page 149 of "IO System Reference Guide".

Issue Error javax.baja.sys.NoSuchSlotException: textOverride when activating KitPx "Export' button for pdf in G3 version 3.6. Environment I/A Series G3 (version 3.6) Cause KitPx 'Export' button included on a canvas as part of a ReportPx.  Activating the 'Export' button causes the export to pdf to fail with the following exception ... javax.baja.sys.NoSuchSlotException: textOverride. Resolution Upgrade the pdf module to 3.6.38 or higher. The zip file (pdf-3.6.38.zip) can be downloaded from The Exchange Download Center.

Issue Error during installation of Vista:  "Unable to Locate Microsoft Excel" or may say "Could not find Microsoft Excel which is needed to use Vista Reports." Environment Windows 7, XP Microsoft Excel Vista Cause Vista may not be compatible with the version of Excel that you have installed on your computer or Excel may not be installed. Resolution Download document TAC Vista Compatibility Matrix Use the matrix to compare the version of Vista you are trying to install and the software installed on the machine Correct any discrepancies by either purchasing a different version of Excel for the computer or using a different version of Vista.

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 When downloading a programmable controller with the Vista system plug-in, the process fails and reports the Error 80041195, Info: Communication port not connected. NOTE: Error 80041195 has also been reported when performing a commence communication command in the Vista system plug-in. Product Line TAC Vista Environment Vista Server 5.1.5 Vista System Plug-In 5.1.5 Cause Vista Server 5.1.5 is not communicating to the LNS server properly Resolution Vista Server hotfix 14 addresses this error within Vista Server 5.1.5. Download TAC Vista Server 5.1.5 Hotfix 14 from The Exchange Download Center. Run the TACVista515HotFix51514.exe file. Reboot the machine. This error has also been observed If the PC is running a a 64-bit operating system which is not supported for LonMaker or NL220. See Echelon LonMaker and Newron NL220 on 64-bit operating systems for more information.

Issue A door configured with entry and exit readers using AC1/AC1A will report door switch trouble after controller is reloaded. Environment CyberStation CX9900 CX9680 AC1 AC1A NOTE: There is no problem if AC1Plus modules are used. Cause Configuration issue Resolution Attach resistors to exit side AC1's door switch, the resistor configuration on the exit AC1 must match the resistor configuration on the entry AC1. DO NOT wire the inputs on the exit AC1 to anything. Only the door switch has this requirement, the REX input does not require adding resistors to the exit AC1. See IO System Reference Guide  connecting a dual reader door for wiring information.

Issue Enterprise Server not archiving to SQL Server database.  Getting the following Error in ErrorLogService:  “Failed to archive (1): tridium.datax.net.DxRemoteException: java.sql.SQLException: The incoming tabular data stream (TDS) remote procedure call (RPC) protocol stream is incorrect. Parameter 2 (""): The supplied value is not a valid instance of data type real. Check the source data for invalid values. An example of an invalid value is data of numeric type with scale greater: than precision.  The SOW displays: at tridium.datax.net.DxExchange.doResponse (bytecode 107) at tridium.datax.net.DxExchange.run (bytecode 118) at java.lang.Thread.run (line 5) Environment R2, WorkPlace Pro 2.301.529, Enterprise Server Cause NA Resolution The coreRuntime-2.301.529a.v1 jar file corrects possible issues related to the archiving of data to a Microsoft SQL 2005 database.  This jar is only required by Enterprise Servers with the IA-SQL-DBS driver feature. Installation: Stop the running station and Niagara service Locate the existing coreRuntime-2.301.529.v1.jar file (e.g. ...\nre\modules) directory.  Rename the existing file to coreRuntime-2.301.529.v1.jar.old Copy in the coreRuntime-2.301.529a.v1.jar file. Restart the Niagara service and Enterprise Server station.

Issue Enterprise Server and the B-OWS capability Environment SmartStruxure site Cause Enterprise Server and the B-OWS capability for viewing BACnet Operator Workstation Resolution The Enterprise Server is a native BACnet/IP protocol operator workstation and controller with a built-in web server. The Enterprise Server also serves as a BACnet/IP Broadcast Management Device (BBMD). The Protocol Implementation Conformance Statement (PICS) document details the BACnet Interoperability Building Blocks that are supported in StruxureWare Building Operation. The PICS are available from the BACnet International labs for BACnet Operator Workstation (B-OWS) Continuum 1.9x The below screenshot is of a StruxureWare Building Operation 1.3 Release and the desired connection using B-OWS to a Continuum 1.94 Release. Workaround is on the BACnet Interface of the ES, highlight the IP Network then Add New BACnet Device. 1. Suggested name would be the Cyberstation Name 2. Upload from BACnet device 3. Instance ID is the Device Node ID (Right-click/Edit on the Cyberstation) 4. Create Then perform an Upload from the newly created Cyberstation. Resulting View from the Enterprise Server: (Note that Cyberstation owned objects are not available in the Enterprise Server) There is an “official” document on Continuum and StruxureWare Building Operation BACnet communication that was produced specifically for this issue. It is a TVDA produced by the Buildings StruxureLab and it is Andover Continuum BACnet with StruxureWare TVDA 1.02

Issue Endura 2 Integration in Continuum V1.92.  Having issues with VideoLayouts not showing the video properly but displaying the date and time properly. Environment CyberStation 1.92 Endura Video Cause Revision incompatibility Resolution See document "Andover Continuum Software and Pelco Video Compatibility Matrix" for video products that can be integrated using Andover Continuum’s video features.

Issue Emailing alarms if Microsoft Outlook is not used on the site? Product Line Andover Continuum Environment Continuum Cyberstation 1.73 and above bCX 4040 Netcontroller II (9680) ACX57xx Series (ACX II) Cause The customers site IT system is unable to provide reliable Email communications from Microsoft Outlook on the Continuum Workstations. Resolution The documented Outlook support: Initially Full Microsoft Outlook or Microsoft Exchange was specified as the requirement 1.92 to 1.94 specified Microsoft Outlook 2007 for Windows XP and Vista (Full Microsoft Outlook or Exchange) 1.94sp1 to 2.03 specified Microsoft Outlook 2007 Microsoft Outlook 2010 (Full Microsoft Outlook or Exchange software package)   For further information on outlook versions see the KB article Outlook 2007 and Outlook 2010 with Continuum email alarms. Notes Only 32bit Outlook was tested/supported Continuum does not support MS Outlook Express for emailing alarms From v2.0 CyberStation has internal SMTP email options see  SMTP Email Alarm Configuration in Continuum 2.00 to 2.03 There are other email option for emailing directly from controllers. There is a feature in the bCX (also NetController II, ACX II) controllers to be able to email messages directly to a SMTP server either manually or via Plain English programs, although this is not directly linked to the Continuum Alarm system and would require a Plain English program to determine what emails are to be sent. See the "bCX1 Controller Technical Reference" Commissioning section for details on how to set up the controller to send out emails to a 3rd party SMTP email server.  There is also the Continuum SNMP Configuration guide for use with SNMP alarming with a Network Management System. Then in the CyberStation online help see the "SendEmail" function help on how to use Plain English to get the bCX (Netcontroller II or ACX II) to send out messages via email.  

Issue Getting an Error 1001 near the end of the EcoStruxure WebReports Installation Reports not functional from WebReports Product Line EcoStruxure Building Operation Environment Web Reports SQL 2008 R2 Windows Server 2008 Windows Server 2012 Cause This error is caused when the WebReports installer is unable to reach SQL Server Reporting Services to configure the WebReports Interface Resolution After a failed install of WebReports you will need to follow the general workflow:   Clean of the Pieces of the failed install. Use the uninstall process listed in the WebReports Reference Guide or Uninstall Process for Web Reports. Correct all possible causes of the failed install Verify that you can connect to the ES using http from the Reports Server PC Verify that you can connect to http://localhost/Reports_SQLInstanceName  Re-install WebReports. NOTE: You may be able to correct the issue without having to remove and re-install WebReports. Possible Issue: The Microsoft Reporting Service SQL databases are not registered Check through SQL Management Studio that the 2 databases "ReportServer$instance" and "ReportServer$instanceTempDB" are registered. If not, the SBO Web Reports installed have nowhere to place the report pack files. If they are not there, you need to add them through "Reporting Services Configuration Manager". Click "Database" and then "Change Database". Here you can chose to create new databases. Possible Issue: Insufficient User Access Log out of Windows and Log back in using a PC admin account. The account logged in for the installation should have full access to Windows and be a DB admin in the SQL Server. Set the User Account Control Settings to Never notify. Possible Issue: PC Configured as a Domain Server In the Server Manager, check that the IIS Role is configured and that there are no Domain Roles assigned to this PC Possible Issue: Another Application is using a Required SQL function Uninstall any application which use SQL on this PC. (The Enterprise Server does not Use SQL) As a Best Practice, the Reports Server should be installed on its own, dedicated PC. Possible Issue: Incorrect Version of SQL Server or Windows Server Check the Reports Server Specification Sheet for your build and verify that you are on the Correct Version of Windows and SQL. Possible Issue: Secure Connection Level set too high This issue typically also results in not being able to log into http://localhost/Reports_SQLExpress. Log into the Reporting Agent Configuration Manager Application Click on the Report Manager URL on the left-hand column Click on the HTTP URL This will give you the correct URL for your installation of SQL If this fails, browse to C:\ProgramFiles\Microsoft SQL Server\MSRS10_50.SQLEXPRESS\Reporting Services\ReportServer (this may vary based on SQL Installation)   Modify the CONFIG file "rsreportserver" Change the Secure ConnectionLevel to "0" Save the file and attempt to log into http://localhost/Reports_SQLExpress again. For more details on this property see: http://technet.microsoft.com/en-us/library/aa179559(v=sql.80).aspx Possible Issue: .NET Framework is not operating correctly. Download the correct version of .NET framework for your version of EBO (The correct required version can be found on WebHelp Reports Server under EcoStruxure Building Operation Software Requirements) Run the installer in "Repair" mode Possible Issue: The Windows account "appuser" is not created because the default password does not meet password policy requirements Temporarily disable password policy on the server and try reinstalling. For clarification of the use of 'appuser', refer to the following article, Report Server "appuser" clarification 

Issue After upgrading from EcoStruxure Energy Expert (formerly Power Manager) from version 1.0 to 1.x or newer, the licensing no longer works. Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Energy Expert (formerly Power Manager) License Administrator Power Monitoring Expert Cause There can be some confusion on what licenses are required to run Energy Expert. There are also differences between version 1.0 and 1.x or newer licensing.  Resolution EcoStruxure Energy Expert License In order to use Energy Expert, an Energy Expert license is needed to be purchased before the previous 90-day trail license expires.  The EcoStruxure temporary license (evaluation) is only for EcoStruxure Building Operation software and does not include Energy Expert   It is important to remember that EcoStruxure Building Operation licenses are needed to work along side Energy Expert (e.g. Workstation, Enterprise Server, etc). The EcoStruxure Building Operation licenses need to be activated separately.  How to activate, release and/or transfer a license in EcoStruxure.   Energy Expert Version 2 and 3 Licensing and Upgrading If upgrading from a previous Power Manager 1.x site to Energy Expert 2.x or 3.x a new license(s) will be required. In order to obtain your new license(s), please follow the procedure found in TPA-EBO-19-0001.00 - EcoStruxure Energy Expert v2.0 License Upgrade. (Full support ends 2022 and limited support ends 2024) Energy Expert Part numbers and Licensing The part numbers for version 1.x or newer are listed below. PSWPMNCZZSPEZZ -  Base Energy Expert license PSWDENCZZNPEZZ -  PME license entry range PSWDMNCZZNPEZZ - PME license mid range  PSWSANCZZSPEZZ -  Standard PME. license For a full list of both current date and obsolete part numbers please download the following spreadsheet https://ecoxpert.se.com/pme-digital-power-launch)   Activating a License Full guidance for activation of your licenses can be found on Page 55 of the Energy Expert 3.0 Solution Guide The Energy Expert 3.0 installer and documentation, can also be found here EE 3.0

Issue Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert There are some best practices and tips that can be used to save engineering time when setting up a EcoStruxure Energy Expert (Formerly Power Manager) system. To find out the differences between Energy Expert and Power Monitoring Expert (PME) see Differences between EcoStruxure Energy Expert and EcoStruxure Power Monitoring Expert. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation EcoStruxure Energy Expert EcoStruxure Power Monitoring Expert ETL Integration Tool Cause The following topics should be considered before and during the implementation of the EcoStruxure Energy Expert offering to achieve the cleanest and most effective database.    For more information on design considerations including IT considerations, software compatibility, server specification, hard drive space, etc; see Design Guide - EcoStruxure Energy Expert - formerly Power Manager. For more information on integration see Energy Expert with EcoStruxure Building Operation.  For more information regarding Power Monitoring Expert (PME) please visit the Solutions Expert Community. Here you can find documentation, content, and additional help.  Resolution You may get some benefit working thorough some older existing support material under Energy Expert's former name of Power Manager such as the Deploy Power Manager for SmartStruxure Solution in a Day document.  Also check out the Power Manager EWS Alarm Web Configuration Quick-Help video on the Exchange. General Always install the EcoStruxure Energy Expert software with full Windows administrative rights. Just logging in with a user that has admin rights may not be enough. If you are unable to save an ETL job or run as a service; close ETL, right click on ETL and select run as administrator.  Create one folder on the root level of the server that holds all of the extended trend logs you wish to transfer to EE. This folder can even be set up to be visible to only a designated admin account to prevent any changes to be made to the trends. If any other items like trend charts are in this folder, it will only slow down the process.  See StruxureWare ETL tool locks up or takes a long time while loading sources for information on how to improve the scan time of the ETL load sources function.    SQL Server It is not recommended to install EcoStruxure Energy Expert on a machine that has another instance of SQL already installed on it unless you have advanced SQL configuration skills. The default SQL instance name is ION and the system administrator password is ION!Everywhere. This should not be changed.   Selecting Between Architecture 1 and 2 The three items to consider when selecting an Architecture are device type, numbers of registers to be requested, and device location. The device type is the most important item to consider though. In order to get the most out of the high feature, more robust meters, Architecture 2 should be used. Architecture 2 should be used if the following features are present; ION meter, multi-address device, power quality functions, onboard logging, and/or onboard alarming. When low-end power meters, energy meters, or pulse meters are used, there is no difference between the two architectures in fulfilling the energy management requirement. Most of the Schneider Electric meters and circuit breakers are fully supported by EE. This means that EE has built-in drivers to utilize the full function of the device and the required commission time is minimized.   Architecture 1: Logging data in EcoStruxureWare Building Operation (EBO) It is recommended to use interval trend logs to log the raw data coming in from the meters.  The only durations that need to be set up in trend logs for ETL is the standard trend log duration. This is generally going to be 15 minutes as a industry standard. EE Dashboards and Reports have an aggregation mechanism to make use of the data. Thus durations such as day, week, or month do not need to be brought over into EcoStruxure Energy Expert (EE) as it can be calculated later based off of the 15 minute trend log value.  If both Trendlogs and Extended Trendlogs are used, it is recommended to send the data in the Trendlog to EE to avoid the lagging between Extended Trendlogs and Trendlogs.    ETL StruxureWare Building Operation version 1.6 RC EcoStruxure Web Services (EWS) do not support Secure Sockets Layer (SSL) URLs. For the ETL Extract task make sure to fill out the web service name (default is admin), web service password (default is admin), and web service URL (replace localhost:8080 with your web server address and port as needed) in the settings. For the ETL Load task make sure that the ION data database connection string and ION network database connection string are correct. Also change the field enable recorder and channel creation to True. The recommended naming convention for the Target Device field is [Group].[DeviceName] with no special characters such as \ * + = | : ; < > _. An example could be BuildingA.SubMeter1 where the building name is used as the group and the meter name is used as the device name. With this naming convention, all values brought in under this particular meter will have the same Target Device name.    The Target Measurement field is very important to set correctly as it will not bring the data over to EE correctly if the right unit has not been chosen. This is a process that will become easier with more experience but you can reference Section 6.9 Measurement mapping for ETL in the Power Manager for SmartStruxure Solution - Integration Manual. This chart can be used to search for the unit type you are dealing with and which corresponding Mapping should be use.