Issue Upgrading the MPMs firmware through the boot loader was unsuccessful. 10.50.80.2 is pingable, but not the default IP 10.50.80.3. The LED's keep blinking in tandem (alternating one after the other), even after having the MPM powered over 10 seconds. 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 This can be triggered by multiple events: - MPM was interrupted (powered off) while the firmware was still being upgraded. - Database does not exist; MPM was formatted and does not have firmware installed. - Database is corrupt (for any reason) Resolution It is strongly recommended that a firmware upgrade be done via the "File Manager" tab in Building Expert. However, if this is not possible, an upgrade can be performed through the bootloader using the following steps: 1 - At the top left part of the screen, make sure "Status" says "Connected". 2 - Format the SD card clicking on the "Submit" button next to "File System Format". "Format Done" will be displayed next to the button once the format has been completed 3 - Click on the "Browse" button and Navigate to the Firmware_update_V2.XX.bp" on your computer then click on "Submit Query". 4 - The previous step will upload the firmware file to the MPM's SD card. Once the file has been transferred, the following message will appear: or 5 - The MPM Must be kept powered-up for at least 15 minutes in order to allow the MPM some time to unpack the firmware file. The best way to determine whether the MPM is back online is to ping its IP address using a "Command Prompt" window. 6 - Once the MPM replies to the ping, Building Expert can be accessible though 10.50.80.3   If the above solution does not work; meaning that every time a new firmware is pushed to the MPM, the MPM keeps coming back to the bootloader, contact technical support

Issue When Vista Server is started the startup process just hangs. Product Line TAC Vista Environment Vista Server 5.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 There can be several causes for this issue. A common issue with this situation is the Vista database has been restored from site without the Lonworks NL220 or LonMaker database. When the Vista server is opened it is unable to contact the Lonworks database and repeated attempts cause the server to hang. Resolution It is possible to prevent the Vista server communications as well as other parts of the Vista server communication. Reference TAC Vista dll Manager to download a tool from the Community that will allow you to disable DLL files and find the cause of the issue. If you are seeing the scenario as stated in the above cause, you would disable Option "10: Network communication" and "11: Field bus communication" in this tool then select the Update button   You must remember to enable the options once you have finished with the site database. If you forget to do this the Vista server will not function correctly when you want to run a live database.

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 There is no clear guidance on how to handle the SNMP settings for TAC Xenta Servers Product Line TAC Vista Environment TAC Xenta Server TAC XBuilder SNMP 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 Previously the SNMP feature has not been widely used and has not been a security concern. There are two types or flavors of SNMP. One is for browsing a device to get information about it (SNMP Agent), and the other is to automatically send alarms from a given device to a central alarm system (SNMP Alarm Trap). Now according to reports from the field, IT departments are starting to get concerned about the SNMP feature in Xenta Servers. A general overview of how SNMP can be used maliciously for intrusion can be studied here. Normally the IT department requests that: The default community string is changed SNMP is disabled Here is an example of what you see when you browse a Xenta Server (having the correct Xenta Server mib file) using a SNMP browser such as "MIB Browser" from iReasoning Here is an example of alarms received from a Xenta Server via SNMP Resolution All (or most) SNMP settings are changed through TAC XBuilder First step is to change the default community name. If the community name is either "private" or "public" (the latter is default), it can be browsed without knowing the name. You simply change the name in "Community Name" and "Trap Community Name". Download all project files to the Xenta Server afterwards. Now when you try to browse the Xenta Server from the SNMP agent without first defining the community name, you will not be able to retrieve data. Next, we can disable the SNMP Alarm Trap. Download all project files to the Xenta Server afterwards. After that, alarms will not be sent to the IP address configured. Following here are advanced steps to change the ports used for SNMP (161 and 162) If the settings described above are not enough, we can change the port number used for SNMP. This is however a little more complicated. You need to connect to the Xenta Server using FTP (Note that the FTP access may be disabled, refer to Disable FTP in the Xenta 5/7/9xx Controllers if unsure how to enable this), and fetch the following file: /sys/system/snmp.cfg Open the file in Notepad Change the two port number as below - you can choose other port numbers, but it is crucial that they are not the same as any other ports used by the Xenta Server. Upload the changed file to the same location on the Xenta Server Download the project from TAC XBuilder, choosing to download all files You now get this message Here you must click "Target system" or the changed settings are overwritten Note that the port numbers defined in XBuilder have not changed yet Save the project and close XBuilder Open the project again You will now see that the port numbers have the value you defined in the file earlier Now when you try browsing the Xenta Server with a SNMP tool, you can no longer connect on the default port 161

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 UNC-520 heartbeat LED had no activity but the UNC appears to be running without issues.  Environment I/A Series Universal Network Controller - UNC-520 Warning Cause The UNC CPU idle is at 0% which resulted in the UNC heartbeat LED not having any activity (always off).  In this case,  this is caused by changing the ControlEngineService executionFrequencies to faster values and objects' executionParameters frequency set to faster or fastest. The station is using large amount of CPU resources.  Resolution To correct this make the following adjustments:  In the ControlEngineService properties, Config tab, change the executionFrequencies back to the default values of fastest at 500ms, faster at 1s, normal at 2s and slower at 5s.    Change the objects' executionParameters frequencies back to the default setting of normal. You can used the AdminTool object to perform a search and replace and changed all the executionParameters frequencies to normal.  There may be a need to change these values from the default values to optimize the UNC performance. Refer to the Niagara Capacities Engineering Notes for details. You should contact Product Support if you are unsure of these settings. 

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 I/NET SQL database becomes too big affecting the performance of I/NET. Backup and restore of the I/NET SQL database take several hours to finish. Product Line TAC INET Environment I/NET SQL 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 There are two files for the SQL database for I/NET: InetDb.mdf and InetDb_log.ldf. The InetDb.mdf file is the data files of the database, where all of the tables, indexes (other than full-text catalogs), stored procedures, etc. are stored. The .mdf is the primary data file for the whole database. While The InetDb_log.ldf is the transaction log. The transaction log is where all transactions are written to. Sometimes it will be the InetDb_log.ldf growing too big. Since it is less important, it can be shrunk without any impact on I/NET operation or any data/events/transactions lost. Resolution Be sure to backup the database first with DBCreate or Microsoft SQL Server Management Studio Open the Microsoft SQL Server Management Studio and connect to the database. Right click on InetDb and choose Property. Set Recovery model to Simple in the Options. Right click on InetDb and choose Tasks-->Shrink-->Files. Choose the File type to Log, and keep the Shrink action in Release unused space. Check the file size of InetDb_log.ldf. It should have decreased in size.

Issue How are the pull down lists populated in the Personnel Manager for fields such as Department, Hair Color etc? How to edit/remove entries from those lists. In the screen shot below the site has changed the name of a department from 'Technical Support' to 'Product Support', how to go about removing the old department name from the list. Product Line Andover Continuum Environment Continuum Cyberstation Microsoft SQL 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 Documentation Resolution The 'Department List' is populated from the department column of the Personnel table, the Personnel Manager walks the column and adds to the list any department name string that is not already present on the list. Since the list is dynamically populated from that database, to remove an entry from the list, all instances of personnel objects that have been assigned to that department must be changed until no personnel object remains with a department string equal to the string that we want removed from the list. In cases where only a few personnel objects are assigned to the department string to be removed, we can manually edit those personnel objects and change the department. In many cases the manual approach is not practical due to a large number of personnel objects that will need to be manually modified, in such cases the change can be made directly in the SQL database using the following query. ***** MAKE SURE TO HAVE A FRESH BACKUP OF THE DATABASE BEFORE MAKING ANY CHANGES DIRECTLY IN SQL **** update personnel set department = 'Product Support' where department = 'Technical Support'--------------------------> To rename an entry on the list. update personnel set department = NULL where department = 'ISIS'------------------------------------------------------------> To remove an entry on the list. Note the all personnel assigned to ISIS department will now have a BLANK department

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

Issue Issues upgrading Automation Servers (AS, AS-B, AS-P) connected to an Enterprise Server (ES) from versions prior to 2.0.x to a version that is 2.0.x. ES and one Automation Server will upgrade but no others connected to that same ES will upgrade and will show an error while attempting to download the new software.  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server v1.9.x Building Operation Enterprise Server v1.9.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 for assistance. Cause If the Automation Servers within the ES environment are not uniquely named, and/or are the same name as the ES, an error will be received if upgrade is attempted stating "Deploy upgraded database failed". Resolution As found within the Enterprise Central section of the 2.0 Release Notes, "All servers must have unique names".   *NOTE* Renaming the Automation Server will break any paths to that Automation Server, as such they will need to be corrected.   Follow these steps to address this issue: Prior to upgrading any devices within the environment, check for and find any servers with non-unique names Detach the Automation Server (with the naming identical to the ES or any other server) from the ES Rename the Automation Server with a unique name Correct any binding path issues Reconnect Automation Server to the ES Upgrade the environment to 2.0.x

Issue Integrating MNL-VAV controllers into the EBO system successfully Product Line EcoStruxure Building Operations, TAC IA Series Environment Building Operation Automation Server Building Operation Automation Server Premium I/A Series MNL VAV 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 Lost flow balancing values during integration Lost S-link offset calibrations Resolution Use the following steps to bring a controller into the Automation Server with all data intact. Using WorkStation connected to the AS/AS-P; right click on the LonWorks Network and select New then Device. Choose the appropriate device object type from the list for the MNL-VAV controller being added, give it a name and click Next. Type in the Neuron ID or use the Service pin method to identify the controller. Check the box next to “Commission” and the radio button next to “Keep current configuration in the device” and click “Create” then click “Close” when complete. Right-click on the new device object in the tree and select MNL and then “Backup flow balance information”. When this is complete notice the blue circle with a white checkmark next to the nciHighFlowCal and nciLowFlowCal SNVT’s indicating the AS-P DB contains the balance data from the controller. If special S-link offset values exist in the controller right click on the device object in the tree and select MNL and then “Backup S-link offsets”. Right-click on the controller device object and select MNL and “Assign application” and click on the appropriate application file for this controller and click on “Assign”. Right-click on the controller and select MNL and “Download application”. Click on “Close” when complete. Right-click on the controller and select MNL and “Restore the flow balance information” Right-click on the controller and select MNL the “Restore S-link offsets”. Verify all data is correct and the controller is functioning properly.

Issue Require details on how to migrate Users from an SP-C-WEB to Security Expert. Product Line Security Expert Environment SP-C-WEB Security Expert 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 Have a site that has outgrown it's SP-C-WEB installation and is upgrading to Security Expert to expand. Resolution Door configuration and programming cannot be migrated from an SP-C-WEB installation to Security Expert, but the User database can be exported to a CSV file and then imported into Security Expert to help with the migration. Exporting User database from SP-C-WEB to CSV file From the SP-C-WEB user interface navigate to Users | User Search. In the User Search page on the top right (under date) is the Export button. Clicking the Export button will generate a .csv file of all User details. (See attached example Exported Users.zip) Editing User CSV file for importing into Security Expert The Security Expert User import requires the CSV file to be in a specific format: FirstName,LastName,FullName,Facility,Card,PIN,AccessLevel The rules for this format are that: Each field must have a value however the firstname/lastname can be omitted if the fullname is used and vice versa. The facility can be omitted if it is prepended to the card number and separated with a colon (eg 123:4567). If a matching Access Level is not found, a new access level is created. The PIN and Card must be unique for each user. The file cannot contain a header row. Some examples of correctly formatted data are: Joe, Stanley,Joe Stanley,123,4587,1418,Warehouse Staff Georgia, Smith,,123,4654,6884,Warehouse Staff ,,Billy Randall,123,4727,3492,Warehouse Staff Frank,Powell,,,123:4639,3160,Warehouse Staff Importing Users from a CSV File into Security Expert In the Security Expert Client navigate to Sites | Import Users to launch the Import Users Wizard. Browse to and select the CSV File you wish to import the users from, then click OK. Figure 1 - User Import DialogFigure 1 - User Import Dialog The Users records are created and a message is displayed to indicate the action was successful.

Issue When you attempt to save a Menta application in Workstation you will get an "Invalid Data" Error. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Menta Editor 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 Some public variable in the Menta application has had Initial bindings added that conflict with the EBO bindings. Resolution Remove the Initial bindings from the variables in the Menta application and use EBO bindings. To find these Initial bindings follow these steps, Edit the Menta device with the issue From the File Menu "export" the Menta application to a known location on the PC and save it as a MTA file. Browse to this MTA file you exported and open this file with the Menta Editor From the File menu select "Save as" option. Give the file a name and in the Save as Type select FDB (*.AUT) Using Note Pad++ edit the AUT file you just created. Search the AUT file for the label "InitialBindings" [see Figure1 below] Make a note of the objects with Initial bindings so the initial bindings can be deleted from the Menta file. In Workstation edit the Menta device and remove the initial bindings from the objects found in step 7 and change the name of the object noting the original name down. Save the Menta application to the server. In Workstation edit the same Menta device and rename the object back to the noted name in step 8. Save the Menta application.