Issue Orphan alarm exists in the Enterprise Server database and acknowledgment of the alarm does not remove the alarm. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server v. 2.0.3 or lower,  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. Cause Backup of the Building Operation database that includes historical data will include the alarm that needs to be purged. IP changes or other reasons can contribute to alarms being orphaned. Resolution Note: Version 2.0.4 and from 3.0.2 and higher there is a built-in solution called Alarms Integrity Check which can be run to verify all alarms and purge any that are no longer in the system.     In order to completely purge an alarm database, it is necessary to delete the PersistedData.dat file that stores this information in the database. Perform an ES and AS full backups Using Building Operation Software Administrator click the "Stop Service" button for the Enterprise Server. Image from Windows XP Image from Windows 7 / 10 Browse to the database path listed in the Building Operation Software Administrator tool. Windows 7/10: C:\ProgramData\Schneider Electric StruxureWare\Building Operation 2.x\Enterprise Server\db Windows XP:  C:\Documents and Settings\All Users\Application Data\Schneider Electric StruxureWare\Building Operation 1.X\Enterprise Server\db Browse to the Persistent subdirectory Move/Delete the PersistedData.dat  file Click the "Start Service" button in the Building Operation Software Administrator tool. When the Enterprise Server restarts and you log in the orphaned events will be removed and any currently present alarms will return to the Alarm window with their proper status and assignment. This process causes a re-evaluation of alarms on the ES and fetches all the alarms from each AS. This can take a few minutes and may cause some slowness in the system. Note 1: Historical perspective of previous alarms, operator actions, or other data recorded in the Event Log will be lost in this process.  

Issue Time synchronisation is often an issue on large BMS installations. A central time signal is normally required to make sure all controllers, terminals or workstations have the correct time. If there is no internet connection available then the time has to be synchronised from a central source. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC Vista Environment Sigma Continuum Vista SmartStruxure Windows XP Windows 7 Server 2003 Server 2008 R2 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. Cause No internet connection available to synchronise the system time. Resolution Important The methods below contain steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. If using Windows XP, please use the following link - http://support.microsoft.com/kb/314054 If using Server or Windows 7 OS, please use the following link - http://support.microsoft.com/kb/816042 This has been tested for Time updates to an AS by simply using the PC IP address as the primary NTP Time Server. If the firewall is turned on you also need to make sure UDP 123 is open. Please note that Windows will add a dispersion to the time that may cause issues with time synchronization, please see Automation Servers ignore time sync message sent from Windows NTP server that uses local internal clock for details.

Issue StruxureWare Building Operation Extended trend logs have an incorrect unit associated with the measured value. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3.x 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. Cause It is possible to create extended trend logs by selecting multiple trend logs and using the right click option to create extended trend logs. The software incorrectly associates all of the created trend logs with the first trend log object's associated unit even if the other trend logs in the selection use different units. Resolution The cause of the problem is resolved in a forthcoming release (1.4.0) however if the system is in the state currently additional steps must be taken. The method to resolve this problem depends on the need to maintain the existing extended trend log data or not. 1. Accept loss of data Delete the extended trend logs that have incorrect units and create each extended trend log individually and avoid multiple selections. 2. Avoid loss of data Export the trend logs in StruxureWare Workstation. Modify the export file and edit the unit value for the Extended trend log The unit will need to be validated with another export that contains an object of the correct unit type. Example of Units % - 0x200001 F - 0x280003 no unit - 0x10001 inH20 - 0x230005 ppm - 0x200002 kW - 0x3210001 Import the modified file and when it detects a naming conflict allow it to rename the Trend log with a "2" notification. Stop the data collection on the original trend logs and once the retention levels of the new trend logs meets your site requirements delete the old trend logs with the incorrect data. Please be aware this issue could impact meter reports from WebReports detailed in Energy Reports not working in 1.3 and earlier

Issue Many alarms showing up during site commissioning for controllers that were not configured properly. Some duplicate id's and controller offline alarms for controllers that are no longer online and the alarms can't be removed. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server SmartStruxure 1.3 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. Cause Alarms are orphaned in the database and are not removed once the duplicate id issue is resolved. Resolution The first thing to do is to attempt deleting the PersistedData.dat file (Purge Alarm from SmartStruxure Building Operation Database) and restarting the AS. If the orphaned alarms are still showing up then the next option is to completely clear the AS. Backup the AS, configuration only. Clear the AS and commission. Once it comes back up, restore the configuration.

Issue Alarm Control Panel items created within the Enterprise Server are not been pushed down to the Automation Server. Product Line EcoStruxure Building Operation Environment StruxureWare Buildings Operation 1.3 SP1 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. Cause There seems to be a corrupt entry in the Automation servers Resolution Log into each Automation server and remove the Lead object from the Alarm panel. Refresh the automation server and the categories are now editable. Delete all user created categories leaving the default Energy Exceptions. Delete all the Cause Notes, Action notes and Check lists. Do the same procedure on all Automation Servers. Log back into the Enterprise Server and then on each Automation server add the Lead object back into the Alarm Control Panel that was removed in step 1. The Enterprise Server will now distribute the entries to the Automation server. If this fails, ensure that all firewalls are open between the AS and the ES. You may want to use the SBO Firewall Config Tool.

Issue For various reasons, it may be necessary at times to change a b3's Device ID (Object ID) to avoid a duplicate. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server (ES) Building Operation Automation Server (AS) BACnet 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. Cause There is little or no formal documentation on steps to change the Device ID of an existing B3 controller. Resolution As seen in the screenshot below, once a b3 is added to the network, its Device ID, EBO Object ID, can not be changed.  The reason for this is that the Device ID references the device and objects contained within it.  Once the ID is changed, such references will become orphans. To successfully give the b3 a different Instance/Device ID the b3 must be deleted from the MSTP Network in the Building Operation database and recreated   Write down the b3's Serial Number, MAC Address, Model, and BACnet Name before deleting it. Right-click and Export all BACnet Objects within the b3's Application Folder to file (.xml) Delete the b3 from under the MSTP network. Re-create the b3 manually using its S/N, MAC, Model, Name, etc but enter the new Device ID Commission/Download the b3 to get the new ID to take effect Import the File (.xml) exported in step 2 back into the newly created b3's Application Folder Commission/Download the controller again Important: References to the old Device ID will no longer work and must be re-created.

Issue While upgrading a database from 1.7.1 to 1.8.1 that has already been prepared, the upgrade log states that a MAP file is missing (similar to one shown below), and the upgrade is cancelled and reports "Database upgrade failed!" MAP file is required for upgrading the type public.lon2.devicetemplates.pidxxxxxxxxxxxxxxxx but none could be found Product Line EcoStruxure Building Operation Environment Upgrade LonWorks Pre-upgrade add-on Observed in version 1.7.1 and 1.7.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. Cause At some point in a previous version of StruxureWare Building Operation, the import of a device template has gone wrong in the sense, that the XIF has been imported and parsed correctly, but stored incorrectly. That means that we have cases where the actual content of the XIF stored in the database, can either be another completely different XIF, or even in some cases just random files. The issue can be verified by performing a "Content Analysis" using the "SBO xbk Analyzer" version 1.0.9 and above. You'll get a message like this: Error in XIF file: Mismatching program ID (SBO: 90001347000604A0 - XIF: 90:00:13:47:00:06:04:3C) This means that Building Operation has a device template with PID 90:00:13:47:00:06:04:A0 but that the actual file this device template points to is 90:00:13:47:00:06:04:3C Resolution A hotfix has been produced to allow replacing the wrong XIF with the correct one. With the following procedure you can manually fix the issue if you don't have the hotfix: Firstly ensure you have run the Pre-Lonworks upgrade configuration and try the upgrade again. Check if the template is in use by searching the specific template while logged in directly to the server Once the device has been identified, proceed with the following steps: Record Neuron ID(s) - this is required since the Export Process does not retain this information. Export device(s) If you have multiple devices you can Export the folder containing these devices, it is not critical to export the devices individually. Delete device(s) remembering to keep references. Import latest XIF for device From WorkStation select: File > LonWorks > Device Template Browse in the correct XIF. Import exported device(s) in step 2 Commission device(s) Run the Pre-Lonworks upgrade configuration The database should now successfully upgrade.

Issue Deleting reports built in Reports Builder using Building Operation WebReports Environment SmartStruxure Building Operation running Reports Server and Microsoft Report Builder 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. Cause Reports built using SQL interface such as Microsoft Report Builder cannot be deleted using the Manage Reports in Building Operation WebReports Resolution Building reports on the SQL side must be deleted on the SQL side.   From the first screenshot below, you can see that when using WebReports, in the Manage Reports tab, custom reports which are made are considered System Reports and the Delete button is grayed out.  Here I have created Top Alarms Test 1 report, which has been selected. Using SQL Server Management Studio, I penetrate to the tb.ReportGroups and see the isSystemOwned is True for the report Top Alarms Test 1 The isSystemOwned is changed to False for the selected report(s) Top Alarms Test 1 Viewing WebReports, in the Manage Reports tab, the Top Alarms Test 1 report is selected and the Delete option is available.

Issue Information needed about how to change the "appuser" password used by the Report Server Agent Product Line EcoStruxure Building Operation Environment Web Reports 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. Cause There is no information available on whether the Web Reports "appuser" account password can be changed and how it's done Resolution NOTE: Refer to the following article Report Server "appuser" clarification for additional information on the appuser   The password defined for the user in the configuration file needs to match the actual password in the operating system. To change the password, do the following   Stop the WebReports Agent service Change the password defined for the "appuser" in Windows Change the password defined for the "appuser" in the WebReports Agent config file: C:\Program Files (x86)\Schneider Electric\StruxureWareReports\StruxureWare Reporting Agent\SE.WebReports.StruxureWareReportingAgent.exe.config Restart the WebReports Agent service

Issue Remove Server information shown in WorkStation drop down list Product Line EcoStruxure Building Operation Environment Building Operation WorkStation 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. Cause Building Operation WorkStation 'caches' user customization's including the server names / IP addresses that it has previously successfully logged on to. Resolution Two tools are available on the Community that can assist in this process. Refer to the details and instructions for both on the Community. SBO Reset WorkStation Login SBO WorkStation Favorites To manually delete the file containing the servers list (among other information), navigate to and delete the file. The location and file name depends on the installed version of WorkStation. Version 1.3 C:\Users\%username%\AppData\Roaming\Schneider Electric\Workstation\TAC.ClientUserProfile.bin Version 1.4 and 1.5 C:\Users\%username%\AppData\Roaming\Schneider Electric StruxureWare\Building Operation\WorkStation\TAC.ClientUserProfile.bin   Versions between 1.6 and 1.9 C:\Users\%username%\AppData\Roaming\Schneider Electric StruxureWare\Building Operation\WorkStation\SBO.ClientUserProfile.bin Version 2.0 and above When hovering over a server in the drop down list, a trash can appears at the right side that allows the server to be deleted from the list: WorkStation 2.0 and aboveWorkStation 2.0 and aboveWorkStation 2.0 and above Alternatively the path to the file is: C:\Users\%username%\AppData\Roaming\Schneider Electric EcoStruxureWare\Building Operation\WorkStation\SBO.ClientUserProfile.bin Next time you run WorkStation again, a new user profile file will be created. Note: All IP addresses will be cleared and you will lose settings such as column widths and similar user customization's.

Issue After successfully setting up KIOSK mode to automatically login in to WebStation another user wants to login through WebStation on the same PC. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebStation 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. Cause The GUEST account login URL used with KIOSK mode retains the last user logged in and the WebStation menu bars have been removed so that user cannot "logout". Any subsequent attempts to access the WebStation using the same browser result in being automatically logged in under the GUEST account. Resolution The "KIOSK" link that you create will login automatically with the GUEST account as long as the GUEST account has already been created in the ES/AS. This then must set the "last credentials" in IE for that website and any subsequent connections to that server, even to the direct login URL, result in automatically being logged in with those last credentials. One of the two options below should work to disable GUEST login depending on where your ES is located. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port while Building Operation Workstation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation Workstation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. To be prompted for a login: Disconnect the ES/AS with one of the options above. Then try to connect to the server page at "http:/localhost:444" (or your specific URL:Port). This results in a "this page can't be displayed" (or similar) message. Then start the service, or reconnect cable, and again attempt to connect to "http:/localhost:444". You should be presented with the login page. Do not try to open up the "KIOSK" URL or else this will again login with the GUEST account and you'll be back to square one. The next time you use the "KIOSK" URL it will automatically login with the GUEST account and this will again be used for subsequent logins until the above steps are repeated. Note1: This could result in loss of data while the Enterprise Server is stopped. Note2: Also see StruxureWare Building Operation Workstation Auto Login feature locked if encountering this issue with a Workstation.

Issue Some IO modules status showing as 'Blacklisted device detected" or "Address shift detected" or a system alarm is received indicating the condition. AS trace logs may show one of the following entries... 2015-08-18 17:41:02.675 [1256862784] nsp.pin.cio.IODevice Module at address 14 is reporting Internal Error Code 32 2015-08-18 17:41:02.757 [1256862784] nsp.pin.cio.IODevice Module at address 28 is reporting Internal Error Code 32 2015-08-18 17:41:02.825 [1256862784] nsp.pin.cio.IODevice Module at address 12 is reporting Internal Error Code 32 2015-08-18 17:41:02.869 [1256862784] nsp.pin.cio.IODevice Module at address 13 is reporting Internal Error Code 32 2015-08-18 17:41:02.951 [1256862784] nsp.pin.cio.IODevice Module at address 15 is reporting Internal Error Code 32   2015-06-18 10:05:13.912 [1255584832] nsp.pin.cio.CIOException Error: Bad_Address (0xb0000), module Automation_Server_Io_Bus(31), moduleCode 0, dispString "AS address is invalid", techString "nsp_servers/plugins/CentralIOPlugIn/CIO/source/IOManager.cpp line 460" 2015-06-18 10:05:20.789 [1255584832] nsp.pin.cio.IOBus IOBusServer::run: Caught CIO exception from slot 3   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server 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. Cause One or more terminal base may have to be replaced. Intermittent IO connection (typically in S-cable). Resolution Follow this document or Blacklisted Device Detected for steps to resolve the problem.

Issue Want to change the sound that is played in Workstation when an audible alarm is triggered Product Line EcoStruxure Building Operation Environment Building Operation Workstation 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. Cause Need to attach individual alarm sounds to different alarms. Resolution EBO V2.0 or higher: You can add a custom audible alarm alert to EBO, which is an audio file that is played when an alarm is triggered. Refer to: Custom Audible Alarm Alert Workflow   SBO V1.9 or lower: The alarm sound is hard coded to the file C:\Windows\Media\notify.wav, and can't be changed from Workstation. The solution is to replace the notfify.wav file with another wave file. Please be aware that if the file is deleted, Workstation will crash when an alarm triggers. To change the file, you need to take over the ownership of the file as described here. The procedure is also described below. Browse to the folder C:\Windows\Media Right click the file "notify.wav" and click "Properties" Click "Advanced" Click "Edit" Select "Administrators" and click "Save" You get the following dialog. Click "OK", and close the properties. Open the properties again, and set the "Administrators" group to have full control Now rename the "notify.wav" file, and paste the wave file you want into the Media folder and rename it to "notify.wav"

Issue No events are transferred to the Report Server SQL database. Trend logs are transferred just fine. In the report agent log you can see this message "Sequence contains no elements" Product Line EcoStruxure Building Operation Environment Report Server 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. Cause The Enterprise Server has been renamed before the Report Server has been installed or before the Report Server Agent has started collecting data. Resolution This issue will be fixed in a future version, but until that, do the following to correct the issue: The fix is split into two sections. First, a section working with the "event.db" file from the SBO database, and second a section working with the "StruxureWareReportsDB" from SQL Management Studio. "event.db" from the SBO database Download http://www.sqliteexpert.com/download.html (Just take the personal one) Stop the Enterprise Server Copy the "event.db" file to a safe location Attach the "event.db" file to "SQLite Expert Studio" Get the first event from the event.db using the following query in the "SQL" tab: SELECT SEQNO,TimeStamp,EventGUID,SourceServer FROM t_7E_2FSystem_2FEvents_2FEventLog_2FEventRecords ORDER BY SeqNo LIMIT 1; Convert the TimeStamp with this "SBO TimeStamp Converter" tool "StruxureWareReportsDB" using SQL Management Studio Write the following SQL query in SQL Management Studio, using the converted time stamp, and the Guid you found previously. INSERT INTO StruxureWareReportsDB.dbo.tbEvents (DateTimeStamp,SeqNo,OriginalSeqNo,Guid) VALUES ('2014-04-17 08:35:23.857','1','1', '380d1c4c-c60b-11e3-8ecb-b8ac6f81243c') Start the Enterprise Server again Restart the Report Agent and let it run for a while.

Issue When viewing a meter consumption report, the values shown in the report does not match the values in the extended trendlog in SmartStruxure Environment SmartStruxure 1.5 and below Web Reports 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. Cause Generally this will happen if the meter is reset and that time the last value of that meter will set a BaseValue. To calculate the total consumption of the meter we are adding the BaseValue to the offset. This means that the value shown will be the logged value + the offset. In some cases however you would want to completely reset the log and just show the same values that are represented in the extended trendlog. It has been identified, that a defect causing a trend logging a 0 after each restart triggers this reset. Request the latest hotfix for 1.5 from Product Support in order to avoid this happening in the future.   Note: This issue (Defect #26360) has been fixed in 1.6.1 release. Resolution 1. Open "SQL Management Studio" and connect to the database "StruxureWareReportsDB" 2. Locate the log you want to reset using this query: SELECT * FROM tbLoggedEntities 3. Note the ID of the log you want to reset 4. Reset the log using the following query, replacing xxxx with the ID of the log DECLARE @ID INT SET @ID = xxxx UPDATE tbLoggedEntities SET BaseValue = 0 WHERE ID = @ID UPDATE tbLogTimeValues SET FloatValue = OdometerValue WHERE ParentID = @ID ##WARNING## The above script will reset BaseValue to 0 this may impact on any previous Meter Readings.  Please contact Product Support to discuss this if you have concerns before applying this script.

Issue SQL Database is full, or the partition the SQL is installed is full Product Line EcoStruxure Building Operation Environment Building Operation Report Server 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. Cause If a site is using SQL Express 2008, the limit is 10 GB. If using the full version(s), it is unlimited. If the database or the partition where the Reports Server resides is full, here are some steps to reduce the SQL table volume and offer a short-term solution. Resolution Before continuing, make sure there is a good backup of the database. Using SQL Server Management Studio, highlight the StruxureWareReportsDB and select New Query Use the following Script in that Query: SELECT t.NAME AS TableName, s.Name AS SchemaName, p.rows AS RowCounts, SUM(a.total_pages) * 8 AS TotalSpaceKB, SUM(a.used_pages) * 8 AS UsedSpaceKB, (SUM(a.total_pages) - SUM(a.used_pages)) * 8 AS UnusedSpaceKB FROM sys.tables t INNER JOIN sys.indexes i ON t.OBJECT_ID = i.object_id INNER JOIN sys.partitions p ON i.object_id = p.OBJECT_ID AND i.index_id = p.index_id INNER JOIN sys.allocation_units a ON p.partition_id = a.container_id LEFT OUTER JOIN sys.schemas s ON t.schema_id = s.schema_id WHERE t.NAME NOT LIKE 'dt%' AND t.is_ms_shipped = 0 AND i.OBJECT_ID > 255 GROUP BY t.Name, s.Name, p.Rows ORDER BY t.Name Select Execute to run that Query as shown in the screen capture below: The Results show each of the tables and the size of those tables as shown in the screen capture below: Purely for example purposes, a script to reduce the number of Events would be delete from tbEvents where DATEDIFF(day, datetimestamp, getdate()) > 180 To gain back the space after deleting rows, right-click on StruxureWareReportsdb > Tasks > Shrink > Database

Issue Log data is not being logged into SQL. The Reports Server indicates that the database is full.   This view will be shown when logging into the WebReports interface. If this chart is not shown, the PC is not running an Express edition of SQL. Product Line EcoStruxure Building Operation Environment Reports Server 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. Cause In most instances, the data that quickly fills the SQL database are Events. Event data fills the SQL Database and prevents log data from passing to the Reports Server database. If the data has filled within a few days, this would indicate an issue, and contacting your local support is the best option here. The Process below allows the user to stop the reporting agent from passing specific information to the Reports Server. If the data files are due to the amount of data stored, then an upgrade to the Standard/Full version of SQL is recommended.   Resolution To verify that the Events table is the likely cause of the SQL filling up, there are Standard Reports in the later versions of SQL.  The below example uses SQL Server version 13.x and shows the "Disk Usage by Top Tables."   If the Standards Reports are not available, then use the following article Building Operation Reports SQL Database Full, for instructions on how to show the details for each table.     The Process below allows the user to stop the reporting agent from passing Event information to the SQL Database: Download the latest SBO Reports Agent Config tool from the community. Load the Tool onto the Reports Server PC. Stop the Reporting Agent Using the Tool Press F7 to get to the Advanced Agent Configuration Page Change the numEventRecordToRead property to 0. This will prevent future event data from being written to the Reports Server database. Press Ok Under the Maintenance tab of the tool - there are two options under Events  Delete future events, alarms, and trends  Delete events and alarms older than... Restart the Reporting Agent This will stop any further Events from being passed through to the SQL Database.  

Issue In some cases the event and trend database can grow really big although not all the space in the files is used Product Line EcoStruxure Building Operation Environment SQLite Building Operation Enterprise Server 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. Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Resolution Stop the Enterprise Server Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Select the event.db or trend.db file from the "historical" folder of the SmartStruxure database folder Execute the following command: vacuum;

Issue Require a method on how to apply individual setpoints in EBO when Users are granted access at a Security Expert  Door. Product Line EcoStruxure Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation 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. Cause An example of this would be to have room temperature setpoints, or other specific settings, be changed when specific Users are granted access to a room or area. One method on how to do this would be to create a separate Access Level and Access Level Output for each user. When the User with that Access Level is granted access the associated output will be enabled. Using the EWS integration, the states of these virtual outputs can then be monitored within EBO and action were taken when they change state. Resolution Perform the following steps to configure this: Create an Access Level for each User object. Create a virtual output for each User object. A virtual output is an output object that is not assigned to an output expanders physical outputs. You could create outputs on existing expanders above the maximum output channel that you will be using but it is recommended putting these virtual outputs on a completely different module address outside the range that will be used for any physical modules. Module address = 32 would be a recommended starting value. Steps would be: Under Programming | Outputs create three new outputs. Set Module Type to "Output (PX)" Set module address to "32" or greater. Set Module Output to "1", "2", "3", etc... Save the changes. For each of the Access Levels add the corresponding virtual output to the Access Levels Output tab. Access Level OutputsAccess Level Outputs Ensure the Access Level has access to the Door(s) in question. Set the Time to Activate (seconds) in the Access Level | General tab to something appropriate such as 5s. The output will disable after this time period. Set the Reader Access Activates Output on the Access Level. Set Activate Access Level Output on the Reader Expander | Misc Options.    

EBO doesn't support save from controller for B3s