Building Automation Knowledge Base

Issue Satchwell CD2201 Compensator Controller–Actuator requires replacement. Environment Stand alone discreet Satchwell CD2201 Compensator Controller–Actuator Cause Obsolescence of Satchwell CD2201 Compensator Controller–Actuator Resolution Replace Satchwell CD2201 Compensator Controller–Actuator with Schneider Electric Satchwell CSC Compensator Controller, compatible Temperature Sensors and MD Series Actuator and Linkage Kit. Replace Satchwell CD2201 Compensator Controller–Actuator with Schneider Electric Satchwell CSC Compensator Controller. N.B. Two models of the Schneider Electric Satchwell CSC Compensator Controller are available :- CSC 5252 Compensator Controller without Time Clock CSC 5352 Compensator Controller with integral Time Clock  Details of the Schneider Electric Satchwell CSC Compensator Controllers may be viewed here. It should be noted however that the CD2201 Compensator Controller–Actuator had no integral Time Clock. Replacement of Air Temperature Sensors It should be noted that the existing Satchwell Outside Air Temperature Sensor associated with the CD2201 Compensator Controller–Actuator is obsolete and should be replaced. Similarly, it should be noted that the existing Satchwell Inside Air Temperature Sensor associated with the CD2201 Compensator Controller–Actuator is obsolete and should be replaced. Details of replacement Schneider Electric STO600 Outside Air Temperature Sensor may be viewed here. Details of replacement Schneider Electric STR600 series Inside Air Temperature Sensor may be viewed here. N.B. It should be noted that the CSC Compensator Controller will perform entirely satisfactorily without the connection of an Inside Air Temperature Sensor. Replacement of Water Temperature Sensor. It should be noted that the existing integral Satchwell Water Temperature Sensor associated with the CD2201 Compensator Controller – Actuator cannot be re-used and should therefore be replaced. In order to minimise mechanical work it is suggested that a Surface Mounting Temperature Sensor is installed on the pipework, rather than an Immersion Temperature Sensor installed in a Pocket in the pipework. Details of replacement Schneider Electric STC600 Surface Temperature Sensor may be viewed here. Replacement of Actuator. Whilst the existing Satchwell MB Valve Body may be retained, a new Schneider Electric Actuator and Linkage Kit will need to be installed on the MB Valve Body in order to permit control from the CSC Compensator Controller. Details of the Schneider Electric MD10B Actuator may be viewed here. Details of the Schneider Electric LMD/AR-MB Linkage Kit may be viewed here. Please be aware: since July 2016 the CSC compensator and other descrete controllers were withdrawn from service. To see "PA-00479 - Discrete Controllers - Notice of Withdrawal - Satchwell" click here.

Issue Serial connection to I/A Series R2 UNC VxWorks Target Shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series R2 Universal Network Controllers: UNC-410-1 UNC-410-1-N UNC-520-2 UNC-520-2-N Cause There maybe a need to access the UNC via its serial port if the IP address of the UNC is unknown or for troubleshooting purposes when the UNC's Ethernet port is not functioning. Resolution Hardware required for connection to UNC's RS-232 port: 8-conductor flat silver satin stranded cable with standard male (plug) RJ-45 connectors RJ-45 to DB-9 adapter (part number: UNCC-405) or a socket-to-plug type RJ-45 to DB-25 adapter (part number: UNCC-430) A functioning COM port on a computer A 2-pin jumper for connection to the UNC's "Mode" connector Refer to the Installations Instructions for UNC-520 (page 15) for details on the cable and adapter (applies for both UNC-410 and UNC-520). Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) also refers to these pin outs. Connection to UNC's VxWorks Target Shell using Windows HyperTerminal (for operating systems without HyperTerminal, please refer to Hyperterminal on Microsoft Windows Operating Systems😞 Connect the cable and adapter between the UNC's RS-232 port and the RS-232 COM port used on the computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to UNC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port used on the computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: Hardware Click OK. On the UNC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 17 UNC-520 Installation Instructions for position of the Mode connector (top right corner). With the HyperTerminal session active, remove power from the UNC, let it cycle down, then reapply power. After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... To enter commands to the UNC, press any key to break out of the boot sequence. A prompt similar to the following is shown: [VxWorks Boot]: To determine the IP address / subnet mask of the UNC, do not break the auto-boot sequence as described in step 7. Allow the UNC to finish booting. When the controller stops displaying new messages, press ENTER to reach the command prompt. The prompt is similar to the following: -> Using the scroll bars on the HyperTerminal window, scroll up until the section that begins with the line 'Press any key to stop auto-boot...'. The IP address of the UNC is listed on the line that begins 'inet on ethernet (e)' The IP address is listed (in dotted decimal), followed by a colon, and then the subnet mask (in hexadecimal). Disconnect from the UNC when complete. Press the 'Disconnect' button on the HyperTerminal toolbar. Exit from the HyperTerminal application, selecting to Save if planning to reuse this HyperTerminal setup for future connection to an UNC. Remove the 2-pin jumper from the Mode connector of the UNC. Reboot the UNC by removing the power connector, waiting for all lights to extinguish, and plugging the power connector back in. * If troubleshooting the UNC, send the HyperTerminal start up messages to Product Support for analysis.

Issue The EBO license is activated on a virtual machine, need to make sure that it will not get damaged. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause Scenarios leading to broken Trusted Storage (license damage), when license is activated on a Virtual Machine. In some cases, the License Administrator can be used to repair the license, and in other cases, product supported will need to be contacted. Resolution FlexNet documentation explains how licensing in virtual machines works, what causes license damage, and how to avoid license damage. Make sure that documentation is related to the FNP version (FlexNet publisher) used by installed EBO, ex. EBO V4.0.2 uses version 2021 (11.18.1) and EBO V5.0.2 uses FNP V2022 R3 (11.19.2).  You can also check the FNP version by checking the properties, details of lmadmin.exe file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server Binding elements for licenses activated on a virtual machine: FlexNet publisher documentation lists three binding elements for virtual machines, all of which are deal breakers: MAC address, UUID, and Generation ID, refer to Binding in a Virtual Environment (revenera.com)  Scenarios that can cause license damage (Trusted-Storage Breakage): In the attached FlexNet White Paper: Understanding Virtualization Features in FlexNet Publisher, Page 9, details binding variables and which scenarios can change each binding element. Page 11 in the same white paper, Recovering from a Binding Break in TS, explains common scenarios leading to broken TS and if a license can be repaired.  WebHelp article EcoStruxure Building Operation Software License Repair, explains other reasons for license damage, for physical or virtual machine.  Please contact your local support if the License Administrator can't repair the license. Best Practices to avoid Trusted-Storage Breakage: To minimize license damage, follow the below steps before making changes to the bindings elements or moving EBO to a new VM. Make a backup of EBO, Backing Up EcoStruxure BMS Servers Manually Return all licenses, Returning an EcoStruxure Building Operation Software License. Verify that all licenses have been returned for all used Entitlements by logging in to https://licensing.se.com. Perform your operation. Activate the licenses again, Activating EcoStruxure Building Operation Software Licenses. FlexNet lists best practices that can also be followed to avoid trusted storage breakage: Best Practices (revenera.com)

Issue Access Control Spec for Tender Offer which usually comes from the Product Marketing Division Environment I/NET Site with Access Control Cause Bidding a job and requests for Access Control Spec or Specification Requests for: General Requirements Site Construction Door Locking Hardware Conveying Equipment / Elevator Controls Electrical Power Communications Video Surveillance Security Management System (SMS) specified For the Access/Security Control Contractor. Typically the SMS provides and explanation and integration for:   • Integrated Access Control • Alarm Monitoring • Integrated Digital Video Management • Interactive Alarm/Facility Graphics Display • Wireless Alarm and Video Transmission • Associated Access Control and Alarm Equipment Control • Multiple Language Operation • Multiple Tenant Operation • Access Initiated and Event Initiated Control  • Elevator Control • Workstation and associated equipment General Requirements Site Construction Door Locking Hardware Conveying Equipment / Elevator Controls Electrical Power Communications Video Surveillance Resolution I/NET Seven Access Control Specification (Available in a MSWord format)  

Issue Databases often have to be moved around or upgraded, especially on engineers laptops where they may do offline engineering. What is the best tool to use for this? Product Line Andover Continuum Environment Continuum Single User (Standalone) Version 1.82 and above with SQL Express (2005) Stand alone DB SQL Server Management Studio Express Cause The WinSQL software as used with previous Continuum versions with MSDE (2000) does not operate with SQL2005 and another method of accessing the database is required. Resolution After installing Cyberstation with a blank database and verifying correct operation, the next thing to install is the “SQL Server Management Studio Express” software a free Microsoft download, see link below and use the 32 bit version: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c243a5ae-4bd1-4e3d-94b8-5a0f62bf7796 This will provide the same user interface as provided on a full SQL2005 installation as used on a LAN system. For Continuum V2.0 and above SQL2012 Express is used, both 32 and 64 bit versions of this are available from the following Micosoft download: http://www.microsoft.com/en-us/download/details.aspx?id=35579 There are 2 methods to transfer your database from one system to another, using a. Backup/ Restore or b. Detach/ Attach, both options are covered below. Alternatively you may already have one or other formats on backup media. To use Backup or Detach you will also need to install SQL Server Management Studio Express as per 1. above on the original computer. Backup Method - you will need to perform a full backup and then restore of the ContinuumDB on the original computer: Using SQLE Management Studio, Right-click on ContinuumDB -> Tasks -> Backup, add a destination where you want to save the .BAK file, Click OK. Detach Method – Detach (or stop the SQL) to allow the files to be copied on the original computer: Using SQLE Management Studio, Right-click on ContinuumDB -> Tasks -> Detach, Click OK. On your new system, make sure you have already created a new ContinuumDB using Database Initialization. If not, do this now - this creates the Database, SQL jobs, stored procedures, adds Andover97 as an admin and a lot of behind the scenes security settings. Stop Cyberstation if it is running. If you are using the Detach / Attach method b. then: Using SQLE Management Studio on the new computer, Right-click on ContinuumDB -> Tasks -> Detach, Click OK. Copy the backed up files to the Data directory your new server. It is advisable to take a copy of the blank database first. Path: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data Using SQL Management Studio, now restore or attach the backed up database depending on which method is being used. Restore Method - Restore the backup over the top of the ContinuumDB on your new system: Right click on ContinuumDB -> Tasks -> Restore -> Database. Select "From device:" and add your Database file, making sure to tick the Restore checkbox to select the source. Next, go to the Options page and select "Overwrite the existing database" and press the "OK" button. Attach Method - Using SQLE Management Studio on the new computer, Right-click on Databases -> Attach, Press “Add” and select the ContinuumDev.mdf file, Press OK. The .mdf and .ldf files will be shown, press OK. The ContinuumDB will appear in the tree. Change the db owner with the below query using the sp_changedbowner stored procedure. Select "New Query" and copy the query text shown below. Run the query. use ContinuumDB go sp_changedbowner 'Andover97' go Run Database Initialization and update the newly restored database. Using Database Initialization from each Cyberstation, initialize your Workstations into the new Database. Run Cyberstation on all Workstations.

Issue A site is required to store Extended Trend Log historical data for an extended period of time, in order to make sure the system has enough capacity for all the data  it is necessary to calculate the storage needed ahead of time Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Cause Understanding the storage requirements for long term trend storage Resolution Formula to calculate the storage capacity needed for Extended Trend Log data. Storage in bytes (S)  = Number Of Records (N) x 70 bytes. EXAMPLE: Consider a trend log of 1000 records with a 10-minute interval, if the requirement is to keep 5 years of data, how much storage capacity will be required? The number of records would (N)  be... 6 records per hour times 24 hours per day times 365 days per year*** times 5 years (*** leap years must be taken into account) N =  6 X 24 X 365 X 5 = 262800 bytes This equates to: S = N X 70 S = 262800 X 70 S = 18396000 bytes or approximately 18 megabytes   Note - The calculations above are for the native SQLite database used by EBO. There are two alternatives to using the ES database for long-term trend storage. Report Server - See the WebReports Database Usage Calculator Knowledge base article for storage calculations External Log Storage is possible from EBO v3.0 using TimescaleDB database - The EBO External Log Storage Installer tool from the community provides a databases size estimator located under the Tools menu item

Issue Scenario 1 Attempting to log in to Web Client you are presented with an error message "Error - SOAP connection failed". SOAP-ERROR: Parsing Schema: can't import schema from   Scenario 2 Upon successfully logging in to Web Client you are presented with "Thank you for logging in" and then immediately presented with another message saying "Log out successful".   This continues in a circuit until it may allow you in but displays a partially populated page with no data showing. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Web Client   Cause The option "Use HTTPS to communicate with SOAP service" was enabled in the Web Client Installation Wizard and antivirus was dropping the connection because of this.   Resolution Uninstall and re-install Web Client without the  "Use HTTPS to communicate with SOAP service" enabled or Browse to the soap.connect.php located at C:\inetpub\wwwroot\SecurityExpertWebClient\include. Edit it using e.g. Notepad and change HTTPS to HTTP and change the port to 8030 so the Web Client uses HTTP to communicate with the SOAP service.

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. Issue Need to backup or share the project with another user. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT)  Cause One way of sharing a project is to move it and another way is to Export the project. Resolution Move the project Stop all servers in each project and stop all projects. Close PCT application. Copy the “projects” folder from the PCT storage location and paste it to another storage location (suggested by WebHelp topic Move a Project) OR backup all servers through Workstation. Default PCT Project Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\storagemodule\projects PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\storagemodule\projects Default PCT Template Folder Locations Versions prior to PCT 1.2 C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\templates PCT 1.2 or higher C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\templates   Export the project In Project Configuration Tool, in the Project view, select the project you want to export. On the Header toolbar, click the Export project button or right-click on the project and select "Export". On the Export selected project(s) dialog box, in the Folder box, browse to the folder on your hard drive where you want to save the exported project. Click OK. TIP: You can select multiple projects and export all of them at once. Note: In order to be more future proof, there is a new export/import format of PCT projects starting in PCT v1.3.2 with exports having an extension of '.pct_export'.  Projects exported at an earlier version have an extension of '.ppb' and they must be converted to '.pct_export' files before import into PCT v1.3.2.    Please refer to point 2.1 in the release notes.   Also prior to PCT v1.3.2 the project had to be stopped before export was possible.  In PCT v1.3.2 the project has to be running before it can be exported.    

Issue When troubleshooting server issues, it can be helpful to look at the logs that are recorded within the Enterprise Server or Enterprise Central Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause Within the Enterprise Server and Enterprise Central logs are many records that are logged as a part of normal operations and unexpected events. Resolution Collect ES and EC Logs via EBO Workstation: Refer to the Workstation section of KB article: Collect logs from an Automation Server Collect ES and EC Logs via Windows Explorer, especially if ES or EC will not run as a service or keep crashing: The ES or EC database path is listed in Software Administrator.   For Windows 7, Server 2008, or higher, the default paths for the logs folder are: Enterprise Server: C:\ProgramData\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\Enterprise Server\db\logs Enterprise Central: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation [n.n]\Enterprise Central\db\logs In EBO V3.2 or higher, shortcut buttons can be found in Software Administrator to go to the folder for logs and database directly.    By default, the "Program Data" folder is hidden, so Windows needs to be configured to view hidden files and folders. For Windows 10 or 11, open Windows Explorer and select View > Show > Hidden items. For other Windows versions, please refer to this Microsoft help article: Show hidden files (microsoft.com). Using Windows Explorer, Navigate to the ES or EC logs folder to find System and Trace logs. Copy the Logs folder contents and send them to Product Support as a compressed file if required. To open a log file, Right-click on one of the logs and select Open with... Expand the window and select WordPad. For Windows XP:   Other ways to review site-specific issues: Is the issue site-specific regarding workstation being used or applications/programs running on these machines? Always try to keep the programs on a workstation to a minimum. Review the Windows Event Logs. What specifically happens when an error occurs? Follow this KB article to view and save the Windows Events: Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes - Communities Make sure that PCs and Windows OS used for WorkStation, ES or EC meet the requirements mentioned in Information Technology System Planning Guide (se.com) Make sure that the firewall and antivirus are correctly configured, and required ports are open for EBO, as explained in Information Technology System Planning Guide (se.com) Make sure that the current installed EBO version is supported, as per the Software Support Policy for EcoStruxure Building Operation - PA-00300. Check if Microsoft currently supports the installed Windows OS: Lifecycle FAQ - Windows | Microsoft Docs

Issue Need to upgrade sites with Report Server to EBO 2022 or higher. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Report Server Building Operation Timescale Database Cause WebReports/Report Server isn’t supported in EBO 2022 (V4.0) or higher. Resolution Since WebReports/Report Server isn’t supported in EBO 2022 (V4.0) or higher, there is a Data Migration Assistant (DMA) tool available which read data from a WebReports 3.x and write it to External Log Storage. You use External Log Storage feature to store historical data from EcoStruxure BMS. The amount of stored data is limited only by the equipment you use, and not by the capacities of the feature.  When the External Log Storage feature is activated and configured, WorkStation and WebStation display the historical data in the event and trend views from the External Log Storage. Any server in the system can be configured to write historical data to the TimescaleDB database.   Data Migration Assistant (DMA) Tool can be downloaded from here. License required: External Log Storage requires license, refer to Software and Features that Require Licenses and Part Number Summary and Hardware Software Matrix  Hardware and Software requirement for External Log Storage: Ensure that the hardware and software requirements for TimescaleDB (www.timescale.com) and PostgreSQL (www.postgresql.org) are met. High-performance SSD storage is required and additional CPU/RAM capacity is required for larger EcoStruxure BMSs. As an example, at least 64 GB of RAM is recommended for systems with 100 EcoStruxure BMS servers. Refer to: Information Technology System Planning Guide (se.com) Merging Log data: External Log Storage decreases the amount of extended trend logs retained on the EcoStruxure BMS servers. You can merge log data from an extended trend log to the source log in External Log Storage. For more information, see Merging of Trend Log Data. Enhanced Reporting (XLSX Report Templates): The EcoStruxure BMS servers (3.2 or higher) provide built-in functionality for basic reporting that can deliver reports in any text format and XLSX, without any dependencies to other external software. Reports for XLSX can be enriched by using advanced functionality such as formulas, conditional formatting, charts and sparklines. If External Log Storage is configured and connected (PostgreSQL/TimescaleDB), then historical report data can be fetched from there. Refer to: Examples for the new native EBO Notification Reports - Communities (se.com)  

Issue Removing software from a PC may leave behind unused / old registry entries and folders from the removed software, this in some cases may prevent software re-installation Product Line Andover Continuum,EcoStruxure Building Operation,Satchwell BAS & Sigma,Satchwell MicroNet,TAC INET,TAC Vista Environment All supported Operating Systems Cause This is due to the windows uninstall program not fully removing all elements for the software. Some of this is due to windows thinking the the software may have been removed unintentionally and therefor all the previous settings will still be saved in case of  re-installation. For example, when SQL is uninstalled the program folders that contain the database will remain intact. This may be an issue if, for example, the software is removed due to a problem with the original installation. This is when a complete removal off all components and registry entries may be needed. Resolution The best solution for removing all the unused registry entries is to use a program designed to remove obsolete registry entries and temporary files. Some examples of these are: CCleaner, which will allow you to clean up your PC by removing past installation components. Revo Uninstaller  which is useful for removing redundant folders / files / Registry entries.   It may be useful to use both of these programs to ensure a complete cleanup. Revo Uninstaller can be used to remove unused software and then CCleaner to get rid of all the Temp files etc.  Finally remove the relevant folders from within the windows explorer, Example: C:\Program Files (x86)\Continuum Once done you should then be able to install a fresh clean copy of the application software. This solution is current in all versions of Windows including windows 10  

Issue PT1000 temperature sensors RTD Input Product Line EcoStruxure Building Operation Environment AS Classic, ASP  UI16, RTD-DI-16 - Central IO Module ASB, RPC, MPC Need for temperature to be extremely accurate PT1000 platinum resistance thermometer, RTD Resistance Temperature Detector Cause The AS Central IO Module Universal Inputs (UI16) were designed to interface to various thermistors that can have resistance values that are usually much higher than 1000 ohms. They were not designed to interface directly to a PT1000 RTD, and will not provide good accuracy when measuring these lower resistance sensors. The resistance input type was intended to allow for measuring the position of a 10K potentiometer that is used on some wall sensors. The accuracy specification for a resistance input is: +/-(7+0.004*R) ohms. This would result in an error of +/-11 ohms at 1000ohms – therefore a temperature measurement error approaching +/-3.0C. Resolution AS, ASP For RTD PT1000 (Pt100, Pt1000, Ni1000, LG-Ni1000, JCI-Ni1000) use RTD-DI-16 - Central IO Module, then choose 2 or 3 wire RTD Temperature Input ASB Choose 2-wire RTD Temperature Input (Pt1000, Ni1000, LG-Ni1000, JCI-Ni1000) RPC, MPC, MPV Choose RTD Temperature Input (Pt1000, Ni1000, LG-Ni1000)   For more details see SpaceLogic Hardware Reference Guide

Issue BACnet 3rd party controller will not respond to Find New BACnet Devices (Who-Is/I-Am), so will not come online to Continuum or EBO Product Line EcoStruxure Building Operation, Andover Continuum Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Continuum Cyberstation Continuum bCX4040 (BACnet) Cause BACnet MSTP device can be master or slave. BACnet MSTP slave will only respond to a request from a master device, and will not respond to the Who-Is broadcast so it can not be discovered. EBO: EBO does not support slave devices. EBO does not currently have a way to statically configure MAC addresses as it relies on dynamic discovery.   Continuum: Slave only devices cannot come online. Resolution Check 3rd party device documentation or contact 3rd party device vendor for Master/Slave settings and configure for Master to communicate on a MSTP network. Use 3rd party interface to convert to a protocol that can be directly supported by EBO or Continuum. Examples of BACnet MSTP Slaves that are known not to respond to EBO or Continuum Who-Is request and so not come online are: - The Babel Buster 485XM from Control Solutions Inc is BTL listed as a BACnet Slave device , their PICs statement can be seen Here. - Wilo pumps Interface Modules: IF-Modul BACnet & IF-Modul Stratos BACnet, their PICs statement can be seen Here.  

Issue Accessing WebPinpoint graphics from a web browser causes one of the following errors…   Failed CreateDNWACServer. Cause:Object reference not set to an instance of an object. URL:HTTP://eceheatsrvr/DNWACServerFactory DNWACServerFactory /WACServerFactory.soap   Failed creating remote objects. DotNet framework is missing.      Product Line Andover Continuum Environment Continuum webClient Server MicroSoft Windows XP MicroSoft Windows Vista MicroSoft Windows 7 MicroSoft Windows 10 MicroSoft Windows Server 2003 MicroSoft Windows Server 2008 Cause User Account Control redirects files to a different folder than expected by WebClient. User permissions are interfering with the WebClient. A variety of other configuration issues may cause this problem. Resolution User Account Controls Redirection The WebClient installation guide goes into detail about why MicroSoft Windows includes User Account Controls redirection. Follow the procedure outlined below.   Give "Everyone" permissions to the C:\Program Files\Continuum and C:\Program Files\Continuum\DNWACServerFactory folders In Windows Control Panel > User Accounts and Family Safety > User Accounts, select an Administrator user on the PC and select User Account Control Settings. Move the slider all the way to the bottom to Never Notify and select Ok. Follow the instructions in the webClient Installation guide section called "Configuring Graphics for webClient: Windows Server 2008, Windows Vista and Windows 7". Site may be setting User Account Control with group policy and setting it upon reboot of the PC to a setting other than Never notify. A batch file may be used to turn User Account Control off before launching WebClient. A Google search for doing this would be needed and is beyond the scope of this article. Each host that will be running a web browser WebClient session should have also have User Account Control settings set to minimum.       Web.config has not been correctly modified   Using Windows Notepad as an Admin user, modify the web.config file which is located in the c:\program files\continuum\dnwacserverfactory folder. Delete the text and replace with the text below, replacing WORKSTATION1 with the host name of the host computer.  This must be done on all hosts which will run WebClient browser sessions. <configuration> <system.runtime.remoting> <application> <service> <wellknown mode="Singleton" type="DNWACServerProxy.WACServerFactory, DNWACServerProxy" objectUri="WACServerFactory.soap" /> </service> <channels> <channel ref="http" machineName="WORKSTATION1"> </channel> </channels> </application> </system.runtime.remoting> <system.webServer> <security> <requestFiltering allowDoubleEscaping="True"/> </security> <directoryBrowse enabled="true" /> </system.webServer> </configuration>     Allow Double Escaping   If for some reason editing this file is still not working. Try the following: In Start >Control Panel > System and Security > Administrative Tools > IIS Manager (Not IIS6) Expand the tree on the left for the webserver name. ie. Webclient1 Expand Sites Expand Default Web Site Click DNWACServerFactory Double Click Request Filtering In the right-hand column select Edit Feature Settings Check Allow Double Escaping and click OK Click on the Default web site and in the far right column click Restart     Test Authentication pass-through for SOAP errors   In IIS Manager; Expand Server> Sites> Default Web Site Left-click on the DNWACServerFactory, on the far right column Select the Basic Settings link Click the Test Settings button. If Authentication pass-through is showing red follow this procedure Click Close Click Connect As> Add a windows user and password that will be used for WebClient Click the Test Settings button Authentication pass through again and it should now show green Perform a local reboot on the WebClient server Test Webclient Graphics     Make sure that the browser PCs are logged in as a Local Administrator for the WebPinpoint and ActiveX installation   Internet Explorer>Tools>Internet Options>Security>(select Zone i.e. TrustedSites)>Custom Level button Make sure that 'Download signed Activex controls' and 'Download unsigned Activex controls is set to prompt or Enable, since the default setting on many web browsers is Disabled.       Add the Webclient PC as a trusted site to the browser PCs   In some configurations, you may need to add the IIS computer into Internet Explorer as a trusted site for each browser. In Internet Explorer: Select Tools > Internet Options > Security > Click Trusted sites > Click Sites Type in http://yourservername/WebClient and click Add (Ex. http://tacweb/WebClient) Deselect the checkbox for Require server verification (https:) for all sites in this zone.  Click OK and then OK again Close Internet Explorer and retry accessing WebPinpoint     Be sure to configure the application pool for 32-bit applications on 64-bit operating systems.   On 64-bit Operating Systems perform the following steps: Open IIS Manager. Expand the computer name in the left-hand pane and click on Application Pools in the system tree view. Select DefaultAppPool and click Advanced Settings. In the Advanced Settings dialog box, change the Enable 32-bit Applications option to True. ** When using 1.94 SP1 and above, check the application pools .net version selected and make sure that the Identity is set to "Network Service" Name                           .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic  4.0 Classic .NET AppPool  2.0 Default AppPool   2.0 WebClient 4.0       DNS issues   Even when you may not be seeing red x’s in Pinpoint View>Options>Web locations and you are able to browse to pin files though IE, WebPinpoint may be giving you a graphic URL error. Try entering using the IP of the WebClient server in place of its DNS name for Pinpoint View>Options>Web locations. Also try using the WebClient Servers IP address in places of the its DNS name and also for accessing WebClient through the browser. For example http://10.159.100.125/WebClient       WebPinpoint fails to register the DNWACClientProxy.dll and tlb files when installed.   On the from the client (web browser) host, perform the steps below:  Close WebClient browser if it is running. Open command line in Administrator mode. Run the batch file C:\Programs Files (x86)\WebClientPinpoint\WPPRegistrationClient.bat     Other items to check:   Disable Windows Defender Turn off all 3 firewalls Shut off SPS software protection service when installing. Run Internet Explorer as an Administrator to make sure the ActiveX controls are being installed

Issue In this specific instance the site was upgraded to Continuum v1.94 and the Cyberstation OS upgraded to Windows 7 64 bit, fresh install. Local Administrator account was logged on to perform Database Initialization which succeeded and Continuum was able to start-up and connect to the SQL Server. Restarting and logging in with another windows user with administrative privileges results in being unable to connect to the database. Logging out and then in as Administrator and re-initializing the Workstation into the Database re-establishes the connection and Continuum is able to be run again. This fails again when another user is logged on. Product Line Andover Continuum Environment Andover Continuum Cyberstation Windows 7 64-bit Cause Windows administrative privileges are required to initialize and make a connection to the database. Resolution Run Database Initialization as an Administrator and re-initialize the Workstation into the Database. Shut down all Cyberstations. Right-click Database Initialization and select "Run as... Administrator".  In Win7 you may need to "Shift-right-click" and select 'Run as a different user...' Select Workstation, confirm details, input password and select OK.

Issue Controller Error Logs - How to gather Continuum Controller error logs if requested by Product Support for troubleshooting. Product Line Andover Continuum Environment BCX CX  CMX 9680 9900 i2 b3 9702 Controller Error Log Gerry Log Cause Troubleshooting controllers often time requires obtaining an error log from the controller Resolution The controller error logs contain useful diagnostic information when it is necessary to troubleshoot a controller or system problem. Much of what is logged are normal system operations that may assist an engineer in diagnosing a problem in the field. To get the error logs from various controllers follow the procedures below: NetControllers - 99xx  Dumb terminal in using HyperTerminal Sign into the NetController Press V then E and press Enter over the NetController you are attached to Press F2 Hit Alt + Print screen and paste into a Word doc Arrow down to single space or Ctrl+D to page down Hit Alt + Print screen and paste into a Word doc Repeat this process until you are at the end of the errors (up to 200) F4 Exits the error log See the CX Controllers Programmer’s Guide for all terminal keystrokes Email the file to Product Support Services   BCX/i2/B3 Controllers CX9680/ACX5720/ACX5740/9702 Controllers Note: You can not retrieve errors from NetController I (CX9900) using this tool Controller Error Log Tool Navigate to C:\Program Files\Continuum Double click on ControllerErrorLogTool.exe to open (This will do an install the first time) Note: The ErrorLogTool.exe is an older version of this utility and will work, but gives less information and does not contain the error lookup feature. Enter in the BCX or master CX IP Transport type = UDP or TCP depending on controller configuration CX Enode ID = AccNetId from the main CX editor Select Continuum in the Mode area, top right If the controller is a field device then enter the following: CX infinet port = Select the one you want to report on Infinet Node ID = port number of the i2 device you want the error log out of Once all the above required entries have been made: Click Get Log and the page will populate with any errors Once this runs, select SaveAs and name the file Email the file to Product Support Services Suppliment - To gather error logs from Continuum controllers transisioned to StuxureWare please see How to pull the error log from a b3 or Infinet controller in SmartStruxure.

Issue The Drayton Theta YBM2 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBM2 Cause The Drayton Theta YBM2 Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBM2 Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBM2 Valve Body the following is required:- S-E Satchwell MB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT The YBM2 Actuator comprised a 3-wire electrical connection enabling it to be operated by a Mains Voltage changeover contact device as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  The YBM2 Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-230 MD20B-230 (if MD10B-230 not available) Details of the MD10B-230 Actuator may be viewed here. Details of the MD20B-230 Actuator may be viewed here.   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBM2 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue The Niagara G3 platform daemon will not run using an administrator account in Windows. Product Line TAC IA Series Environment Niagara G3 Cause Possible causes: The niagara service is not started IIS is running on the computer Port 3011 is blocked Authentication Resolution There are a number of possible causes: The niagara service is not started. Run Platform Daemon (Start > Programs > Vykon AX Supervisor > Install Platform Daemon) IIS is running on the computer.  Disable IIS in Control Panel > Administrative Tools > Services Port 3011 is blocked. Ensure there are no firewall, antivirus, or remote access software blocking port 3011 There are two types of platform authentication: Basic platform authentication (the default for a Windows-based host) provides integration with existing Windows installations, and provides two levels of platform access, which are determined by a user’s group membership(s). The levels of platform access are: User - Platform access at this level allows full use of most Workbench platform views. This includes the ability to install or delete licenses and stations (including the one running), also to install, reinstall, or upgrade the platform dist file and/or modules, and to start, re-start, or stop a station. Admin - Full access. This includes all user-level platform operations, plus the ability to configure host TCP/IP settings and dial-up configuration, change platform authentication, change platform daemon HTTP port, change host date/time settings, use the File Transfer Client, and reboot the host. Digest platform authentication provides only full level platform login access, using a single platform user account. With Digest platform authentication, there is no linkage between Windows OS user accounts and the platform administrator. If Basic authentication does not work, then Digest authentication must be used. To enable digest authentication, do the following: Using Notepad or WordPad, open the daemon.properties file located in C:\niagara\[release]\daemon folder Add the following lines to the end of the file: installFlag=doc authtype=digest/file user=[username] (where you select the username) password=[password] (where you select the password) stationIsAdmin=true Save, then close the file Restart the platform daemon (Start > Programs > Vykon AX Supervisor > Install Platform Daemon) Launch Workbench AX, then open the platform using the username and password you provided in step 2. Consult the Niagara AX Platform Guide for more information.

Issue How to add Web Service and create SOAP Web Service with Graphic Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add SOAP Web Service files and how to add to a project or site How to create values from SOAP Web Service Files How to add values to graphic that uses the values from SOAP Web Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: are hardware, programming language, and operating system independent Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services Web Service interfaces are supported in both the AS and ES(does not support connection over a ProxyServer) Like BACnet, Lon, and Modbus, you can create a Web Service interface. EWS Interface - EcoStruxure Web Services Script Web Service - Generic Consume via Script (Web Service addition Script Web Service) Simple XML Web Service - Rest Generic Consume via Binding Tool (Web Service addition Simple XML Web Service) SOAP Web Service - SOAP Generic Consume via Binding Tool This article explains adding Sunrise and Sunset for a particular location data using SOAP Web Service: Select New > Interface > Web Service > SOAP Web Service Next Paste the URL which has the SOAP Web Service feature ((to find sunset/sunrise for your area, Google WSDL data) and location coordinates Get Operations button pulls in the data. Select Next  which shows the values and times and then select Create Create values by highlighting SOAP Web Service then File > New > Value Choose Next and highlight the specific for the values then select Create Here are the SOAP Web Service sunrise/sunset values If desired, Bind those values to a graphic Lastly for SOAP Web Service a graphic is created and the values which come from the SOAP Web Service are place on the page

Issue What are the fields in the FIPS-201 PIV FASC-N? Product Line Andover Continuum Environment CyberStation NC2 (9680) ACX2 (ACX5720, ACX5740) Cause Documentation Resolution The Federal Agency Smart Credential Number (FASC-N) consists of 40 total characters encoded as Packed Binary Coded Decimal (BCD) format with odd parity creating a 200 bit (25 byte) record.