Building Automation Knowledge Base

Issue All Controllers appear offline with any associated I/O showing a status of “Unknown”. The Security Expert Event Service's memory usage builds up until it gets close to 2GB when the controllers go offline.  Restarting the Security Expert Event Service brings the controllers back online. After a period of time the issue re-occurs and controllers again appear offline. Product Line EcoStruxure Security Expert Environment Security Expert Cause A potential memory leak in the Event Service would cause the service to stop working resulting in controllers appearing offline. Resolution 1. Upgrade to Security Expert version 4.3.370.1 or greater as discussed in known issue. 2. A potential workaround to mitigate the frequency of the problem is to disable the Event service from using MSMQ. As long as there are no site integrations using MSMQ then this option can be disabled in the Event Service Config file. Go to ..\Program Files (x86)\Schneider Electric\Security Expert and edit the SecurityExpertEvtSvr.exe.config file. Search for the MSMQ key <add key="MSMQ" value="1" /> and replace it with the following. <add key="MSMQ" value="0" />

Issue Cardholders and door schedules are no longer working and they were yesterday Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause There is likely a holiday or holiday group that is affecting the entire system Resolution A holiday in Access Expert will make every schedule in that instance NOT run that day. Holidays are exceptions to a normally scheduled interval. The holidays within the system apply globally to all schedules. Schedules normally activate at the beginning of an interval and deactivate at the end, however, on a holiday, the schedules do not activate. This creates Holidays as global exceptions to schedules.   Example: A site recently lost all card access and schedules did not work on Veteran's Day. Not all cardholders were out of the office that day.  Reviewing the Instance's Holidays showed that Veteran's Day was configured, so schedules and cards were not working.   ** To resolve this issue: 1. The Veteran's Day holiday was deleted from the above list 2. Next, the controller(s) needed a right click and then "Push controller database" After doing this, the schedules and cardholder access worked normally.

  Issue Cardholders are getting automatically changed from Active to Inactive (deactivated). When the LDAP/AD integration is configured to map the Active Directory attribute UserAccountControl to Card Status in Access Expert; records that have useraccountcontrol = 512 (normal active account) are getting their cards deactivated. These records should NOT be deactivated.   An LDAP query mapped to UserAccountControl Card(s) showing Inactive in Access Expert   Event History record showing the date and time the cardholder record was set to Inactive by LDAP Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Active Directory Cause A version of the LDAP service less than 24.2.1 Resolution Manually set the cardholder to Active as a workaround Ensure the LDAP service installed is greater than version 24.2.1. See the following link to a KB article showing how to "Identify which LDAP service is currently installed" : https://community.se.com/t5/Building-Automation-Knowledge/Identifying-which-Access-Expert-LDAP-integration-version-is/ta-p/480424    If the version installed is older than 24.2.1, perform the following steps: Uninstall LDAP from Windows Programs and Features Navigate to C:\ProgramData\Feenics_LDAP and delete the .dat file Restart the PC Install an updated version of LDAP from Feenic's web site: https://s3.amazonaws.com/download.feenics.com/ldap/Feenics.Keep.Installer.ActiveDirectory.msi  Test to ensure the issue has been resolved with the updated LDAP service

Issue Esmi Transition tool stopped working after upgrading to SX-SOAP version 1.7.0.0 or higher Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Esmi Transition Tool SX-SOAP Cause The SOAP service no longer allows unencrypted communications over HTTP (port 8030) Instead use HTTPS over port 8040. Resolution 1. Open Esmikko Database transition tool 2. Go to the tab "Data Sync Service" the change the SOAP Server Address from http://localhost:8030/SecurityExpertSOAPService/service.svc to https://localhost:8040/SecurityExpertSOAPService/service.svc or https://SERVER_HOSTNAME:8040/SecurityExpertSOAPService/service.svc Note: bolded characters in the second line     3. Click on the button Create Data Sync Service Settings File The tool will stat working.

Issue The Access Expert Bosch integration User sync stopped working whereas previously the Users and their passcodes from the Bosch Panel could be brought into Access Expert using Import Configuration. Example: In the case below, there should be 4 Users, not 2 compared to Bosch RPS.   Note: User 0 is not counted Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Bosch Panel Integration Bosch Remote Programming Software (RPS) Docker Cause There was a September 2024 update from Feenics to fix a User synchronization defect and there are pre-requisites for the User synchronization to operate normally Resolution 1. Check the version number of Access Expert that is displayed when logging in. The version should be 24.9.1.0 or greater 2. Pre-requisites for the User synchronization     a. Area Authority Assigned     b. Person assigned to the User - the person cannot be blank. This can happen if LDAP is used     c. At least 1 Area Assigned To verify: In Access Expert> Access Configuration Select Area Assighnment 1, or 2, etc. Blank Person for a User Open Bosch RPS and connect to the panel, Expand User Configuration> User Assignments 3. Check Access Expert Live Monitoring and the Docker Logs  If the Import is still not working after ensuring Access Expert client software is up to date and the pre-requisites are set, check to see if there are any entries related to the Import or Users that may help troubleshoot by using Live Monitoring in Access Expert and/or the Docker Logs. An Example of the Docker Logs: Launch Docker> Under the Bosch Service> Logs (User 2 and 4 were not coming in prior to the Sep. Update) If the above steps do not resolve the issue, please open a case with Product Support for assistance.

Issue Extended Jace 9000 Commissioning Time. Product Line TAC IA Series Environment I/A Series Jace 9000 Cause With the release of the Jace 9000 using Ubuntu Core 20 Linux as it’s operating system the commissioning/upgrade times increase as compared to the previous Jace 8000. Initial commissioning times can take longer then 15 minutes to finish. There are scenarios where multiple reboots are needed after the initial commissioning is completed. Once the commissioning has been completed for the Jace 9000, boot times should be significantly lower. Resolution Users will need to reboot their Jace at least twice and will need to set more time aside for commissioning of the new Jace 9000s. Please allow for a minimum of 15 minutes for commissioning. If you continue to experience issues with bootup or commissioning on the Jace 9000,  please contact your country level product support. Please note that the JACE-9000 does not print a lot of output on the debug port when you cycle power so give it time to fully bootup.

Issue Incorrect Default Gateway setting may prevent communication with the JACE-9000 Product Line TAC IA Series Environment I/A Series Jace 8000/9000 Cause The Jace8000 and Jace9000 both have primary and secondary LAN adapters. Previously, Workbench prevented users from some invalid IP configurations, but current versions of Workbench, when connecting to a 9000 will allow invalid configuration in the default gateway. Resolution In the 9000, a user can set different default gateways for the Primary (en0) and Secondary (en1) ports. This should not be allowed on a single network device, and leads to unpredictable behavior when routing. Compare the location of the IPv4 Default Gateway in the TCP/IP Configuration of the Platform on a 9000:      And the same page as seen in the 8000: In future versions, this will be changed, but users should avoid invalid configurations in the affected versions. When configuring both LAN ports for use on a 9000, only enter a value for the default gateway field in one adapter. Leave the other intentionally blank. It does not matter which is given a default gateway and which is left blank. Note: Sometimes, when an Adapter has the Default Gateway, you cannot connect to the other Adapter (despite correctly being on that Adapter's local subnet). These symptoms can be triggered by the Ethernet "link" (active connection) toggling up or down.  The link state can change whenever: the JACE is rebooted or power-cycled; and/or the Ethernet switch ("hub")  is rebooted or power-cycled; and/or the Ethernet cable(s) are un- or re-plugged (at either end). In some cases, the symptoms can alleviated by toggling the Ethernet link state, in the ways listed above.

Issue In earlier SLP firmware the sensor displayed the CO2 with yellow and red as shown below:                               However new sensors display CO2 differently.   Is it possible to go back to the old look?   Product Line Field Devices Environment SLP Sensor Cause When launched, the SLA/SLP PM series sensor firmware was updated to display stoplight indicators (red, green, yellow) over the CO2 and PM values. In previous firmware, the stoplight function only applied to CO2 and the full screen showed red, green or yellow, but current firmware highlights the individual CO2 or PM value in the appropriate color. Resolution Firmware of this offer is not field upgradable; it is not possible to revert to the previous functionality.  

Issue Are stainless steel pockets suitable for use in seawater/saltwater applications? Product Line Field Devices. Environment STR Sensor. Cause Customer asking if stainless steel pockets are suitable for use in seawater/saltwater applications. Please note that the answer would need to cover both static (stationary) water and flowing water in the pipe, because seawater/saltwater has different effects on metals depending on whether it is moving or not. Resolution Highest corrosion class is Class III for stainless steel, which seems not suitable for intended application.   ISO 12944 Impact Interior Exterior C1 Very low Heated buildings with clean air, such as offices, shops, schools, hotels, etc. None C2 Low Buildings not heated, where condensation may occur, such as warehouses and sports halls. Atmosphere with low pollution. For example in the country. C3 Middle Buildings for production with high atmospheric humidity and some air pollution such as food manufacturers, breweries, dairies and laundries. Urban and industrial areas, moderate sulphur dioxide pollution. Coastal areas with low salt content. C4 High Chemical manufacturers, swimming baths and ship- and boatyards by the sea. Industrial areas and coastal areas with moderate salt impact. C5-I Very high - Industry Buildings or areas with almost permanent condensation and with high pollution. Industrial areas with high humidity and aggressive atmosphere. C5-M Very high Buildings or areas with almost permanent condensation and with high pollution. Industrial areas with high humidity and aggressive atmosphere.  

  Issue The LEDs on the Flex server indicate the status of the gateway's connection with the Internet and server. This document contains the details that will help in understanding the gateway status.   Product Line EcoStruxure Building Activate Environment ESXBFXSVR00B008 ESXBFXSVR0BC008 ESXBFXSVRBCW008 Cause The behavior of top LEDs and Bottom LEDs are different in terms of troubleshooting and understanding the Flex server state. Resolution The LED blink patterns are indicators used to check the status of the internet connection, server connection, SD card health, gateway firmware health, device connection, and data transfer. Fig 1: Side View of the Flex-Server showing LED location     Fig 2: Gateway Status LED indication   Fig 3: Network Status LED   Fig 4: Ethernet Status LED   Fig 4: Power LED indications            

  Issue While performing the verification tests, an error is displayed: 'error: There is no change in the configurations' as shown below:   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Partner Portal Cause This error occurs under the following conditions: The user made changes in the Partner Portal but later reverted to the original settings/configuration, assuming there should be some changes, and then started the verification tests again. The user chose to perform the test and verification process once post-submission, resulting in this error message. Resolution When the verification process is initiated, it goes through four checkpoints. The user can safely ignore this error message and proceed with the tests directly. Clicking on the 'Load Mapping' button will remove this error message.

  Issue How to program the function buttons in Esmi Fire Panel Product Line ESMI Fire Detection Environment FFSULH1001. FFSULH1002. FFSULH1003. Cause Customer wants the specific buttons for specific actions. Resolution Up to 24 customer specific, on-screen function buttons may be configured to provide control, disablement and engineering functions. The function buttons can be configured to be either available or hidden for each log-in profile. The following procedure describes how to: Set function button attributes/properties. Allocate function buttons to user groups.  Create password specific user accounts for inclusion within a nominated user group. Setting attributes Function buttons (inputs) may be set to operate by association to output devices with the same properties e.g. a security input will activate any device that has security ticked as part its output properties, or as part of a cause-and-effect rule where the function button is the “Cause”.   With Loop Explorer open, select the Configure menu button and select System Manager to open the function button configuration page. Select the 'Details' button to open the properties section of the function button that you wish to configure. Note: Input Properties The properties page allows the user to configure the input action and associated messages, to set individual colours and either to work as a latched (cleared on user interface reset) or toggled action (press function button to operate and again to turn off). Mapping to zones is optional, and the location text is the name given to the function button when completed. Feature Groups There are 4 default user groups that can be configured with specific permissions for different users.     When configured, the function buttons will be included as selectable options in each of the feature groups. It should be noted that if a function button is allocated to the Logged-out group, then it will be present alongside the User Options button when all other user groups have been logged out. Note that at this level then the user options are limited to system information and basic panel tests such as display colour and LED function.     Note: Profile Configuration The example (left) shows that user level 2 is in group one. Group numbers increase as more groups are added (where necessary). Session timeout is the period that the function button will remain available on screen after the user has logged in and has a range from 1 to 255 Seconds. User function buttons are selected according to the users who will be required to access this group. Additional panel related permissions can also be set in the User Menu Options section.   Function buttons allocated to User level 2 and 3 may be accessed using the default login codes. If users are to be allocated unique numerical codes, then it would be advisable to change the panel default level 2 and/or 3 codes where required. As can been seen (right) then the panel event log will record individual user activity.