Building Automation Knowledge Base

Issue The LNS credits and the NL220 credits quantities do not match Product Line TAC Vista Environment NL-220 Cause Some LNS credits have been consumed while another NL220 dongle was used on the system. When you commission a device, both a NL credit and a LNS credit are consumed. When using another dongle on a given computer, (likely in “move” mode) it will consume a NL credits from it and a LNS credit from the computer. This can bee seen from the NL220 information bar. Resolution If the LNS credits are inferior, this means you are running in deficit. To fix this, you should order additional LNS credits to level up their quantity. When we deliver you credits, we send at the same time NL and LNS. This is why the dongle has to be confirmed on the computer when ordering credits and also why we highly recommend to commission devices only when the dongle is confirmed. Ordering more LNS credits is a link on how to order LNS credits.

Issue NM24-SR is obsolete and needs be replaced. Environment   8760020000 NM24-SR  8751019000 MD10A-24 Cause Obsolete product needs replacement. Resolution   NM24-SR (8760020000) is replaced by the MD10A-24 (8751019000)

Issue ACX7xx (ACX701, ACX781) swipe of card that is not in DB results in reader LED blinking slowly for over a minute. Then an access events 'No response from access server' is logged in the access event log. Product Line Andover Continuum Environment CyberStation ACX701 ACX781 Cause AccessServer system variable set to an incorrect value. For example, a value of 1 will cause the ACX to attempt a remote validation to the controller with ACCNetId of 1, whether it exists or not. Resolution Set the AccessServer to 0 (zero) if not remote validation is desired, or set it to the ID of the Primary Access Server workstation. NOTE: The old ACXs require a reset when the value of AccessServer is changed. After making the changes reload the controller.

Issue How to display custom text and properties of an alarm in the email notification. Product Line EcoStruxure Building Operation Environment Email Notification Substitution Codes Cause There may be certain situations where a specific property of the monitored value needs to listed in the alarm email that is sent out. For example when an alarm is triggered, the value at the time the alarm state changed my need to be documented in the notification email. These are called substitution codes. Resolution The properties of the Email Notification can be set to customize the message that is sent out when an alarm changes states. As seen in the properties window of the Email Notification above, the "Subject" and "Text" can be changed to say whatever is desired. There are special codes that can also be entered into these fields to pull actual properties from the value that went into alarm. Below is a table that lists all of the Codes for the different value properties. This same information can also be found on the EcoStruxure Building Operation WebHelp. Substitution Codes for Notifications Code Description @(AcknowledgedBy) Writes the user that acknowledged the alarm. @(AcknowledgeTime) Writes the time the alarm was acknowledged. @(AckRequired) Writes an indicator if the BACnet alarm requires acknowledgement. @(AlarmState) Writes the present state of the alarm. @(AlarmText) Writes the alarm messages that is added to the alarm. @(AssignedID) Writes the unique ID of the user the alarm is assigned to. @(​AssignedState) Writes the current assigned state the alarm is in. The possible values are Unassigned, Assigned, and Accepted. @(​AssignedTo) Writes the name of the user or group that the alarm is assigned to. @(​AssignedToDomain) Writes the domain of the user or group that the alarm is assigned to. @(BACnetEventType) Writes the BACnet event type for this alarm. @(BACnetNotificationType) Writes whether the BACnet notification was an alarm or event. @(BasicEvaluationState) Writes if the alarm is active or not. @(Category) Writes the category name of the alarm. @(CommandValue) Writes the value which was commanded for a BACnet command failure alarm. @(ConfirmedNotification) Writes an indication whether a BACnet notification was issued as a confirmed or unconfirmed BACnet message. @(Count) Writes the number of times the alarm has toggled between the alarm and reset states. @(Deadband) Writes the value of the deadband used for limit checking for BACnet out of range alarms. @(DeviceName) Writes the name of the I/NET device that generated the event. @(​DisabledCause) Writes the cause of the alarm being disabled. An alarm can be disabled by User, Shunt variable, and System. If the alarm isn't configured correctly it can be disabled by System. @(ErrorLimit) Writes the difference limit that was exceeded for BACnet floating limit alarms. @(EvaluationState) Writes the present evaluation state of the alarm. For example, Upper limit alarm is displayed when the monitored value reaches the upper alarm limit. @(EventFromState) Writes the event state of the object prior to the occurrence of the alarm condition for BACnet alarms. @(CWSid) Writes the EcoStruxure Web Service identification of the alarm on the external system. @(CWSSourceId) Writes the EcoStruxure Web Service identification of the external object that generated the alarm. @(ExceededLimit) Writes the value of the limit that was exceeded for BACnet out of range alarms. @(ExceedingValue) Writes the value that exceeded a limit for BACnet out of range alarms. @(FeedbackValue) Writes the value that differs from the commanded value for a BACnet command failure alarm. @(FirstName) Writes the first name of the individual whose key/card was used at the I/NET door point. @(Hidden) Writes the visible status of an object. False is displayed when the object is shown. @(IndivNdx) Writes the individual number of the individual whose key/card was used at the I/NET door point. @(LastName) Writes the last name of the individual whose key/card was used at the I/NET door point. @(Logging) Writes whether the alarm should be logged or not. @(MessageText) Writes the text of an I/NET action or dispatch message, if there is one. @(MonitoredObject->DESCR) Writes the description property of the monitored object. @(MonitoredObject->NAME) Writes the name property of the monitored object. @(MonitoredObject->NOTE1) Writes the note 1 property of the monitored object. @(MonitoredObject->NOTE2) Writes the note 2 property of the monitored object. @(MonitoredObject->LabelText) Writes the label text of the monitored object. This requires that a MonitoredVariable is configured. @(MonitoredValue) Writes the value depending on the alarm states selected under 'Notify on transition to'. @(​MonitoredVariable) Writes the path of the monitored variable. @(NewMode) Writes the new mode of the monitored object for a BACnet change of value alarm. @(NewState) Writes the new state of the monitored object for a BACnet change of state or change of life safety alarm. @(NewValue) Writes the new value of the monitored property for a BACnet change of value alarm. @(NotificationClass) Writes the distribution information of an alarm notification within a BACnet system. @(OperationExpected) Writes the next operation requested by the monitored object for a BACnet change of life safety alarm. @(OriginalAlarmText) Writes the alarm text from the matched alarm. This substitution code is only available for Alarm Decorators. @(PossibleOperatorActions) Writes the possible actions one can perform on the record, given permissions. @(PreviousAlarmState) Writes the previous alarm state. @(Priority) Writes the current priority level of the alarm state. @(ProcessId) Writes the process identifier configured by the notification for a BACnet alarm. @(ReferencedBitString) Writes the new value of the monitored bitstring property for a BACnet change of bitstring alarm. @ (Report) Writes the name of the report connected to the notification. @(SEQNO) Writes the sequence number of the record. @(SetpointValue) Writes the value of the setpoint when the alarm condition occurred for a BACnet floating limit alarm. @(​Source) Writes the path of the source object. @(SourceName) Writes the name of the source object that generated the alarm. @(SourceObject->DESCR) Writes the description property of the source object. @(SourceObject->NAME) Writes the name property of the source object. @(SourceObject->NOTE1) Writes the note 1 property of the monitored object. @(SourceObject->NOTE2) Writes the note 2 object of the monitored object. @(​SourceServer) Writes the path to the server where the source object is located. @(StatusFlags) Writes the status flag of the object. @(SystemAlarmId) Writes the alarm ID generated by the system. @(TenantNdx) Writes the tenant number of the individual whose key/card was used at the I/NET door point. @(TimeStamp) Writes the time and date when the event was generated. @(TriggeredTimestamp) Writes the time and date of the last state transfer from normal state to alarm state. @(TYPE) Writes the record type.

Issue Getting an Error 1001 near the end of the EcoStruxure WebReports Installation Reports not functional from WebReports Product Line EcoStruxure Building Operation Environment Web Reports SQL 2008 R2 Windows Server 2008 Windows Server 2012 Cause This error is caused when the WebReports installer is unable to reach SQL Server Reporting Services to configure the WebReports Interface Resolution After a failed install of WebReports you will need to follow the general workflow:   Clean of the Pieces of the failed install. Use the uninstall process listed in the WebReports Reference Guide or Uninstall Process for Web Reports. Correct all possible causes of the failed install Verify that you can connect to the ES using http from the Reports Server PC Verify that you can connect to http://localhost/Reports_SQLInstanceName  Re-install WebReports. NOTE: You may be able to correct the issue without having to remove and re-install WebReports. Possible Issue: The Microsoft Reporting Service SQL databases are not registered Check through SQL Management Studio that the 2 databases "ReportServer$instance" and "ReportServer$instanceTempDB" are registered. If not, the SBO Web Reports installed have nowhere to place the report pack files. If they are not there, you need to add them through "Reporting Services Configuration Manager". Click "Database" and then "Change Database". Here you can chose to create new databases. Possible Issue: Insufficient User Access Log out of Windows and Log back in using a PC admin account. The account logged in for the installation should have full access to Windows and be a DB admin in the SQL Server. Set the User Account Control Settings to Never notify. Possible Issue: PC Configured as a Domain Server In the Server Manager, check that the IIS Role is configured and that there are no Domain Roles assigned to this PC Possible Issue: Another Application is using a Required SQL function Uninstall any application which use SQL on this PC. (The Enterprise Server does not Use SQL) As a Best Practice, the Reports Server should be installed on its own, dedicated PC. Possible Issue: Incorrect Version of SQL Server or Windows Server Check the Reports Server Specification Sheet for your build and verify that you are on the Correct Version of Windows and SQL. Possible Issue: Secure Connection Level set too high This issue typically also results in not being able to log into http://localhost/Reports_SQLExpress. Log into the Reporting Agent Configuration Manager Application Click on the Report Manager URL on the left-hand column Click on the HTTP URL This will give you the correct URL for your installation of SQL If this fails, browse to C:\ProgramFiles\Microsoft SQL Server\MSRS10_50.SQLEXPRESS\Reporting Services\ReportServer (this may vary based on SQL Installation)   Modify the CONFIG file "rsreportserver" Change the Secure ConnectionLevel to "0" Save the file and attempt to log into http://localhost/Reports_SQLExpress again. For more details on this property see: http://technet.microsoft.com/en-us/library/aa179559(v=sql.80).aspx Possible Issue: .NET Framework is not operating correctly. Download the correct version of .NET framework for your version of EBO (The correct required version can be found on WebHelp Reports Server under EcoStruxure Building Operation Software Requirements) Run the installer in "Repair" mode Possible Issue: The Windows account "appuser" is not created because the default password does not meet password policy requirements Temporarily disable password policy on the server and try reinstalling. For clarification of the use of 'appuser', refer to the following article, Report Server "appuser" clarification 

Issue Additional information for creating Lonworks networks in ES, not covered by the StruxureWare Technical Guide. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 SP1 Cause Additional information for creating Lonworks networks in ES, not covered by the StruxureWare Technical Guide. Resolution Setup of the NIC852 network interface for the ES is covered in the StruxureWare Building Operation Technical Reference Guide, chapter 37.9 L-IP router setup is covered in the StruxureWare Building Operation Technical Reference Guide, chapter 37.10   Here are some additional points not covered in the Reference Guide: To use the NIC852 as a network interface for the ES, you must configure the Loytec LConfig software to run as a service.  See Not able to get Service pin from LON devices connected with Loytec NIC from ES for more details. The L-IPs must be used in Smart Switch mode in StruxureWare.  There are two Smart Switch modes: 1.  Smart Switch Mode 2.  Smart Switch mode with No Subnet Broadcast Flooding. Only use the first of these modes.  This should be the default, out of the box.  See the L-IP User Manual for details of the DIP switch positions for each mode. The ES version 1.3 can host up to 100 Xenta devices + 100 LON devices in total. These can be divided across 5 logical networks (different domains). It is possible to have multiple L-IPs in the same network if needed - but the limit of 100+100 is per ES, not per network or L-IP. Loytec recommend that in Smart Switch mode an IP channel should have no more than 10 L-IPs and packet rates no more than 500 packets/s. If additional Xenta/LON devices are needed you can add them to one or more AS, below the ES. Observe the standard Lonworks guidelines when creating your network topology e.g. maximum number of devices per network segment, maximum length of runs for the chosen cable type.  Group your devices so that network traffic across channels is minimized. StruxureWare is unaware of your physical network topology - it just sees it as one big channel.  It will reserve a different subnet for each Xenta group you create, starting at subnet 253, but each Lonworks device you create will just be assigned the next available subnet/node address, starting at subnet 254 node 1.  This means that devices with the same subnet address will most likely appear on multiple physical channels. The Loytec L-IP in Smart Switch Mode can still provide effective routing in this situation as it builds its routing table based on the physical location of subnet/node addresses, not just subnets.  Other manufacturers' routers, even in learning mode, may not be so forgiving.

Issue Archiving and database size with FIFO not working Product Line TAC INET Environment I/NET site Cause dbo.Events keeps growing and presumably is not in FIFO mode (First In First Out) Resolution Note: Autogrowth is not used with TAC I/NET Seven or TAC Andover Continuum The size of the InetDB can be set through Microsoft SQL Server Management Tool:   By selecting the InetDB database properties you can set the Autogrowth setting via the Files page.  Under the Autogrowth column select the browse button as shown:   The Change Autogrowth setting by either disabling the Autogrowth check box or you can set Autogrowth to a Maximum File Size as shown:     The Autogrowth value now shows this setting is restricted to setting define in step 2.   Disabling Autogrowth allows the events to be removed from the table when the total size of the SQL database reaches the limitation set in the properties of the db. The table dbo.Events has all the current events and it should be the biggest. The dbo.currenteventdetail table keeps up with the current max events and the current minimum events. Lets say it is around a million (1,000,000) events and so the first event in this table would be 01 and the last would be the 1000000. If items are removed from the other table, the dbo.Events, then this other table, the dbo.currenteventdetails is off. This means we run the risk of losing those events that are not correctly numbered. Manually removing items from one table can have an impact on other tables and how this data is kept and archived. About archiving and shrinking the db, this is a function of SQL. SQL goes into a FIFO mode, which means First In, First Out. This keeps the db from getting to large. The archived records are designated as archived in the db and even though they are still (secretly) in the db, they will be out as soon as the db is over the capacity amount and the amount designated in the db.currenteventdetail table is the guide for what is current. The thing that keeps the db from getting to large is the archive is setup correctly and old data is archived. It is still available via Reports, but considered not technically in the db. That is what shrinks the db and keeps it from getting over size.    Note: Autogrowth is not used with TAC I/NET Seven or TAC Andover Continuum

Issue Modbus Register Groups feature can overcome some Modbus communication problems. It has been seen before where the Modbus controller falls offline for a few seconds then comes back online. This cycle will repeat every few seconds. When register groups are not used, there may also be issues with the amount of time it takes for a Modbus points to update. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause In a normal Modbus network, a Modbus polling device obtains data from a polled device by sending a query message to the device and then waiting for the response message that contains the requested value from the selected register. If data from another register is required, the polling device sends out a new query message and awaits the response message. This process is repeated until all subscribed points values have been read. The Modbus Register Groups are a batch read function to poll Modbus devices. Instead of reading each register individually, the batch read function reads registers in manually created groups. When all registers in a group have been read, the response message returns subscribed register values for the whole group. Register grouping provides a dramatic saving in the time taken to poll your devices. For more guidance and tips on this topic, see Section "Batch Read Function" in the EcoStruxure Building Operation Technical Reference Guide.  Note: When viewing a graphic containing Modbus values, those values will update at the same interval as their Modbus register group. Resolution When grouping Modbus points, it is important to keep in mind some of the following points. Try to ensure that as many Modbus points as possible are contained in as few groups as possible. This will reduce the overall time it takes the Enterprise Server or Automation Server to read all the subscribed points in each Modbus device. Network performance can be enhanced by choosing the method of grouping that is most suitable for each device in the Modbus network.  Network performance can be enhanced by selecting a different default poll time for each register group. Network performance can also be enhanced by grouping points that have the same or similar polls. Start with higher group poll times to ensure a stable system before reducing the poll time. Make sure to delete Modbus points out of a register group individually before deleting the group. If this is not done, it can cause system delays. See article Modbus Batch Read Multiple Registers Groups Creating a Modbus Register Group In Workstation, in the System Tree pane, right-click on a Modbus device and select New Object (1).  In the create object window select Modbus Register Group (2), provide a name and select Create (3). Now that the group has been created, existing Modbus points can be dragged and dropped into the group. New Modbus points can also be created in the group.  Right-click on the Modbus Register Group and select New Object (1).  In the create object window expand Modbus Point (2), select a point type (3), provide a name and select Create (4).

Issue Users are getting two possible errors when trying to open WebReports page Error #1 - "The Web Site URL for Reports is not configured. Please contact the administrator" Error #2 -  "The webpage cannot be found" can also be generated. Product Line EcoStruxure Building Operation Environment Web Reports Cause These Errors can occur when the link to the Reports Server is not correct.  This is usually caused by having the Enterprise Server and Report Server on the same PC It should be noted that having both the Enterprise and Report Server's on the same PC is not recommended.   The reason the Workstation can not access the Web site / Web service URL's is because the Report Manager points to the "Localhost".  When you try to use a Workstation that is not local to the Report Server it can not locate this URL, hence the error.   This issue is not seen if when installing the Report Server on a different machine to the Enterprise Server as designed. Resolution Even though the Enterprise Server is local to the Report Server if access required by any other Workstation or WebStation you must enter the IP or PC Name of the Report Server within the Report Manager's Web site URL.  In this instance changing only the Web site URL will rectify the problem but it is recommended to change both the Web site and Web Service URL settings. This will allow any remote Workstation / Browser to find the Report Server. In workstation, Browse, to the System folder Click on System>Report Manager Set the Web site URL to http://localhost/SchneiderElectric/WebReports/Login.aspx Set the Web Service URL to http://localhost/SchneiderElectric/WebReportsService If the Enterprise Server resides on a different PC than the Reports Server, change "localhost" to the Report Server computer name or IP address After making this change WebReports should display correctly:

Issue BACnet bCX MSTP network loses communication when a b-Link is added or removed Product Line Andover Continuum Environment MSTP b3 bCX4040  b-Link Cause The bCX MSTP circuitry is slightly different to the b-Link  MSTP circuitry , thus under some circumstances, other faults on the MSTP network can cause communication to change, when the network is connected via a b-Link Resolution If an MSTP network is installed correctly, then it will operate correctly at all speeds up to 76.8k (assuming all devices operated up to this speed) If the MSTP network is not stable up to 76.8k, or adding or removing a b-Link causing a loss of communication, then it is likely there is some fault on the network. (adding or removing the end of line termination resistors, is also a useful fault finding option) The bCX MSTP components are slightly different to the b-Link MSTP components, thus under some circumstances, other faults on the MSTP network can cause communication to be lost, when the network is connected via a b-Link Example This has been seen when third party variable speed drives (VSDs) were connected to a bCX MSTP network (these unit had switchable termination resistors that by default were in circuit) The communication was ok at a low speed (19200) connected directly to a bCX, but when the network was put on the secondary side of a b-Link, the communication failed. Once the termination resistors were switched out of circuit, the communication via the b-Link was fine. In the example above the VSDs were by ABB Related: How to change the Baud Rate of a field bus (Infinet or Bacnet MSTP) when there is an Infilink or B-link on the network

Issue Confusion in documentation of the output type of an STR300 temperatire transmitter Product Line Field Devices Environment STR300 series transmitter Cause The STR300 is an electronic living space transmitter that converts a measured temperature into an electric current signal. The transmitter is delivered as a complete unit, comprising a Pt100 classB sensing element and an amplifier mounted in a housing. STR300 is intended either for surface mounting on a wall or installation in a standard switch box in dry, dust free rooms.   The HVAC Sensors Catalogue incorrectly shows that the STR300 Series has an Output of 0-10V while  the datasheet correctly shows the output as 4-20ma. Resolution The STR300 has an output signal of 4 to 20 mA corresponding to a temperature range of 0-40°C

Issue Are the Infilink and B-Link interchangeable or can they be converted? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infilink 200 B-Link Cause Both units are RS-485 repeaters; is there a difference? Resolution You cannot convert from an Infilink 200 to a B-Link. They are both RS-485 repeaters, but the circuitry is slightly different to handle the electrical requirements of the BACnet MS/TP and the Infinet. You must use the correct unit for the network type you have. The multiple ports on both repeaters (Infilink and B-Link) allow you to construct a star topology configuration, but note that devices in each spoke (port on the repeater) MUST be connected in a daisy chain topology. Neither product contains any firmware that can be changed.

Issue Notifications (email or text file) are sent when an alarm is enabled by the shunt variable Environment Notifications Cause The Alarm object has 6 possible states that it can take   Normal - Idle state where the alarm monitors the variable. Alarm - When an alarm is triggered, the state of the alarm changes from the normal state to alarm state. Disabled - You can disable an alarm when the alarm is triggered by faulty reasons, the alarm toggles between the alarm state and reset state, or maintenance will trigger the alarm. A Disabled alarm can be hidden in the Alarms pane or Alarm Views. To reset the alarm, you have to show hidden alarms and then enable it. When you show disabled alarms, enabled alarms are hidden. Alarms are also disabled by using the Shunt Variable in the alarm configuration. Reset - The monitored variable has returned to a value that is within the normal condition of the alarm, but the alarm has to be acknowledged by a user before the alarm returns to normal state. Acknowledged - A user or user group has acknowledged the alarm. Fault - If a BACnet device reports values that it knows are not trustworthy, the monitoring alarm is put in fault state. The notification is triggered by transitioning to any of these states as selected in the "Notify on transition to" portion of the notification configuration This means that if you wish to receive a notification on transition to the Normal state, you can check the Normal box. However, this means that not only are notified when the alarm transitions from Alarm to Normal, but from Disabled to Normal or Fault to Normal.  Some of the scenarios may be undesirable. Resolution There are two ways an alarm can go to Normal: Alarm to normal Disable to normal In the Email notification main filter, you can choose to not get a notification from disarm but you might want to get a email about normal since you want to get a email when an alarm goes to normal. To accomplish this you need to add another filter called "Previous alarm state." (This filter does not work in releases prior to 1.3 SP1.) To add the filter Previous Alarm State: Click on the green + Check the boxes you want: Acknowledge Alarm Normal Reset Make sure Disable is not checked This means that when the previous state was disabled (shunted), a notification will not be sent.   Example1: This object will always trigger a notification on Alarm.  The notification will be triggered regardless of Previous State. If the Alarm is Disabled by a shunt, then enabled, but the Monitored Variable is still out of Range, a notification will be sent.   Example2: This object will only trigger a notification on the Transitions from Alarm to Reset, Alarm to Normal, Acknowledged to Reset or Acknowledged to Normal. This might be desirable for a user that wished to know when an object in Alarm returns to normal operation, but not know when an alarm goes from Disabled to normal operation.

Issue An Enumerated schedule created under the BACnet Interface application folder will not control a digital value (Occupancy) in a b3 controller.  Other b3 controllers are handling this with no trouble. Product Line EcoStruxure Building Operation Environment b3 Variable Connectors(variable connectors were replaced in v1.5) Schedules bindings Cause Broken variable connectors. Resolution Delete the bindings and perform a Repair References on variable connectors. The digital value responded properly once the schedule binding was re-established. NOTE Variable connectors were replaced in SBO 1.5 and therefore this article in not relevant to the current product

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 On a new installation of SmartConnector, the service is not able to start. The log shows a SQL server authenticate error. Product Line EcoStruxure Building Operation Environment SmartConnector Cause For some countries, the administrator account has been localized. (List available here: If the operating system is using one of these localized languages, the Windows administrator account may not be recognized by the SmartConnector service, https://social.technet.microsoft.com/wiki/contents/articles/13813.localized-names-for-administrator-account-in-windows.aspx ) Resolution Workaround 1:  Reinstall a non-localized version of Windows.   Workaround 2: Create a new user in the SQL database.   Workaround 3: Open Microsoft SQL Server Management Studio and connect to the SQL instance the SmartConnector will use. Using the Object Explorer menu, navigate to the logins folder: 'Machine-name > Security > Logins' Right-click on the Logins folder, and select 'New login' A window will appear, to configure the new user account. Provide a Login name: this is the log-in the SmartConnector will use. Then select 'SQL Server Authentication', fill in the password field, and type it a second time in the 'Confirm password' field. Select 'Server Roles' from the menu on the left side of the account windows. Check both 'public' and 'sysadmin' if not already checked. Move to the next page: 'User Mapping' Select 'SmartConnector.Service' row, update 'User' and 'Default Schema' with 'dbo' value. Check the 'Map' box, then in the bottom list check the 'db_owner' box. Repeat steps 10 & 11 for 'SmartConnector.User' entry. Click 'OK'  Now that the user is created Uninstall the SmartConnector and restart the machine Reinstall the SmartConnector, and select 'SQL authentication' when requested Provide the newly created login with the associated password. Complete the SmartConnector installation. Validate the service is running without error.  

Issue Create EWS between SmartStruxure and SmartStruxure Lite Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Building Operation site SmartStruxure Lite site Cause Steps to create EWS (EcoStruxure Web Service) between SmartStruxure and SmartStruxure Lite Resolution Release requirements: SmartStruxure Building Operation Release 1.3.938 and higher SmartStruxure Lite Version: Schneider Electric 2.7.0 and above Verification the Enterprise Server is running Open Building Operation Software Administrator. If Status shows Stopped, you must configure Building Operation. Otherwise, proceed to step 2. Ensure all Ports are correctly configured. Click Start Service and wait until application running shows in Path field. Click OK. Building Operation is now ready to integrate with SmartStruxure Lite The following example is using Server 1 in System Tree tab. In System Tree tab, right-click on Server 1. In newly opened window, select New. In newly opened sub window, select Interface. Click on Web Service to expand. Select EcoStruxure Web Service. In Name field, enter EcoStruxure Web Service. Click Next button. In Server field, enter IP address of Multi-purpose Manager (MPM) Controller you are connecting with. In Protocol field, ensure Communication port matches that on your server. In SOAP Endpoint field, enter ews in lower case letters. Take note that from SBO version 1.5 onwards, 'SOAP Endpoint' has been renamed to 'EWS Path'. IMPORTANT: You must enter ews in lower case letters in step 11. NOTE: If you are connecting to another StruxureWare Server, you must use an account that is in the default domain for log in credentials. Click Create button. Allow database to save completely before moving on to next step. In Server Tree tab, ensure new interface shows. You are now ready to connect your MPM Controller with Building Operation. Refer below to “Procedure - Connect MPM Controller to Building Operation." Procedure - Connect MPM Controller to Building Operation Ensure your MPM is physically connected to your workstation. In Server Tree tab, expand System folder. Expand Hardware folder. Expand EcoStruxure Web Services folder. Right-click C2G_root folder and select Host EWS Objects in sub window. Expand EcoStruxure Web Services folder. Select EcoStruxure and then select Web Services Properties Tab. Set Alarm Polling to Disabled. Procedure - View and Watch Data Points Expand CAN2GO controller. The List View tab shows all Objects available in Device. NOTE: EWS Consume in Building Operation server does not support connection over a ProxyServer.

Issue How to estimate the disk space required to accommodate a given Security Expert installation. Product Line EcoStruxure Security Expert Environment Security Expert Microsoft SQL Server Cause The Security Expert databases will grow in size depending on the configuration and logging requirements. Therefore, estimating how much a database will grow over time should be done to determine which Microsoft Database solution and hard drive requirements. Resolution The Installation Guide does have some hardware recommendations under the System Requirements section, and these should be used as a baseline for allowing appropriate database storage. 10 controllers w/ 16 modules each - 40GB More than 10 controllers w/ any number of modules each - 100GB. The configuration database (SecurityExpert) is relatively small and will typically not grow much. The events database (SecurityExpertEvents) is what logs all events and alarms, and it will grow over time, rapidly depending on what is being logged and how often. There are many variables in play from one site to another. The space required for a standard Security Expert Database is dependent on, but not exclusive to: The amount of Inputs/Outputs/Readers you have with Log Events enabled. The amount of traffic through the site. The number of Expanders and other Records. The frequency of backups and purging of events from the SecurityExpertEvents database. As a guideline, we can broadly calculate storage requirements based on the size of each event being logged. Typically this will be 564 bytes per event. If you have 2000 Events per day, here is the calculation for how many MB will be used per day: 564 B x 2000 = 1128000 B = 1.07 MB per day If those events that are being logged are alarms as well, then this total would be doubled. Another way to calculate this is to take what a typical usage requirement would be for a site or monitor a live site over a week/month to calculate the sites' average usage and extrapolate that to fit. For example, a site with 130 doors being used 8 hours a day and with door openings and closings 10 times an hour would equate to just under 1GB a month. Please note these are very rough guesses; individual sites might be busier/quieter. Performing regular SecurityExpertEvents database backups and purges will ensure that the database size does not get too large for the installation. For instructions, see the System Backups section in the Installation Guide and AN 279 Security Expert Differential Backups.

Issue Email alarms can be configured in the AS and ES and understanding that interaction is needed Environment SmartStruxure Windows 7 Windows Server 2008 Cause There is a need to know what happens when creating email alarms in the AS and ES Resolution The server (AS or ES) that has the email notification object will send the email. So if you want to be sure that the AS alarms still send emails even if the ES is offline, then you should have email notifications configured on the AS and not rely on a global email notification on the ES. If notifications are configured on both the ES and AS which triggers on the same alarm, then two emails will be sent. One when its triggered on the AS and one when the ES fetches the alarm from the AS. You may be able to manage the triggering of the AS alarm by a program that checks the online status or alarm indication of the ES being offline.

Issue When launching Security Expert after restarting the PC, a License Expired message is shown. The license is not able to be found. Product Line Security Expert Environment Security Expert Client Security Expert Licensing Cause This is a timing issue. The Security Expert services are attempting to start simultaneously as Windows components that they rely on. Resolution Change the Startup Type of the Security Expert services to use Automatic (Delayed Start), so they start after the Windows OS components. Services - Automatic Delayed   It is also possible that the Security Expert Data Service may be the only service that requires being set to a delayed startup to resolve this problem.

Issue Security Expert Smart Connector integration is working but Alarms states are not updating, the following error is appearing in Smart Connector logs:   2021-01-07 15:19:22.2621,Info,Processor,<no principal>,Validation Prompt for Security Expert Alarm Update Processor: MayNotContinue : The EwsServer was not located or the credentials you supplied were incorrect. Please verify your credentials and try again. Product Line EcoStruxure Security Expert Environment Smart Connector Cause It appears that the SOAP credential within the Security Expert Discovery Processor does not match the credential within the Security Expert Client SOAP operator credential.   This is a known issue where the credential does not update when changed/edited within the Processor Configuration of the Security Expert Discovery Processor configuration.   Resolution A workaround is to log on to your local Smart Connector portal and edit the credential value within: Setup/Processor Values/SecurityExpertSettings      Change the username and password as required here.                Then save and the new credentials should be updated.