Building Automation Knowledge Base

Issue Archiving historical information Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Serve Workstation Cause Options for archiving historical information Resolution Archiving of historical data is available via WorkStation and Enterprise Server or WebReports Server. (Archiving is not available via Automation Server or WebStation, also the IE built in option to "Export to Microsoft Excel" has not been implemented) The Archive options on the ES are shown below. A manual archive can be forced by right clicking on "Archive Settings" and choosing "Actions" then "Create archive(s) now" NOTE1 - CSV option currently produces a Semicolon Separated Value file. NOTE2 - Individual logs can be saved to a CSV or XML file from an AS or ES within WorkStation only, see How to Export a Trend Log List as a .csv File.   The .CSV file that is used by SBO to export logs uses a semi colon to separate the fields. This makes it suitable for use in all countries around the world. Some countries use the comma to signify decimal places, so they would show a temperature of 22.5 DegC as 22,5 DegC which would confuse a CSV import with Comma delimiters. CSV files can have many delimiter characters not just commas. To show the formatted data in Microsoft Excel the following options can be used: One option is to rename the SBO log file as a .TXT file, then from Microsoft Excel, go to Open a file and select the type from the drop down list a "Text file". Browse to your log file and press Open. It will then start the Text Import Wizard. Choose the "Delimited" option and go to the next page. Here select the "Semicolon" option, select next, choose a date format and press finish. This will show the data formatted in columns as shown in the manual.   A second way to show the data is to open the .csv file in Microsoft Excel where all the data will be shown as text in the first column as per your description. Select the first column. Then go to the "Data" tab and start the "Text to Columns" Wizard. Select "Delimited" Original Data Type. Press Next. Select the "Semicolon" as the delimiter. Press Next. Change the date format if required and press Finish. This will also show the data in individual cells. Also other vendors Open Office applications may be used that unlike Microsoft Excel will allow semicolon delimited files to be opened directly.

Issue The following errors occurred in succession when trying to run LonMaker. Could not listen on poet/tcp: the address specified is already in use (-2532) Database error. (Subsystems: LNS, #25) [DB #-2506] The global database is not open. (Subsystem: LNS, #64) The following errors have also been seen to be caused by the same issue. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Error opening LCA Global database. Problem connecting with the database server process. (Subsystem:LNS, #36)[DB#-2523] Environment LonMaker for Windows 3.1 and 3.2 Sentinel Protection Installer 7.6.1 Cause Sentinel Protection Installer 7.6.1 was recently installed on the computer. This is the driver for the Satchwell Sigma dongle key. The Sentinel Protection Server is installed together with the driver. The Sentinel Protection Server is use to manage the Sentinel SuperPro and UltraPro keys attached / installed on the system. This is causing a conflict with the POET Server as it uses the same port(s). Refer to Error: LNS #25 lcaErrDatabase for details. Resolution Stop the Sentinel Protection Server in Windows Services. In Windows, go to 'Start' > 'Run' and type in 'services.msc' to bring up the Services windows. Find Sentinel Protection Server and stop the service. This is not required for the dongle driver to work. You can also disable the service

Issue Upgrading an AS results in an empty database. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 StruxureWare Building Operation 1.1.0.362 to 1.2.0.767  Cause When upgrading the database, the Enterprise Server (ES) upgrades without error, but when upgrading the AS, the result is an empty database. Resolution StruxureWare Building Operation 1.0.0.173 to 1.1.0.264 The problem is caused by the initial engineering of the system being carried out on an old AS that was not LON or BACnet specific, copying into new hardware at R1.0 then when upgraded to R1.1 the upgrade fails due to the wrong type of AS being used (LON or BACnet). This practice is not common place and rather rare. When the trace log is examined, they find that the upgrade fails due to the fact that an illegal object type is attempted to be created – a BACnet interface. This is not legal in an AS-L. The reason that this occurs is that the backup file is from an AS-L that had been restored from a 1.0 AS-B backup file. Check New Release or Upgrade StruxureWare Building Operation Site Software. The issue you face could possibly be a procedural one and this article clearly defines the steps. StruxureWare Building Operation 1.1.0.362 to 1.2.0.767 The solution is identifying problems with a period, space, or other character in names. Placing a period at the end of a name or accidentally having a space at the end is suggesting something is following or further action. If using BACnet, please see the note below. Problems with bindings which were still in tact when values were removed also are a potential issue and not properly removed.    Work Around: Backup AS Upgrade PC to 1.2 Open Device Administrator Upgrade AS to 1.2 DO NOT close Device Administrator Open StruxureWare Workstation Log into AS If Database is Blank go back to Web Browser Connect to AS Log in In the top right hand corner of the screen select Setting>Device Configuration Select the Server Log tab Click “Get all log files” Once downloaded, open “trace” using Notepad Click Edit>Find Type the word “nsp.csc.UpgradeManager ERROR:” The error lines run from date stamp to date stamp so isolate the line beginning with the year and ending with the next instance of the year. Here is an example: 2012-08-29 16:39:32.990 [32] nsp.csc.UpgradeManager ERROR:    Error Parsing Dump Objects:  RecoverableException: source/Path.cppy) ) Error: Invalid_Path (0x10001), module Coml(11), moduleCode 0, dispString "Heatsink Temp.", techString "Path& Path::Append(const UTF8String& name)"  The “dispString “_______”” section of this line will give you the object name that contains an illegal character. Downgrade the AS back to 1.1 Locate the dispString object and change the name so that it does not contain any illegal characters. This is typically a name ending in a period. NOTE: when the rename dialogue pops up, it will indicate that an illegal character is present to confirm you are modifying the right object. Backup the AS Re-Upgrade the AS to 1.2 If the upgrade fails, repeat steps 9-20 or call product support. Be prepared to provide a Db backup at 1.1 as well as the trace file from the 1.2 failed upgrade. BACnet Note: A BACnet device including an object name "East Duct Max." is no longer valid because of the illegal character at the end of the name. Before upgrading the ES from 1.1 to 1.2, remove any full stops/periods from any object names. "East Duct Max." is changed to "East Duct Max"  Other illegal characters include *°?|/"<> or ~ and an object cannot begin or end with a white space or period. Select TPA-SBO-12-0008.00 - ES upgraded from 1.1 to 1.2 loses database to review this TPA.

Issue Links not working after TGML conversion Converting I/NET graphics to TGML using the "Create Source Tree" option Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.44 Cause I/NET stored graphics on the hard disk and allowed for complex folder structures to be used in organizing those graphics. When these graphics are converted to TGML, this structure may need to be preserved in order to prevent duplicate graphic names. Resolution For this example I have created a site with 3 buildings containing Identical I/NET graphics. Each Building has a summary page and a VAV page. All pages link back to a home page. In I/NET select System>Export Graphics to TGML(you can also right click on the I/NET interface in StruxureWare Workstation) Set your Source and Destination Path and click All Yes.  When you set your destination path, it must point to a folder that already exists in Windows.  The Export INET Graphics to TGML tool does not create this directory Notice that the default setting is to "Use destination path" If we click convert with that option, we will get only 3 graphics.  The graphics from other folders with the same name are over-written. Select the "Create Source Tree" option, ensure the correct graphics are scheduled to convert and click convert. Notice that In Windows Explorer a new folder structure is created that is identical to the original folder structure. Open StruxureWare Workstation. Create a folder system that matches what is on the Hard disk. Drag and drop the TGML files from Windows explorer to the corresponding folders in StruxureWare Workstation. Test you graphic links to ensure everything is functional. Note: Once the graphics are imported, StruxureWare will allow you to move them freely without breaking the binding between pages. There is another way to import all the I/NET graphic folders in one time. Refer to Import all converted I/NET graphic folders into EcoStruxure at one time.

Issue Not all 3rd party manufacturers use the same Modbus addressing. Product Line Andover Continuum, EcoStruxure Building Operation Environment Modbus RTU X Driver bCX1, CX controllers, NC2 Building Operation Enterprise Server Building Operation Automation Server Cause Not all manufacturers use the same Modbus addressing. Resolution Many manufacturers have put their own slant on the "Modbus Standard" for addressing and number formats. The standard only defines 16 bit integer and binary data, but many manufacturers needed to use long integers (or swapped) and floating point numbers. They will transmit them as 2 integers over the protocol, then the receiving system needs to interpret them accordingly. To cope with this, special function codes were added which cover most formats. There are various interpretations by different 3rd party systems on addressing. Some number from 0 and others starting at 1. Some require a 30000 or 40000 offset including in the address, depending on I/O type. What is implemented in the X Driver is that whatever decimal address you enter in the X Driver point is what is sent down the bus. If the other system supplier is asked exactly what address they want sent down the bus, that is what is required in the X Driver point. Sometimes this is not the address that is on their datasheets. Sometimes there may be a need to add or subtract a value of 1, 30000 or 40000. This article was written for Continuum, but is still relevant to EBO Also see Helpful Modbus register Information for further information on Modbus registers.  

Issue When adding Shadow Schedule in AS, it isn't synchronized with the Lead Schedule in ES. This issue only happens when  there is an Exception schedule assigned with another Calendar added to the Lead Schedule in ES. Error: "cannot verify lead object status" Product Line EcoStruxure Building Operation Environment SmartStruxure Lead and Shadow Cause If a Lead Schedule contains an Exception with another Calendar assigned in ES, and a Shadow Schedule needs to be pointed to this Lead Schedule in AS, both the Shadow Calendar and Shadow Schedule need to be created and pointed to corresponding Lead Calendar and Lead Schedule. If only Shadow Schedule is created, it will fail to update to Lead Schedule, or even wipe the original setting with a blank schedule. When involving Calendars the following should be considered: The only way that the lead and shadow relationship can be maintained where calendars are concerned is where the calendar has the same name and is at THE SAME RELATIVE PATH as it does with respect to the lead schedule. Consider the following examples: Example 1 - Lead Schedule is at Root and Shadow Schedule is at root and Referenced Calendar is at root. - under these conditions there is only a need for one Calendar object. The Lead Schedule has an exception that references the calendar at the root and everything works great. Example 2 - Lead Schedule and Referenced Calendar are in Folder 1 and Shadow Schedule is in Folder 2. This will not work because the Shadow Schedule is trying to reference a calendar at the same relative path, i.e., in Folder 2, and there is none there. Example 3 - Lead Schedule and LEAD Referenced Calendar are in Folder 1 and Shadow Schedule AND SHADOW CALENDAR are in Folder 2. This will work fine. In simple terms keep the names and paths within the ES and AS consistent (the same) to avoid issues. Resolution Before the steps below, ensure the communication between AS and ES is OK. Refer to Binding between ES and AS or two AS shows Unresolved and Shadow Schedule in the Automation Server is not syncing to the Lead Schedule in the Enterprise Server. If the communication is fine, continue to the following steps: Create Lead Calendar and Lead Schedule in ES, and assign the Lead Calendar to the Exception of Lead Schedule (Should already done before). Create Shadow Calendar and Shadow Schedule in AS, and point them to corresponding Lead Calendar and Lead Schedule in ES. Now the Shadow Calendar should be able to synchronized with the Lead Calendar after changes have been made to the Lead Schedule.

Issue When upgrading to 1.4, the reference system will be changed to follow newer more strict rules. Product Line EcoStruxure Building Operation Environment Device Administrator Cause With the release of 1.4, StruxureWare now has a tighter control on bindings. This is to prevent users from creating bindings which hinder system communication. When a system is upgraded from 1.3, to 1.4 any bindings that do not follow the new rule set will be dropped. Here are the 3 major items for this new rule set. See Reference Guide and References beginning with 1.4.x for a full explanation. Public Signal bindings will be dropped Multiple bindings will be restricted to one Bindings to Local Node NVIs will be dropped during the upgrade. Resolution To upgrade the Automation Servers, follow these steps: NOTE: You will need to have a copy of Workstation at 1.3 in order to make changes to the Automation Server during the upgrade process. Use 1.4 Workstation after you have completed Perform a Manual Backup of the Automation Server. This backup must include historic data. Ensure that a copy of that backup is saved to an external disk as a recovery option. Open Device Administrator 1.4 Connect to and Select an Automation Server Click Upgrade Device. Please Read the warning in this pop up message. This will upgrade the most recent backup of the Automation Server. Any changes to the system made since the last backup will be lost at the end of this process. Note that the yellow Progress bar means that you MUST review warning in the conversion log. If the progress bar is Yellow or Red, proceeding may result in irreversible system changes. Click "Open" under the conversion log column. This is very difficult to read in Notepad. Perform a Save as .txt and open this file in either Word Pad or NotePad++ for easier reading Notice the Change in display when the information is viewed in WordPad Use the notes from Reference Guide and References beginning with 1.4.x and the conversion log analysis from AS Conversion Log Analysis to make sure that all objects with WARNINGS meet the new rules. This will require making changes to the system via workstation. Repeat steps 1-8 until you are happy with the conversion log. Please note, that you must perform a new backup to get an updated log. Click on "Download updated database to devices" Click Okay in the pop up Wait for the Installation to finish successfully. If any errors occur, be sure to get a screen shot and contact Product Support Note: If the upgrade doesn't complete correctly on one of the AS, cycle power on the AS, go back to the previous version and perform the upgrade again.

Issue SE7000 Series RS-485 transceiver unit load Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment SE7000 series room controllers Cause The room controller RS-485 transceiver unit load is not included in the data sheets. This information is needed to determine the number of BACnet MS/TP devices per RS-485 segment. Resolution Refer to Application Note AN05-RS485-VT7000 and Quick Guide RS485-VT7000. The links to these documents can be found in MS/TP and Modbus RS485 Communications on StruxureWare Automation Server

Issue How can you use Loytec's LPA software with the AS as the interface Product Line EcoStruxure Building Operation Environment Automation Server Loytec LPA Cause A Loytec LPA can be a valuable troubleshooting tool to diagnose communication problems on a LON Fieldbus. Resolution As the Automation Server uses Loytec's Lon chip, it is possible to use Loytec's LPA software over the Lon port on the AS. Some Prerequisites:   A license is required to use the LPA software. Either the "LPA-IP" or the "LPA-IP-SW" package depending on your setup. LPA (loytec.com) shows a product overview.   Downloads | Software - Device Firmware and Readme (loytec.com) to download the software. Create a free login in order to download software from Loytec's home page For additional help Buying and registering the LPA software read LonTalk Protocol Analyzer Software License and Registration Steps Lonworks troubleshooting read Troubleshooting LON Network Communication Troubleshooting Lon communication with TAC Xenta's read Actions for reducing Bandwidth in a Vista network There is a limitation when using LPA through an AS. Refer to Not all traffic on a segment is captured when using the LPA through an Automation Server Please make sure that you have a LonWorks interface configured in the Automation Server before proceeding. You will also need to add a Local Node to the interface and to commission it. Make sure to set the LPA state to Enabled under the Advanced tab in the properties for the LonWorks Interface: Once the above have been checked and understood the following steps can be performed:   Start the LPA software Click on "Profile -> Network Interface..." Click on "Remote LPA Assignment" Click on "Add Device" Enter the IP address of the Automation Server, click on "Get Info" and click on "Add Device and Restart Search" Select the Automation Server device and click on "Assign/Add" Select the interface you want to assign to the Automation Server, and click "Assign" With the interface assigned, click "OK" Select the Building Operation interface and click "OK" Now the LPA software is using the Automation Server as the interface Start a new LPA log

Issue Time Synchronization in Cyberstation  Product Line Andover Continuum, EcoStruxure Building Operation Environment Multiple Cyberstation Workstations Cause Security or HVAC and want to have exact time stamp from two or more Cyberstation workstations Resolution Continuum uses the Workstation time for events and transactions which are recorded in the database. Time Synchronization with the Server is not critical since they have internal time logs with the SQL database.  Time Synchronization with the Cyberstations so they have the exact time stamp on events and transactions is done by synchronizing the Windows workstation time to either a Network Time Server (NTS) (see Public time sync Servers for the United States) or by a third party software or device. Recommended is the Windows time which automatically synchronizes with the Domain Controller when logging in. If the computer(s) is not on a domain, double click on the clock in the lower right hand corner. This opens up the time settings and has a third tab as shown in image below: Select to synchronize with the Static IP Address of a primary workstation which can be seen by this computer. Visit Google and search for "Synchronize the time with Windows Time service" for your operating system If Internet access is not available, there are 3rd party USB and PCI devices available which synchronize with the Atomic Clock via radio frequency. Check your local listing to see if available.

Issue Upgrade warning and Error Conversion Log Analysis Additionally upgrading an AS from version 1.3 to 1.4 can create a number of unresolved or invalid references. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, ASP, ASB Building Operation Enterprise Server Building Operation Device Administrator Conversion Log Cause When upgrading using the Device Administrator various warning and errors can be seen. Errors will prevent the upgrade, but warning will still allow the upgrade to continue. Starting in version 1.4, new rules have been put in place that will invalidate some bindings that had previously been made in older versions. These rules may cause errors to be produced in the Conversion Log found in the Device Administrator. The three new rules are: Public Numeric/Signal bindings will be dropped. Multiple bindings will be restricted to one. Binding to Local Node NVIs will be dropped. For more information regarding the rule changes made in version 1.4 see Reference Guide and References beginning with 1.4.x. Resolution Instructions on how to perform the Automation Server upgrade and how to obtain the Conversion Log, see Upgrading Automation Servers from 1.3 to 1.4. Breakdown of the Conversion Log The file paths given in the Conversion Log entries will direct you to the location of the unresolved or invalid reference. Depending on the type of entry it is, it may require further action to correct the problem.   Type of entries found in the Conversion Log WARNING: ERROR: Invalid_Property_Reference (destination) (source) Explanation: Either rule 1 or 3 has been broken. If a public numeric/signal is bound programmatically to another object then it violates rule number 1. The public numeric/signal in the program must be changed to an input or output before upgrading the database. If the destination of the binding is an NVI in the Local Node then it violates rule number 3. A change to the configuration of the local node must be implemented before performing the upgrade. In many cases the substitution of an NVO for the NVI will address this issue. Explanation: This binding should not have been allowed in SmartStruxure version 1.3. In the StruxureWare Building Operation Technical Reference Guide, you will find on page 2107 that BACnet priority 6 is reserved for future use. This binding needs to be made to a different priority. WARNING: ERROR: Object_Does_Not_Exist (object). Explanation: The object that the reference is trying to bind to does not exist. In other cases the binding was already broken in the source database so it will remain broken in the target database. The binding fix can be addressed before or after the upgrade. WARNING: Property (property) bound to (property), so binding to (property) is dropped. Multiple bindings are not allowed in SmartStruxure version 1.4 and above. Explanation: The object is being written to by multiple objects and/or programs. This violates rule number 2 and is no longer accepted. After the upgrade, only one of the bindings will be left connected and all others will be dropped. This will require changes to be made to the configuration to maintain the same operation. Note: In some cases this warning can occur due to a default value of a configuration object that is mistakenly interpreted as a duplicate binding. The binding is in fact preserved by the upgrade and no further action is required. WARNING: Discarding incomplete binding for (object) -unknown source. Explanation: Due to a version 1.3 defect, the source version configuration database contains an incomplete binding error. This is not a problem but it may be a sign that someone intended for the property to be bound to something but failed to do so. Therefore, the configuration should be examined after the upgrade has been completed to insure that everything is okay. No information has been lost in the upgrade but check the configuration to rule out any errors in the source version database. WARNING: Property (property) in (object) is Unit configured but is not configurable in the new. Explanation: This property has a selected unit configured in the source version database, while in the target version configuring the unit of this property is no longer possible/meaningful. These errors should be investigated to insure that there has been no negative impact on the operation. Generally this error will not be a problem and will require no further action. WARNING: Property REF in (object) is not defined in the new system, skip REF. Explanation: The REF property prior to version 1.4 held a back-reference to an object or property that was referring to the property at hand. Starting in version 1.4 and on, the back-references are handled by other means and are no longer represented in the configuration database. This information can not be upgraded but this is not a problem and no further action is required. WARNING: Invalid value for (property) in the object, (object). The default value has been applied. Explanation: The value seen in the source version is invalid or can not be found; therefore the upgrade process sets it back to the default value. No further actions needs to be taken. WARNING: The declared instance (instance) is obsolete but contains non-default data which has been discarded. Explanation: If the instance is a SavedUserTokens or System/Remote Server warning then the warning can be ignored. No further action is required. WARNING: Property (property) in (source) is not an acceptable property type and is not configured. Explanation: This has to do with the lead reference for shadow Alarm Control Panels that cannot be properly upgraded due to changes to the type of system in version 1.4. There is logic in place that automatically sets the lead reference to the ES again. This is a warning that can be ignored. Explanation: There have been changes made to the type of system. This change prevents the hidden SynchSource property of the Time Zone setting in the source version of the database from being upgraded automatically. If the lead reference was set for Time Zone in the source database, this may have been erased and will have to be done again after the upgrade. This should be followed up manually. Explanation: The new referencing scheme expects all references to be relative so if there is a full binding path it is perceived as an error. This is not an issue and requires no action. Explanation: MatchedDevice is a hidden property that can not be seen. This warning refers to old items that have not been cleaned out. This warning can be ignored. Note: Also keep in mind that the upgrade process considers any empty link "not an acceptable Property". This error can be ignored, no changes need to be made. INFORMATION: Property "Value" in (location) is Unit configured but is not configurable, default unit is used. Explanation: This property has a configured unit that is no longer allowed to be configured in the target database, a fixed default value is used. This is unlikely to cause a problem, no further action needs to be taken.  

Issue Depicting the differences between Bacnet points and Central IO points. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.3 and lower Cause Explanation of difference in points Resolution Creating Central IO points When you create inputs and outputs in a non-BACnet SmartStruxure system, you simply create the inputs and outputs and then provide programming to control the Requested value. Trends, alarms and graphics would monitor the value property. In a BACnet SmartStruxure system, the inputs and outputs are created under the IO Module in the same way; however an additional point is created in the Application folder under the BACnet Interface Device. On the property page of that point is a field designating the “Associated Value”. You should browse to the appropriate CIO point and select it. At this point all monitoring, display and control of the object should be accomplished with the BACnet point. (It is also possible to make the link between the associated value and the IO value by using the binding tool.) There is no other binding necessary to make the link between the CIO point and the BACnet “proxy” that is created in the application folder. For SmartStruxure versions prior to 1.4 please see the attached document for some implications and proper method of operation for using the IO associated value property: PSS Building Operation Attachment 14040rev2.pdf For SmartStruxure 1.4 and above see Associate AS BACnet Interface IO points with points on the IO bus in SmartStruxure 1.4 and above.

Issue Communication issues between the Enterprise Server and Automation Servers result in an offline status of the AS. More information is required on how this status is detected.  Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause An AS behaves as if it is online yet shows up as offline in Workstation.  Resolution As of 1.5.0.10001 there is a new model for detecting online / offline servers. Prior to 1.5.0.10001 When a communication error was detected the Automation Server was marked as offline. As of 1.5.0.10001 and Newer An immediate DetectOnline call is scheduled. Only after three failed DetectOnline with an interval of one second we consider the  server to be offline. When offline an alarm is generated.and set the offline status as normal, and also go back to one minute interval for online detection. In 1.5.0.10001 the number of retries and interval is possible to set in server.properties. From 1.6.0 this is configurable from WorkStation. *** Server Communication folder is hidden in more recent versions of SBO See Also: How BACnet b3 controllers are established as being Online / Offline How the communication status of BACnet devices are verified

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. 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 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 Unable to login to AS directly when using Domain user. It is possible to login to AS directly with "Local" Domain and to the ES with same Domain. Receive error "Can not continue because server is offline or temporarily unavailable" even though ES is online. Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Domain Cause AS is unable to communicate with the ES to properly authenticate the Domain user.  If the ES is picking up a WiFi IP address instead of the LAN IP address, this can be the cause. All other communications can still function correctly with the ES but the issue occurs when the AS tries to connect directly to query the Domain, it will be using the wrong IP address. Resolution Changed the order of NIC''s in Windows so that the Local Area Connection was first, confirmed the ES had the correct IP address, confirmed the AS saw the change, and was then able to login to the AS directly using the Domain user. See How to set the Enterprise Server IP address for details on how to ensure you are using the correct IP address.  Another thing to look out for is that you are using the correct port number for the ES communications as seen from the AS.

Issue When restoring database, an error will show up, saying that version is incompatible with this server. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause This is usually caused by restoring new SQL database to older version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Microsoft doesn't like to do this. Resolution There is build number matrix for each SQL server version:     RTM (Gold, no SP) SP1 SP2 SP3 SP4 SQL Server 2012 11.00.2100.60 11.00.3000       SQL Server 2008 R2 10.50.1600.1 10.50.2500 10.50.4000     SQL Server 2008 10.00.1600.22 10.00.2531 10.00.4000 10.00.5500   SQL Server 2005 9.00.1399.06 9.00.2047 9.00.3042 9.00.4035 9.00.5000 So check the build number in the error message and download the corresponding version of SQL to restore and be used for I/NET.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue When having issues with a specific NCI (SCPT or UCPT) in a XIF file it can be hard to understand the FILE definition in the XIF file in order to troubleshoot a given issue For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks XIF Cause The FILE definition can be somewhat cryptic - here is an example   FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 Resolution The FILE section describes the configuration variables (or SCPT's and UCPT's) for a device. Here is an explanation of the various parts of the FILE section.

Issue Downloading a Xenta Programmable controller under a SmartStruxure Automation Server LON channel fails with message: "Application Download Failure." Viewing error details, the Progress view window shows "Wrong device version." Product Line EcoStruxure Building Operation Environment Automation Server LON channel Xenta Programmable Controllers Cause Right click on the Xenta controller in StruxureWare Building Operation Workstation. Go to the Xenta tab. Check the Software version. If this is below 3.6, then the controller's .MOT file is out of date and must be updated. Resolution The controller's software version must be at least 3.6 to be compatible with SmartStruxure. Use the Download Wizard to load an updated .MOT file into the controller. See Download an .MOT file into a Xenta Programmable controller for further instructions.

Issue When the EWS interface is created, the Status show "online". However, after clicking on the Hardware > EcoStruxure Web Service > SSLite, the Status will go offline. Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Building Operation 1.3 and above SmartStruxure Lite 2.7 and above EcoStruxure Web Services Cause Make sure the SOAP Endpoint field says "ews" and not "EWS". Lua program is a case sensitive program. Resolution Change the SOAP Endpoint field to "ews". For firmware version support in EWS, see Firmware versions to support EcoStruxure Web Services (EWS) in SmartStruxure Lite MPM Controllers.

Issue Workstation Log on failure. Difficulties with Login, port settings, and Server localhost: 80 8080 443 444 and other ports Product Line EcoStruxure Building Operation Environment StruxureWare 1.2.x.xxx and higher StruxureWare Building Operation Device Administrator StruxureWare Building Operation License Administrator StruxureWare Building Operation Enterprise Server StruxureWare Building Operation Workstation Cause Logging into Workstation, since I have changed my HTTP and HTTPS port setting to avoid conflict, and error is produced when the login fails: Resolution Beginning with StruxureWare Building Operation 1.2 and forward, Workstation uses the HTTPS as the default protocol (to make communication safer).  Below is the Software Administrator screen capture. Notice HTTPS is using port 450 in this example rather than default 443 since that port is used by another program on the computer.    Now when logging into Workstation, change the Localhost to that HTTPS port number. In this case, it is Localhost:450 Note: Remember, Server field in the Login screen shot above is for the AS or ES you want to connect to. To connect to an AS, plug in directly with ethernet cable (see Ethernet port is AutoSensing (No Crossover Cable required)), and put in IP address of AS.