Issue Security Expert Smart Connector integration is working but Alarms states are not updating, the following error is appearing in Smart Connector logs:   2021-01-07 15:19:22.2621,Info,Processor,<no principal>,Validation Prompt for Security Expert Alarm Update Processor: MayNotContinue : The EwsServer was not located or the credentials you supplied were incorrect. Please verify your credentials and try again. Product Line EcoStruxure Security Expert Environment Smart Connector Cause It appears that the SOAP credential within the Security Expert Discovery Processor does not match the credential within the Security Expert Client SOAP operator credential.   This is a known issue where the credential does not update when changed/edited within the Processor Configuration of the Security Expert Discovery Processor configuration.   Resolution A workaround is to log on to your local Smart Connector portal and edit the credential value within: Setup/Processor Values/SecurityExpertSettings      Change the username and password as required here.                Then save and the new credentials should be updated.  

Issue When launching Security Expert after restarting the PC, a License Expired message is shown. The license is not able to be found. Product Line Security Expert Environment Security Expert Client Security Expert Licensing Cause This is a timing issue. The Security Expert services are attempting to start simultaneously as Windows components that they rely on. Resolution Change the Startup Type of the Security Expert services to use Automatic Delayed, so they start after the Windows OS components. Services - Automatic Delayed   It is also possible that the Security Expert Data Service may be the only service that requires being set to a delayed startup to resolve this problem.

Issue How to populate customized information on the SmartX Sensor display Product Line EcoStruxure Building Operation Environment SmartX Living Space Sensor EcoStruxure Building Workstation Cause Additional information required on how to customize information to be displayed on the SmartX sensor Resolution Before starting, make sure the Integrator Menu icon and the custom information page have been activated: The Integrator Menu icon can be configured under "SmartX Sensor Device/ Display/ Button and Scene configuration" as shown in the screenshot below: Turn on "Allow custom information page" under "SmartX Sensor Device/ Display /Advanced" tab. By doing this, the custom information page is created under the Integrator menu icon of SmartX Sensor Display:        To show how to add custom information to the custom information page of SmartX Sensor display, create a sample script program, where DI1 is a digital input and Status1 is a string output.   In this program, when DI1 is on, the Status1 gets the string value of “Running”, otherwise the Status1 gets the string value of “Not Running”. DI1 is bound to a Digital Value (Green Arrows) under the Application folder and Status1 is bound to the CustomValueText1 (Red Arrows) as shown below:   Open the Watch pane, under the View tab, and add Digital Value and CustomValueText1 (access it through the “SmartX Sensor Device/ Display/ Basic” tab) to it.  When the Digital Value is Active the Custom value text 1 shows “Running”. On the SmartX Sensor, navigate to the custom page through the Integrator menu icon, this will show the “Running” string . Likewise the “Not Running” string would be populated on the SmartX Sensor custom information page screen when the Digital Value is Inactive.  

Issue How to change the IP address in the EC/ES software when it is grayed out. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central (EC) and Enterprise Server (ES) Building Operation WorkStation Cause The EC/ES IP address is grayed out in the Network Tab of the Server Properties and cannot be changed.  This setting is only used to view the IP address that the server is currently using - typically the IP of the network interface card of the PC running this.  To change this setting it must be done through the Communications TAB of the server as detailed in the resolution.  Resolution EcoStruxure Building Operation 2.0 and above EBO 2.0 and above now supports multiple NIC configurations, see 2.0.1 Release Notes for details, in particular, the following note.   Note: That from 2.0 the server will still listen for incoming requests on all network adapters so this setting is only used for choosing which communication settings that the server will use to communicate with child servers. This allows other IP protocols on different networks, e.g. BACnet, Modbus, etc. to communicate with the Server.    It is now possible to select which network adapter the Enterprise Central and the Enterprise Server use.  See the following WebHelp Topic Configuring Network Interface Card for an Enterprise Server or for an Enterprise Central StruxureWare Building Operation 1.9 and below  When the IP address of the computer changes the ES will automatically update the "IP/DNS Address" in the Properties, Network tab. If your computer has multiple network connections, ensure that the Network Interface Card (NIC) to be used for the SmartStruxure network is set to be at the top of the list in the Adapters and Bindings. Go to the computer's Control Panel > Network Connections Select "Advanced, Advanced Settings... " from the menu. In the "Connections:" section, select the Network Connection to be used and press the up arrow to move it to the top of the list. For Windows 7 / Server 2008 See the following link on how to change the order of protocol bindings: How to change the network connection priority in Windows 7 For Windows 8 and beyond, please refer to Adapter priority setting unavailable in Windows 10 In addition to the ES Network Properties, there is also the Communication tab in the ES that lists all of the Server IP addresses in the system. If these need to be changed this can be done by selecting the server and clicking on the "Show/ Hide Communication settings" button circled in red below.

Issue The Exchange Download Center contains all of the assets you once accessed through the Buildings Extranet are now available on a brand new platform. It's easy to search and fast to download. Stay tuned for more great features as we roll this into the all-new extranet solution for Buildings. We ask that you register for a new account on The Exchange.   Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Other, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Exchange Download Center Cause You can utilize the new Buildings web experience from The Exchange. Resolution Navigate to https://ecoxpert.se.com/ * Use a modern browser for the best experience: Google Chrome, Mozilla Firefox, Microsoft Edge, and Microsoft Internet Explorer version 8 or later. If you receive the following error in Internet Explorer despite using version 8 or later, the browser displays the page in Compatibility View. Click here for more information on Compatibility View and how to disable it. The Download Center will not function properly in Compatibility View.   On the header bar, you will see the option in the top right corner for “Login / Register.” Click it.   If you are already registered, enter your email address and password. If this is your first time registering, click the link for “New to the Download Center? Register here!”   Answer whether or not you are a Schneider Electric employee using the radio buttons. If you are a Schneider Electric employee, enter your SESA ID and your desired password for The Exchange. Click to accept Schneider Electric’s Terms and Conditions and hit “Create Account.” * The first time you register, you must be connected to the Schneider Electric network or connected via VPN. This is only required at registration. All future logins can be done externally. If you are not a Schneider Electric employee, enter your first name, last name, company name, location, business email address, and desired password for The Exchange. * It is important to use your business email address if you are a licensed partner. Your email address is used to automatically validate your Partner status and assign the correct permissions to your user profile.   An email is sent to your designated inbox with a link to click through and validate your email address. Once this is done, your login is created, and you are ready to start using the Download Center. * If an error is displayed when trying to validate your authentication code, please try to log in. This happens when an email address has already been verified and oftentimes does not indicate an error with the registration.   Once logged in, you can search and download assets available to your user profile. If you attempt to download a file that you do not have access to, you will be given a chance to report if this is in error. Your username, email, and the asset you are trying to access are recorded. Please enter a message if any further description is required and hit “Submit.” A member of our team will get back to you promptly with a resolution. Web Site Support For any issue regarding The Exchange Download Center, please contact us at exchangesupport@schneider-electric.com.

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 ES takes up to 30 minutes to perform a shutdown. Trace log contains multiple entries indicating "Subscription service forcefully shutting down; [sub-server name]"  "Subscription service forcefully shut down; [sub-server name]"   A secondary issue - When performing Windows Updates automatically, Windows attempts to shut down all running services within one minute which can end the Enterprise Server service prematurely Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server 3.1.x and below Large Multi-server installation  Cause During a shutdown procedure of the Enterprise Server a call to every sub server is made to remove subscriptions. However, the thread pool that executes these commands may already be stopped and the server then waits the 15 seconds timeout period prior to moving to the next item.  On a large 100+ multi-server installation, this 15 second delay can accumulate to a lengthy shutdown period.     The trace log will contain the messages shown  in the issue and the 15-second delay between each server  Enterprise Server Trace log messages seen during shutdown showing the 15-second timeout delay. Resolution Upgrading to 3.2.2 (and above) will rectify the timeout issue provided that the subscription thread pool has already stopped.  These versions now ignore the 15-second timeout for each sub-server if the thread pool has already stopped.   It is possible to extend the Windows service shutdown time by adding or adjusting a registry entry called WaitToKillServiceTimeout .   To change the timeout: Start the registry editor (“Regedit”) In the tree on the left, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control In the right panel, find the WaitToKillServiceTimeout value. If you don’t see it, create it by: Selecting Control on the left Choosing Edit > New > String Value (not DWORD) from the menu Naming the new value WaitToKillServiceTimeout. Double-click the WaitToKillServiceTimeout entry to bring up the Edit String window. Enter a numeric value (e.g. 60000) in the Value data field in milliseconds and click OK to save your change. Reboot your computer. The new timeout setting will not take effect until Windows restarts. Note that this modification will not make Windows wait indefinitely for your service to finish. If your service takes longer than the entered time (in this example 60 seconds), it will still be terminated. Be sure to choose a timeout value that is long enough to cover your scenario, but not too long to make shutdown time intolerable.

Issue WebStation connection is unreliable when using a 4G (cellular) connection Auto logoff times are not be obeyed  Product Line EcoStruxure Building Operation Environment Building Operation WebStation 3.x Broadband Cellular Networks Cause WebStation creates a subscription with the Building Operation server, so it will attempt to connect every 10 seconds.  If this connection is removed/interrupted/ or no longer required for a period of 60 seconds, WebStation will force itself to log out.  This setting is currently fixed and cannot be adjusted.    Currently, there have been instances where this connectivity issue is seen when using, as shown below, a device with a broadband cellular connection attempting to connect to a Building Operation server that also connected to the same/similar cellular network this is the most common scenario where this issue is seen. Resolution It is recommended not to use these cellular network connections to permanently display Building Operation Server information, especially from mobile devices connecting to the cellular network.  This type of connection should be used sparingly and for quick access to view/check information as necessary.  Connection loss can be expected if you move away from the webpage for more than 60 seconds.  Any lengthy connections to the Building Operation Server are recommended to use a more permanent network connection.     Issues have not been seen when using broadband Internet or a similar connection as shown below to a remote cellular Building Operation Server.  This meaning that the EcoStruxure Building Operation system has remote Internet access via a broadband cellular connection. To troubleshoot this further, capture a HAR file using the details provided here How to collect a network trace | Microsoft Docs and reproduce the issue while this debugging window is open within your browser.  Note: This capture must be done at the source; that is where WebStation is running.  This may not be easy to do using a mobile device.   Send this saved HAR file and the Internet browser version and EBO version used along with connection types to your local support channel. 

Issue Upgrading from EBO 2.0.x to 3.0.x causes I/NET to become incompatible. After upgrading to 3.x the I/NET controllers do not come online. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure Building Operation (version 3.0.1 and later) I/NET Seven Software (version 2.44 and above) Cause I/NET Seven Software is built using a 32-bit interface. Starting with EBO 3.0.1, EcoStruxure requires the use of a 64-bit interface. Resolution For INET seven to operate with EcoStruxure Building Operation 3.0.1 it is necessary to obtain a 64-bit DLL from the Exchange and install it in the INET installation prior to the upgrade. Search for INET IPortAPI64 - Software on Exchange.  Download the IPortAPI64_EBO.dll. Unzip the DLL and copy the DLL to the same folder as the 32bit INET install, by default this will be C:\Program Files (x86)\INET Seven folder. Note: if INET was installed in a different folder this can be found by examining the Windows registry key ”INETSevenPath” at HKLM\SOFTWARE\WOW6432Node\CSI - Control Systems International\I/Net 2000/Configurations. Install EcoStruxure Building Operation 3.0.1 When the ES restarts the InetPlugIn will connect to InetIoSrv via the 64-bit IPortAPI64_EBO.dll.

Issue Setting up, using, and troubleshooting Windows Active Directory with Building Operation Workstation and WebStation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation WebStation Windows Active Directory Windows Server Cause When integrating EcoStruxure with Windows Active Directory, NO user accounts need to be created in EcoStruxure, all that needs to be done is map the EcoStruxure User Account Group(s) with the Windows group(s) that will be used.  You can map Windows Active Directory groups to Building Operation user account groups if Building Operation runs on a network that uses this directory to manage users and user account groups. A Building Operation user account group that includes a Windows account group can also be a member of another Building Operation user account group. Mapping Windows Active Directory account groups to Building Operation user account groups has advantages both for administrators and operators. Administrators can manage the user accounts in the Windows Active Directory, rather than managing the accounts in two places. Any changes are instantly implemented to the mapped Building Operation user account group. Operations only have to remember the Windows login. Once logged in to a Windows user account that is mapped to a Building Operation account, the user is authenticated to access WorkStation without having to log in a second time. Note: The Building Operation domain used to map the Windows Active Directory user account groups must be a member of the Windows domain where the Active Directory is located. Windows Active Directory account groups can only be mapped on servers that are based upon Microsoft Windows operating system. Automation Servers, cannot map Windows Active Directory groups. For example, the Windows Active Directory user account groups Main Admin and Main User are mapped to the Building Operation user account groups Administrators and External Users. The External Users user account group is a member of the Operator user account group. The Administrators account group, which is a member of the External Users, inherits access to the Operation workspace. The user will then log into Windows on the PC where the WorkStation is installed. When logging into EcoStruxure Workstation the authentication is automatically done from the Windows user account. Resolution NOTE: Active Directory association cannot be achieved using the inbuilt Local Domain Create a new EBO Domain and associate it with your active windows Domain. Create an EBO Domain Group within that new Domain and associate it with the Windows Domain Group in which the Windows Active Directory user(s) reside. Log in using Windows Username, Password, and Domain rather than EBO credentials.  When logged on the Enterprise Server PC as a Domain User it is also possible to select the "Log on as" box. See WebHelp: How to Create and Configure a Domain Conceptual Information on Windows Active Directory User Groups How to Create User Account Groups Troubleshooting Windows Active Directory with Workstation Log in Error: Wrong user name or password If the EcoStruxure Building Operation Domain has the same name as the Windows Active Directory domain name, it will expect the user account to exist locally in the Building Operation domain. Log in Error: "User account not associated with a group. Contact your Administrator." Verify that the Windows user is a part of the Windows group configured in the Building Operation Group settings. In order to identify every group that the current windows user belongs to, run the command: whoami /groups Once the Windows user has been confirmed as a member of the configured Windows group, try changing the Log On as credentials for the Enterprise Server service. The default user that is used when installed is the "Local System account". The Windows account used to run the Enterprise Server service needs "read access" to all places (e.g. OUs) in the Active Directory where user groups potentially involved in an EBO Windows log-on can be found. Note: By default, all domain users in an Active Directory have read access to Active Directory "Users and Computers" objects so it is the sites that have restricted this in some way that may face issues. You do not need to use “domain admin” type accounts for this as they are granted way too much authority in general. An account that has read access to sufficient parts of the AD while having only normal local user privileges on the machine where the Enterprise Server is running will suffice. From the Windows Start menu, launch Computer Management. In Computer Management go to Services and Application > Services. Find Building Operation X.X Enterprise Server, select it and Stop the service. Right-click on Building Operation X.X Enterprise Server and go to Properties. Select the Log On tab. Under Log On as select "This account". Enter a Windows user login that has sufficient Windows rights for the Enterprise Server to log on as. Click OK and then start the service again. Log in to Workstation again using Active Directory. Troubleshooting Windows Active Directory with WebStation From version 1.5.0 and up, using Windows Domain accounts is supported in WebStation. However, the following must be done in order to log in. You need to use HTTPS. Use your Windows username and password.  The Windows domain must be defined (It needs to be the actual Windows domain, not what you named the domain in Building Operation). For Windows 10 you can locate this as follows: Click on the Start button. In the search box, type Computer. Right-click on This PC within the search results and select Properties. Under Computer name, domain, and workgroup settings you will find the Domain name listed. Windows Domain information (note this is case sensitive) An example of logging in via WeStation using the above configuration is shown below:     NOTE: In some cases, only the first part of the domain is required i.e. apa as shown in the above example.  But the case must be maintained - in this case, lower case. Download a TVDA for Single Sign-On Instructions

Issue Unable to access the SE7xxx Room Controller configuration parameters menu - displays an error code. Product Line EcoStruxure Building Expert, Field Devices  Environment SE7xxx Room controller SE7000 Series Ex. Viconics branding VT7000 Series Cause The display shows an error code when used, this is indicating a password is required, an example of the error code may be 977 or 996. Resolution Contact your region's Customer Care Center for a temporary password. The error code which is unique to that controller will be required by the Customer Care Center to calculate the temporary password. Note for PSS; Check Internal article. 

Issue Is any version of Security Expert compatible to install in SQL Clustering? Product Line Security Expert Environment Security Expert Microsoft SQL Server Cause Installation and configuration of Security Expert databases (Security Expert and Security Expert Events) in SQL Clustering Resolution There is not currently a Tested Validated Documented Architecture (TVDA) for Security Expert compatibility with SQL Clustering so it is not officially supported. It is recommended to install and configure in standard SQL Server versions. Click here to refer compatibility matrix for supported environments.

Issue Upgrade warning and Error Conversion Log Analysis Additionally upgrading an AS from version 1.3 to 1.4 can create a number of unresolved or invalid references. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, ASP, ASB Building Operation Enterprise Server Building Operation Device Administrator Conversion Log Cause When upgrading using the Device Administrator various warning and errors can be seen. Errors will prevent the upgrade, but warning will still allow the upgrade to continue. Starting in version 1.4, new rules have been put in place that will invalidate some bindings that had previously been made in older versions. These rules may cause errors to be produced in the Conversion Log found in the Device Administrator. The three new rules are: Public Numeric/Signal bindings will be dropped. Multiple bindings will be restricted to one. Binding to Local Node NVIs will be dropped. For more information regarding the rule changes made in version 1.4 see Reference Guide and References beginning with 1.4.x. Resolution Instructions on how to perform the Automation Server upgrade and how to obtain the Conversion Log, see Upgrading Automation Servers from 1.3 to 1.4. Breakdown of the Conversion Log The file paths given in the Conversion Log entries will direct you to the location of the unresolved or invalid reference. Depending on the type of entry it is, it may require further action to correct the problem.   Type of entries found in the Conversion Log WARNING: ERROR: Invalid_Property_Reference (destination) (source) Explanation: Either rule 1 or 3 has been broken. If a public numeric/signal is bound programmatically to another object then it violates rule number 1. The public numeric/signal in the program must be changed to an input or output before upgrading the database. If the destination of the binding is an NVI in the Local Node then it violates rule number 3. A change to the configuration of the local node must be implemented before performing the upgrade. In many cases the substitution of an NVO for the NVI will address this issue. Explanation: This binding should not have been allowed in SmartStruxure version 1.3. In the StruxureWare Building Operation Technical Reference Guide, you will find on page 2107 that BACnet priority 6 is reserved for future use. This binding needs to be made to a different priority. WARNING: ERROR: Object_Does_Not_Exist (object). Explanation: The object that the reference is trying to bind to does not exist. In other cases the binding was already broken in the source database so it will remain broken in the target database. The binding fix can be addressed before or after the upgrade. WARNING: Property (property) bound to (property), so binding to (property) is dropped. Multiple bindings are not allowed in SmartStruxure version 1.4 and above. Explanation: The object is being written to by multiple objects and/or programs. This violates rule number 2 and is no longer accepted. After the upgrade, only one of the bindings will be left connected and all others will be dropped. This will require changes to be made to the configuration to maintain the same operation. Note: In some cases this warning can occur due to a default value of a configuration object that is mistakenly interpreted as a duplicate binding. The binding is in fact preserved by the upgrade and no further action is required. WARNING: Discarding incomplete binding for (object) -unknown source. Explanation: Due to a version 1.3 defect, the source version configuration database contains an incomplete binding error. This is not a problem but it may be a sign that someone intended for the property to be bound to something but failed to do so. Therefore, the configuration should be examined after the upgrade has been completed to insure that everything is okay. No information has been lost in the upgrade but check the configuration to rule out any errors in the source version database. WARNING: Property (property) in (object) is Unit configured but is not configurable in the new. Explanation: This property has a selected unit configured in the source version database, while in the target version configuring the unit of this property is no longer possible/meaningful. These errors should be investigated to insure that there has been no negative impact on the operation. Generally this error will not be a problem and will require no further action. WARNING: Property REF in (object) is not defined in the new system, skip REF. Explanation: The REF property prior to version 1.4 held a back-reference to an object or property that was referring to the property at hand. Starting in version 1.4 and on, the back-references are handled by other means and are no longer represented in the configuration database. This information can not be upgraded but this is not a problem and no further action is required. WARNING: Invalid value for (property) in the object, (object). The default value has been applied. Explanation: The value seen in the source version is invalid or can not be found; therefore the upgrade process sets it back to the default value. No further actions needs to be taken. WARNING: The declared instance (instance) is obsolete but contains non-default data which has been discarded. Explanation: If the instance is a SavedUserTokens or System/Remote Server warning then the warning can be ignored. No further action is required. WARNING: Property (property) in (source) is not an acceptable property type and is not configured. Explanation: This has to do with the lead reference for shadow Alarm Control Panels that cannot be properly upgraded due to changes to the type of system in version 1.4. There is logic in place that automatically sets the lead reference to the ES again. This is a warning that can be ignored. Explanation: There have been changes made to the type of system. This change prevents the hidden SynchSource property of the Time Zone setting in the source version of the database from being upgraded automatically. If the lead reference was set for Time Zone in the source database, this may have been erased and will have to be done again after the upgrade. This should be followed up manually. Explanation: The new referencing scheme expects all references to be relative so if there is a full binding path it is perceived as an error. This is not an issue and requires no action. Explanation: MatchedDevice is a hidden property that can not be seen. This warning refers to old items that have not been cleaned out. This warning can be ignored. Note: Also keep in mind that the upgrade process considers any empty link "not an acceptable Property". This error can be ignored, no changes need to be made. INFORMATION: Property "Value" in (location) is Unit configured but is not configurable, default unit is used. Explanation: This property has a configured unit that is no longer allowed to be configured in the target database, a fixed default value is used. This is unlikely to cause a problem, no further action needs to be taken.  

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 Locating and downloading latest images Product Line Satchwell Sigma Environment 3.46.57, 3.46.62, 3.46.70, 3.46.72, 3.46.73, 3.46.79, 3.46.80, 3.46.81, 3.46.85, 3.46.86, 3.46.89, 3.46.98, 3.46.104, 3.46.105, 3.46.106, 3.46.107, 3.46.108, 3.46.110, 3.46.111 Cause Identifying the correct image version for different hardware versions. Resolution Sigma UNC/ (V53) = Firmware 6b Sigma Firmware UNC596 6.b - Release note   Sigma UNC3 (ARM7) = firmware build 1.p.0 Sigma Firmware 1.p.0 UNC3 - Release note   UNC 532 V25 = Firmware 6b Sigma Firmware UNC532 6.b - Release Note   IC-Modbus = Firmware V5h IC-Modbus v5h Release Note   IC3 Modbus = Firmware1.n.2 IC3 Modbus - Release Note   IC SNP = Firmware 5d IC-SNP Integration Controller v5d for Sigma Rel 3 - Release Note   IC3 SNP = Firmware 1.g.1 Sigma 4.05 Firmware Supplement - Release Note (there is no release note specific to SNP Firmware 1g.1).   IC York = Firmware V3e - Not available to download. IC-York Integration Controller v3e for Sigma - Release Note   IC3 York = Firmware 1.d.0 IC3 York = Firmware 1.d.0 – Release Note   Sigma IC3 Unifact 1.d.0 – Firmware Sigma IC3 Unifact (RTC) - Release Note

Issue When setting up the TH90x series thermostats there are communication limitations.  Unable to pull multiple registers.  Some registers are only in Celsius, regardless of the display setting. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic TH903 Series Thermostat SpaceLogic TH907 Series Thermostat Cause The TH903/TH907 does not support multiple/block register reads in Modbus.    The following parameters will show their value in Celsius only via Modbus communication regardless of whether the display is showing values in Celsius or Fahrenheit:   All SpaceLogic Series TH9xx thermostats Register 30 - Function Code 3/6 - Room Temperature (from the remote Modbus Controller) Register 1 - Function Code 4 - Actual Room Temperature 7 Day Programming Versions of TH900: Register 26 - Function Code 3/6 - 7 Day program schedule, heat set-point Register 27 - Function Code 3/6 - 7 Day program schedule, cool set-point Register 30 is used by the customer to override the current temperature. This register expects a value to be written to it every 15 seconds. If no values are written to it every 15 seconds, then it will populate with our internal temperature sensor value. Resolution Registers must be read one at a time rather than in groups. When using Modbus write the set-point values in Celsius. 

Issue After loading SigmaX on to a new laptop it does not run.  An error appears "The file SigInterfaceMfc.dll is not found." If accepted then another error message occurs, "The file SigShell.dll is not found." Product Line Satchwell Sigma Environment SigmaX Windows XP, 7, 10 Cause The Windows Environment Path "C:\sigma\bin" is not set when SigmaX was installed. Resolution Manually add the setting “c:\sigma\bin” to the Windows Environment Path. On Desk Top find the icon "My Computer". Using right hand mouse button select "Properties". Select the "Advanced" tab. Select the "Environment Variables" button. In the "System variables" window highlight the "Path" variable. Select the "Edit" button Scroll to the end of the "Variable value" text box and append the text string with “;C:\Sigma\bin\” Select "OK" buttons to close and save the changes (three times).   Also see similar KB article - SigmaX reports a missing DLL.

Issue The address used to access the Generate Authentication URL up to and including PME 9.0 no longer works. Product Line EcoStruxure Building Operation Environment Energy Expert Power Monitoring for Building Operation Cause Up to and including PME 9.0 the following address could always be used to access the 'Generate Authentication URL' page which allows a user to manually create urls/hyperlinks for specific PME pages (with and without authentication) to use in EBO: http://<yourservername>/SystemDataService/Auth/GenerateAuthURL .     However with the advent of PME2020 this address is no longer valid. Resolution The address for the 'Generate Authentication URL' page has changed in PME2020 and permission to access this new address must also be activated via an Query run on the SQL database of the PME2020 install. Page 1676 of the PME 2020 System Guide  - Manual integration steps without using the Integration Utility - shows the required steps and the new address to be used.

Issue ES Database has grown to several gigabyte Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause ES Database size can grow quite large when the ES crashes often. Open Software Administrator and find the location of the ES db folder. Below are two screen shots of the Logs and Crash Information folders. As can be seen, these dump files can increase the size of the database. Resolution Once the reason for the Enterprise Server crash is resolved, these files can be either be deleted or, preferably be moved to another storage/drive location. If the ES/EC is still crashing, all the core dumps should be collected and sent to to your local support team for processing. Due to the size of the crash dumps, upload to BOX or similar and provide the link to the support team.

Issue The License Server is not working and may show Vendor Daemon Down errors. The LMadmin log shows the error. LicenseEngine (taclic) exited with status 28 Product Line TAC Vista Environment Vista License server Cause DEP is activated. Antivirus or other software can scan/use the port used by the vendor daemon. If the time drifts over two minutes and a time synch occurred, the vendor daemon can stop. https://support.citrix.com/article/CTX137111 Resolution First, check so DEP is not activated. Make sure that there is no antivirus program that has portscan activated Make sure there is no other software that uses the same port as the vendor daemon Make sure that the time does not drift too much, if the time drift two or more minutes and then resynch the vendor daemon can stop This is more true on VMware that can make time synch from either the domain or VMware tool. Check Windows event log (Security) for time synch messages. NOTE: It can also appear just by stopping the server manually.

Issue After transitioning an INET security system to Security Expert, SCU1200 and SCU1280 controllers do not come online Product Line Security Expert, TAC INET Environment Security Expert Controller (SP-C) I/NET SCU1200 I/NET SCU1280 Cause The INET-to-Security Expert transition brings each SCU1200/1280 into Security Expert as an Input Expander but there is a known issue that causes the devices to remain offline. R&D is working on a fix. Resolution The workaround for bringing a SCU1200/1280 controller online in Security Expert is to create a Reader Expander and then edit the inputs and outputs associated with the SCU1200/1280 to point to the Reader Expander you’ve just created.   Important:  Create a backup of your Security Expert database before proceeding with the instructions that follow.   For a transitioned SCU1200/1280, create a Reader Expander as follows: In Security Expert, navigate to Expanders > Reader Expanders. Choose a Controller from the drop-down list. Click the Add icon. Define a Name for the expander.  The transition tool would create a name like SCU1200 <703503> for the expander.  In this example, the SCU’s link address is 70, its station address is 35, and its point address is 3. When manually defining the name of the new expander, you may wish to use this naming convention to keep the system uniform. Set the Physical Address of the expander.  This address should be 1 higher than the point address of the SCU.  So, for SCU1200 <703503>, the point address is 3 (7035 03 ) and so the physical address of the expander should be set to 4. Set Port 1 Network Type to “Third Party Generic”. Set Port 2 Network Type to “Third Party Generic”. Expand the Commands section and enter the following commands:       PortOne=INET       HardwareType=INET Navigate to the Reader 1/2 tabs and perform the following steps: Set Reader 1/2 Keypad Type to “None”. Uncheck Allow Reading Opened/unlocked. Uncheck Display Card Detail when Invalid. Navigate to the Reader 1/2 Options tabs and perform the following steps: Uncheck Door Sense Enabled. Uncheck REX Enabled. Uncheck Invert REX Input R1/2. Uncheck Always Allow REX R1/2. Save the expander. When presented with the Configure Module wizard, perform the following steps: Set Inputs to 0. Set Outputs to 0. Uncheck Add Trouble Inputs. Uncheck Add Doors. Click Add Now.   Edit the inputs associated with a transitioned SCU1200/1280 as follows: In Security Expert, navigate to Programming > Inputs. For each input associated with the SCU1200/1280, change the Module Type to “Reader (RD)”. Save the input.   Edit the outputs associated with a transitioned SCU1200/1280 as follows: In Security Expert, navigate to Programming > Outputs. For each output associated with the SCU1200/1280, change the Module Type to “Reader (RD)”. Save the output.   When you have finished with all of the steps above, perform a Module Update on the Reader Expander.  Repeat these steps as necessary for other SCU1200/1280 devices.  Once you have verified all SCU1200s/1280s are working properly, you can delete the Input Expanders that were created by the transition tool since they are now unnecessary.

Issue Replacements for Satchwell AY series actuators Product Line Field Devices Environment AY Actuator Cause Obsolescence of AY series actuators from Satchwell Options range Resolution The following pop top actuators can be used to replace the AY actuator series:   AY1201                                              AG13U230 AY1251                                              AG23U230 AY1301                                              AG13A230 AY1351                                              AG23A230   For further Knowledge Base information - Types of TAC Erie Pop Top valves and actuators available from Schneider Electric in the UK.