Building Automation Knowledge Base

Issue Support for OPC or DDE integration with EcoStruxure Building Operation Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Premium Cause The OPC Server is a software program that converts hardware communication protocol into the OPC protocol. The OPC client software is any program that needs to connect to the hardware. The OPC client uses the OPC server to get data from or send commands to the hardware. Resolution Neither the OPC server nor the DDE configuration is supported at this time. There is not currently a roadmap for direct OPC client or server capability within the EcoStruxure Building Operation. To avoid problems with OPC Integration (and lose a project), there are two options for OPC integeration: It is possibe to use a converter to convert OPC to/from one of EBO supported protocols.  For example, use a 3rd party software to translate all the OPC points into BACnet Objects, “OPC Server -> BACnet Server”, or translate all EBO BACnet points to OPC. Perhaps one of the software programs below will be of benefit. Take into consideration what specifically will the ES be doing. If it is exchanging point values then it should work fine. Kepware Matrikon SCADA engine Note: These are 3rd party products that are not supported by Shneider Electric.    Use a SmartConnector Extension to be a middleware between EBO and OPC cilent or server. Check available extenstions at Exchange shop and SmartConnector Server and refer to EBO SmartDriver and Smart Connector KB article for more information.

  Issue Is it possible to use the RP-C relays to control LED Light?  The specification sheet does not specify the maximum inrush current. Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) 24 V Building Operation Room Controller (RPC) 230 V Cause RP-C is not designed for switching light loads, and especially not LED loads. LED loads will result in a very high inrush current and require relays that are designed for that. Furthermore, the light application often requires relays that keep the light on in case of power failures which is not the case for RP-C. Resolution The CRS light modules and the Hotel Relay modules have that type of relays and can handle peak currents up to 800A, which is typical for LED loads. If using the CRS modules is not an option for the customer another possibility is to use a contactor connected to the RP-C.

Issue How to add Basic Authentication header to SendWebRequest function in Script RESTful Web Services 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 Cause A 3rd party web service requires basic authentication for HTTP requests to ensure that data is requested securely, otherwise, the request will be rejected with an "Authorization Error".   Resolution Basic Authentication is a type of Authorization Request Headers, which transmits credentials as user-id/ password pairs, encoded using Base64, as defined in RFC 7617 - The 'Basic' HTTP Authentication Scheme (ietf.org).  Follow the below steps to create a Basic Authentication header in Script RESTful Web Services: Combine the User ID and the Password with a colon ex. "aladdin:opensesame". Encode the resulting string in base64 using script function to base64 encode a string posted in the Community or using the online encoder as Base64 Encode and Decode - Online, ex.  "aladdin:opensesame" will be "YWxhZGRpbjpvcGVuc2VzYW1l" after Base64 encoding. Construct SendWebRequest header in the following format:  Authorization: Basic <credentials>, as below example:  Headers= "Authorization: Basic YWxhZGRpbjpvcGVuc2VzYW1l"'User ID=alaadin Password=opensesame Resultstring= SendWebRequest(BaseUrl,Method,ContentType,Headers,Message) Note: Basic Authentication is not a secure method of user authentication unless used in conjunction with HTTPS/TLS, as the user ID and password are transmitted as clear text. User ID and Password are Base64 encoded but Base64 can be easily decoded.  For more information refer to Script RESTful Web Services WebHelp and Authorization - HTTP | MDN (mozilla.org)

Issue This is a project to support integration with the Schindler PORT system. It should be deployed on a customer site to directly connect to the Schindler PORT firewall and be configured to connect to the customer instance on the Access Expert (AX) side to add, update, or remove people from Schindler PORT based on which access levels they belong to in AX.  Product Line EcoStruxure Access Expert Environment Access Expert Hosted software Cause Please read all the instructions to properly deploy and configure this service. Resolution Card formats The Schindler reader produces a 16-digit hexadecimal value after reading a card and sends it to the Schindler Port system for validation. The value from the Schindler reader is a different value from what is entered as the encoded card number in AX. Therefore, there needs to be an additional entry of the hexadecimal value in AX in the Hex Value field of a card assignment. The Hex Value will be sent to the Schindler Port system as the card number so that it matches with the Schindler reader value to get access.   To find out what the Hex Value needs to be, the process was to send Schindler 10 cards from a particular project then they get back to us with the correct hexadecimal representation of those cards. This will need to be done between you and Schindler for your project.   Prior to version 22.3.1 of the AX Schindler service, the service was used to encode the Encoded Card Number from AX using a 16-digit value of 0100000020000000, then replace the zeroes at the end with the hexadecimal representation of the Encoded Card Number. The service will still do that if no Hex Value is specified for a card but that may not be the correct encoding for your project.   In short, you need to enter the Hex Value of a card assignment in AX as the value that is generated by the Schindler card reader. Deployment The Schindler service is deployed using Docker. If you are using Windows, we recommend having WSL2 installed and enabled for Docker. The installer needs to pull the images for both Seq (for logging) and the Schindler service from the Docker hub.   The installer also needs to create a Docker network called ax-net. To create the network, execute: docker network creates ax-net To get the Seq image: docker pull datalust/seq To get the Schindler service: docker pull feenics/feenics-keep-schindler To install Seq (replace /path/to/seq/data with the actual path of a directory on disk, this is the linux notation): docker run -d --name seq --restart unless-stopped --network keep-net -e ACCEPT_EULA=Y -v /path/to/seq/data:/data -p 5341:80 datalust/seq To install Schindler (env.txt is in the same directory where you are executing the docker run in this case): docker run -d --name feenics-keep-schindler --restart unless-stopped --network ax-net --env-file env.txt feenics/feenics-keep-schindler Environment configuration The following environment variables can be specified in a file (env.txt in the example above) that is passed to the container when launching it from Docker. In the file, each of these properties will be followed by an equal sign then its value. ClientInstance= ClientUsername= ClientEncryptedPassword= ClientWSS= ClientAddress= Company= TagName= SchindlerServerIp= SchindlerServerPort=   Below is the description of each property: ClientInstance - the name of the client instance ClientUsername - the username to login the client instance ClientEncryptedPassword - the encrypted password obtained from the service password utility ClientWSS - the address of the MQTT event publisher (for USA: wss://keepevents.feenicshosting.com/mqtt) ClientAddress - the address of the API (for USA: https://keepapi.feenicshosting.com) Company - the company name as configured in the PORT system TagName - the tag name that will be assigned to the Schindler access levels in Access Expert SchindlerServerIp - IP address of the Schindler PORT firewall SchindlerServerPort - Port to use to connect to the Schindler PORT firewall Password The password in the environment configuration needs to be encrypted. The service has an embedded encryption utility. If you start the service with an additional parameter called "password", it will run the password encryption utility instead. Copy the encrypted password and add it to the configuration. To run it, execute the following: docker run --rm -it --name feenics-schindler-utility feenics/feenics-keep-schindler password The --rm will remove this container after it exists so you do not have to delete it manually.   Permissions The service user needs to have permission to read access levels, read people, read event messages and publish all Schindler event types. This is done by creating a group that has those permissions and assigning that group to the service user in Access Expert. The service will monitor the changes in the current instance and all the instances below it in the hierarchy.   Operation The Schindler PORT integration limits the configuration capabilities that can be performed from AX. We are able to add, update, or remove people from profiles in PORT. The Schindler PORT system has profiles defined with particular access to certain floors. These profiles need to have access levels in AX with the exact same name as the profile in order to add, update, or remove people from these profiles in PORT automatically. An access level matching a profile needs to be tagged with a tag name agreed upon and configured in the Schindler service (TagName). A person can only be in ONE profile in the Schindler system. This means that a person can only be in one access level tagged for Schindler sync. If a person is in more than one Schindler tagged access level, only one of the access levels will be chosen. If a person needs to have access to additional Schindler access levels, this needs to be performed from the Schindler system by defining a profile with all the required access and then adding an access level in AX with that profile name and Schindler tag. The Schindler service listens to changes in people and checks if they belong to a Schindler tagged access level then sends an update to Shindler PORT (first name, last name, 3 card assignments, profile name, start and expiry date) PORT only supports one start and expiry date for all three cards so we take the union of the three The Schindler service also listens to changes in access levels that have the defined TagName, whether a Schindler tag was added or removed to either send or remove the people in that access level from the Schindler system Warning: DO NOT delete an access level that has a Schindler tag. You need to remove the tag first in order for the service to know which updates it needs to send to PORT. Schindler command and response numbers (logged in Seq) The first three numbers in the command are an index, it is incremented with each command sent, and the PORT systems reply with the same command index. The next two numbers are the command type or the reply type as follows: SendAlive = "00" SendAliveSuccess = "01" ChangeInsertPerson = "06" ChangeInsertPersonSuccess = "03" ChangeInsertPersonError = "07" DeletePerson = "08" DeletePersonSuccess = "05" DeletePersonError = "09"   Important Add a permission restriction that an access level tagged with the Schindler tag cannot be deleted. This is important because we need to remove the people in Schindler PORT before deleting the access level. The workflow would be to delete the Schindler tag first, then you are allowed to delete the access level.   Recommendations The enterprise should review all access levels tagged with the Schindler tag to audit the entities that are giving elevator access. The enterprise creates the profile (access level) in the PORT system. If the tenant has a shared instance, the enterprise informs the tenant of the access level name and the Schindler tag to automatically send their people to the PORT system.

Issue Trend charts don't display any data in Advanced Display v3 (ADv3) although the data can be seen in a trend log list  The trend charts display data normally on other WorkStation and WebStation clients. Product Line EcoStruxure Building Operation Environment Advanced Display V3 Cause The ADv3 date is incorrect, therefore the trend chart when opening shows an interval that doesn't include any data. Resolution Set the correct date and time in the ADv3:   Exit the SmartX HMI Kiosk app - Short press the power button (less than 3 seconds) Enter the password to exit the app and return to SmartX HMI Kiosk To Exit the Kiosk mode repeat the previous 2 steps. In the Home screen mode slide up and tap Settings Tap the System option Tap the option Date and Time and adjust accordingly or enable the option Automatic date and time.  

Issue Some graphics are not visible from specific WorkStations but are visible in other WorkStations or WebStation. The graphic has an orange exclamation point overlay in the system tree and the graphic has an INVALID OBJECT error with the following error description: "An unexpected error occurred when fetching type udt <alpha numeric string>. The type cannot be decoded." No Showing graph in WorkStation Product Line  EcoStruxure Building Operation Environment Building Operation WorkStation Cause This issue is due to corruption in the WorkStation cache. Note that the WorkStation cache is NOT cleared when WorkStation is uninstalled, it needs to be manually removed. Resolution Uninstall ALL versions of WorkStation on the PC Navigate to: %AppData%\Schneider Electric EcoStruxure\Building Operation\ Delete the WorkStation folder Re-install WorkStation and open the graphics again.          

Issue “Invalid certificate for https communication” alarm pops up after upgrading to EBO 4.0     Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Cause "Invalid certificate settings for Server to Server communication" is set to enabled (Generate Alarm) by default for new installations/upgrades. This function was deliberately designed to alert existing installations that their sites might be subject to security-related issues, and necessary action needs to be taken. Resolution If users want to get rid of this alarm, they need to: Suppress the alarm by unchecking the “Generate alarm” under Security Settings/ Invalid certificate settings for server to server communication   Or Replace the server certificates with one that can be validated against a CA certificate.   Note: Please refer to the following web pages for more information. CA Certificate Management Security Settings – Control Panel  SSL Certificates 

Issue Presented with a message saying the activation was completed but "The license file could not be found". The license was then not activated. Product Line EcoStruxure Security Expert Environment Security Expert License Activation Cause This is a credential issue. What happens during a license update is that the license is downloaded to ..\ProgramData\Schneider Electric\SecurityExpert\License folder and is then loaded from that location. If the current Windows user doesn't have the correct permissions to write or read from that folder then the process will fail and we will get the error message Resolution Go to the C:\ProgramData\Schneider Electric\SecurityExpert\License location and right-click on the folder white space and select properties.  This will bring up the properties window of the folder "License" shown in the screenshot below.  Go to the Security tab and ensure that the SYSTEM and Users accounts have  the same permissions set as what is shown in the screenshot below (specifically read and write permissions).

Issue Unable to login to Webstation when it is embedded in an iframe on a webpage even though the security setting Enable WebStation to be embedded into another website is set. Clicking Log on after entering credentials just makes the login page reload. Security Setting "Enable WebStation to be embedded into another website" security setting   Webstation login page in iframe Webstation might even go into a login loop if the Guest account is activated and Webstation logs in automatically to this account: Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Webstation Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause The Webstation login functionality relies on HTTPS redirect to function properly when it is embedded in an iframe. Error message in the browser developer tool console says: Blocked autofocusing on a <input> element in a cross-origin subframe. Resolution Webstation needs to redirect web clients to HTTPS. There is a setting in Security Manager that controls this. Follow the steps below to activate the redirect: Login to Workstation and go to Control Panel and then Security Settings. Check Redirect web clients to HTTPS and save the change.

Issue WorkStation will play audible alarms but the same alarms will not play in WebStation Product Line EcoStruxure Building Operation Environment Building Operation WebStation   Cause Alarms can be viewed in WebStation but they do not have audible alarm sounds.  Resolution Audible alarms are available in WebStation from 3.2 onward.   See online help topic: WebStation and WorkStation Differences - EcoStruxure WebHelp

Issue Users or engineers may be unsure of how to access the best support for issues with EBO Smart Connectors, especially where site specific Smart Connectors have been developed, or believe the issue is with the underlying framework. Product Line EcoStruxure Building Operation Environment Integration Cause Unlike EBO, which is a standard EcoStruxure product that falls under normal R&D, the Smart Connector (formerly known as Mongoose) was developed by Schneider Electric Buildings Labs and a separate R&D Team.   Resolution If using a Smart Connector developed specifically for a project by a separate Integration Team within Schneider-Electric, then it is always best to go back to that team with your technical issues. In all other cases, the Smart Connector Framework is now supported via normal Product Support channels by raising a support case with your local Customer Care Centre, just as you would for any other EcoStruxure Issue.   The  SmartConnector Developer Forum: can still also still be found on the community.  

Issue Numbers are rounded. Why two values of nearly equal magnitude are subtracted, significant digits are lost.  This occurs in a variety of places within EcoStruxure Buildings Operation, and explained using a script program in the example below. Product Line Ecostruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause In a string program and the NumToStr function, if a number (example 5.7) is entered and Save is selected, then the Value in the Variables window at the bottom shows 5.6999998. The value is altered from the original. Resolution When looking at a value in the watch window or variables view, there is no rounding so you are going to see the full length of the float number which suffers from a thing called “loss of significance” More information on float numbers can be found at: https://en.wikipedia.org/wiki/Loss_of_significance This phenomenon happens everywhere. An alternative would be to add a formatting feature to do the rounding. Script handles numbers as IEEE754 single precision floats, so the accuracy is limited to (IIRC) seven significant digits. The accuracy loss starts around 1.677E7. On www.binaryconvert.com/convert_float.html?decimal site, a decimal number can be converted to binary and then back to decimal in order to see how the decimal number will be handled in Script. Script handles numbers as IEEE754 single precision floats, so the accuracy is limited to (IIRC) seven significant digits.   The accuracy loss starts around 1.677E7.   On this site you can convert a decimal number to binary and then back to decimal in order to see how the decimal number will be handled in Script. http://www.binaryconvert.com/convert_float.html?decimal

Issue Require details on how to configure duress events from Doors and Keypads to be registered and displayed as alarms. Product Line EcoStruxure Security Expert Environment Security Expert Cause Door and Keypad duress trouble inputs are not configured to trigger alarms when activated. Resolution Use an Event Filter to filter for specific Trouble Input events and then setup an Alarm to use that Event Filter. Configure an Event Filter for duress events by creating an event filter with the Event Type: Trouble Input<TROUBLE_ZONE_NAME>Opened If you need an alarm for when the duress trouble input is closed then also add: Trouble Input<TROUBLE_ZONE_NAME>Closed Event Types Then on the Records Tab add the specific Trouble Input(s): User Duress Code Door Duress Record Filter Create a new Alarm record under Events | Alarms. Add this Event Filter, created in step 1, to the Alarm.

Issue The SX-IPI-C documentation does not show how to stream video from the IP Intercom. Product Line EcoStruxure Security Expert Environment Security Expert SX-IPI-C Cause The currently available documentation does not adequately describe how the video stream can be viewed and that RTSP is the only streaming protocol that is supported. Resolution 1. Locate the video stream URL From the Intercoms web interface go to Intercom Settings > Video. The stream URL's can be viewed under the RTSP Information heading.   2. Configure Security Expert to use the video stream URL To view the Intercoms camera feed within Security Expert, follow the instructions on how to set up a direct camera outlined in the Security Expert Operator Reference Guide under the Direct Camera heading. The direct camera URL for the Intercom to be input here is the one found in Step 1 above.

Issue Site upgrading ES from 3.2.1.630 to 3.2.3.59. After the upgrade, some graphics and custom types are missing Before Upgrade: EBO 3.2.1.630   After upgrading to EBO 3.2.3.59   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Enterprise Server Cause Error "is not defined in the target version, discarding object ~ " is found in the upgrade log. Resolution This video demonstrates the steps to upgrade ES successfully displaying all Graphics and Custom types Upgraded ES from 3.2.1.630 to 3.2.3.59 Graphics and custom types were missing Used CP11 3.2.3.1300 to upgrade Successful upgrade showing all Graphics and Custom Types When upgrading within the same version (from 3.2.1 to 3.2.3) we must use a hotfix. We shouldn’t be using the Full installer since the work folder and original folder is the same.

Issue Unable to log in to Web Client. After filling in the username and password and clicking "Sign In" the Sign In box disappears and the Username, Password, and Language Box are shown. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Web Client Security Expert SOAP Cause Configuration issues are usually related to a mismatch between SOAP and Web Client security settings. Resolution Commonly this problem is resolved after re-installing SOAP and Web Client then rebooting the machine. If this does not resolve the problem then continue to check the below troubleshooting steps and gather information for support if those steps do not resolve the problem.   Is everything on one machine or are the various components spread across a number of machines? If so, where is SQL, Security Expert Server, SOAP, Web Client, and Security Expert Client installed? If different machines, provide these details to support, which components are on each and what Operating System (OS) is installed. Are you using the HTTP connection for SOAP or HTTPS? If HTTPS and SOAP are on the same machine as Web Client then try using the HTTP port. Either re-install SOAP and Web Client using the HTTP option instead of or: Browse to the soap.connect.php located at C:\inetpub\wwwroot\SecurityExpertWebClient\include.  Edit it using e.g. Notepad and change HTTPS to HTTP and change the port to 8030 so the Web Client uses HTTP to communicate with the SOAP service. Then in IIS Manager restart the SecurityExpert and SecurityExpertWeb services. If a hardware or software firewall is being used, test the connection without these enabled. If Chrome is the browser being used then test with another browser such as Internet Explorer, Microsoft Edge, or Firefox. Confirm that all Security Expert services are running and started. Confirm the SOAP prerequisites have been installed for your Operating System (OS). See the Enabling the Required Windows Features section in the SX-SOAP Security Expert - SOAP Service - Installation Guide. In this document, there is a heading with instructions for each supported OS. Confirm that a Windows local admin user has been used to install all components. If in doubt, re-install Security Expert, then SOAP, then Web Client. Confirm if Security Expert was installed with Windows Authentication selected, if so then SOAP will need to have this option enabled as well during its installation.  Determining Security Expert authentication settings after installation  Confirm that you have adequate concurrent client licenses available on your Security Expert license. SOAP uses one of these when connecting to the Data service and if none are available the SOAP connection will fail.  See Unable to log in to Security Expert Web Client - 'Too Many Connections' The Microsoft Visual C++ 2015-2019 Redistributable Package is a requisite install for Web Client. Web Client installs this as part of the setup, confirm that this was installed. Check the Windows Event Logs for Security Expert errors. Open Windows Event Viewer: browse to Windows Logs > Application. Review logs and save all events to file. Provide this to Product Support if raising a support case. browse to Applications and Services Logs > Schneider Electric Security Expert. Review logs and save all events to file. Provide this to Product Support if raising a support case. Reboot machine after re-installation of SOAP or Web Client. If SOAP was re-installed then also re-install Web Client. Please provide findings and responses to the above steps through to your local support channel for additional assistance should the problem continue.  

Issue Need to manage car park usage based on the company associated with each vehicle. Product Line EcoStruxure Security Expert Environment Security Expert Controller (SP-C) Cause Area counting can be configured to count the users with a defined access level who are present in the area. In a shared car parking application, this can be used to limit the number of parking slots assigned for each company. Resolution The steps below are based on AN 278 Security Expert - Access Level Area Counting - Integration Guide Navigate to Users | Access Level and create an access level for each company and take note of the database ID for each access level.   Navigate to Automation | Data Values and create the following data values for each company: Counter data value: This will be used to store the current car count for each company, take note of the database ID for Counter data value.   Setpoint data value: This will allow the operator to define the maximum number of parking areas assigned for each company. Ensure that the Preset Power Up and Preset Value options are selected.   Assign these data values to variables, which allow data values to be monitored via a floor plan or status page. Navigate to Automation |Variables and create one variable for each Data Value record.  Enable area counting:  Navigate to Programming | Areas and select the relevant area to enable area counting in.  Select the Options 1 tab.  In the Reporting Options section, enable the Enable User Counting option.  Click Save. Set The Max User Count to define the maximum number of users that the system will allow to occupy an area. Navigate to Programming | Areas and select the area to configure. Select the Configuration tab. In the Setup section, enter the maximum area occupancy in the Max User Count field. Click Save. Important: The Max User Count cannot be left at zero for area counting. If occupancy restriction is not required, an unrealistically high value should be set to implement area counting without restricting access. The CountOnAccess function needs to be defined for the parking area, using the counter data values that will record the count and the access levels that will determine which users will be counted. Navigate to Programming | Areas and select the area to be configured. Select the Configuration tab. Scroll down and enter the following command into the Commands field: CountOnAccess=W[X,Y,Z]where:  W refers to the Database ID of the relevant Counter data value and,  X, Y, Z refer to the Database IDs of the included access levels Up to 16 comma-separated access levels can be included in each command. Up to four commands can be applied to each area. Each command must begin on a new line. Virtual outputs are required for the system to be used on the programmable functions. The number of virtual outputs depends on the number of companies.  Navigate Expanders | Output Expanders and add a new output expander (16 outputs). Ensure that the Virtual Module option is selected, and the module address is set to a high number (e.g. 32). Navigate to Programming | Outputs and assign appropriate names to the new virtual outputs, as below screenshot.                                                         One programmable function for each company is required to compare the current car count with a setpoint.  Navigate to Automation | Programmable Functions and create one function for each company with the following settings; Type: Value Compare. Out to Enable This Function: Function Enable (This is optional, Function will operate only when the enabled output is on. Output can be controlled manually or linked to a time schedule if required. If no enabled output is set the value compare function will run continuously.). Activate Output when Below Set Point: Company X Under the Limit. Analog Input Data Variable Register: Company X Data counter. Set Point Data Value: Company X Data Setpoint. Where X is the company number. One Schedule is required for each company to enable or disable access based on programmable function output. Navigate to Sites | Schedules and create one Schedule for each company that is always valid (i.e. from 00:00 to 00:00, for all days of the week and ignoring holidays). Select the Options tab and select a Qualify Output: the schedule should be valid when the Company X under the limit output is On.  Navigate to Users | Access Levels, in the Configuration tab of each company access level assign the relevant schedule in the Operating Schedule field, or in the Doors tab you can apply the Schedule to specific doors, ex. park gate. Create Status Page or Floor Plan to monitor the system. In the example below, the user from the company will not be allowed access because his company has used all assigned parking slots.   

Issue If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Product Support personnel may ask to see a copy of the Windows Event Log. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, EcoStruxure Building Expert, Access Expert, Security Expert Environment Windows Operating System Cause If an application hangs or crashes, Windows systems are sluggish or have problems, or new software fails to install properly one of the first places to look for information on what may be happening is the Windows Event Log. Resolution   Open the Event viewer by one of the ways below: Start Event Viewer by pressing Windows key + R to open the Run dialog box and type eventvwr. Right-Click on "This PC" and select "Manage" then navigate to Computer Management (Local) > System Tools > Event Viewer. Select the type of logs the need to be exported. Application, Security, and System logs in the Windows Logs and Schneider Electric Security Expert logs under Applications and Services Logs (for Security Expert cases) are required.  For each log, view recent messages then click the "Action" menu and select "Save All Events As". Enter the log name, include the log type (Application, Security, or System) in the log name, and location the click "Save". For non-English Windows, make sure to select English (United States) in "Display information" then click OK. 

Issue Data Sync Service won't run after installation Product Line EcoStruxure Security Expert Environment Security Expert Server Cause Mismatch in authentication type during the installation of Security Expert Server and Security Expert Soap Service Resolution First completely uninstall the Security Expert Soap Service and Security Expert Server... Then reinstall Security Expert Server ensuring to UNTICK the box to hide advanced database configuration options When asked about Customize WCF TCP/IP Port, make note of your selection. Please note that using TLS 1.2 is the recommended method for authentication. Then reinstall the Security Expert Soap Service matching up the authentication type used for the Security Expert Server.

Issue The WorkPlace Tech application drawing contains a hardware tag that is outlined in red and displays this error message when viewing the right-click Display Errors option for the tag Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series WorkPlace Tech Building Operation Workstation (WorkPlace Tech Editor) Microsoft Visio Cause The issue may be caused by incorrect copying and pasting of objects inside or between drawings.  An absolute cause has not been determined  Resolution Open the application in WorkPlace Tech or Editor.  Don't open the .vsd or .vsdx file in Visio alone. Enable the Developer in the Visio ribbon. File/Options/Customize Ribbon/check "Developer"  The Developer must be enabled to have the Show ShapeSheet option available  Right-click the Input object and select Show ShapeSheet In the ShapeSheet:  Step 1. Select the corrupted string for the Connection Points Step 2. Delete the string Step 3. Click the green check mark to save Unlink and Relink the connector between the previously corrupt object, UI01 in this case, and the Analog Input object.  Note, that this could be a Binary Input object as well.  This will add the correct string to the Connection Points.