Issue How can duplicate Handle errors be fixed? Product Line Andover Continuum Environment All versions of Continuum CX, i2 and infinet Controllers 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 An SQL database gives every object a unique handle that is used internally to reference that object. If Continuum requests a value from an Input point that has handle 1234, but that controller has handle 1234 for example as a TimeDate point, then problems will ensue. Every object in the DB has a unique handle. This includes all classes: points, programs, graphics, reports, schedules, etc. Duplicate handles can be caused on sites where engineers use multiple databases during commissioning on new panels (maybe a Single User on their laptop), It can also be caused by importing dump files with handles created from other databases, or just from database corruption on the server from failures etc. It can also be caused by the use of an Infinity LSX280 see Handle mismatch issues. Resolution Usually reloading the controller will re-sync the controller and all of its object handles back to the site database. If the DB has become corrupted, run the analyzer and try to fixup (Clean) any issues You may even have to manually delete the offending objects, running the Import Export Fixup utility (See How to run the Import/Export Fixup Utility) Follow this with a controller reload Worst case would be to revert to a backup DB if it is found to be corrupt. To avoid issues altogether, it is best to engineer a project all from a single DB and take care when importing dump files.

Issue How can I clone an MPM? How can I upload config.db to an MPM? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager 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 Unable to upload config.db to an MPM Resolution An MPM can be cloned from Building Expert by exporting default.db from one MPM and importing it to another (using the "Export Database" and "import Database" buttons) Note: Allow MPM a few minutes before attempting to access Building Expert. MPM will reboot automatically and install Database files. If it is necessary to clone the system configuration objects as well, refer to the procedure below: This procedure show you how to upload the Database to an MPM. To download a backup of the database, refer to MPM database information. Power up the MPM and ensure either its IP address can be pinged or Building Expert is accessible. In address bar of browser, enter 10.50.80.3/test.html. (assuming IP address of MPM is set to default) In Remote Path field of File Upload section, enter config.db. Click Browse and Navigate to the backup config.db file and select it. Click Submit Query. Wait for {“success”: true} to show before you proceed. Note: Uploading the config.db file first does not cause the MPM to reboot; which is why it is uploaded first On Browser, click to return to previous page. In Remote Path field of File Upload section, enter default.db. Click Browse and Navigate to the backup default.db file and select it. Click Submit Query. Wait for {“success”: true} to show before you proceed. Allow MPM a few minutes before attempting to access Building Expert. MPM will reboot automatically and install Database files. Note: MPM must not powered off during this time In address bar, enter 10.50.80.3 to connect to Building Expert and validate Database upgrade is correct.

Issue Large data base log file causes Continuum to run very slow and/or crash. Environment SU CyberStation MS SQL Express 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 When Continuum starts and attempts to connect to the DB it takes too long due to the size of the log file (14GB in the case covered by this article) Resolution Shrink the database. Go to http://technet.microsoft.com/en-us/library/ms190757.aspx for steps from Microsoft to shrink the database files.

Issue How to setup automatic table truncation on Single-User SQL Express systems. Product Line Andover Continuum Environment Continuum Cyberstation Single-User SQL Express SQL Server 2005 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 Only the ExtendedLog table is automatically truncated on an Single-User SQL Express Continuum system. The other tables that can fill up quickly and need to be truncated regularly are not catered for (accessevent, activityevent, alarmevent, and errorevent). Resolution IMPORTANT: Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and, if not already installed, where to get Management Studio from) Use the attached file SQLExpress to add table truncations.zip, to configure your Single-User SQL Express system to automatically truncate these tables when it does the ExtendedLog truncation. After downloading the file, follow the steps below. There are three files in the archive, these need to be copied to your Continuum folder on your Single-User system running SQLExpress as the database engine. LogTruncate.SQL This file is the SQL script that performs the truncation of the four tables (accessevent, activityevent, alarmevent, and errorevent) to the number of days you specify - I have selected 90 days as my default but you can change this to whatever you require for each table. CS_LogTruncate_OneOff.bat This batch file will run the LogTruncate.sql script once when manually executed. You will need to change the server name "PC3" to whatever your PC's name actually is on your system. CS_Hrly - with LogTruncat.bat This is the batch file that will be renamed and replace the existing "CS_Hrly.bat" file currently located in your Continuum folder. This is the same as your current file except it has added the LogTruncate.sql script so that this will now be executed every hour along with the rest. Backup "CS_Hrly.bat" file in Continuum folder by renaming the file to something like "CS_Hrly ORIGINAL.bat". Rename "CS_Hrly - with LogTruncat.bat" to "CS_Hrly.bat", copy into (overtop the existing file if you haven't renamed it) the Continuum folder, and change the server name "PC3" to your PC's name. This should now execute this table truncation script along with the other database maintenance scripts every hour.

Issue Is it possible to have a link on a GxPage to run an executable file to launch an external application outside of the web browser? Product Line TAC IA Series Environment I/A Series R2 graphics Firefox web browser 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 To launch an external application via a link on graphics page in a web browser. Resolution It is not possible to launch an external application from an I/A Series R2 GxPage. Two suggested workarounds are as follows. Create a hyperlink on a GxPage that links to a standard HTML web page. There would be a link to run a script on the standard HTML page to launch the external application. If the site graphics has a HTML tree created, create a new link in the tree which will run a script to launch an external application. * Take note that the HTML web page with the script link has to reside on the same computer as the external application. As an example the following script and procedure which will launch an external application in a Firefox web browser. In this case, the script will launch Windows notepad.exe. This method has been provided as a workaround but you should use and troubleshoot any information given below at your own discretion. Example of a script to launch an Notepad in Firefox: Right Click on this link and select "Save target as" to download this script as a text file We also need to configure Firefox to allow Java script to run. Run Firefox and type in 'about:Config' at the address field. Set the 'signed.applets.codebase_principle_support' to true. Be careful not to make any other changes. NOTE: This script and browser configuration may or may not work in other web browsers. Further changes may be required for this functionality in any other web browser other than Firefox.

Issue After time settings have been confirmed as per "The time on the workstation is less than the time of one or more controller log entries"., some ExtendedLog points are not being gathered. The below time synchronization errors are seen in the Errors Listview. Extended logging time synchronization problem. The time on the workstation is less than the time of one or more controller log entries. Product Line Andover Continuum Environment Continuum Cyberstation 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 Due to the incorrect time settings previously configured, the controllers may have log events that occur in the future (as far as the Workstation gathering the logs is concerned). Resolution Reload the controller that has the ExtendedLog points showing this error, this will clear out the local log entries and allow the Workstation to gather new log entries.

Issue Some objects are protected by default in Vista requiring that changes be made to the authorities of the object in order for it to be deleted. Protected database objects will be in gray text whereas unprotected objects are in black. Additionally, the Delete option when right-clicking a protected database object will be grayed out. Text on protected database objects is gray   Text on objects that are not protected are black Environment Vista 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 Even though administrators have full control to read or write any database objects, some objects are protected so that they are not accidentally deleted. An administrator must remove the protection before deleting the object. Resolution Ensure that you are logged into Vista as an administrator then perform the following steps to delete a protected database object: Right click the protected database object and select Authority. In the Authority dialog box check Change access level on subunits and Change access level on existing objects. The two check boxes for Require signature on database object change and Protected database object at the top of the dialog box will likely change from check marks to dark boxes. Click on these boxes until they are empty.   Click OK.   Refresh the window by pressing F5 or clicking the refresh button. The database object should now have black instead of gray text and can now be deleted.

Issue Procedure for converting a bCX9640 to a CX9680 (NC2) Product Line Andover Continuum Environment CyberStation bCX9640 CX9680 (NC2) 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 Documentation Resolution This article provides some guidelines for converting a bCX9640 to a CX9680 in the field. As of version 1.94 CyberStation does not automatically convert a bCX9640 to a CX9680, such conversion while complex and error prone can be done manually.   DISCLAIMER: Be aware that due to the differences between the two models not everything can be converted; certain items may have to be re-created from scratch in the new CX9680 controller. DIFFERENCES BETWEEN BCX9640 AND CX9680   Feature bCX9640 CX9680 1 System Variables 47 65 2 Comm Ports 2 4 3 IO Expansion Modules IOU Modules 4 Infinet 1 2 5 Access Control No Yes 6 UPS Support No Yes 7 Display Module Support Yes No   Procedure: Make sure you have a recent backup of the SQL ContinuumDB as a precaution. From CyberStation send the bCX including children to a text file, the dump file can be later used for reference. Take note of the bCX9640’s name, AccNetID and network settings. Put the CyberStation in offline edit mode and delete the bCX9640 then create the CX9680 using the exact Name, ACCNetId and network settings as the deleted bCX. After creating the new controller object it will come online, at this point you are still communicating with the bCX9640 hardware. In the ‘Send to Database’ options make sure to select ‘Save attached objects and controllers’ then select the new controller in the Continuum explorer and perform a ‘Sent to database’, depending on how many Infinet devices you have this make take a while. When the send to database operation has completed you are ready to remove the bCX9680 hardware and connect the CX9680 hardware. After disconnecting the bCX from the network commission the CX9680 hardware with the same AccNetID and network settings as the bCX it is replacing. When the new hardware comes online reload it from Continuum making sure you don’t reload the Infinet devices (Reload attached objects but not attached controllers)   At this point you have converted the bCX9640 to a CX9680, the next steps in the process is fixing the items that do not convert properly due to the differences between the two controllers. LCD Display Configuration If the bCX has an display module attached all configuration related to the display module must be removed as the CX9680 does not support it. Fixing IO If the bCX had IO then appropriate IOU modules must be configured in the CX9680. In some cases points may have to be moved to a different IOU. For example if you were using a xPBD4 (which has both inputs and outputs) then you’ll have to put the inputs and outputs on different IOU modules as there is not an IOU module that is the equivalent of the xPBD4. Fixing References Any references in programs/functions to objects that do not exist in the CX9680 must be manually removed/fixed. For example the CX9680 does not have some system variables supported in the bCX such as all the system variables related to the display module (ACCLCDBeeper etc) Other items that need partial or complete manual fixing include… Alarms, links will convert ok, but references to Graphics, Program, Video may be have to be re-assigned. Extended logging   Use the dump file created on step #2 for reference when manually re-entering lost configuration.   Article as a document: Procedure For Converting a bCX9640 to a CX9680

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 Active Event Viewer contents and column headers are blank.   Product Line Andover Continuum Environment CyberStation 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 Windows registry corruption. Resolution Method #1 Close Continuum and use Windows System Restore to put the system back at a point where the Event Viewer were fine. Method #2 NOTE: Any customization previously done to the event viewers such as column name changes etc  will be lost when this method is used Shut down CyberStation then backup the Windows registry as a precaution Edit the Windows registry and delete HKEY_CURRENT_USER\Software\Andover Controls\Continuum\Access Event View Start CyberStation and open the event viewer which recreates the entry in the registry using default values.

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 Access Event Viewer running in a CyberStation other than the primary access server works initially but after some period of time stops displaying access events. Product Line Andover Continuum Environment CyberStation MSMQ 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 Product support has identified several scenarios that can result in Cyberstations other than the primary not showing events in the Live Event Viewer. The commonality with all these cases is that the Primary Access Server(PAS) will always show the events, so before using any of the solutions specified below make sure that is ONLY workstations other than the PAS that are not displaying events in their Live Event Viewer   NOTE also, that we are referring strictly to the Live Event Viewer in this article so it is assumed events are showing in a list view including the Access Events tab that shows events in the door's editor.   CAUSE #1 (Primary failed over to Secondary then back to Primary) In systems configured with a Primary and secondary Access Server (SAS), it has been found that after a failover to the SAS due to the PAS going offline, event viewers in other workstations continue to show events UNTIL the PAS WS returns online and resumes its role of PAS at which point all workstations (other than the PAS) stop displaying events in their Live Event Viewers.   CAUSE #2 (MSMQ issue reported and fixed by Microsoft) Continuum running under MS Windows 7, Vista or MS Windows Server 2008 (including R2) Access event viewers at Cyberstations other than the PAS do not show events. Alarms acknowledged at one CyberStation would remain unacknowledged in the other CyberStations.  Please see MSMQ issue causes Alarms and Access Event delivery problems between CyberStations for more information.   ISSUE #3 MSMQ CleanupInterval setting is too short. Resolution SOLUTION #1 First, make sure the ControllerStatus notification object is configured to send the offline alarm to all the Workstations in question. Second, put a PE program in the SAS to serve as a monitor to let the Live Event Viewer know when the PAS has returned online, this is accomplished by referencing an object from the PAS  SAMPLE PE POGRAM SOLUTION #2  (MSMQ issue reported and fixed by Microsoft) Click MSMQ issue causes Alarms and Access Event delivery problems between CyberStations for more information.   SOLUTION #3 In the Windows registry add the key \SOFTWARE\Microsoft\MSMQ\Parameters\CleanupInterval The recommended setting is 3600000 which is the number of milliseconds in an hour   For additional information about the CleanupIntervalKey, see the following article from Microsoft: http://msdn.microsoft.com/en-us/library/ms703235(VS.85).aspx

Issue Sample programs for carpark access control. Environment Continuum Access Control Carpark Access Carspace Counting 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 Want sample code on how to provide Carpark Access Control. Resolution It is possible to do car park control with Continuum Controllers. There are a number of different ways to do this depending on the sites specific requirements. PSS doesn't provide programming for specific projects but we can provide generic examples. *** Note: This sample code is provided as-is to be used as a sample only.   *** To start off, a very simple solution could be:   To have three Areas defined, Outside, CommonCarPark, and EmployeeCarpark. You then create Door objects for the Entry Readers at the entrance to CommonCarPark and EmployeeCarpark. Use a PE Program to Monitor the CommonEntry Entry Reader for ValidAccess and set a pre-alarm flag (Numeric). Have an AlarmEnrollment attached to the pre-alarm flag and set for a specific amount of time (3 minutes). Have another PE Program that monitors the EmployeeEntry Entry Reader for ValidAccess and then re-sets the pre-alarm flag stopping the alarm from being sent. You could use this sample program, with some modifications, to provide you with this functionality. This is a very simple way of doing it that doesn't take into account having more than one car coming in at the same time though...you could expand on this to include using arrays to store the details of the Personnel that have badged and then have a timer associated with that specific Personnel, set both values into an Array and then have another program monitor that Array and compare the time they entered against the current time...if the difference was more than your alarm time then raise an alarm. When that Personnel badges at the EmployeeEntry Reader you remove their entry from the Array. A sample on how to do this is here. This one is a bit more complex than the previous example but it should give some ideas to start with to mold into a solution. There is a WS program as well as a controller program. The controller program does all of the carpark control which uses arrays to store the number of car spaces currently available for each department group (company/tenant) and allows of disallows new cars from that dept depending on available slots. This solution required both a roller door and a gate inside the roller door to create a "mantrap" for the desired control but the same principle could be applied in a simpler design. The WS program was used to provide a solution to the tenants locking themselves out of the carpark when they didn't badge out properly. It uses an object to search though all Personnel to find a specific card number and then resets that Personnel's current Area so they can badge at the anti-passback enabled Door. From memory, this part of it didn't work as well as the carpark access. The code is good just the method of searching through all Personnel was prone to locking up. Depending on the number of Personnel and size of Database it can take a longtime to do the search ... and the program can time out and go to disabled. So there was human intervention needed at various times.  

Issue Exporting data from a corrupt taclogdata database because it's no longer possible for Vista to log data to the database. Product Line TAC Vista Environment Tac Vista 5.1.X SQL 2005 or newer SQL Management Studio 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 original database is corrupt, there are no backups available and Vista is unable to write to the database. Resolution If not already installed, download and install SQL server management studio. Use a search engine to search for the appropriate version for your installation. Once installed, log on to your database instance (localhost\TACVISTA by default) and locate/select the taclogdata database in the Object explorer. Then follow the steps below: BACKUP! BACKUP! BACKUP! before starting this procedure! Create a new clean DB via Vista server setup - don't start Vista. Right click on the source DB in SQL management studio and select Tasks->Export Data. Follow the wizard and select the source and destination DBs. When you get to the "Select Source Tables and Views" stage, select the tables you want to copy. For each table selected, select the table and click on the "Edit Mappings" button. In the dialogue that appears, select "Append rows to the destination table" and check the "Enable Identity insert" check box. Click Next twice and then Finish. The data should be copied from the old database to the new. The progress can be monitored in the wizard.

Issue How to convert a NL220 database into a LonMaker database. Environment NL220 LonMaker LNS 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 are a number of steps that must be taken to convert a NL220 database to LonMaker.  Resolution Note: Before beginning this process make sure that the NL220 database has all devices underneath one root system (In this example, everything was moved into the InfraStructure root system). If this is not done, the controllers will not appear in the LonMaker Visio drawing. Make a backup of the NL220 database before doing anything else.   Create a new LonMaker database and open it up (For this example it was named NLtoLM). Note: You do not need to register any plug-ins or go OnNet at this time. Now close the LonMaker project.  Go to the location of the NL220 database and copy all of the folders and files in the database that you want to convert. In most cases you can find the database files here; C:\NLprj\PROJECT NAME. Go to the location of the LonMaker database that you just created and delete all of the files located in the project folder. In most cases it will be located here; C:\Lm\DB\PROJECT NAME. Paste the project folders and files from the NL220 database into the LonMaker database folder. Now go back to LonMaker and create the Visio drawing for the new LonMaker database. Make sure to select the project you created in the Drawing directory field and to select " " in the Drawing name field. Click Create Drawing. You may get a Database error. Click OK. The LonMaker database has now been created with the Visio drawing. The drawing may be a mess and will require additional time to move nodes around and clean up the appearance of the database. If there are subsystems in the project it will create each subsystem layer in a separate Visio drawing. In order to combine the subsystems back into one drawing follow steps 8 through 13.   On the main Visio drawing, click and drag a new subsystem to the Visio drawing. Give the new subsystem a name that is not used in the database. Go to the subsystem that you want to move and select everything on the page. Right click and go to Move Device > Change Subsystem... Navigate to the new subsystem that was created in step 8 and click OK. Repeat steps 8 through 10 for each subsystem you want to move. Go back to the main Visio drawing and delete the original subsystems that were on the page. Now the new subsystems can be renamed to the original subsystem names by right clicking and going to Properties. You now have one LonMaker Visio drawing for your entire database.

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 Workstations are no longer logging all points configured for Extended Logging. Lots of these errors seen in the Errors Listview and ACCtrace. "Unable to find Extended Log records to download. This can occur when a log is added to a point through offline editing and the change is never sent to the controller." Product Line Andover Continuum Environment Continuum Cyberstation SQL Server Management Studio 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 What has probably occurred is that in the database the point is set for extended logging but in the controller this same value is not set. It happens when the controller recovers from flash and the database stored in flash didn't have the extended log points configured or it was offline edited. This could also be due to a corrupt entry in the ExtendedLogReservation table that is stopping new points from being assigned. Resolution After the troubleshooting steps in Getting error Unable to find Extended Log records to download have been followed but were unable to resolve the problem, truncating the ExtendedLogReservation table and then rebuilding it did resolve the problem in a number of situations. Please note that this is a brute force approach that requires truncating a table using an SQL query. I want to stress that even after following the below steps to re-enable logging, each affected controller should be reloaded at some point to ensure that it has the most recent up to date information. The steps below are a quicker method of getting the logging start working right away without having to wait to reload each individual controller. The best method to disable and then re-enable the Extended Logging on the points that have it configured is to use individual Listviews filtered to show them. One of Numerics, Inputs, and Outputs. The only change required, and this is a critical one, is to change the "Live Data Refresh Rate" to 0 for each of those three Listviews. This will ensure that the view is not refreshed automatically unless we do this ourselves. See image below for details. After importing the three ListViews, follow the below steps to toggle the ExtLogEnable values for all Numerics that were currently setup to trend. Run the imported listviews, Export the results to CSV files, (do this as a backup so there is a record of what points are currently configured). Edit the listviews to disable live refresh, see attached image for exact details of what to change. [** Important **] Shut down all Cyberstations and backup the ContinuumDB. Go back and confirm that step 4 above has been done. Truncate the entire ExtendedLogReservation table and rebuild it. In SQL Management Studio, run the below query to truncate the table. truncate table ContinuumDB.dbo.ExtendedLogReservation   Start up the Cyberstation Set Workstation to Offline (workstation icon in task tray) Run each of the three Listviews, select Edit->select all, select Edit-> set attribute, set the ExtLogEnable attribute to False, Wait for the changes to take effect on all, you can see when this is done (and it may take awhile) by the tasks in the Distribution Properties window. Then select all again and set the attribute back to True, wait for this to complete. Now when you start up the Workstations you should see that the ExtendedLogReservation table gets populated and slowly start to see that some of the Workstations get assigned logs to start logging. You can see which entries are assigned to a Workstation by the value of ReservingWSLo. This will be set to 0 if no Workstation has been assigned to gather the point yet or it will assigned to the IdLo value of the Workstation that has picked it up.  

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 Under rare circumstances, resetting your Manager to its factory defaults may be necessary.  For example, if you have forgotten your Manager's IP address, or if you are experiencing login problems.  Environment SmartStruxure Lite Web Browser SmartStruxure Lite MPM 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 All SmartStruxure Lite™ Managers are equipped with a bootloader, accessible via a special IP address that lets you access several Manager firmware functions, among them, a factory reset.  Resolution WARNING: Restoring your Manager to factory settings should only be performed as a last resort; doing so will erase all its objects and devices, requiring you to reconfigure your Manager from scratch. Accessing the Bootloader As its name suggests, you access the bootloader at boot time, i.e., when you power up your Manager. To perform a factory reset: 1. Disconnect electrical power from your Manager by unplugging its power connector or unplugging its power supply from the AC outlet. 2. Ensure that your computer's TCP/IP settings are on the same subnet as the bootloader IP address:10.50.80.X.     IMPORTANT: Upon restarting your Manager, you will have only a brief interval–approximately 5 seconds–during which you will be able to access the bootloader. As such, we recommend that you perform the following steps 3.  Open your browser and type the following IP address into the address bar, but do not click the browser's Go icon or press any  key on your keyboard: 10.50.80.2 4. Reconnect your Manager's electrical power. 5. Within approximately 5 seconds, click your browser's Go icon or press the key to navigate to the  bootloader's IP address.  The bootloader screen displays.    6. In the Restore factory defaults area, click Submit. The Manager begins restoring its settings to the factory defaults. When completed, a success message displays.  7. Restart your Manager by clicking the Submit button in the Restart system area. 8. You may now log in to the Manager using its restored IP address: 10.50.80.3. If you cannot connect successfully to the bootloader using the above steps, chances are you are not navigating to the bootloader's URL within the defined 5-second window.       As an aid, some users may find it useful to do the following:      Open a command window and type the following: ping 10.50.80.2     As soon as you see a ping reply, return to your browser window and press the key to navigate to the address previously entered into the address bar.   Restoring your Manager to Factory Settings download as PDF.

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.