Building Automation Knowledge Base

Issue A system with multiple WebRequest calls appears to become erratic after upgrading the AS-P to EBO 2022 and above. After a reboot, multiple scripts execution are hanging.   In previous EBO versions, the script would be stopped and return an Unknown Exception error message.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause The Architectural Guidelines always recommended a maximum of 5 concurrent WebRequest calls. In EBO 2022, this limitation is enforced to limit the impact on the system resources and prevent scripts stopping due to Unknown Exception errors.   Architectural Guidelines    Web requests exceeding this number will be queued, and the scripts doing these calls will hang on that function as the queue is emptied. This will directly impact the execution of other scripts.   Resolution 1. Enforce a good scripting practice to prevent more than 5 concurrent Web Request calls. 2. Cascade the execution of scripts to make sure that after a reboot, the scripts are executed in a sequence to prevent simultaneous calls filling the queue and causing scripts to be stopped.  

Issue In some projects there is demand for importing a large number of individuals from an existing spreadsheet for individual information at one time. Product Line TAC INET Environment I/NET Seven Revision 2.xx and higher Microsoft SQL Server Management Studio Express Cause In some cases the customers have a spreadsheet or database of employees and/or users which they want to quickly import into their I/NET Seven Access control database. Resolution The whole process is to import the data from the excel file to the IDWorksView table of SQL database of I/NET. The steps below needs to be followed: Prepare the Microsoft SQL Server Management Studio Express. Click here to down this tool for version 2005 free of charge. If for version 2008, click here to download. Then install this tool. Download the individual spreadsheet Excel template and SQL script here. Save to the C:\. Ensure that the Tenant, Group have been added in I/NET already. Also ensure that all the card numbers in the spreadsheet don't conflict the ones already in I/NET. Enter the individual information into this template. If there are photos for individuals, the folder of the photos also need to be entered. Open the Microsoft SQL Server Management Studio Express and connect to the database. Find the InetDb database, and open the SQL script just downloaded from the File menu. Click Execute to run the script. Then if without any problems, the successful result will be shown in the output message window. The next step is to get the imported data downloaded to the controllers. For each SLI perform a station SAV and station restore – it may take some time for all this information to be downloaded to the DPUs and may fail in some instances.  You may also notice the system slow up for some time (hours) until all of this information has been successfully downloaded to the controllers.  It may also be necessary to force the data into the DPU by performing staggered DPU Restores on specific doors that are experiencing incorrect functionality.  There is also a method that download the imported data without any operation in I/NET software by a function called Automatic DPU Restore. Refer to Automatic DPU Restore and Individuals added via Datacard ID Works are not getting access to doors for detailed information about how to set Automatic DPU Restore in I/NET. This is the method using SQL Server Management Studio Express. The Microsoft Access can also be used to do the importing work. Refer to How to import a large number of Individuals into an I/NET Access Control database for detailed information.

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 JACE 8000 WiFi radio Product Line  TAC IA Series Environment I/A Series N4 Jace 8000 I/A Series N4.15 Software Cause Niagara Framework, Niagara 4.15, includes an update to the QNX operating system that no longer supports the WiFi chipset in the JACE 8000. Resolution Customers who have deployed JACE 8000 devices with the WiFi connectivity option will not be able to activate or configure the WiFi radio under Niagara 4.15.  Blackberry QNX has dropped support for the WiFi chipset used in the JACE 8000. This change was effective with the latest release of its QNX 7.1 Software Development Platform (SDP) in November of 2024. Niagara 4.15 includes this QNX 7.1 SDP update and will install based on the current setting of the JACE 8000 WiFi radio.   What should the Jace 8000 WiFi customer expect When upgrading a JACE 8000-WiFi unit to Niagara 4.15, switch the WiFi radio to the DISABLED setting before attempting to install. In this configuration, 4.15 will install normally. Note that after commissioning, you will no longer see the WiFi Configuration option on the platform menu, and you will not be able to connect via WiFi. Also, note that Niagara 4.15 will not install if the WiFi radio is set to ENABLED.     What to do in situations where WiFi connectivity is needed A factory reset will restore Niagara 4.9, and the JACE will regain its WiFi functionality. You can then commission the JACE 8000-WiFi unit with Niagara 4.14.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 For hardware failure or persistent issues, it is necessary to replace Security Expert hardware components Product Line EcoStruxure Security Expert Environment Security Expert SP-C or SP-C-Web controller Expanders (i.e. RDM2 or SP08) Card Readers Cause A hardware failure occurs or a persistent issue happens that requires steps to replace Security Expert hardware Resolution At times it's necessary to replace Security Expert hardware   Steps to replace Security Expert SP-C Controllers: 1. Determine if the original controller has encryption turned on If the failed controller was setup for encrypted communications with the Security Expert server, the newly installed replacement controller will not have the encryption keys to be able to decode the packets from the server. Attempting to bring it online will be unsuccessful. On the controller's Configuration tab press the Disable controller encryption, then Yes to confirm. A replacement controller will typically be unencrypted. As soon as it shows online you can decide if you want to encrypt it. If it was already encrypted in Security Expert before replacing it, you might need to hit the encryption button again to get it in sync. Note: It can be helpful to use the event server diagnostic. If you see messages including “unencrypted” set encryption on the controller and see if it comes online. 2. Disconnect the old controller from its networks unplug ethernet and RS-485 module network and other hardware 3. Replace the Serial Number in Security Expert In Security Expert, navigate to Sites | Controllers. Replace the Serial number of the old controller with that of the new one. 4. Disable encryption In the Configuration tab, click Disable controller encryption. 5. Default the Controller If the controller has been used on a different server, default the new controller. See the SP-C Installation manual for detailed steps on performing a controller default https://ecoxpert.se.com/search?documentUUID=b4fb1237-fd07-2ee5-d9ad-4324178c364c&title=SP-C%20Security%20Expert%20-%20Security%20Purpose%20Controller%20-%20Configuration%20Guide  6. Enter the event server settings on the controller Log in to the new controller's web interface. In Settings, enter the same IP settings, event server and ports as those of the old controller, then restart the controller. Note: Remember to remove the jumper used to default the controller 7. Connect the new controller to the networks and hardware The controller should come online in Security Expert if all the network settings, serial number and encryption settings are in sync. 8. Download the controller In Security Expert, right click on the controller record and select Force download. The controller should receive the download. 9. Enable encryption Once the controller is online, in the Configuration tab click Enable controller encryption in Security Expert if desired. Steps to replace Security Expert SP-C-Web Controllers: 1. Take a backup of the old SP-C Web controller Login to SP-C Web, In System | Backup controller This creates a .bak file prompting to save in a folder or in the downloads folder 2. Disconnect the old controller Unplug the controller from the ethernet network, the RS-485 module network and other hardware. 3. Register the new controller Log in to the new controller and register it in System | Licensing 4. Restore the previous backup taken Navigate to System | Backup and Choose File and browse to the previously created .bak file 5. Configure the IP settings In System | Settings, enter the same IP settings as those of the old controller, then restart the controller 6. Connect the new controller to the networks and hardware and Test Steps to replace Security Expert Expanders: 1. Disconnect the old expander from the RS-485 module network and any inputs, outputs or card readers. 2. Connect the new expander to the module network and hardware. 3. Set the new expander's address to the same as that of the old expander.  In Security Expert, navigate to Sites | Controllers, right-click the controller and select Module addressing.  In SP-C-WEB, use the Expanders Wizard. To address a keypad, power cycle it and then press [X], [Enter]. Enter the new address and press [Enter] to save. Note: Sometimes the old expander can remain in the module addressing window even after being physically disconnected. To free up the address, module update the expander record. This will fail, but the address should become available. 4. Module update the new expander. The expander should start operating normally using the programming from the original expander. Steps to replace Security Expert Card Readers: 1. Disconnect the old card reader from the reader port. 2. Connect the new card reader 3. Apply any Custom Configurations If the reader needs any custom configuration, apply it within two minutes of the reader starting up using the config card. 4. Wiegand and RS-485 readers should connect automatically For OSDP readers, put the card reader into installation mode, then send an OSDP install mode command to the reader expander.   Additional configuration after controllers have been replaced If used at the site, areas that are configured for duress alarms default to un-armed after a SP-C has been replaced and need to be re-armed via forced arming. If used at the site, the alarm dialer (Contact ID) "Service Mode" defaults to "0 - Manual Mode" after a SP-C has been replaced (see the arrow below) and needs to be changed to "1 - Start with controller OS". Service mode Test the replaced hardware to ensure the issue is resolved

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 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 When following the Enabling Transparent Data Encryption configuration steps in the SX-SRVR Security Expert - Client Server - Installation Guide, an error is seen running the supplied script to backup the certificate and encryption key.   Cannot find the certificate ‘TDECertificate’, because it does not exist or you do not have permission. Product Line EcoStruxure Security Expert Environment Security Expert Server Microsoft SQL Server Cause When copying the text from the SX-SRVR Security Expert - Client Server - Installation Guide the formatting contains a carriage return that stops the script from being able to be run in SQL. Resolution 1. Ensure the correct database is being run against by selecting it from the drop down in the SQL Server Management Studio menu bar or by adding "use master" as the first line in the script. 2. Create folders "c:\storedcerts" and "c:\storedkeys". 3. Fix the script by removing the carriage return breaking up the "TDE Certificate" file name.   The following script was successfully used to backup one file in each directory. use master; go BACKUP CERTIFICATE TDECertificate TO FILE = 'c:\storedcerts\TDE Certificate' WITH PRIVATE KEY ( FILE = 'c:\storedkeys\TDE Key' , ENCRYPTION BY PASSWORD = 'Hard_drive' ); GO  

Issue There is a need to identify the Ports, URLs and Static IPs which must be open through customer's firewall for EcoStruxure Building Activate Flex Server and Partner Portal Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause Ports, URLs and Static IPs list needed to create firewall exceptions for EcoStruxure Building Activate Flex Server and Partner Portal in order to keep them functioning correctly. Resolution Below are the list of ports, URLs and static IPs that must be open through a site's firewall/network: URL Port Protocol Usage https://sentry.zenatix.com 443 TCP Allows the gateway to upload error logs and diagnostics. https://router.zenatix.com 443 TCP Allows the gateway to download Linux & Python updates from the Zenatix Server. Regularly polls the Zenatix Server to check internet connectivity. https://timesync.zenatix.com 9090 TCP Time server allows the gateway system & gateway clock to remain synchronized with Zenatix Server. https://gitlab.zenatix.com 443 TCP Used for troubleshooting to update the gateway codebase from the Zenatix Server. https://telemetry.zenatix.com 443 TCP Used for sending IoT device data and gateway health data to the Zenatix Server. https://emqx.zenatix.com 8883 TCP Used for communication between gateways and Zenatix cloud services for getting configuration or alarms from Zenatix Server to gateway and vice versa. 54.169.200.193 1194 UDP Allows Zenatix to remotely access and do API calls to the gateway through OpenVPN. https://mender.zenatix.com 443 TCP Used to download firmware updates to gateway from Zenatix Server.   Note: For the list of URLs to be whitelisted for the Global Portal, please refer to Required list of URLs/Ports to be whitelisted under firewall/network for EcoStruxure Building Activate (Global Portal).

  Issue EcoStruxure Building Activate Flex Server doesn't pass the GSM Signal Strength test.   Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause The Flex Server must achieve a GSM Signal Strength greater than 14 to pass the test. If the signal strength is less than 14, the test will fail.   Resolution Below are the troubleshooting steps which should be checked/followed: Ensure the Gateway is located in an area with good network coverage. If possible, reposition the Gateway to improve signal strength. Verify that the APN settings for the SIM card in the Device Management Dashboard are correct. Change the network carrier and reconfigure the APN again

Issue Schedules are not unlocking or locking doors according to the dates and times specified by the scheduled events Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Cause The Security Expert system has a number of variables that schedules take into consideration when determining control of doors and if one of these isn't configured correctly, it will affect proper schedule function and control. Resolution 1. Verify that the schedule has the appropriate dates and times set 2. Check Holiday Groups and ensure that any calendar actions created to repeat each year have the same start and end date. Having different start and end dates with a repeat can cause the action to span long periods which can affect scheduled operations.    

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 Bog File Encryption Changes in 4.15 Product Line TAC IA Series Environment I/A Series N4 Enterprise Server I/A Series N4 Jace 9000  Cause In Niagara 4.15, to continue to provide the best security practices, the user password hashes are now included in the encryption by the system passphrase. Resolution The system passphrase was introduced in Niagara 4 to provide additional protection to sensitive data from the Niagara system. Prior to Niagara 4.15, this included all reservable passwords (such as Niagara Network, database connection passwords, etc.), excluding the user's passwords as those are protected by being hashed. If you do not have the system passphrase for a station and need to unlock it through Workbench, both the user and encrypted data such as passwords will be removed where prior to Niagara 4.15 the user were left untouched as they are hashed. If you are copying a station from a remote host which you do not have the system passphrase for, you will need to reset the passphrase to successfully copy the station onto a new remote host. You will be required to enter the passphrase to edit or modify users or encrypted properties such as password fields for email, Niagara Network, etc. Prior to Niagara 4.15, you could edit and modify users without the passphrase, in Niagara 4.15 this will require the passphrase to decrypt the users.   Operation Niagara 4.14 Niagara 4.15 Modifying users in offline station bog file Users can be modified without entering the station bog file passphrase Station bog file passphrase is required to modify users Reset station bog file passphrase Removes reversable client passwords such as email, Niagara Network, etc. Hashed user passwords are not impacted Removes both reversable client passwords and hashed user passwords Understanding the System Passphrase in 4.15 Workbench or Supervisor When Niagara is installed on the engineering or supervisor device for the first time, the user will set the passphrase for that device. NOTE: When setting system passphrases, make sure that you take note of what they are. These should be shared with the owner of the building/site as the passphrase is owned by the device. You can change the system passphrase in the Platform Administration screen. You will be required to enter the current passphrase in order to successfully change it to a new passphrase, highlighting the importance of providing it to the owner of the building/site. JACEs & Remote Niagara Devices The passphrase is set during the commissioning process of the remote device. The remote device's passphrase can also be changed through the Platform Administration view with the same requirements as changing the Supervisor/device's passphrase.   Station Bog File Passphrases In 4.15, you will have the option to encrypt the new station with either the local system passphrase or a custom passphrase in the New Station Wizard. This passphrase is required to unlock the bog file in the user home when configuring encrypted properties as well as when copying this station onto a remote host. New Station Wizard: Note: When selecting the "Use the system passphrase" option, this is the passphrase for the local host (Workbench) Unlocking the station in the User Home: Copying the Station to a remote host with a different passphrase: Understanding how the station passphrase changes when using the Station Copier When a station from a remote host to your local host, the passphrase which is encrypting the data will be the system passphrase of the remote host. Copying a station from your local host to a remote host: For a station that originated on your local host with a passphrase encrypting its sensitive data, once you enter the current station bog file passphrase and successfully copy the station onto the remote device, it will utilize the system passphrase of the remote device when copying from the remote device back to your local host. Copying a station from a remote host to your local host: When a station is copied from the remote host, it will automatically be encrypted with the system passphrase of that remote host.   What do I do if I do not know the system passphrase of the remote host I copied the station from? In the user home,  you are able to reset the passphrase of the station, however, you will lose the encrypted sensitive data including system and user passwords. In this workflow, you have the option to remove all users except for one new super user which you provide the new username and password in the Bog File Passphrase dialog:  

Issue Building Commission (EBC) self closes at Login screen in Windows. It seems to be after application is unused for an extended period of time. Product Line EcoStruxure Building Operation Environment Building Commission Tool Cause There is a fault in Microsoft.ui.xaml.dll as observed in the Windows Event Viewer. Resolution Uninstall the application via Windows Add or Remove Programs Reinstall the application via the Microsoft Store Open this link in a browser Building Commission - Free download and install on Windows | Microsoft Store Click Open in Store App button in upper right by sign-in

Issue How to collect log files from the Project Configuration tool 2.0. Product Line EcoStruxure Building Operation Environment Project Configuration Tool Cause When contacting Product Support about issues with the PCT, log files should be provided. Resolution Collect log files through the Web interface on both Windows and Ubuntu installations: Logon to PCT server, Click Diagnostic  Click Collect logs Log starts collecting. After the log collection process is complete, the file will either be saved to the browser's default download location or a window will pop up asking where to save the ZIP file. Select the desired location then click Save   Log collector tool for PCT for Ubuntu: If the PCT web interface is unavailable, you can use the Log Collector tool to gather log files. This tool is included with the PCT installation on Ubuntu, eg. pct-2.1.1.8-log-collector-ubuntu. Give the file proper permission to be able to run as an executable either using chmod command:  chmod +x pct-2.1.1.8-log-collector-ubuntu​ or via file properties, as shown in below screenshot: Run the log collector tool. ./pct-2.1.1.8-log-collector-ubuntu​ A zip file containing the required log files will be saved in the same folder where the log collector tool is located.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices.   Issue Fire Panel unable to display the Media Gateway Card version in system information. Product Line ESMI Fire Detection. Environment FFSULH1007. Cause Panel message output on Media Gateway Card TCP/IP port not functioning and impacting BMS integration with the panel.  Resolution The Media Gateway Card firmware needs to be updated. Follow the steps below to update the Media Gateway Card firmware.   Prerequisites An SD card and SD card reader is required to make a bootable SD card for the firmware update files.   Prepare the SD card The first stage to update the firmware of the media gateway card is to prepare and install the firmware file onto the SD card. The media gateway card requires a micro-SD card. The firmware file is approx. 320MB, so select an SD card with suitable memory size. Format the SD card. Open up Win32Diskimager software. You should see the screen appear below. Click on the open file tab and then select the firmware file. When the firmware is selected it will populate the image file box. Click on the ‘Write’ tab and you should then get a pop-up screen shown below. Click on the ‘Yes’ tab. The firmware will now install onto the SD card. When you see the pop-up screen ‘Write Successful’ appear click on the ‘OK’ tab. The firmware is now loaded onto the SD card. Close down the Win32Diskimager software and eject the SD card form the PC. Install the Firmware Install jumper link onto the middle and top pin of X7 (as per the image below). There is a sliding cover on the socket. First slide the cover to unlock it, then hinge it up. Place the SD-Card in the socket. Hinge down the cover, then slide it to lock it as below The media gateway must be restarted to initiate the installation of firmware. This is done by pressing the reset button, shown in the picture below. The Media Gateway card has a set of 6 LEDs that indicate the status of the card. During normal operation one of the LEDs flashes regularly once each second. After a few seconds you will see a moving pattern progressing through the six LEDs. This indicates that the installation is in progress. The installation will take a few minutes to complete. Note: During this time the panel may display a fault condition that the media gateway card is not present or not working correctly. You can ignore this fault indication. When the firmware installation on the media gateway card is complete, the pattern displayed on the six LEDs will change. Instead of a moving pattern progressing through the six LEDs, all six LEDs will flash on and off together. Once you see this pattern, with all the LEDs flashing together, you should uninstall the jumper, remove the micro-SD-card, and then press the reset button. The media gateway will restart then running the newly installed firmware. It will take a few seconds for the media gateway board to achieve its normal operating state. If the panel displayed a fault indication that the media gateway board was missing, this fault should clear. The ESMI ULTIMA panel now needs to be rebooted to accept the updates from the media gateway card.13. Once the ESMI ULTIMA panel has initialised the firmware installation is now complete.  

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 It is sometimes necessary to move a previously configured Infinet i2 device from one Infinet network to another in the same parent Automation Server. EcoStruxure Building Operation does not provide an automatic way to move an i2 device; it must be done manually. Product Line  EcoStruxure Building Operation Environment Building Operation Automation Server Cause Guidance on steps to move Infinet i2 device from one Infinet network to another in the same host Automation Server Resolution In this example, we are going to move multiple Infinet i2 devices from the Infinet network on COM-A to the Infinet network on COM-B.   Backup Make sure to make a backup of the Automation Server before attempting the steps below. This is in case there is a need to revert the changes for whatever reasons. Export Devices from COM-A From COM-A Infinet network, display a List View of the devices, making sure to have columns displaying the Infinet ID and Serial Number. Write down the Infinet IDs and Serial Numbers of the devices to be moved. In the List View, multi-select the devices to be moved, right click and perform an 'Export', leave the Export Reference Filter at default (Export). After successful export, right click on the selected devices again and delete them from COM-A Infinet network. Prepare COM-B for Import From COM-B Infinet network, display a List View of the devices, making sure to have columns for Infinet ID and Serial Number. Observe the Infinet ID column, and compare with the notes taken above of the moving devices' Infinet ID, for IDs that are already in use in COM-B, you will need to assign a new ID to the device moving from COM-A Infinet network to COM-B, update your notes to include an available ID on COM-B. (see example below of what the notes might look like)   Import Devices to COM-B ***  In the System Tree, select the COM-B Infinet network and perform an import of the XML file created via export above. Physically move the devices from COM-A Infinet to COM-B Infinet. When doing so, avoid introducing duplicated Infinet IDs into COM-B Infinet. Make sure to power down the devices you are moving, connect them to COM-B Infinet, and only then power up the devices. On power up, the devices perform an ID check and stay off the bus if they detect their IDs are already in use. Configure Devices in COM-B From COM-B Infinet network, display a List View of the devices making sure to have columns for Infinet ID and Serial Number. Right click each device moved from COM-A Infinet to COM-B Infinet, and select "Properties", in the "Advanced" tab, enter the appropriate Infinet ID and Serial Number for the device then click "OK". In the List View, right click the device from previous step again, select "Device->Commission", after successful commission the device should go ONLINE Final Steps After all the moved devices are online, you should download ALL (whether moved or not) the devices to have their programs recompile and rebuild their Import/Export tables. Fix any references that were lost due to devices changing Infinet network and Infinet ID *** NOTE Due to an issue that was corrected in EBO 6.x, import may fail with error "Invalid InfinetId", the workaround for this problem is to manually create the Infinet devices on the destination port using the appropriate name, serial number and Infinet ID, then do the import selecting the option to merge on conflict.

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 Validation of SSL Certificate does not work Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Space-Logic Server (AS-X) Cause Cloud Connectivity makes use of the Baltimore CyberTrust Root Certificate for communication to the cloud, and often this certificate is not updated due to lack of maintenance routines on the Windows Server. Resolution Run Windows Update: On the server running the ES/EC, run Windows Update and make sure the Operating System is updated to the latest maintenance version available. Manually update certificate:  On the server running the ES/EC, go to https://curl.se/docs/caextract.html using a web browser and follow the instructions to download a collection of the most commonly used certificates on the web that are up to date. Click on the start-menu, type in ”certmgr” and press enter. Navigate to Trusted Root Certification Authorities/Certificates Under Trusted Root Certification Authorities, right-click the Certificates folder and select ”All Tasks > Import…” Follow the guide, click ”Next” and then locate the file you downloaded in Step 2a (make sure you filter to All Files). Click ”Next” on all steps and then click ”Finish”.

Issue The instance values the Function Block program had when the backup was taken is lost when the backup is restored in an AS-P running in PCT. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause When the program is first initiated, the values for it is written to the database. If the “Program executions” Is turned off, the instance values the program had when the backup was taken is not read. Hence the values are set to 0.   On a real AS-P, a Cold start is performed after the restoring of the backup. When restoring a backup on an AS-P in PCT, one or two cold starts are done, followed by an additional warm start at least for the PCT 2. Resolution To get the instance values from the backup when it is restored, the “Program execution”/”Enable program” In PCT should be turned on before the restore is done.   Since a warm start is done for the PCT, the issue regarding Retain level vs. FB Backup property needs to be taken into consideration. https://ecostruxure-building-help.se.com/bms/Topics/show.castle?id=15741&locale=sv-SE&productversion=7.0&a=1

Issue Attempting to update the System Identifier to align with the newly created ID in the EBO system, is causing a 'Duplicate BMS System Data Source' error. Product Line EcoStruxure Building Advisor Environment Building Advisor Cause A duplicate ID has been identified in Building Advisor. This may correspond to an older system ID or one from a different site.   Resolution The error indicates the site where the duplicate ID is found, which usually corresponds to the site you are attempting to update. - Go to the admin menu, select the site, then choose 'Clear' on the BMS System and click 'Save'. - Click the pencil icon to add or edit the BMS System. Enter the new ID and then click 'Save'.    

Issue After installing the Feenics Keep Bosch Service to integrate Bosch panels with Access Expert the service will not start Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Bosch Service and panels Cause A configuration issue is preventing the service from starting successfully Resolution The Feenics Bosch Service will fail to start for a number of reasons: 1. Check that the Feenics Keep Bosch Service exists and hasn't been deleted. "C:\BoschService" 2. The service is unable to authenticate to the Access Expert Instance.  Double-check the username and password being used for the service. Ensure they haven't been recently changed or the username and/or password is correct. Typically the username is Bosch with a configured password. 3. While attempting to start the Bosch service open Live monitoring and see if there is a failed login attempt or other related errors. 4. Open the Windows application log on the PC that has Access Expert and the Bosch service installed and check if there is an exception or a similar error like the following: 5. Install and use the SEQ Log to troubleshoot For Install Instructions for SEQ, see the following article:  https://community.se.com/t5/Building-Automation-Knowledge/Access-Expert-Installing-SEQ-Logs/ta- p/436521  Once installed, run the SEQ Log http://localhost:5341 while attempting to start the Bosch Service and see if errors are being posted. Example:   6. Check the last ping from the Bosch service to the Feenics host API : This date/time will give an idea of the last successful ping which can help target what may have been changed on the system or network that has affected the service. 7. Run the telnet command to access the Feenics host server If the DOS page is blank/black after hitting enter on the telnet command, that is a good sign. If there are any errors these can be a clue as to what is happening. If a firewall is blocking this connection you won't be able to reach the Feenics server.   Note: If the telnet command isn't recognized, telnet may not be enabled on the PC If none of these steps help to identify the issue, please open a Support case.