Building Automation Knowledge Base

Issue What can be used to get the Device Log (aka Error Log) from a b3 or Infinet connected to an Automation Server (AS)? Product Line EcoStruxure Building Operation Environment Building Operation Server Bacnet Infinet Cause Need to get the Device Log (aka Error Log) from a b3 and/or Infinet connected to an AS. Resolution A tool called Building Operation Device Log Viewer (SE.SBO.Device.Log.Viewer.exe), starting with v1.9 now contains a dropdown used to choose BACnet (b3) or Infinet.  Prior to v1.9, it was limited to only obtaining b3 error logs.   64-bit Windows OS Default Location: "C:\Program Files (x86)\Schneider Electric [EcoStruxure|Struxureware]\Building Operation [n.n]\WorkStation\Script\SE.SBO.Device.Log.Viewer.exe"   32-bit Windows OS Default Location: "C:\Program Files\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\WorkStation\Script\SE.SBO.Device.Log.Viewer.exe"   Note: Based on the EBO system version you are connecting, use either [EcoStruxure|StruxureWare] and version [n.n] that matches. Note: Before v1.6 it was called Building Operation b3 Device Log Viewer and had a similarly named EXE file.   The Log Viewer tries to connect to the AS-P via UDP port 33487 when BACnet is selected and UDP port 33488 when Infinet is selected.

Issue Identify which Access Expert LDAP Active Directory Keep version is installed Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Access Expert LDAP Active Directory Keep Integration Active Directory Cause Windows Control Panel Programs and Features doesn't indicate which version of the LDAP Active Directory Keep Integration is installed Resolution Login to Access Expert and the Instance that has LDAP Active Directory Installed Navigate to the General Configuration Tab> LDAP Agents LDAP Right Click on the LDAP agent and select View Event History Note: You may need to change the Priority from 50 to 0 and the Date Range to see an event Expand (Click the plus sign) of one of the LDAP Events (i.e LDAP Agent - Started) The version of the LDAP Active Directory Keep installation will show

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 Access Expert LDAP agent unable to connect to Instance Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted LDAP agent installed OnPrem on-site server (Not the appliance installed by Feenics) Cause LDAP agent cannot connect because the Username/PW may be stored in a registry that is no longer valid Resolution Double-check the site setup documentation records that the Username/PW combination is correct Run the SEQ Log and see if there's an entry that indicates that the 'Ldap agent is not able to connect to the instance' Note: Earlier versions of the LDAP on-site installer did not remove all registry entries including username/pw, so an older username/pw combination may be used instead of an updated combination.  If the username or password was changed at some point or if alternate combinations were used for troubleshooting then an incorrect combination could be used by the LDAP agent to connect to the instance and it cannot. Check the login to Access Expert with one of the LDAP username/password combinations and if there are 2 (Users) listed in Access Expert, delete the username/pw combination that does not work in Access Expert. Regedit Backup and old Username/PW deletion To obtain a registry backup just in case before deleting an entry: https://support.microsoft.com/en-au/topic/how-to-back-up-and-restore-the-registry-in-windows-855140ad-e318-2a13-2829-d428a2ab0692  It is suggested to back up the entire Feenics.Keep.ActiveDirectory.Service subkey Open regedit and delete the imagepath subkey Windows Start/Run> regedit Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\Feenics.Keep.ActiveDirectory.Service Right-click on the ImagePath subkey and select 'Delete' Only delete this subkey, not the other Reinstall the LDAP integration using the media received directly from Feenics or SE Product Support. i.e. Feenics.Keep.Installer.ActiveDirectory.msi The most recent version of the install can be found on Feenics site: Feenics Keep Active Directory LDAP Installation Media  During the installation ensure the tested username/pw combination is used Verify that the 'Feenics Keep Active Directory Service' starts successfully Go to Start>Run>Services.msc and click Ok Locate the 'Feenics Keep Active Directory Service' Right-click and select Start Open SEQ Log and verify that the Ldap agent is able to connect to the Instance. The SEQ entry at the top of this article 'Ldap agent is not able to connect to the instance.' should no longer appear in the SEQ log. The following entry should be there instead. Verify that the Access Expert Windows User(s) can now be used login to Access Expert

Issue How to configure PCT memory in Hyper-V. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Hyper-V Cause There is more memory available but PCT 2.0 can't start more servers. Example: Users with over 8 GB of memory can't start more than 36 servers.  Resolution This is because the default memory is set to 8GB, approximately 36 servers. (8GB - 2GB)/.170 GB = 36 server. Open the Hyper-V Manager In the left panel, right-click on "pct" and select Settings. The Setting dialog box opens. In the left pane, under Hardware, select the Memory item. The memory settings open in the right panel. The RAM shows 8192 MB(8 GB * 1024 = 8192 MB), the "Enable Dynamic Memory box" is checked, the Minimum RAM is 8192 MB and the Maximum RAM is 262144 MB(256GB *1024 = 262144 MB).    Enter the amount of memory assigned to PCT, 10240 MB(10 GB) in the example. If the "Enable Dynamic Memory" box is unchecked, the memory assigned to PCT will be 10240 MB. If the "Enable Dynamic Memory" box is checked, the memory assigned to PCT will be between 8 GB and 10 GB(not 256 GB or other amount because the limitation is set at 10 GB from the RAM setting above). R&D recommends not using "Enable Dynamic Memory".   Helpful Link: PCT 2.0 memory usage calculation

Issue When attempting to update the firmware on the SP-MRDM module, the update process fails, and the module appears offline with the fault LED activated. A "Module not responding" error message is displayed that indicates the module should be disconnected, and a utility used to restore the firmware.   Product Line EcoStruxure Security Expert Environment SP-MRDM SP-MRDM2 Cause The module has lost its firmware during a failed firmware update attempt, leading to the offline status and fault LED activation. Resolution To resolve this issue, follow these steps: Establish a connection to the SP-C controller using a web browser. Force a module update operation from the Application Software tab. Note that it may be necessary to check the "Skip Verification" checkbox during the update process.

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 SmartX SpaceLogic/EasyLogic device is offline, inspection of the device's status LED reveals a solid red pattern instead of the normal solid green.   Product Line EcoStruxure Building Operation Environment SmartX SpaceLogic Controller SmartX EasyLogic Controller Cause A solid red status LED indicates the application can't be launched, typically there could be two reasons as the root cause of this situation: The application has become corrupted, this happens very rarely. Application keeps crashing on startup. To prevent an infinite startup->crash->startup loop, the firmware in the SmartX SpaceLogic/EasyLogic devices implement a feature known as the application startup retry counter, if the application has crashed multiple times, never running for longer than an internally defined time (typically 10 minutes), the boot applet will stop all attempts to launch the application. Resolution We can attempt to recover the device by performing the following steps: Cycle power to the device. Cold start the device by holding down the reset button for more than 5 seconds but less than 9 If the controller starts up and shows a normal status LED (solid green), immediately start  a device upgrade firmware operation, the goal is to get the uprev operation going before the application crashes again.

Issue Using a VPN, the Building Commissioning Tool is unable to recognize the network adapter Product Line EcoStruxure Building Operation Environment Building Operation Building Commissioning Tool Cause VPNs have not been specifically tested and therefore are not supported Resolution Though VPNs have not been tested and are not supported, some sites have found that this is possible. If the VPN adapter IP is available then it may work, if you have a VPN adapter that does not show up, please enter an enhancement request If the above isn't available, run the tool after turning off the VPN application or Global Protect.

Issue Licenses required to upgrade SBO/EBO to EBO 2022 v4.0.x Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium - Secure boot Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause Clarifying licensing upgrade requirements for EBO 2022 v4.0.x Resolution Example: Upgrading a site SBO 1.x or EBO 2.x to EBO 2022 v4.0.x or later directly. Site has an Enterprise Server (ES) the ES has 7x Automation servers AS-Ps and 2x AS-Bs attached. One AS-P has a Modbus interface, and 1 AS-B has a Modbus interface. Adding 1 additional AS-P classic (non-secure boot), 1x AS-P-S secure boot and 1 AS-B scalable. The SBO 1.x or EBO 2.x licenses need to be upgraded to EBO 3.x first. Upgrade ES licensing from SBO 1.x license to EBO 3.x.  These licenses need to be activated using License Administrator.   1 x SXWSWESUP13010 ES Upgrade from 1.X to 3.0 with 10 or less AS    The following additional licenses are required for each AS-x when upgrading a site from SBO 1.x to EBO 3.x or upgrading a site from EBO 2.x that was originally installed at SBO 1.x and upgraded to EBO 2.x. These are not required if the site was originally installed at EBO 2.0 and upgrading to EBO 3.x. These licenses need to be activated using License Administrator.   7 x SXWSWASUP00001 license will be required one for each AS-P. 2 x SXWSWASUP00001 licenses will be required one for each AS-B.   Note: If the site has more than 24 AS-xs then part number SXWSWASUP00099 provides 999 licenses. EBO 3.2.x architectural guidelines allows a maximum of 250 AS-xs per ES.   Upgrade ES license from EBO 3 to EBO 4 This license needs to be activated using License Administrator.   1 x SXWSWESUP30010 ES Upgrade from 3.X to EBO 2022 or later (i.e. to the current EBO version) with 10 or less AS Upgrade AS-P/B licensing from EBO 3 to EBO 4 or later These licenses need to be activated using Device Administrator.   For each AS-P (non secure boot AS-P and AS-P-NL), one of the following bundles would be required for each AS-P.   SXWSWASPUP30SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standalone SXWSWASPUP30SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard SXWSWASPUP30EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle - Enhanced SXWSWASPUP30FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Full SXWSWASPUP30BP Full Bulk pack for upgrading AS-P-XX from EBO 3.x to EBO 2022 or later, contains 125 pieces of SXWSWASPUP30FU. For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics.   Note: Once an AS-P license is upgraded, there is no differentiation between AS-P Secure Boot and AS-P Non-Secure Boot (Classic):   If the “SXWSWASPUP30SD Upgrades an AS-P from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard” license was purchased for an AS-P classic, and later it requires an enhanced or full license.   SXWSWXUP00SDEN ASP Bundle upgrade - Standard to Enhanced SXWSWXUP00SDFU ASP Bundle upgrade - Standard to Full Would need to be purchased.   If the “SXWSWASPUP30EN Upgrades an AS-P from EBO 3.x to EBO 2022 or later AS-P Bundle – Enhanced” license was purchased for an AS-P classic, and later it requires an  full license. SXWSWXUP00ENFU ASP Bundle upgrade - Enhanced to Full Would need to be purchased.   For the AS-Bs (AS-B-24, AS-B-24H, AS-B-36, and AS-B-36H), one of the following bundles would be required for each AS-B. These licenses need to be activated using Device Administrator.   SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle – Standard SXWSWASBUP30FU Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs Note: Once an AS-B license is upgraded, there is no differentiation between AS-B Scalable and AS-B (L) Non-Scalable (Classic): If the “SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 AS-B Bundle – Standard” license was purchased for an AS-B (L) classic, and later it requires a full license.   SXWSWXBBUPSDFU ASB Bundle upgrade - Standard to Full, would need to be purchased.   To upgrade the AS-B-L (classic) type, the SXWSWASBUP30SD ASB Upgrade – Standard license is all that is required.   For the additional AS-P classic one of the following licenses would be required. SXWSWASPUP30SA Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standalone SXWSWASPUP30SD Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Standard SXWSWASPUP30EN Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle - Enhanced SXWSWASPUP30FU Upgrades AS-P-XX from EBO 3.x to EBO 2022 or later AS-P Bundle – Full For the AS-P with the Modbus interface, an SXWSWX000MBRTU license is not needed as Modbus is grand-fathered for AS-P classics.   For the additional AS-P secure boot one of the following licenses would be required. SXWSWXBU0000SA ASP Bundle - Standalone  SXWSWXBU0000SD ASP Bundle – Standard  SXWSWXBU0000EN ASP Bundle – Enhanced  SXWSWXBU0000FU ASP Bundle - Full  For the AS-P secure boot if a Modbus interface is to be used the SXWSWX000MBRTU Modbus license would be required. For the additional AS-B Scalable one of the following licenses would be required. SXWSWXBBU010SD ASB Bundle – Standard SXWSWXBBU050FU ASB Bundle – Full A SXWSWX000MBRTU Modbus license is not needed with AS-B scalable. If an additional AS-B classic was added one of the following licenses would be required. SXWSWASBUP30SD Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle – Standard SXWSWASBUP30FU Upgrades AS-B from EBO 3.x to EBO 2022 or later AS-B Bundle - Full A SXWSWX000MBRTU Modbus license is not needed with AS-Bs     Addition: If the site had an Enterprise Central (EC) at EBO 2.0 and was upgrading to EBO 2022 v4.0.x or later, one of the following licenses would be required to upgrade to EBO 3.x first:   SXWSWECUP23005 EC Upgrade with 5 or less ES SXWSWECUP23010 EC Upgrade with 10 or less ES Then one of the following licenses would be require to upgrade from EBO 3.x to EBO 2022 v4.0.x or later:   SXWSWECUP30005 EC Upgrade from 3.x - with 5 or less ES SXWSWECUP30010 EC Upgrade from 3.x - with 10 or less ES   For more information on the bundles, search for 'software bundles" in the  “Part Numbers and Hardware/Software User Matrix – EBO 2024”   For information on software and features that require licenses  

Issue When attempting to attach an Enterprise Server to a parent Enterprise Central, the error "Server name not unique" is encountered, despite the Enterprise Server having a unique name. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause The error may arise due to either the server's name not being unique or one of its child servers' names not being unique. Resolution To resolve this issue, ensure that the server's name is indeed unique, and also verify that the names of the its child servers are also unique. For example, if an Enterprise server "ES1" has a child Edge server named "Edge_1" attached to Enterprise Central "EC", and another Enterprise server "ES2" also has a child Edge server named "Edge_1", it cannot be attached to "EC" until the child Edge Server is renamed to ensure uniqueness.

Issue The SUM Alarm does not generate an alarm when an Automation Server goes offline Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause The online status of the Automation Servers needs to be monitored so that an alarm can be generated if any of them go offline. Using the following configuration does not work. 1. Create a sum alarm 2. Add Source and set to AS path (e.g /SWXnetwork/servers/AS1). Replacing AS1 with a * makes no difference 3. Add System alarm ID and set to "Server Offline" 4. Add Alarm State and set to "Selection as required" Resolution Options that do work Option 1 System Alarm ID = Server offline Alarm Text = */Servers/* Alarm State = Alarm and Alarm Acknowledge - (Select as required). Option 2 System Alarm ID = Server offline Alarm State = Alarm and Alarm Acknowledge - (Select as required). Source Name = AS1 or AS*   Option 3 System Alarm ID = Server offline Alarm State = Alarm and Alarm Acknowledge - (Select as required). Source = /SWXnetwork/System/Server Communication/To/AS* - (As the alarm is in the ES, the path comes from the ES).

Issue How to calculate memory needed for PCT. Product Line EcoStruxure Building Operation Environment Project Configuration Tool. Cause Unclear memory usage in PCT. Resolution The specifications show that the PCT default memory is 8 GB in Hyper-V. Each running PCT server takes 2 GB and 170 MB per running server. A 4-core CPU can run up to approximately 100 servers and an 8-core CPU can run up to approximately 200 servers. Memory Usage calculation example: For 23 servers, i.e. 23*0.170 GB + 2 GB = 6 GB For 36 servers, i.e. 36*0.170 GB+ 2 GB = 8 GB (default) For 47 servers, i.e. 47*0.170 GB+ 2 GB = 10 GB To start 100 servers, 100*0.170 GB+ 2 GB = 19GB   Helpful Link: PCT 2.0 memory configuration in Hyper-V

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Finding the correct procedure for migrating Infinet controllers from a Continuum controller fieldbus to an AS-P. Product Line Andover Continuum,EcoStruxure Building Operation Environment Continuum Cyberstation Building Operation Automation Server Premium (1.9 onwards) Building Operation Automation Server Bundled (1.9 onwards) Cause The wrong procedure has been followed which is not the approved and tested procedure to be used when migrating Infinet controllers from Continuum to EBO.  Resolution Procedure for Converting / Transitioning the Infinet Bus Prior to migrating the Infinet The RS-485 network cable should be routed in a continuous daisy chain bus configuration. There should not be any stub connections, stars or ring configurations. The bussed cable should pass through each node to be connected with no splits or branches in the cable network. Repeaters can be used to achieve the star, distributed star (backbone with clusters), off of the backbone. For additional information, review the article: EBO Webhelp Cabling Using the conversion tool and other engineering efforts, create the AS-P database for all Infinet devices, Infinet, Interface items, etc. in either a live AS-P or in the PCT. At the site From Continuum CyberStation,  the following must be completed to each Infinet controller that you are moving to an AS-P. Upgrade all Infinet devices that are going to be converted to the latest firmware version.  Firmware upgrading capability will not be available in EBO until a future release. Clear the memory of all Infinet devices involved before relocated to the AS-P com port by editing the controller object and selecting Runtime > Reset. If the conversion was done on the PCT, deploy the AS-P. Verify that the AS-P firmware is 1.9.0.73 or higher. Disconnect Infinet bus from the Continuum controller com port(s). Move the Infinet bus (busses) to the corresponding RS485 port(s) on the AS-P. Confirm that the Infinet devices are all showing online under the AS-P Download the Infinet devices. * Backup all Infinet devices to flash memory.   *  If the Infinet devices share data with other Infinet devices then it may be necessary to repeat this step in order to establish the complete Import/Export table. PLEASE NOTE The above steps are important! If not followed, offline and bus problems can occur. There may be a desire to skip the rest of the controllers, but the steps must be followed The likelihood is high that there will be substantial difficulties in getting the i2 controllers online and in a stable state to accept the download files. All of the Infinet controllers must be reset in Continuum before moving the bus to the AS-P.  The controllers should then be backup up to flash memory to ensure that they do not revert to their Continuum configuration following a cold start. If problems occur that make it necessary to abort the migration process and return the controllers to the Continuum system, all of the Infinet controller must have their memory cleared before re-attaching the bus on the comm port of the original Continuum controller.  For those controllers which have not established communications under the AS-P, this will mean performing a hard reset at the Infinet controller hardware. At no time should the Infinet bus be connected to the both the AS-P and the Continuum controller at the same time as this  confuses the Infinet controllers causes communications issues that will take some time to resolve. Please also see the "Infinet under the hood" community post Continuum Conversion Tool NOTES V3.0.x and v3.1.x Conversion Tools should not be used. The Workaround is to use the 2.0 Conversion Tool then upgrade. (The Conversion tool was fixed by v3.1.2.6000 (CP5)) V3.2.x onwards the Conversion Tool operates correctly v4.0.3 has an issue converting Infinet controllers, 4.01 or 4.02 should be used instead Now fixed in v4.0.3.5005 CP3(Known Issues) v3.x outperform 4.x, 5.x and 6x.(known Issues). The Workaround is to convert the dmp file in CCT 3.x then upgrade the DB to the expected version in PCT or AS-P.

Issue When using the SBO xbk Analyzer, a warning with the following details is observed:  *** possible configuration issue *** (QC#49504)  Issue: 'Communication failed' alarms between servers, even if no bindings are made Action: Make sure servers can communicate with each other so they can synchronize. Product Line EcoStruxure Building Operation Environment Building Operation Server backups version 3.x and above.  Cause The defect mentioned in the tool (QC#49504 / DBSQA-57599) was initially created because alarms were generated between two (or more) Automation Servers that had no bindings (or references) between them. This behavior is considered normal. This occurs because the servers attempt to synchronize references but fail due to communication issues, resulting in the alarms. These Automation Servers were previously part of the same system but were separated before reference synchronization was completed. A possible scenario for this issue is: Two servers can see each other. Bindings are established between the two servers. The connection between the two servers is then disrupted (i.e., offline). Subsequently, one or more of the bindings are deleted, leading to offline alarms between these servers, even if no binding exists now, due to pending synchronization. Resolution  The XBK analyzer tool detects this situation via a "SyncPending" flag, indicating that it needs to be investigated if a "Communication Alarm" exists between these servers. This warning can be ignored if no communication alarms are associated with the servers listed by the analyzer tool.   In most cases, if the server names listed by the tool are part of the system, the issue can be resolved by checking and verifying for unresolved bindings via Binding Diagnostics. while connected to a working EBO System.   If the tool lists any other server names that are not part of the system, these server names can be cleared by upgrading to EBO 2024 (v6.0.x) and above.  As stated, it is only a warning for earlier versions and can be ignored, as there can be instances where this is not cleared until upgraded to this release.        

Issue During an Enterprise Central or Enterprise Server upgrade, the upgrade is halted with a message that the "server has not stopped". "Error: server state 'ServerShuttin'"   Upgrade Fails on Server not stopped state = starting Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Cause If the last shutdown of the ES/EC process was due to a crash or if it was stopped through the task manager, the current ES/EC server state is not updated, causing the upgrade to fail. Resolution Check that the server process is stopped: SE.SBO.EnterpriseServer.exe or SE.SBO.EnterpriseCentral.exe in the Task Manager. Open the database folder for the server in question, e.g., %programdata%\Schneider Electric EcoStruxure\Building Operation 3.2\db Edit the file: nsp_servers.serverstate Change the text "ServerShuttin" or "ServerRunning" to "ServerStopped". Save the file and try again (retry)

  Issue Fail to login to the selected server when the User name and Password are correct. Product Line EcoStruxure Building Operation Environment Project Configuration Tool 2.0 Cause In the example, the Server is in EBO 3.2.1.630 and the Workstation is 3.2.3.59. The Workstation is at a higher version than the Server but it's not the latest version. PCT loads the incorrect IP(192.168.10.2) in the WS due to the version.     Resolution PCT requires to use of the latest version of WorkStation for all releases (3.2, 4.0, 5.0, 6.0).  For example: EBO 3.2.1.630, 3.2.2.61, 3.2.3.59 and 3.2.4.1009 use WorkStation 3.2.4.4007(CP2) or above. EBO 4.0.1.86, 4.0.2.559, 4.0.3.176, 4.0.4.45 and 4.0.5.7 use WorkStation 4.0.5.3004(CP2) or above.    

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 A full backup immediately fails on the Automation Server.  Performing a configuration-only backup completes successfully. Product Line EcoStruxure Building Operation Environment Building Operation 3.x - first detected Building Operation Automation Server  Building Operation Automation Server Premium (AS-P) Building Automation Server AS-B Cause A directory under the DB folder, called tc [TypeCache], within the database of the Automation Server, had grown close to 1 GB in size.  The combination of this with the large TrendDb caused the backup failure with the following message seen in the trace log:    nsp.csc.bar.BarBackupOperation BarBackupOperation Execute failed with: Internal Server Error: Insufficient_Space_For_Backup (0x80008) in module Bar_Manager(51). "/<servername>": Insufficient space for backup, XXXXXXXXX bytes estimated for new backup but only XXXXX available   This tc directory contains types fetched from other servers that are used in runtime. These are loaded either from the local database or the tc directory. If a type for another server is not found in the tc directory when accessed, it will first be fetched from that server.   There may be other reasons for the backup failure, presenting this Insufficient_Space_For_Backup message in the trace.log. Clearing this Type Cache does not adversely affect the controller and can be cleared as the first step to see if this will allow the full backup to occur.    The issue has only been seen in Building Operation 3.x, if the issue is presented in a later revision or you continue to have failures, then contact your local support and reference this article.     Resolution To clear the Type Cache contents, follow these steps: Navigate to the RuntimeDBManager object under /System/Modules/RuntimeDBManager/ Right-click on the TypeCache object. Select Type Cache Clear All Attempt a full backup of the server again.  If failures continue to concur, then contact your local support

Issue WorkPlace Tech 5.8.x, 5.9.x, 5.10.x, and 5.11.x Operating System and Microsoft Visio Compatibility Product Line TAC IA Series Environment WorkPlace Tech Tool Software release 5.8.x, 5.9.x, 5.10x, and 5.11.x Microsoft Windows and Microsoft Office Visio requirements, see the "Resolution" section, below. Visio 2010, 2013, 2016, 2019, 2021(.msi install)  Visio 2013, 2016, 2019, 2021 (subscription "Click to Run", Plan 2) Office 2010, 2013, 2016 (.msi install) Office 2013, 2016, 365 (subscription "Click to Run", Plan 2) Support for Workplace Tech 5.10 / previous and Workplace Tech Editor Note: Visio 2019 and Visio 2021 are not supported in 5.9.4 or EBO versions before EBO 2022.  Visio 2019 and Visio 2021 are supported when using Workplace Tech 5.10.x and EBO 2022. Cause What Microsoft Windows operating systems and what versions of Microsoft Visio are compatible with the WorkPlace Tech Tool version 5.8.x, 5.9.x, 5.10.x, and 5.11.x? Resolution Microsoft Windows WorkPlace Tech Tool releases 5.8 through 5.8.6 are certified to run on the following versions of Microsoft Windows: Microsoft Windows XP Professional with Service Pack 2 or Service Pack 3 Microsoft Windows Vista 32-bit Business, Ultimate or Enterprise Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional WorkPlace Tech Tool release 5.8.7 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool releases 5.9.1 to 5.9.4 are certified to run on the following versions of Microsoft Windows: Microsoft Windows 7   32-bit Professional Microsoft Windows 7   64-bit Professional Microsoft Windows 8.1   32-bit Pro or Enterprise Microsoft Windows 8.1   64-bit Pro or Enterprise Microsoft Windows 10    32-bit Professional Microsoft Windows 10    64-bit Professional Microsoft Windows Server 2012   64-bit WorkPlace Tech Tool release 5.10.0 to 5.10.x is certified to run on the same as WorkPlace Tech 5.9.x and the following versions of Microsoft Windows: Microsoft Windows Server 2016 64-bit Microsoft Windows Server 2019 64-bit Microsoft Windows Server 2022 64-bit Microsoft Windows 11 Professional (Workplace Tech 5.10.4 only) WorkPlace Tech Tool release 5.11.0 is certified to run on the following versions of Microsoft Windows: Microsoft Windows 10 64-bit Professional Microsoft Windows Server 2022 64-bit Microsoft Windows 11 Professional Microsoft Visio Microsoft Windows 7 32-bit Professional Microsoft Windows 7 64-bit Professional Microsoft Windows 8 32-bit Pro or Enterprise Microsoft Windows 8 64-bit Pro or Enterprise Microsoft Windows 8.1 32-bit Pro or Enterprise Microsoft Windows 8.1 64-bit Pro or Enterprise Microsoft Windows Server 2012 64-bit WorkPlace Tech Tool releases 5.8 through 5.8.6 require one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WPT 5.8.0, WPT 5.8.1, no known issues with WPT 5.8.2 through 5.8.5) Microsoft Office Visio 2007 with Service Pack 1 or Service Pack 2 Microsoft Office Visio 2010 with or without Service Pack 1 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.8.7 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2007 with Service Pack 3 Microsoft Office Visio 2010 with Service Pack 2 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool release 5.9.1 through 5.9.4 requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2010 with Service Pack 2 Microsoft Office Visio 2013 with Service Pack 1 Microsoft Office Visio 2016 NOTE: Standard or Professional edition of Microsoft Visio may be used. WorkPlace Tech Tool releases 5.10.0 through 5.10.x requires one of the following versions of Microsoft Visio (32-bit version ONLY) Microsoft Office Visio 2016 Microsoft Office Visio 2019 Microsoft Office Visio 2021 Microsoft Office Visio Office 365 Subscription Plans 2 WorkPlace Tech Tool releases 5.11.x requires one of the following versions of Microsoft Visio (64-bit version ONLY) Microsoft Office Visio 2019 64-bit Microsoft Office Visio 2021 64-bit Microsoft Office Visio Office 365 Subscription 64-bit Plans 2 Warning: WorkPlace Tech 5.11 is not compatible with EBO WorkPlace Tech Editor. Do not install WP Tech 5.11 on a PC that has EBO WorkPlace Tech Editor installed. Continue to use WP Tech 5.10 on PCs where EBO WorkPlace Tech Editor is required.   Note: Workplace Tech Tool 5.10.0 and later releases require .NET Framework 4.8 to support Open LDV 5.1 which is included in the installer.  .NET Framework 3.5 Sp1 is no longer required.   Follow the instructions in the article link for the security updates required. Workplace Tech 5.10.x and previous / Workplace Tech Editor (EBO) Microsoft Security Updates required for Visio and Office For the Visio requirements for earlier versions of the WorkPlace Tech Tool software, see What versions of Visio are required for WorkPlace Tech?.

Issue What versions of Visio are required for WorkPlace Tech? Product Line TAC IA Series Environment WorkPlace Tech Microsoft Office Visio (32-bit version only on WPT versions 5.10 and earlier ) Microsoft Office Visio (64-bit version only on WPT versions 5.11 and later) Cause Software requirement - Microsoft Office Visio must be installed on the computer before beginning the installation of WorkPlace Tech. Resolution Below is a list of the WorkPlace Tech revisions and compatible Microsoft Visio versions.  The "Pro" versions are not required.  The "standard" versions of Microsoft Visio are typically recommended.  Only the 32-bit versions of Visio are supported in WPT 5.10 and earlier and only 64-bit versions are supported in WPT 5.11 and later. WPT Visio 3.1 Visio 5 Technical Plus 3.2 2000 SP1 4.0 2000 SP1, 2002 SP1 5.0 2002 SP1, 2003 SP1 5.1 2002 SP1, 2003 SP1 5.2 2002 SP2, 2003 SP1 or SP2 5.3 2002 SP2, 2003 SP1 or SP2 5.4 2002 SP2, 2003 SP1 or SP2 5.5 2002 SP2, 2003 SP1 or SP2 5.6 2002 SP2, 2003 SP1 or SP2 5.7 2003 SP3, 2007 SP1 5.8.0 to 5.8.5 ** 2003 SP3, 2007 SP1 or SP2, 2010 SP1 5.8.6 2007 SP1 or SP2, 2010 SP1 5.8.7 2007 SP3, 2010 SP2 5.9.1 to 5.9.4 2010 SP2, 2013 SP1, 2016 5.10.0 to 5.10.4 2016, 2019, 2021 Office (Visio) 365 Subscription Plans 5.11 2019 64-bit, 2021 64-bit, Office (Visio) 365 Subscription Plans 64-bit ** Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WorkPlace Tech 5.8.0 and 5.8.1, no known issues with 5.8.2 through 5.8.5)

Issue EBO acts as a BACnet server and a BACnet client send SubscribeCOVProperty to get value updates of specific property of a BACnet object, ex. present value, but EBO respond with "NOT_COV_PROPERTY".   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Specified property does not support COV notifications. Resolution EBO only supports SubscribeCOVProperty (DS-COVP-B) for the following properties and object types: Status_Flags: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop, Trend Log Event_State, Reliability, Out_Of_Service: AI, AO, AV, BI, BO, BV, MI, MO, MV, Loop When a client attempts to use SubscribeCOVProperty for another property not listed above, the appropriate response is 'Not COV Property', as specified in BACnet standard. When getting this response from EBO, the client is expected to automatically use another method to acquire the property value (either via COV subscription or polling). If the client is attempting to read Present_Value, then using SubscribeCOV would be the preferred mechanism.

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 7798C stops communicating after BIN file download Is the 7798C supported in the older versions of I/NET Seven (1.14 and below). How to reset the 7798C hardware (i.e. place into boot mode) if no communication is possible with the 7798C    Product Line TAC I/NET Environment I/NET Seven 1.14 and lower I/SITE LAN 7798C Cause I/NET revision 1.14 and lower does not support 7798C and can mistakenly be assumed by the I/NET Host software as a 7798B.  If a software restore is completed to the 7798C with these revisions, it disables the device from communicating via the Controller LAN and disables any communication via the serial port with the Hand Held Console (HHC) software.   Resolution If you have downloaded the incorrect BIN file (i.e. 7798) to the 7798C, the handheld console software will not work, and hence, the device can not be placed back into a boot state, allowing the correct BIN file to be restored to the 7798C.  If the serial port is still configured/enabled for direct connection via the onboard TAP, this is the easiest solution to try a software restore to blank out 7798C with the correct BIN file. If either of these options are not available, the following steps can be performed very carefully directly on the hardware: Very Important:  Make sure you turn OFF the power to the 7798C unit. If you fail to remove power, this process could damage the board.  If unsure, please contact Product Support On the top edge of the board is the EPROM, and just below are two RAM chips. Between the EPROM and the two RAM chips are two mustard-colored capacitors (Labeled C2 & C3) If you short across each Capacitor, one at a time, this will take the device to boot. If you still have issues with the device, sending the 7798C in for repair is recommended. Once the device is communicating again, the correct firmware can be restored to the 7798C. At this point, you should be using I/NET Seven revision 1.17 or above.