Building Automation Knowledge Base

Issue When trying to log on to an ES or AS using HTTPS, you get "No connection to server" or it takes a long time. Using HTTP it works fine. Version 1.6.0 and below you get "No connection to server" Version 1.6.1 and above you get in but it takes an extra 25 seconds compared to normal Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Workstation Cause The most common reason for this is that the port used for HTTPS is changed in the Software Administrator, and not added in Workstation when logging on. For a solution to that, please check Workstation Log on failure due to unidentified port. A more rare reason for this has been identified on sites with strict network policies or no connection to the internet. The reason this is happening is because an application using SSL or TLS (e.g. OpenSSL) is regularly checking for certificate revocation. That can normally only be done if the PC has internet connection. If the PC can't connect to Microsoft's server to get the newest list of revoked certificates, the application will appear to hang or fail to use SSL. For a deep explanation of certificate revocation check and the base of this article, read Citrix' article: Slow Web Interface\MMC console? CRL explained. The issue can be confirmed using Fiddler. Here is an example on how to identify the issue.: Another way to check it, is to enter the URL used to retrieve the list on the PC having the issue: http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab?baa88d4bbbfc38e4 When trying to access that URL from a PC having this issue, you should get "HTTP Error 502 Bad gateway". Resolution Download the newest CRL updates from a PC with internet connection http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl http://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crl Copy the two files to the PC having the issue Open a command prompt and navigate to the folder where the files are located Install the CRL files using the following commands CertUtil -AddStore CA CodeSignPCA.crl CertUtil -AddStore CA CodeSignPCA2.crl

Issue Web client does not display ActiveX graphics. Environment web client Graphics to not display. Cause The Sigma web client has been loaded and is the correct version, but when the web client is run, the display shows "Error" Resolution After investigation it was found that Java had not been installed on the PC. This must be installed for the Sigma ActiveX graphics to function correctly. Having installed Java, the Sigma web client must be reinstalled. If during the installation the web page shows a script, then you must add the site to the "Compatability View Settings" in Internet Explorer.

Issue In Dataview and Dynaview, the am or pm is not shown when the time is after 10am to 12am or 10pm to 12pm when crosshairs is used on a graph Environment Sigma 4.08 Cause In Dataview and Dynaview, the am or pm is not shown after 10am or 10pm when crosshairs is used on a graph Resolution The workaround is to use the 24hr clock. Goto Control Panel > Region and Language > Formats and change the Short Time and Long Time to a format that does not have 'tt'.

Issue All Script programs in the AS have status unloaded. How do I get them working again? Environment Struxureware Building Operation 1.5. Cause A script program had an output binding that was linked to a PVR block in a Function block program. It looks like on the server boot up, the script engine tries to start up before the function block engine does and when an output of a script sees that the binding is null, it throws an exception and shuts down the script engine. This only seems to be a problem when binding a script programs output to any PV type in a function block program. Resolution  Bind to a Numeric output instead of a PVR block in the function block program.

Issue Getting authentication failure when trying to set to password for "SystemReportsService" through "Building Operation WebReports Administrator" Environment Web Reports 1.6.0 RC and above Cause The Reports Agent can't check the password with the ES. This is dues to one of the three causes below: [1] The Enterprise Server path is not correct [2] The HTTP port entered for the reports agent is not correct [3] The ES is not started [4] The password entered is not correct [5] The reports agent is not started [6] The "Local System" account does not have high enough privileges to communicate out of the server Resolution [1] Enter the right ES server path e.g. using "SBO Reports Agent Config" [2] Enter the same port in HTTP in the ES Software Adminsitrator and the reports agent e.g. using "SBO Reports Agent Config" [3] Start the ES [4] Enter the correct password (you can change the defined password for the "SystemReportsService" through Workstation) Be sure to use the SystemReportsService account in the local domain of the ES [5] Start the reports agent [6] Change the report agent service to run under a local administrator account

Issue Unable to find data sheet for TAC M500 actuator Environment TAC M500 actuator Cause No data sheets are to be found on the Extranet Resolution The data sheet for TAC M500 actuator can be found here

Issue How to trigger different alarms with different alarm texts depending on the value of a single variable Product Line EcoStruxure Building Operation Environment Building Operation Workstation Alarms Cause There is a requirement to trigger different alarms based on the value of a single variable.  As an example, a variable coming from an APC Symmetra UPS will report various alarm states as a number from 1 to 7 in the same variable, and it is required to differentiate the alarm text on each value. Value Status Alarm text 1 unknown Module is in Unknown state from UPS 2 not installed Module not installed in UPS 3 Off OK Module not installed in UPS 4 On OK Module not okay in UPS 5 Off Fail Module off fail in UPS 6 On Fail Module on fail in UPS 7 Lost Communication Module lost comm. in UPS Resolution Here are two examples on how to do it Example 1: 7 different alarms with different alarm texts monitoring the same point Example 2: 1 alarm monitoring a point, and a script dynamically changing the alarm text     From version 1.9 upwards Alarm Decoration is available and could also be used in various ways to achieve the same result.  Similar to example 1 a decoration could be created for each state.  For example for state 3, create a decoration that filters on the active alarm (1) and when the value at change is three (2) override the alarm text message (3) with the relevant text (4). The decorations have the added benefit they can be applied to multiple point alarms.  

Issue A job site is being retrofitted for SmartStruxure. It currently uses Network 8000. When the GCM is removed, the existing MicroFlo II controllers must control individually until a SmartStruxure AS is ready. Can the EMSCO attribute be used to switch to local control until the AS is online? Product Line TAC IA Series Environment Network 8000 MicroFlo II controller Cause Standalone control requirements Resolution From the MicroFlo II Engineering Manual (F-23119): EMS CONTROL [EMSCO] * default = OFF If this input is ON, the MICROFLO II controller will operate from the GCM's setpoints. If this input is OFF, the local setpoints are used. If the input goes ABNORMAL or NOT ACTIVE the controller will treat it as an OFF. Under typical operation, EMSCO is ON and setpoints from the GCM are used. The moment it switches to OFF (ie: loss of communication to a GCM), the local setpoints will be used. At this job site, ensure the local setpoints are identical to the GCM-based setpoints so that when the GCM is removed and EMSCO switches to OFF, the MicroFlo II continues to control. This will provide temporary control until an AS is brought online. There are other 'EMS'-based attributes that should also be reviewed depending on how applicable they are to VAV control at a job site. See the engineering manual for more information.

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 There is no clear guidance on how to handle the SNMP settings for TAC Xenta Servers Product Line TAC Vista Environment TAC Xenta Server TAC XBuilder SNMP Cause Previously the SNMP feature has not been widely used and has not been a security concern. There are two types or flavors of SNMP. One is for browsing a device to get information about it (SNMP Agent), and the other is to automatically send alarms from a given device to a central alarm system (SNMP Alarm Trap). Now according to reports from the field, IT departments are starting to get concerned about the SNMP feature in Xenta Servers. A general overview of how SNMP can be used maliciously for intrusion can be studied here. Normally the IT department requests that: The default community string is changed SNMP is disabled Here is an example of what you see when you browse a Xenta Server (having the correct Xenta Server mib file) using a SNMP browser such as "MIB Browser" from iReasoning Here is an example of alarms received from a Xenta Server via SNMP Resolution All (or most) SNMP settings are changed through TAC XBuilder First step is to change the default community name. If the community name is either "private" or "public" (the latter is default), it can be browsed without knowing the name. You simply change the name in "Community Name" and "Trap Community Name". Download all project files to the Xenta Server afterwards. Now when you try to browse the Xenta Server from the SNMP agent without first defining the community name, you will not be able to retrieve data. Next, we can disable the SNMP Alarm Trap. Download all project files to the Xenta Server afterwards. After that, alarms will not be sent to the IP address configured. Following here are advanced steps to change the ports used for SNMP (161 and 162) If the settings described above are not enough, we can change the port number used for SNMP. This is however a little more complicated. You need to connect to the Xenta Server using FTP (Note that the FTP access may be disabled, refer to Disable FTP in the Xenta 5/7/9xx Controllers if unsure how to enable this), and fetch the following file: /sys/system/snmp.cfg Open the file in Notepad Change the two port number as below - you can choose other port numbers, but it is crucial that they are not the same as any other ports used by the Xenta Server. Upload the changed file to the same location on the Xenta Server Download the project from TAC XBuilder, choosing to download all files You now get this message Here you must click "Target system" or the changed settings are overwritten Note that the port numbers defined in XBuilder have not changed yet Save the project and close XBuilder Open the project again You will now see that the port numbers have the value you defined in the file earlier Now when you try browsing the Xenta Server with a SNMP tool, you can no longer connect on the default port 161

Issue EcoStruxure Building Operation - Sigma logging does not work. Product Line EcoStruxure Building Operation, Sigma Environment Building Operation Enterprise Server Satchwell Sigma Cause Sigma logging has been transitioned to EcoStruxure Building Operation, but does not work. Resolution  The Procedure is as follows; Import the log data sets from Sigma to EcoStruxure Building Operation. Highlight "Log Sets" in the system tree under the Sigma Interface and select to "Send log sets" To confirm that the controller has started logging, select the appropriate controller, and choose "Diagnostics" and "Log Set Statistics" where you can see the statistics which include the log set/object details. To upload the logging, highlight the required log set and select "Retrieve Logged values". To review the uploaded data, highlight the required log value and view it as required Once that the logging in the Sigma controllers is working correctly to EcoStruxure Building Operation, logging from the Sigma server should be disabled.

Issue After changing the sa password in SQL Server Management Studio, subsequent logon attempts fail. Environment SQL Server 2008 Cause It appears that SSMS retains the last saved password in its cache when the Remember Password checkbox is selected, even when the new password is entered into the password field. Resolution Deselect the Remember Password checkbox and login to SSMS. 

Issue Does the Niagara R2 Transition Tool convert graphics? Environment Niagara R2 StruxureWare Building Operation Cause Product inquiry Resolution The tool does not convert graphical images.  It does convert bindings to inputs of a GxPage.  See the R2 Transition Guide (F-27835) for more details.  An excerpt from the guide follows: 3.4.3 GxPage The TAC I/A Series R2 GxPage object is converted to a Building Operation Graphic object. The converted Graphic object contains a Dynamic Text object for each dynamic Gx object at the coordinates of the corresponding Gx object from the GxPage. The Dynamic Text objects in the Building Operation Graphic are named to match the corresponding Gx objects from the GxPage. Graphical images from the GxPage are not converted to the Building Operation database. Bindings to inputs of the GxPage are converted to the Building Operation database as links to the corresponding Dynamic Text objects within the converted Graphic.

Issue Niagara R2 Transition Tool list of R2 Functionality that transitions and does not transition Product Line EcoStruxure Building Operation, TAC IA Series Environment Niagara R2 StruxureWare Building Operation Cause Quick Reference Resolution From page 15 of the R2 Transition Tool Guide (F-27835): TAC I/A Series R2 Functionality That is Transitioned Certain functionality is transitioned to Building Operation: Common control functions BACnet/IP network BACnet MS/TP networks 1 and 2 BACnet MS/TP networks 3 and 4 as routed networks BACnet device objects BACnet shadow objects Container and object tree structure LonWorks Service LonWorks networks LonWorks device objects V2.x Standard MNL LON devices V3.x Standard MNL LON devices V4.x Standard MNL LON devices and associated application files MNL-800 LON devices and associated application files R2 Local LON Device SNVTs Many type conversion, LON multiplexer and demultiplexer objects IbsASDNetwork Service ASD network ASD Device objects TAC I/A Series R2 Functionality Not Transitioned Not all UNC functionality can be transitioned to Building Operation. This functionality is listed in the Objects report. Functionality that is not transitioned includes: BACnet Ethernet network User accounts Address book Security Trigger mechanisms TRIPL program object runtime Object bundling Command objects Right-click commands Communications other than BACnet, ASD, or LonWorks Configurable routers and repeaters LON manufacturer specific control and conversion objects External LON Network Management Tool support UNC physical points (UNC-410 NDIO)

Issue Bindings on every I/NET point in a converted graphic show the Server 1 instead of the correct server name Environment StuxureWare Building Operation Workstation I/NET 2.42 or higher Cause The INET Interface path parameter set in the Export INET Graphics to TGML converter does not revert to default after each conversion.   If the parameter is set to: /Server 1/INET Interface All binds will use that path even if the Server is named 'Building 1' Resolution OPTION 1 - Reconvert Graphics Change the INET Interface path to reflect the correct location. The most common is: ~/INET Interface The '~' symbol points the remainder of the path to the Server that the user is logged into during the import. If the user is not logged into the correct server, this may cause errors. INET Interface is the default name of the I/Net Interface but can be changed. For a site where the I/NET interface is named 'INET' and the Server is name 'Enterprise Server' the INET interface path could be set to: /Enterprise Server/INET OR ~/INET Option 2 - Change Server Name If every path on the I/NET interface references the incorrect server name: Change the Server Name to match the bindings Verify that the bindings now function with the matching Server Name Change the Server Name back to the desired name. The bindings should follow the name change.

Issue Getting error message: “Login Failed - Could not connect to fox server. Check that fox and web SSL settings match or try connecting using https.” when trying to connect to G3 station via a web browser. Product Line TAC IA Series Environment In Niagara G3, Version 3.7.106 Cause Security setting for the Web browser and Fox Service do not match, or the FOX or FOXS port is being blocked. In Niagara G3, Version 3.7 and later, users can set up SSL for both HTTP and FOX connections. The intention is that, when using the applet, SSL settings for HTTP and FOX must match (i.e. HTTPS/FOX or HTTP/FOXS are not allowed). In Niagara G3 3.7 update1 and earlier, users can connect to the applet using the invalid HTTPS/FOX combination. In addition, when loading the applet while using HTTP/FOXS, users are redirected back to the login screen with no error message. In NiagaraAX 3.7 update2 and later, users attempting to use the applet with an invalid HTTPS/FOX or HTTP/FOXS connection will be redirected to the login screen. An error message will appear indicating what went wrong. The Web and Fox settings do not match. They must be set to either HTTP/FOX or HTTPS/FOXS. We’ve found that there is a condition where the error message still displays even though both Fox Service and HTTP match. Reason being is during login to a station via web browser, a check is performed to determine if the Fox Service match the HTTP setting be used. If accessing via HTTP, then port 1911 (FOX) is checked. If accessing via HTTPS, then port 4911 (FOXS) is checked. We found that the corresponding, FOX or FOXS, port were not opened.  Resolution Open the needed FOX or FOXs port: Depending on if HTTP or HTTPS is used, the correct port must be opened for the corresponding FOX or FOXS connection. Port 1911 needs to be open if using HTTP/FOX connections, and if using HTTPS/FOXS, port 4911 needs to be open. Port need to be open to bidirectional TCP traffic.

Issue I/A Series G3 graphic pages can be displayed in a web browser but any graphic images on the page are not rendered properly or are rendered as blank after the Java version is updated to Java 7 Update 65 or later. The issue may not immediately appear but generally appears after navigating between various pages containing graphic images. This issue is most apparent when the user is logged in to the I/A Series G3 system via a WB profile. Product Line TAC IA Series Environment I/A Series G3 systems of any release. Cause Java language issue Resolution If the I/A Series G3 graphics server is running I/A Series G3 release 3.7.106, install the updates from the file Consolidated_Patches_3.7.106_SE_01222015.zip. If the I/A Series G3 graphics server is running I/A Series G3 release 3.8.37, install the updates from the file Consolidated_Patches_3.8.37_SE_01222015.zip. Updates for this issue in other I/A Series R2/G3 releases are not available.

Issue Does the MNB-1000 have a point archiving feature? Environment MNB-1000 (all firmware revisions) Cause Field request (for troubleshooting) Resolution The MNB-1000 does not come with any point archiving features.  That would have to be provided at the network level (i.e. SmartStruxure AS).

Issue Do any of the SmartStruxure Lite room controllers come with a morning warm-up cycle? Environment SmartStruxure Lite SE8x000 SE7x00 Cause Spec requirement Resolution None of the room controllers come with morning warm-up.  It would have to be provided at the network level (i.e. Automation Server).

Issue Want to make a phone call and send a voice message when in an alarm condition. Environment Alarm actions, ES, AS Cyberstation b3 controllers Cause There is no option within SBO or Cyberstation to record or send a voice message on alarm. Resolution To send a voice message when an alarm conditions is detected a third party Autodialler will be required. Autodiallers are available as add on's to the security alarm panels, they have digital inputs that when active can make a call to one or more numbers and send out a pre-recorded voice message. The products are usually sold for a specific country with the appropriate telecoms approvals for the location. An example of this type of product is: http://www.coopersecurity.co.uk/products/productsindex.aspx?intProductID=209&intTab=0   Within the controllers Script or Plain English programming the alarm condition can be detected and a digital output relay switched to trigger the autodialler to make the phone call.

Issue Cannot download the log file through Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause Feature not implemented Resolution To download a copy of the log file, you can type the following in the address bar of your browser, given that the MPM is powered up and accessible. 10.50.80.3/root/log.dat     (assuming the MPM's IP address is set to default 10.50.80.3)