Building Automation Knowledge Base

Issue After successfully downloading a Menta application directly through the serial connection, the pop-up window below is displayed:  tam32 No blueprint in TAC Xenta! Don't forget to download the network configuration if the TAC Xenta is to function in a network! Product Line TAC Vista Environment Directly connected Menta Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The blueprint is also called an .NDB (network database) file.  It contains network information that allows the controller to communicate to other controllers or I/O modules.  When downloading a Menta application directly, this warning is displayed as a reminder that that necessary network information has not been included in the application-only download. Resolution If the controller is running stand-alone and no networked communication is required, then no further action is required.  The message is only a warning alerting the user to the fact that the NDB file has not been included in the download. If the controller needs network variables and I/O module communication, follow the direct download (most often done only for troubleshooting purposes) with a download from the front end Vista Workstation for classic networks Vista System Plug-In for LNS networks If no front end exists, but network communication is still required (most often for I/O modules), lonTool32 is a suitable work around for those rare instances.  See Using lontool32 to download a stand-alone controller.

Issue BACnet bCX schedules cannot be edited without an error. Product Line Andover Continuum Environment Continuun bCX4040 Schedule Firmare v4.500082 Cause Following an upgrade to firmware v4.500082 the  Schedule end date year 2038 now enforced and schedule cannot be modified if the end (effective) date is beyond this Resolution For all schedules newly created or otherwise, the end (effective) date needs to be set to 2038 or earlier see Script Programs in Continuum compared to StruxureWare Building Operation and using floats (32 bits) and 64 bit numbers If the date is set after 2038 then an error is seen when trying to edit the schedule "An error code was returned from a BACnet operation, but the reason could not be determined."   Creating a new schedule with a date > 2038 can also give the error: " Error setting attribute 'DeviceID' An error code was returned from s BACnet operation , but the reason could not be determined " Defect was corrected in v4.500083

Issue Use of the Building Operation Script editor and general Script programming is covered in the Training courses and technical reference guide, what other techniques can be used to debug a program? Product Line EcoStruxure Building Operation Environment  Building Operation Script editor. Cause Often additional techniques are required to debug Script programs, especially when attempting to analyze, modify or fault find other people's code. Resolution Some techniques you can use for debugging your program and isolating problems are: Add in additional line labels to the program to isolate where the program is disabling or failing, if it disables you will be able to see the "CurrentLine" it has failed on and therefore know which line of code is causing the problem. Use the Trace feature to step through a program and monitor the binding variables, stepping through each line of code to ensure the values are all set as expected. Even if a program does not disable you can use the "Stop" keyword in the program, it will act as a break in the code and you can look at the values of the various variables, this may be a useful alternative to the Trace feature. Use the Watch window and the Binding Variables window to show the values of the various objects, when used with the above two techniques it allows you to accurately trace a program flow. Ensure all of the code used is compatible with the Script programming rules and that Continuum Plain English programs are not just used without conversion. Check the Plain English and Script Difference Guide. For programs in an i2 or b3 controller, ensure none of the Program size limitations are exceeded, see Plain English program limitations on number of characters in program and line labels.  

Issue Cannot open a file from TAC Vista Webstation from a TGML graphic Environment Vista IV TGML Webstation graphics Workstation graphics File access Cause  The "OpenFile" command doesn't work in a web browser. Resolution For an alternative way of viewing the reports and other files, refer to this document on the Community: DOC-7604 Guideline on how to open the same file in both TAC Vista Workstation and TAC Vista Webstation. To achieve opening a PDF or DOC file from a TGML graphic both in TAC Vista Workstation and TAC Vista Webstation, typically in workstation there's no problem. Use the "OpenFile" button, and the file should open. "OpenFile" button function in Webstation is not the same.  The "OpenFile" command to open the document from a button in a TGML graphic doesn't work in a web browser.  To open a file from a dynamic TGML graphic in Webstation Define a "Hyperlink" in TAC Vista. Direct the hyperlink to a document located in the "C:\Inetpub\wwwroot" folder on the server. Call the hyperlink with http://ip_address/docName.   Typical graphic behavior Opening a PDF document: Can be viewed in Workstation. Can be viewed in Webstation, but will not open in a new window even defining target as _blank. Opening a DOC document: Can be viewed in Workstation, but opens an "extra" window which must be closed after viewing the document. Can be viewed in Webstation.

Issue Without knowing the Device ID / Device Instance these devices cannot add to the MSTP network in the AS or ES. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment Automation Server Enterprise Server BACnet SE7000 Cause Only the MAC ID / Com Address is shown in the display but not the Device ID / Device Instance. Resolution SE7200x Models Default Device ID is set to: 72000 + MAC Where MAC is the current MAC address of the device. The device ID will also be upgraded as soon as there is a change to the device’s MAC. For example, when a SE7200F5045B controller with a MAC address of 41 is connected to a network, its default Device Name will be SE7200F5x45B-41 and its default Device ID will be 72041. SE73xxx Models Default Device ID is set to: 73000 + MAC Where MAC is the current MAC address of the device. The device ID will also be upgraded as soon as there is a change to the device’s MAC. For example, when a SE7300C5045B controller with a MAC address of 63 is connected to a network, its default Device Name will be SE7300C5x45B-63 and its default Device ID will be 73063. Click here for the Integration Manual. Please refer to the SE7300 series BACnet controller does not come online in StruxureWare Building Operation if SE7300 controller does not come online.

Issue Installing StruxureWare Building Operation Workstation fails The following error message is displayed when installing Workstation:     Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Workstation Earlier versions Cause This issue occurs if the PC has a newer version of Microsoft Visual Studio 2010 Tools for Office Runtime Language Pack previously installed than the one in the Workstation installer, which will abort the installation. Resolution Uninstall the Microsoft Visual Studio 2010 Tools for Office Runtime Language Pack from "Add or remove programs" in Windows. Run the Workstation installer again. It should now complete successfully. Before step 1 (uninstalling) you may first check which version of Microsoft Visual Studio 2010 Tools for Office Runtime Language Pack you have installed, this is also found in "Add or remove programs".  After finishing step 2 you may download the latest  Runtime Language Pack separately from Microsoft, or even the complete Runtime.  Note: This resolution only applies if you specifically get error 1603. There is a similar issue but with error 3010, please see Getting the error "Failed to install XXXX redist, error: 3010" during installation.     StruxureWare 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. Issue How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Product Line TAC Vista Environment Microsoft Windows OS Vista 4.3 to Vista 4.5 Cause Occasionally it is beneficial to be able to remove a TAC Vista installation completely, removing any indication it was ever installed. Resolution When using SQL 2000 or enterprise version not administered by TAC Vista: Backup SQL database named "taclogdata." Use the backup function in SQL Server manager. Save the database outside of the Microsoft SQL Server and TAC root directory (usually C:\Program Files\TAC and> C:\Program Files\Microsoft SQL Server). When using SQL MSDE administered by TAC Vista: Backup TAC Vista log and event database using backup function in TAC Vista. Backup TAC Vista database using backup function in TAC Vista. Stop SQL manager, Task manager/processes – stop sqlserv.exe and sqlagent.exe if running. Remove TAC Vista Config1.x using the uninstall program in Control panel Add/Remove programs. Remove all TAC Vista hotfixes. Remove TAC Vista Server 4.x.x using the uninstall program in Control panel Add/Remove programs. If additional TAC programs like TAC ToolPack, TAC XBuilder etc. are installed remove them as mentioned before. Remove SQL (Microsoft SQL server desktop engine) using the uninstall program in Control panel Add/Remove programs. Save off a customer's license (.lic) file to another location.  Delete remaining uninstalled TAC folders (usually C:\Program Files\TAC). Delete remaining files in C:\Program Files\Common Files\TAC Shared. Delete remaining uninstalled SQL (Microsoft SQL server) folders (usually C:\Program Files\Microsoft SQL Server) Check to see if TAC needs to be removed from the registry – Start, Run, REGEDIT. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls Remove all keys containing "TAC Shared," e.g. C:\Program Files\Common Files\TAC Shared\TACADDON01_ENG.dll. If applicable - Remove SQL from registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL server Go to user profiles delete the profile Computername\TACA_Computername (Versions of Vista <5.0) Go to My computer, right click manage, local users and groups, users, and delete user account TACA_Computername and TACM_Computername. Reboot. Reinstall desired version. See How to uninstall and completely remove TAC Vista 5 for steps on removing TAC Vista 5.

Issue How to update a demo Security Expert License once it expires. Product Line Security Expert Environment Workstation Cause Not sure how to re-active the demo license after it has expired. Resolution To extend the demo license, contact your local country product support group. Product support can have the license expiration date extended and then it can be updated/download again.  Go to About -> License, go to License Update tab and click on Download License and then OK to update. From v4.2.243 you will now be able to perform manual license activation's that can be used for installations that do not have Internet access. For more information see Performing a manual license registration.

Issue You get an error, "Unable to load the .Net control for this page." when trying to open a schedule in WebClient. Product Line Andover Continuum Environment webClient Cause The problem is that the .Net zone permissions are not set on the browser machines. Resolution Depending on the revision of the WebClient the procedure for correcting this on the browsing machines is different. If you are running WebClient version 1.73 or below then refer to the WebClient installation guide on setting the .Net zone permissions. If you are running WebClient version 1.74 or higher, which uses .Net 2.0, the procedure is different. Below is the procedure that will need to be performed on the browser machines at the command prompt to set the .Net Zone Permissions for .Net 2.0. The following command will add FullTrust to the Internet_Zone in DotNet 2.0: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Internet_Zone -zone InterNet FullTrust -name FullTrust The following command will add FullTrust to the Trusted_Zone in DotNet 2.0 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\caspol.exe -m -addgroup Trusted_Zone -zone Trusted FullTrust -name FullTrust This will result in output like: The operation you are performing will alter security policy. Are you sure you want to perform this operation? (yes/no) Then select Y and you should see: Added union code group with "-zone" membership condition to the Machine level. Success You should then be able to open the .Net 2.0 editors on your web.client browser machine. In some cases adding the webclient IIS PC to the trusted sites in the browser is needed Internet Explorer> Internet Options> Security> Click Trusted Sites> Click Sites Type in http://your server name/webclient and click Add (i.e your server name is specific to your install) Deselect the checkbox for 'Require server verification (https:) for all sites in this zone Click Ok, Ok Close explorer and access webclient schedules Note: Every browser PC that will be accessing schedules needs to have the caspol commands run on it. Download a batch file that can be run on each PC (Rename the .txt file to .bat and run at a DOS prompt  C:\> caspolwebclient.bat)   Note: When using 1.94 SP1 check the application pools .net version selected Name .Net Version ASP NET v4.0 4.0 ASP NET v4.0 Classic 4.0 Classic .NET AppPool 2.0 Default AppPool  2.0 WebClient  4.0 Note: If .net framework 4.5.x has recently been installed on browser PCs, see Webclient Cannot open .net editor with .NET Framework - 'There was an error trying to create the .NET control for this page'.

Issue Unit Conversion Exceptions Unit selection of 'bar' defaults to N/m 2 unit Units are not displaying unit as selected in the properties Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 and above Cause Building Operation supports both the SI metric system and the US Customary System for units of measurement. The operating system regional settings on which WorkStation is installed determine whether SI units or US Imperial units are displayed. The conversion between the two measurement systems is managed automatically. For example, the temperature 42,82 °C is stored in Building Operation. A WorkStation on an operating system with the US Customary System converts the temperature and displays it as 109.08 °F. To display the original unit of a value in WorkStation, open the Properties pane for the value and go to the Unit selection dialog box. As part of this process some units selected, default to a default display unit, and not what was originally selected.  For example, selecting the pressure unit 'bar' when configured in a SI regional setting will display by default the unit 'N/m 2 ' and not 'bar' as selected.  This functionality is as per design but can be altered by using the Unit Conversion Exceptions feature. Resolution First reference Adding a Unit Conversion Exception on the Building Management WebHelp site.    In the release version 1.2 and above there is a feature that allows the operator to create unit exceptions, called Unit Conversion Exceptions.  This is located under the Domain folder and allows various conversions for different domains.  The steps below indicate how this is achieved. Locate the Unit Conversion Exceptions under the required Domain The Unit Conversion exceptions are now displayed in the Workspace.  The Add remove buttons are located at the bottom of this workspace Add the Configured unit, which is the selected unit for the variable you wish to be converted Then change the SI Display Unit and / or US Display Unit to the desired unit you wish the configured unit to be displayed / converted too Save these changes and confirm that it is now displayed in the desired unit.  In some cases you may need to log out and then back in for the changes to be applied. Online Web Help is also available here: If your system is based in US region then you can default you measurement system to US as per Metric vs. English (Imperial) Operating System.

Issue Unable to successfully install Continuum keyless license software. Product Line Andover Continuum Environment Continuum Keyless Soft License Hasp Key Utility Sentinal HASP License Manager Cause Various causes. Resolution The following articles address issues with the Continuum Keyless license software. Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped Web based email should not be used to deliver Keyless Licensing information files (c2v) or activation files (v2c) How to determine the Continuum version, features and the Hasp license ID on a Keyless Continuum License Hasp Key Utility will not activate keyless license Version Error Getting Id. -- Key Id Not Found Hasp Key Utility will not activate keyless license Version Error Getting Id. - HASP License Manager service has stopped

Issue "No license for LonWorks communication" with TAC Vista Server LE Product Line TAC Vista Environment TAC Vista Server LE (LE= Limited Edition which has no Webstation or multiserver functionality) Cause If TAC Vista Webstation is installed on a TAC Vista Server LE machine, Lon communications will not work correctly. It will work for 10 minutes then an alarm message appears, "No license for LonWorks communication," and all communication with the Lon network will stop. Resolution Uninstall Webstation Related Articles: "No license for LonWorks communication" error when using a non LE dongle. "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network. "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue Every so often one or two programs on the Continuum workstation stop working. Editing the program results in: A Cached Program cannot be opened while it is being written. Product Line Andover Continuum Environment CyberStation WebClient Continuum Programs Cause CyberStation was not installed properly. Too many demands are being placed on the workstation. Resolution If the problem results from a problem with the installation of Continuum Cyberstation, refer to Problems installing Continuum. Once Continuum has been properly installed, the problem may result from placing to many demands on the Continuum workstation.  Some questions that should be asked are... How many programs are being run on the Cyberstation concurrently. The default setting for Run on any workstation when a workstation program in created is false. This property should be checked for all workstation programs whether they must be run from another workstation or not. This setting can be found in the Program properties editor. An a cached program cannot be opened while it is being written error may occurring when a report program is writing to disk. Verify that the Cyberstation PC conforms to the Continuum Compatibility Matrix for the Continuum version. How many PE programs are running on this workstation, how complex are these programs and are high level commands such as: Rotate, Run, Shell, OpenFile, OpenList, GetName, GetObject being used frequently. How many report programs are running concurrently.  Is the report workstation 100% dedicated to running reports and nothing else; no alarm reporting, no schedules, no extended log downloading, no Access server functions? Is the workstation hardware and operating system sufficient for the work CyberStation is expected to do. Managing these demands may involve sharing the reporting load over several CyberStations and/or adjusting the timing of processor intensive programs so that the workstation is executing fewer tasks at any given time.  In some cases program performance may be impaired due to insufficient memory allocation. See Getting a Smart Heap error when starting Cyberstation or not all processes start and Cyber doesn't open.

Issue How to order more NL credits in order to commission more devices. If the following message displays when opening a NL220 database, then more credits will need to be purchased soon. " BEWARE: less than 20 credits are available on this machine. If you need to install more than 20 device please order the amount of needed credits as soon as possible. Do you want to ask for new credits?" Product Line TAC IA Series, TAC Vista Environment NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   Echelon LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. Echelon LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. Newron NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LNS credits see Ordering more LNS credits. To order more Echelon LonMaker credits see Ordering more Echelon LonMaker credits. Resolution When working in NL220, it is wise to maintain a higher level of LNS credits than NL credits to help avoid locking out the LNS server license. To check the amount of NL credits remaining go to Start > All Programs > NL Suite > NLCreditsGenerator and look for Remaining NLCredits. The number of NL credits remaining can also be found at the bottom of the NL220 LonWorks Manager window with a project open. To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available. The number of LNS credits remaining can also be found at the bottom of the NL220 LonWorks Manager window with a project open.   To order more NL220 credits: Open the NLCreditsGenerator Utility that is installed with NL220. Go to Start > All Programs > NL Suite > NLCreditsGenerator > NLCreditsGenerator Utility. Enter the number of NL220 credits to be added  in the request area. Click Next. Click "Yes, this PC will be used for commissioning" Enter your name and contact details. Select "Copy to clipboard". Then either paste the information into notepad or in an email. Send the NL credit request to your local Schneider Electric Buildings Business order department  (NLCredits@buildings.schneider-electric.com). When you order has been processed by the local Schneider Electric Buildings Business order department you will receive an upgrade key. Open the NLCreditsGenerator Utility again. Go to Start > All Programs > NL Suite > NLCreditsGenerator > NLCreditsGenerator Utility. Click the Next button. Enter the key into the "Upgrade key" field of the credits generator. A message indicating you credits were added is then displayed.   Note: Once the request key has been generated, DO NOT commission or decommission any devices with the dongle until the upgrade key has been applied to the dongle. If devices are commissioned before then, the upgrade key will no longer be valid.

Issue Webstation TGML links used to navigate between Graphics pages do not work. These TGML page links work in workstation Product Line EcoStruxure Building Operation Environment SmartStruxure Cause The name of the Enterprise Server database has an illegal character. A sample of this would be if the Enterprise Server is named "Server'1"  The ( ') affects the HTTP application and prevents the page links from working. Although the name is accepted and works in Workstation, WebStation does not allow this character. This will be corrected in a later revision. Resolution The only resolution at this stage is to rename the Enterprise Server to a name with valid characters. If there are Automation Servers already installed under the Enterprise Server then there is a major issue with renaming the Enterprise Server and we would not recommend renaming you servers unless you are in the early stages of your project. You will need to detach and delete all of the Automation Servers and then Rename the Enterprise Server. Bindings will be lost in this process and will need to be recreated when the Automation Servers are added back in. See Illegal object name characters in StruxureWare Building Operation.

Issue How to get the XIF file of Xenta free programmable controllers? Product Line TAC Vista Environment Xenta Free programmable controllers (Xenta 281, Xenta 282, Xenta 283, Xenta 301, Xenta 302,  Xenta 301C, Xenta 302C, Xenta 401, Xenta 401B, Xenta 401C) TAC Menta editor Cause If Xenta free programmable controllers need to play as a third party device in another system, a XIF file is needed. Resolution Open the preprogrammed Menta file in the Menta Editor.  Note: If you are opening the file directly from the Vista database, it will first need to be saved to the local harddrive before generating an XIF. Go to Options > Simulate (or press F12) Go to Commands > Generate An XIF file with the same name as the .MTA file will be generated in the same location on the harddrive as the. MTA.   Alternatively, if you are connected live to the controller, you can also generate an XIF by connecting live: Open the preprogrammed Menta file in the Menta Editor. Connect the Xenta free programmable controller to the computer with a RS232 to USB cable. For details please refer to Downloading a Xenta Device Using Direct Connection to Menta Programming Tool. Go to Options->Simulate (F12), and select connect. A XIF file will automatically generated under the same folder that the Menta file is saved. NOTE: in order for third party system to be able to view points in Menta, those points need to be set as SNVTs.

Issue Satchwell TR Series 230 V ac / 24 V ac Transformer requires replacement. Product Line Field Devices Environment Satchwell TR1 (25VA), TR2 (50VA), TR3 (80VA), TR4 (200VA) and TR5 (300VA) 230 V ac / 24 V ac Transformers. Cause Obsolescence of Satchwell TR1, TR2, TR3, TR4 and TR5 230 V ac / 24 V ac Transformers. Resolution Replace Satchwell 871-1-201 TR1 (25VA) 230 V ac / 24 V ac Transformer with S-E TR 32 (32VA) 230 V ac / 24 V ac Transformer SE part number 3413032000. Replace Satchwell 871-1-202 TR2 (50VA) 230 V ac / 24 V ac Transformer with S-E TR 60 (60VA) 230 V ac / 24 V ac Transformer SE part number 3413060000. Replace Satchwell 871-1-203 TR3 (80VA) 230 V ac / 24 V ac Transformer with Transformer of another manufacturer's origin. Replace Satchwell 871-1-204 TR4 (200VA) 230 V ac / 24 V ac Transformer with Transformer of another manufacturer's origin. Replace Satchwell 871-1-205 TR5 (300VA) 230 V ac / 24 V ac Transformer with Transformer of another manufacturer's origin. The S-E TR range of Transformers provide the same functionality as the Satchwell TR range of Transformers but differ in appearance, dimensions and the range of VA ratings available. Specification EN 60742, with which the Satchwell range of Transformers complied, has been superseded by Specification EN 61558, with which the S-E range of Transformers comply. To review the transformer data sheet, see TR32-60 Transformer Data sheet en [101917].pdf.

Issue Invalid user name or password dialog when logging into webclient with acc that works in Continuum Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Windows 2003 Windows 2008 Cause Activex control didn't download or an update to .Net requires a re-register of .Net to IIS Resolution This happens when attempting to login to webclient when there are higher security restrictions on Internet Explorer so files that need to get installed on the client machine get blocked. A. Add the webclient server as a Trusted site in Internet Explorer on each client machine as follows: Open Internet Explorer and select> Tools> Internet Options> Security> Click on Trusted Sites and Click the Sites button Deselect "Require server verification (https) for all sites in this zone Add the webclient server name Ex. http://Servername (This typically populates automatically.) B. Also, change the default security settings to medium-low as follows: Open Internet Explorer and select> Tools> Internet Options> Security>Click on Trusted Sites and Click the Custom level button In the "Reset to" drop down, select Medium-Low and then Click The Reset button Click Yes to the "Are you sure you want to change the settings for this zone?" In the Settings list, manually enable "Download unsigned ActiveX controls Click OK, Click Yes to "Are you sure you want to change the settings for this zone?" Click Ok and Ok again C. Run the aspnet_regiis.exe -i command from DOS to re-register .Net with IIS From DOS> CD\ Windows\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis.exe –i Once these steps are completed, enter the URL for webclient again, the appropriate activeX controls will install and the login will work normally. If this still doesn't work and you get a message that "Internet Explorer is currently running without add-ons" then take a look at the following Microsoft articles.   https://social.technet.microsoft.com/Forums/ie/en-US/53a3b82c-e61a-4576-8d80-91e204d4b1e9/internet-explorer-is-currently-running-with-addons-disabled?forum=itprovistaie Also see Internet Explorer gets "web.Client only supports Internet Explorer 32 Bit version 8.0 and greater" when logon to the Webclient server. This article is similar, but mentions changing the compatibility view in Internet Explorer.

Issue Using I/NET trends in StruxureWare Building Operation Product Line EcoStruxure Building Operation, TAC INET Environment I/NET StruxureWare Building Operation 1.3 Cause Ideally trends should reside in the controller rather than at the sever level as this prevents sample data loss due to communication errors. Resolution Before you begin, ensure that all I/NET trends are set up correctly and trend data is visible. For assistance with this see Setting Up I/NET Seven Trends. Ensure that messaging is working so that SmartStruxure receives I/NET messages, and ensure that all controls have points to be trended, are already added to the I/NET Interface. NOTE: For the Enterprise Server level integration, the I/NET Trend Object must be configured as a Seven Trend. For the Automation Server level integration, this is not required, therefore skip to step 3. In I/NET, Select Trends>Data Inquiry/Edit View the trend you wish to see in SmartStruxure and verify that it has data. Open StruxureWare Workstation Refresh the system tree and upload any I/NET controllers that do not show a green dot. Right click on the I/NET Interface and select New>Value When the "Create Object" Window appears, name the value and click "Create" The Value will appear in the I/NET Interface Right Click on the newly created Value and select "Properties" Locate the "Point to Trend" Field Click on the "..." and select the point object you wish to trend Click the select button Verify that the Point to Trend field is correct and Click OK Wait enough time for several samples to populate. Right click on the Value object in the I/NET interface and select View>Trend log lists>New Trend log list The New Trend log List should open and values should visible. The Trend Value object under the I/NET interface will now function the same as a trend object in StruxureWare. If you wish for the I/NET trend to show up as part of an Energy Report, you will need to Ensure that the Extended Trend Log is referenced in a Meter's "Meter Trend Log" property NOTE: For the Enterprise Server Level Integration, In order for the initial connection between the StruxureWare Value Object and the I/NET Seven Trend to be enabled, the following conditions need to be true: The Controller with the I/NET point being trended must not require an upload The Controller with the I/NET point being trended must have a current save file The Controller with the I/NET point being trended must be online The I/NET workstation located on the Enterprise Server must be masked to receive data from the trend log on the controller to the Seven Trends Definition For the Automation Server Level Integration, In order for the initial connection between the StruxureWare Value Object and the I/NET Seven trend extension to be enabled, the following conditions need to be true: The Controller with the I/NET point being trended must not require an upload The Controller with the I/NET point being trended must be online The I/NET trend object and point object must have some level of masking so that the data will leave the controller.

Issue The network administrator requires that the SQL Andover97 password be changed every three months.  How will this affect the Continuum System? Is it necessary to do a Database Initialization each time the password is changed? Product Line Andover Continuum Environment Andover97 SQL Database Initialization Cause Once the Andover97 password has been changed, the workstations will lose their connection with their access to the database until the workstation (not the database) can be initialized with the new password. This will be indicated by a Database Fault error at the workstations.  Resolution The proper way to change to transition to the new password is to: Shut down all cyberstations. Change the Andover97 password in SQL. Launch Continuum Database Initialization. Select Workstation and enter the new password on the Database page, then select OK. Relaunch all cyberstations.  Once the password is changed, it is only necessary to do perform a workstation initialization (not a database initialization), but this must be done on each workstation.   Refer also to the following article that discusses how Continuum uses the sa password: When is the SQL System Admin (sa) password required?