Issue Event server crash causes the controllers to flip between Online/Offline Product Line EcoStruxure Security Expert Environment Security Expert Software Microsoft Windows Server 2016 Microsoft Windows Server 2019 DataCenter Cause Event Server crashes and shows that the controllers are online. This status shows temporarily and then drops out showing the controller is then offline yet still operational. Resolution Browse to C:\Program Files (x86)\Schneider Electric\Security Expert\ Right-click on SecurityExpertEvtSvr.exe and select properties Check the box for Run this program in compatibility mode Once completed, restart the services and then Security Expert.

Issue You need to change from the Small Number Format to Large Number Format (Hex) Product Line TAC INET Environment INET Seven Cause The system is limited to a maximum number of access cards of 32,000.  If a larger number is required then INET must be configured to used large card numbers.  Resolution To convert INET to use the Large Card Number support, the following steps must be performed:  Conversion of Card Numbers (small) to Large Numbers Sort the Individuals list according to the Individual Number. Look in the Individuals Editor “Options” function to set this up. Look at the tenant editor to determine the Tenant Code/ Facility code of the cards. From this use the circled items the Tenant Code (Facility Code) and the First Individual Number as the lowest possible card number in the next step.  Verify in the door editor that the cards in this system are in a known Weigand bit format.  In this case, we are using 26-bit. Attached are various Excel spreadsheets that can be used to determine the Decimal number of the first card in the system (Card #970 Facility code 199) is Decimal number 13042634 depending on which card format is been used. This number will become the source number in the Key card table. These include 26-bit 32-bit ABA115 format Create a Key/Card Translation table similar to that shown below in the Inet Seven Access Control editor.  This table will be removed after running the provide SQL Script  At this point shut down Inet Seven and run the attached SQL Script. Then once the script runs then restart Inet and look in the individual’s editor and you will see what is shown below. Start INET and delete the Key/Card Translation table create above. Open the Individual Parameters and verify that a Hex number and the decimal number in the Individual editor In order to have large numbers working on a site DipSw #7 has to be turned ON for the 7920 DPU's. For the SCU1284 in the door editor at the top center of that editor, there is a check box "Card Translation" you have to check that box for large numbers to work in the SCU's. You will have to do an SLI “SAV” because that is where the Card numbers are now stored and then do an SLI restore. Followed by a DPU restore to all of the door controllers.  

Issue After starting the Enterprise Server(ES), the memory usage increase constantly until it finally hangs, which happens in a couple of days.  Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server version 3.2.x Building Operation Automation Server 3.2.x Cause Running a Notification report including many trend logs can take a long time to finish; for example, a report including 91 trend logs can take up to 10 minutes. If the Notification report is triggered more often than 10 minutes, reports will start to queue up, making the memory usage for the ES increase over time, and it will finally hang. Resolution When having a Notification report which includes many trend logs, make sure that it is not running too often as it is a rather slow process to create a report including many logs. Example: A Notification report which includes 91 trend logs with 168 log records takes 10 minutes to finish.

Issue After a successful commission of MP-x SmartX controller, the device is online and operating properly but fails to come back online after a warm start. The issue is seen more often when MP-x device is configured for DHCP but can also happen when configured for static IP address. (See the attached video which demonstrates the issue) Product Line EcoStruxure Building Operation Environment Building Operation SmartX IP Multi-purpose Controller (MP-X) Building Operation SmartX IP Room Controller (RP-C) Building Operation SmartX Controller IP-IO Series Cause Communication settings out of sync between the physical device and configuration database Resolution To synchronize the IP settings between the device and the configuration database follow these instructions from the online help   Discarding MP Series Controller IP Network Settings Changes

Issue Webhelp and the Technical Reference Guide supply information for using the AS-P/B DHCP server option, however, a number of relevant questions have not been answered. Product Line EcoStruxture Building Operation Environment Building Operation Automation Server Premium (AS-P 0.62 hardware) Building Operation Automation Server Bundled (AS-B) Building Operation SmartX IP Multi-purpose Controller (MP-X) Building Operation SmartX IP Room Controller (RP-C) Building Operation SmartX Controller IP-IO Series Cause There are typically a number of options to configure DHCP servers, but since the DHCP server included with the AS-P/B is very basic and NOT configurable, it's important to understand which options are and are not available. Resolution Webhelp has some helpful information about the DHCP Server Options. The AS-P/Bs built-in DHCP server assigns unrouted IP addresses within the range of addresses from 10.110.210.2 to 10.110.210.254. This was developed to allow for a quick configuration of a private MP-X/RP-C network. The AS-P/B DHCP server can be disabled and another DHCP server can be used. Here is a list of other questions and answers that may come up based on typical options in other DHCP servers: Can the scope of the IP range be configured? There is no way to configure or limit the range of the standard IP address range or to have multiple scopes. Can IP exceptions be configured? There is no configuration option to prevent the AS-P/B DHCP server from assigning a specific IP address. The AS-P/B DHCP server is unaware of static IP addresses, so if a switch or other device has a static IP set in the 10.110.210.2 to 10.110.210.254 range, you run the risk of having the AS-P/B DHCP server assign an IP address twice which can cause a number of issues. Can a Default gateway be configured? Not configurable Can a Subnet mask be configured? Not configurable Is IP6 supported? No Can lease types be configured? No Can multiple DHCP servers be installed on the private LAN? No Should MP-X/RP-C IP level devices only be hosted within the private AS-P/B network? Most site IT departments prefer that the BAS networks be isolated, however, if the network switch (Not the AS-P/B) is used for assigning DHCP IP addresses, it could hand out addresses to the AS-P/B and the MP-X/RP-C devices if they are on the same subnet. A managed (RSTP Enabled) switch can reside as a client to the AS-P/B. This is due to how the Private DHCP option is advertised. On-site IT departments may not want the switch on the customer's LAN so it is placed in the private AS-P/B network. Does the AS-P/B DHCP server assign addresses to 3rd party devices? Yes, if the 3rd party device supports this. This would be a configurable option in the device.

Issue BACnet AlignIntervals Error when downloading b3 controller after a Continuum conversion Product Line EcoStruxure Building Operation Environment Continuum conversion b3 Controllers Cause After a Continuum conversion the b3 controllers will not download correctly and AlignIntervals error is seen. Resolution This is most likely a result of have older firmware in the b3 controllers. No exact EBO supported version is stated for the b3 controller, but it is advised to always use the latest firmware version. Early versions of SBO (v1.0 to v1.9) would have been tested with v4.500064 (June2010) and v4.500076 (Mar2014). M ost EBO testing being done at v4.500077 (Nov2017). It is likely a b3 with firmware v4.500049(Jul2009) could operate correctly.   It is advised to use the current version of firmware in a b3 controller.   Continuum Conversion Tool Notes See   Known Issue v3.0   See   Known Issue v3.1 So for Continuum conversions, EBO v3.0.x, v3.1.1 and v3.1.2 up to CP4 should avoided. The work around for these versions is to convert using v2.0 then upgrade to the required version. Or for v3.1, use v3.1.2.6000 CP5 or later. The issues are fixed in v3.2.

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 What is the correct procedure for migrating Infinet controllers from a Continuum controller fieldbus to an AS-P. Product Line EcoStruxure Building Operation Environment Continuum Building Operation Automation Server (AS-P AS-B) 1.9 onwards Cause It is critically important to follow an approved and tested procedure when migrating Infinet controllers from Continuum to EBO.  Resolution Procedure for Converting / Transitioning the Infinet Bus Prior to migrating the Infinet 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 1.          From Continuum Cyberstation,  the following must be completed to each Infinet controller that you are moving to an AS-P. a.      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. b.         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. 2.      If the conversion was done on the PCT, deploy the AS-P. 3.      Verify that the AS-P firmware is 1.9.0.73 or higher. 4.      Disconnect Infinet bus from the Continuum controller com port(s). 5.      Move the Infinet bus (busses) to the corresponding RS485 port(s) on the AS-P. 6.      Confirm that the Infinet devices are all showing online under the AS-P 7.      Download the Infinet devices. * 8.      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. Continuum Conversion Tool NOTE 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

Issue When attempting to login to Web Client the below error is seen. “The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state." Product Line Security Expert Environment Security Expert Web Client Cause The typical cause of this error is a mismatch in the security bindings between the SOAP Service and the Security Expert Data Service. For example if you enable the Windows Authentication checkbox in the Security Expert installer but not in the SOAP Service installer (or vice versa) then you have a mismatch. Resolution Either uninstall the SOAP service and update the checkbox selection to match whatever was selected in the Security Expert installer, or follow the instructions under Troubleshooting | Communication Fault/Failure in the SX-WEB Web Client Installation Manual.pdf for editing the config files of the SOAP service to match the Security Expert Data Service.

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 Timeout errors appear while attempting to download a controller assigned to the secondary download server after editing the configuration file to add a secondary Download Server Product Line Security Expert Environment Security Expert Application Server Security Expert Download Server Cause A Download pending and a timeout error may show when trying to download a controller assigned to the secondary server if the secondary download service isn't started or the configuration files have not been properly edited .     The Application Note AN 290 Security Expert - Setting up a Secondary Security Expert Download Server - Integration Guide describes changes to the  SecurityExpertSV2.exe.config file required for the second download server. The SecurityExpertSV2.exe.config Modified Connection Strings section needs additional clarification and there is no mention of SecurityExpertSV.exe.config file in the application note which also needs to be configured. Resolution Open the An-290 Security Expert - Setting up a Secondary Security Expert Download Server from the link above. Follow all the steps up to the Server Configuration section on page 7. This article is to clarify just that section of the application note. (The app note will be changed in the future) Ensure both Security Expert download server installations are on a domain. Note: A multiple download server configuration will not work within a workgroup. Make a copy of 2 files: C:\Program Files (x86)\Schneider Electric\Security Expert\SecurityExpertSV2.exe.config and SecurityExpertSV.exe.config                                  Note: the different names of these files). Rename the original files or delete them Download SecurityExpertSV-SV2.exe.config.BLANK.zip from this article's attachment section and unzip both files into the C:\Program Files (x86)\Schneider Electric\Security Expert folder on the secondary download server Edit the new SecurityExpertSV2.exe.config file with Notepad++ or Notepad with admin rights Change the fields highlighted in yellow in the image below (PrimaryServerIP address, database name(if not using the default) and password), to match the site and save the file. Edit the new SecurityExpertSV.exe.config file with Notepad++ or Notepad with admin rights Change the fields highlighted in yellow in the image below (PrimaryServerIP address, database name and password), to match what the site configuration and save the file. Continue to Page 8 of "Setting up a Secondary Security Expert Download Server Integration Guide" to complete setting up the Secondary Download server

Issue Firewall issues when trying to reach out to the activation server for a license Product Line EcoStruxure Building Operation, Satchwell Sigma, TAC Vista Environment Building Operation Licensing Firewall Cause If the corporate network has a very restricted firewall policy or rules, the port needed to reach and activate a license may be blocked. Note: The same license server is used for EcoStruxure Building Operation, Satchwell Sigma and TAC Vista software licenses. Resolution Open both (http) Port 80 and (https) Port 443 for the server hosting the license server, and ensure that the routing paths to the Flexnet Licensing server URL's are all fully open. The Licensing Server URL should be opened from the site, and it is: https://schneider-electric.flexnetoperations.com If the site of the old server has issues with the non secure communications or the communications forwarding between the previous and the new server, there is a tool available to configure EBO to only use the new server. See the Exchange Community article for the download: SBO License Setup Note: From EBO V2.0 only the new license server is used.

Issue Upgrade path from version 1.0 to a current version Product Line EcoStruxure Building Operation Environment SmartStruxure Building Operation versions 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9 EcoStruxure Building Operation versions 2.0, 3.0, 3.1, 3.2, 3.3 (limited) Cause Upgrade path from version 1.0 to current - version Important - The upgrade process is sequential, for example, 1.1 to 1.2 to 1.3 to 1.4 From v1.9, non-sequential upgrades are possible  The primary released versions were, Release Note Dates (approximate) 1.0.0.161   1.1.0.362 Dec 2011 1.2.0.767 July 2012 1.3.0.938 Nov 2012 1.3.0.10100 SP1   1.3.0.20011 SP2   1.4.0.4020 Sept 2013 1.4.1.68-73 Oct 2013 1.5.0.532 July 2014 1.6.0.250 (RC) Dec 2014 1.6.1.5000 Feb 2015 1.6.2.27 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.7.0.255 (RC) July 2015 1.7.1.89 Oct 2015 1.7.2.29 Maintenance Release Jun 2016 see TPA-SBO-16-0003 1.8.0.244 (RC) Mar 2016 1.8.1.79-87 Jun 2016 1.9.1.95 Apr 2017 1.9.2.45 Maintenance Release Oct 2017 1.9.3.24 Maintenance Release April 2018 1.9.4.29 Maintenance Release April 2019 2.0.1.130 & 135 June 2018 (130(License, WS, Reports Server) 135 - Server (AS, ES, EC)) 2.0.2.67 Maintenance Release Sep 2018 2.0.3.45 Maintenance Release Dec 2018 2.0.4.83 Maintenance Release June 2019 3.0.1.104 May 2019 3.0.2.33 Maintenance Release July 2019 3.0.3.11 Maintenance Release Aug 2019 3.0.4.43 Maintenance Release Dec 2019 3.1.1.312 Dec 2019 3.1.2.29 Maintenance Release Mar 2020 3.2.1.630 Aug 2020 3.2.2.61 Maintenance Release Nov 2020 3.3.1.59L Limited distribution release Feb 2021 - intended for specific feature compatibility with some hardware or applications - See release note Resolution It is most important to read the Release Notes and System Upgrade Reference Guide for each version you are upgrading to, as there are some special notes that only apply to some installation types. Click Here for Release Notes Click Here for Upgrade documentation The Minimum upgrade path would be as below (See Release Notes for any special instruction) 1.0.0.161 1.1.0.362 See StruxureWare Building Operation v1.0 to v1.1 upgrade issues Appendix A 1.1.0.1225 See Appendix A 1.2.0.767 See Appendix A This version can be avoided by using 1.2.0.1412 if possible 1.2.0.2207 (Hotfix) Available from PSS See also Appendix A 1.3.0.938 See also Appendix A 1.3.0.10100 (SP1) (needed if runtime compatibility is required during upgrade) 1.4.0.4020 or 1.4.1.68 (Only needed if runtime compatibility is required during upgrade) See Upgrading Automation Servers from 1.3 to 1.4 1.5.0.532 1.6.1.5000 See Upgrade to 1.5.0 or 1.6.0 fails 1.7.1.89 1.8.1.87 See Product Announcement 00471 Pre-Upgrade LON Add-On 1.7.1 to 1.8.x 1.9.1.95 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions Option to 1.9.2.45 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.3.24 Upgrade options more limited with this version, only from v1.7.2, see the release note Option to 1.9.4.29 Upgrade options more limited with this version, only from v1.7.2, see the release note 2.0.1.130/135 Possible to upgrade directly from v1.5, but carefully study the release notes and upgrade instructions. NOTE the new License structure for v2.0. 3.0.1.104 Possible to upgrade directly from v1.8, see the table in "System Upgrade Reference Guide" (3.0.1 System Upgrade Overview), but carefully study the release notes and upgrade instructions. NOTE the new Licenses for v3.0. 3.1.1.312 Possible to upgrade directly from v1.8 See Release notes and upgrade documents for full details 3.2.1.630 AS Classic not supported, Win 7 and Win server 2008 not supported 3.3.1.59L Limited distribution release - intended for specific feature compatibility with some hardware or applications, see release note for details. If you do not require the specific features outlined in this Release Notes, it is recommend installing EcoStruxure Building Operation 3.2.x instead Appendix A - Upgrading from Specific 1.x Builds Upgrade from V1.0.0.XXXX to V1.3 (via V1.1 and V1.2) Upgrade from 1.0.0.XXXX to 1.1.0.1225 Upgrade from 1.1.0.1225 to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.1.0.XXXX to V1.3 (via V1.2) Upgrade from 1.1.0.XXXX to 1.2.0.1412 (Do not use 1.2.0.767) Upgrade from 1.2.0.1412 to 1.3 Upgrade from V1.2.0.767 to V1.3 Apply hotfix 1.2.0.2207 Upgrade from 1.2.0.2207 to 1.3 NOTE: These hotfix builds are not available for download from the Extranet site, you will need to contact Product Support and request them

Issue A BACnet devices can contain 1000's of objects, performing an upload on these devices can take upwards of 30 minutes to complete when only a few objects are required for integration. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building operation Automation Server BACnet Device, Device discovery Cause Upload of all objects in a controller can take a large amount of time and is often not required. Resolution From version 2.0 Open the device discovery view / BACnet - then Discover All. Once the Device is hosted, click on the device (in the Device Discovery window) and open the right hand Object pane. Drag/drop the required Object into the hosted BACnet device Application folder. Alternatively the Hardware folder can be used, this was the best method for some earlier versions Perform the BACnet discovery, then view the Hardware folder at /ServerName/System/Hardware/BACnet devices. Navigate to the required Device/Object, then Drag and drop the Device and Object as above.

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

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 AS status LED solid red for a few seconds followed by a quick blink. Device administrator and/or event log shows ..."Error - Upgrade using DFU mode system alarm" Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, AS, ASP, ASB Building Operation Device Administrator Building Operation WorkStation Cause The indication of "Error – Upgrade using DFU mode" occurs due to the fact that a possible problem with writing to the file system has been detected when booting the system. This error can be seen in WorkStation as an Alarm Event, in in the Server Logs or in Device Administrator. The configuration of the system could had been compromised as a result, although the issue is not necessarily fatal and therefore the AS is allowed to run and the situation indicated via the red status light. A system alarm is also generated as a warning as seen in the screen shot above. Resolution Since the AS file system could have been compromised, it must be re-initialized from scratch. To clear the red light: Make sure a backup of the AS is available. Attach the Device Administrator to the AS via USB and put the AS in DFU mode (press the reset button 3 times in rapid succession) Install a new database Once the AS has had its FW and database reinstalled, restore the backup using Workstation. NOTES See https://ecostruxure-building-help.se.com/bms/Topics/show.castle?id=10005&productversion=3.3&locale=en-US&a=1 If this error occurs, especially if it occurs multiple times on the same server, check the site installation include Grounding/Earthing and power supplies and for possible EMC issues (Electromagnetic Compatibility)

Issue How can the format of a custom card be determined/understood Product Line Andover Continuum Environment Access Control AC1 AC1Plus ACX Cause The format of access cards is unknown. Resolution The document Understanding custom card formats in Continuum describes how to determine the custom format of proximity cards.  

Issue How to get the data to display automatically (expanded) when running the Trend Log Comparison report. When running the Trend Log Comparison Report, the data is not shown in the tabular format automatically, and the + must be clicked on to expand this table to show the values.  Product Line EcoStruxure Building Operation Environment Building Operation WebReports Microsoft SQL Server Report Builder Cause When either using a Dashboard report or Exporting reports, some situations require the data to be expanded automatically when generating the WebReport.  The following discusses the changes required to be made to this report to allow this to happen.  Resolution To have the report automatically display this data fully expanded, the default WebReport "Trend Log Comparison" needs to be edited using Microsoft SQL Server Report Builder.  See the following online Help Topic for additional detail on using Report Builder with Reports. Open the Trend Log Comparison report using Report Builder. Scroll down to the bottom section of the Report and select (left-click) the DateTimeStamp field Under the Row Groups, Right-Click on [DateTimeStamp] and open Group Properties. Select the Visibility and change this option to Show  Save the file - It is recommended to save the report with a new name and not alter the default factory report.  This new report must then be deployed to the WebReports Server.  This is done by Synchronizing the new report as detailed in the online help: Synchronizing WebReports with a New Report. Running the report should now automatically have this data expanded.  

Issue The ServerPack installation process does fail to complete on a new PCT installation PCT presents the following error. : 'beee::vm_module::VirtualBox::make_disk_multiattach' due to: 'VBoxManage.exe: error: Cannot change the type of medium 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\docker.vmdk' because it is attached to 1 virtual machines VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The VBoxHardening.Log (\\Users\John Boehmer\VirtualBox VMs\NoteTEst\Logs) is flagging dll flags that are incorrectly signed. supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll [lacks WinVerifyTrust] If an attempt is made to create a virtual instance in VBox the machine fails to run with the following error. Resolution Uninstall all non-essential software applications from the host machine.  In this case, PCT was being installed on a brand new Hewlett Packard PC that had a variety of HP security software.  In some cases, other non-essential applications may need to be uninstalled as well. Once the software was uninstalled PCT was reinstalled over the top of the existing installation. Virtual machines created in VBox could then be started and PCT began to function normally.

Issue SOAP service can't be reached @ http://localhost:8030/SecurityExpertSOAPService/service.svc  HTTP Error 404 Product Line Security Expert Environment Security Expert Server Cause Confusion related to the indicator Windows uses to denote when features have been enabled. Instructions in the Security Expert SOAP service installation manual not sufficiently clear. For instance, the documentation shows a checkmark in the .NET framework feature but it does not show the sub-items, a checkmark here means all of the sub-items are also enabled but this is not necessarily intuitive.  When not all of the sub-items are enabled, Windows shows the check box filled with a black square but many users are interpreting this as meaning the same as a checkmark. Resolution When a feature check box shows a checkmark in the documentation, make sure to expand the feature and enable ALL of its sub-items 

Issue The hard drive fills up with logs generated by PostgreSQL/Timescale. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause Trend meta table missing information Resolution In the ES, go to the TimeScaleDB configuration. Set Trend and Event storage to false and click save. Set Trend and Event storage to true and click save.

Issue The site has Alarm Action to email certain door alarm condition but only at a specific time of day and/or day of the week Product Line Access Expert Environment Access Expert Hosted Software Access Expert Premise Software Cause Alarm actions do not allow association with a regular schedule, instead, the filter query can be used to specify a time and/or the day the action should take place. Resolution The screenshot below shows the schedule that the site wanted to use to specify when the action should be carried out... Since we can not associate the schedule with the alarm action, we should instead specify the days/hours in the filter query using the following filter...   ((EventData["Status"].AsString == "Activated")&&(((OccurredOn.Date.Hour < 17 && OccurredOn.Date.Hour < 4)&&(OccurredOn.Date.DayOfWeek == "Tuesday"|| OccurredOn.Date.DayOfWeek == "Wednesday" || OccurredOn.Date.DayOfWeek == "Thursday" || OccurredOn.Date.DayOfWeek == "Friday")) || (OccurredOn.Date.DayOfWeek == "Saturday" && OccurredOn.Date.Hour > 4)|| (OccurredOn.Date.DayOfWeek == "Sunday")||(OccurredOn