Building Automation Knowledge Base

Issue Error when installing SQL 2005 Express on a machine that had previously had MSDE installed Product Line TAC INET Environment SQL 2005 Express Cause  MSXML 6.0 SP2 is causing the installation to fail Resolution Download the program linked below Remove SQL 2005 from the system Run the application to remove MSXML 6.0 from the system Re-install SQL2005 Express MicrosoftFixit50568.msi.zip For alternative solutions see SQL Express install fails on MSXML 6 and Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.).

Issue Workstation Pro License fails to allow running of v2.0 or v3.x EcoStruxure WorkStation following an upgrade Product Line EcoStruxure Building Operation Environment WorkStation Licensing Cause Workstation Pro License SXWSWWORK00002 (SW-STATION-PRO-0) is the same for v1.x and v2.x, so that WorkStation Pro should continue to operate after an upgrade. However, there was a License upgrade/change at v1.7 (from v1 to v2) and if the License was registered before this the version remains at v1 and this will not run v2.x WorkStation Resolution The WorkStation Pro License needs to be returned, then re-installed using the online Licensing system.   Before License is returned   After license is returned  The process to return a license can be found in Webhelp.

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 The size of ContinuumDB has reached or is near the 2Gb limit imposed by MSDE. The size of ContinuumDB has reached or is near the 4Gb limit imposed by SQL Express. Environment MSDE SQL Express Continuum Stand Alone. Cause The database is well over the SQL size limit (2Gb for MSDE, 4Gb for SQL Express) Since the database size has already exceeded SQL's limitations it is not possible to use the deletion query statement to truncate the log tables.  This is because SQL will attempt to guard against data loss during the deletion process by making a copy of the tables contents before deletion occurs. Before a single row has been deleted from the table the size of the database will actually grow larger, exacerbating the problem. Resolution You must delete the contents of each log table entirely (Alarm, event, error, log) using the TRUNCATE statement. This will delete the contents of these tables entirely without first storing them the data. Please note, you must... Make arrangements with the customer so that they can archive any log and event data they wish to retain. Backup the database before using the TRUNCATE TABLE command. Here is the syntax for the TRUNCATE statements TRUNCATE TABLE ContinuumDB.dbo.AlarmEvent TRUNCATE TABLE ContinuumDB.dbo.AccessEvent TRUNCATE TABLE ContinuumDB.dbo.ActivityEvent TRUNCATE TABLE ContinuumDB.dbo.ErrorEvent TRUNCATE TABLE ContinuumDB.dbo.ExtendedLog Once the table have been truncated, Right click on ContinuumDB and select Shrink > Database. Once the database has been size has been reduced, check the size and retest. Please note that once the database size has exceeded SQL's limit it is likely that the database has been damaged.  This process may or may not correct damage that has occurred to the database.  

Issue Timestamps in Script programs are different by an amount equal to the UTC offset of the workstation's timezone settings. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Building Operation WorkStation Script editor Cause Take the following program as an example:   Datetime Output TimeOut, TimeOut2 TimeOut = StrToDate ("1/17/2012 15:00") TimeOut2 = StrToDate ("1/17/2012 3:00 PM") In EcoStruxure Building Operation, the values will read:  "1/17/2012 9:00:00 AM" (in this example, the UTC offset is set for -6). In servers, all time values are stored in UTC, then the offset is applied by the client.  When it receives a value from a Script program, it stores the value as UTC, then the offset for the selected timezone is applied. Resolution Write code in the Script program to adjust the time values to UTC. Check the example code below to help understand operation: Datetime Output dtOut1 Datetime Output dtOut2 String Output str1 dtOut1 = Date 'Local time, displays with added UTCOffset dtOut2 = Date - UTCOffset - DST 'Local time, adjusted by the UTCOffset and DST, displays properly Print Date to str1 'Local time String value displays properly (UTCOffset system variable is available in v2.0 or higher, DST system variable is available in EBO 2022 v4.0 or higher)

Issue An unexpected database error occurred. "There can only be one LCA Object Server ActiveX control per process. Please make sure that you only have a single Object Server control in this process." "Could not listen on _poet/tcp: The address is already in use or another server already running. (-2532)" Environment LonMaker NL220 Vista LNS Cause Microsoft Exchange 2003 Server and other OEM software sometimes use TCP ports 6001 or 6002. This causes a conflict since the POET server (FastObjects DB) defaults to TCP ports 6001 and 6002. Resolution For an automated solution, refer to: https://community.se.com/t5/TAC-Vista-Forum/LonMaker-POET-Port-Changer/td-p/271427   For a full explanation from Dialog Semiconductor, refer to: https://edgesupport.diasemi.com/hc/en-us/articles/206494283   Further details   Check that the ports used by LNS are not being blocked (firewalled) or used by another application. To verify this, type in the following command from a DOS prompt: netstat -bn You should now get a list of in-use TCP ports. Look for an entry saying {your computer name}:6001 or 6002. If you find one, you have located a conflict and you will need to change the POET Port numbers. Check if you run a firewall on this PC. If yes, you need to find the list of Programs with their Internet Access level and make sure you have given access to the appropriate files. To run LonMaker/LNS , you need to give access to ptserv32.exe, LonMaker.exe, lonpoint.exe, visio.exe, lmwbrw32.exe and lsass.exe. You can modify the ports used by the POET server and clients by modifying the "Services" file (%WINDIR%\System32\Drivers\Etc\Services) using a text editor like Wordpad.exe or Notepad.exe. For example, to change the POET port numbers to 7001 and 7002, add/modify the following lines in the "Services" file. The  '#' in the example indicates that the following text is a comment. For Win XP: use "Windows\System32\Drivers\Etc\Services". If you see the "poet" and "_poet" entries, go ahead and change the port numbers from 6001 and 6002 to 7001 and 7002. If you don't see these entries, simply add the lines below. poet          7001/tcp    #FastObjects services _poet        7002/tcp    #FastObjects services https://echelon.force.com/support/s/search/All/Home/562?tabset-95728=2

Issue Planning an upgrade and need to know which Infinity system controllers can NOT be upgraded to Continuum. Product Line Andover Continuum Environment Infinity Continuum CX9000, CX9100, CX9001, CX9101 CMX220, CMX221, CMX222, CMX230, CMX231, CMX232, CMX240, CMX241, CMX245, CMX246 Cause Some Infinity system controllers can NOT be upgraded to Continuum. Resolution CX9000, CMX220 series,CMX230 series, CMX240 series and CX9500 ranges can not be upgraded to Continuum, all other controllers can be upgraded, some via a chip change, others can be upgraded via Continuum update. The LSX280 Laptop service tool is not compatible with Continuum, a RoamIO should be used. Check out the Software and Firmware compatibility matrix for older versions of the traditional product lines for the minimum versions required for Cyberstation, but the following gives an overview of the requirements: CX9200 (CX9300,CX9201) - Requires chip replacement with Continuum firmware V1.5x CX9400 Eclipse (CX9410) - Requires flash upgrade to Continuum V1.5x firmware, but will require working SX8000 system to flash the controller, otherwise send to Repairs for upgrading. ACX780 -  Requires chip replacement with Continuum firmware V1.5x ACX781C ACX700 -  Requires chip replacement with Continuum firmware V1.5x ACX701C DCX250 - Requires Infinity V2.16 firmware chip Other i1 (generation 1 infinet controller) controllers require a minimum of V1.4 firmware chips

Issue How can I add a SmartStruxure Automation Server to TAC Vista using BACnet/IP and what is needed Product Line TAC Vista, EcoStruxure Building Operation Environment TAC Vista Xenta 913 Automation Server Cause Building Operation versions earlier than 3.2 are not FDA 21 Part 11 approved, In instances where the version is lower than 3.2 it can be achieved by using  TAC Vista as a front end, and having Automation Servers as field controllers. In Building Operation version 3.2 and later an optional Regulated Industries Compliance Pack is available that can be used without the need for  TAC Vista as a front end. Resolution 1. Create a BACnet interface in Automation Server. 2. Create BACnet points in the "Application" folder 3. Browse the Automation Server with a BACnet browser (Here is a free tool) 4. Note the instance id's of the points 5. In TAC Vista, create a Xenta 913 6. Edit the Xenta 913 7. Create a "BACnet IP Client" interface and give it the IP address of the Automation Server 8. Create a BACnet device template containing the points you need - refer to the id's previously discovered 9. Add the device template to the "BACnet IP Client" interface in XBuilder 10. Save and download the project 11. Now you get the live values from the Automation Server in TAC Vista

Issue Re-addressing I/A Series BACnet controllers on an existing BACnet MS/TP installation Environment I/A Series R2 BACnet integration to I/A Series Micronet BACnet Controllers Cause There are gaps in BACnet MS/TP addressing which needs to be fixed. Gaps in addressing add delays in communications. Addressing should begin with node 0 (zero) and progress through all nodes, without any gaps, for each separate MS/TP network. Refer to the I/A Series MicroNet BACnet Wiring, Networking, and Best Practices Guide (F-27360-7). Resolution The procedure to change the addresses of the MNB controllers involves the following steps. Changing the physical DIP switch address on the MNB controllers. Making sure the MAC Address of the BACnet shadow device object in the I/A Series R2 UNC reflects the change. Changing the Max Master property in each MNB controller using WorkPlace Pro. Alternatively, you can change the Max Master property using the WorkPlace Commissioning Tool. 1. Changing the physical DIP switch address on the MNB controllers Have a piece of paper ready to note down the physical DIP switch address before and after the change. DIP switch addressing should be sequential starting from ‘0’ with no gaps in between. However, the physical location of the device does not matter. For example, if we have 30 MNB controllers on the BACnet MS/TP network, the addresses should be from 0 to 29 but they do not have to be in order physically. As an example, the first MS/TP device could have an address of '0' while the second MS/TP device on the wire can have an address of '10'. The MNB-1000 should be address ‘0’ if it is the first MS/TP device. If the first MS/TP device is an UNC, the UNC should be address '0' (set in WorkPlace Pro). Use Table–2.3 to calculate the DIP switch value for physical addressing. Take, for example, that the address must be set to 16. To do so, you would set switch number 5 (value=16) to ON. If the address is to be set to 43, instead, you would set switches 1, 2, 4, and 6 to ON (value=1+2+8+32=43). The controller should reset itself about 10 seconds after the change and the new address will be in effect. 2. Check / change the MAC Address of the BACnet shadow device object in the UNC using WorkPlace Pro. After changing the physical DIP switch of the device, we will need to make sure that they change has been reflected in the corresponding BACnet shadow object device in the UNC. Using WorkPlace Pro, open the UNC station. Go to the Properties of the MNB shadow device object and go to the ‘Config’ tab. Make sure that the 'MAC Address' field is showing the new address (in HEX) of the controller. 3. Changing the Max Master property in each MNB controller using WorkPlace Pro. Each MNB controller under a particular BACnet MS/TP trunk needs to have their ‘Max Master’ setting changed. Set ‘Max Master’ to 1 or 2 higher than the highest address on the MS/TP network. If the highest addressed device is DIP switch value 50, set the Max Master to 51 or 52. In WorkPlace Pro, open the UNC station. Go to the Properties of the MNB shadow device object and go to the ‘Engineering’ tab. Change the ‘maxMaster’ to a value that is 2 higher than the highest addresses device. Click ‘Apply’.

Issue Allowing write access from BACnet Product Line TAC IA Series Environment I/A Series G3 BACnet Integration Cause By default, the BACnet driver provides external BACnet (client) devices "read access" to all exposed (exported to BACnet) objects in the station. Access depends on a station user named "BACnet." If this user does not already exist in the station, the Bacnet driver automatically creates it, upon startup. The BACnet user is initially created without any permissions. Resolution See below which is extracted from the Niagara Ax BACnet Guide: To allow any external writes (from BACnet) to properties of exported components, including invoking commands (actions), you must assign the BACnet user the necessary permissions to those components. For example, to allow an invoked "Active" action from BACnet to an exported BooleanWritable, in addition to making it "BACnet Writable" at priority level 8 when exporting, you must configure the station’s BACnet user to have operator write permissions on that BooleanWritable, at a minimum. Or, if an exported NumericWritable has an alarm extension, and you want to permit external BACnet writes to its "alarm limit" values, configure the BACnet user to have admin write permissions on the exported NumericWritable. In either example, to allow an external BACnet write to a property like "Out Of Service" or "Notify Type," you must give the BACnet user admin write permissions on the BACnet export descriptors. For details about station user security, see "About Security" in the User Guide. Note: BACnet user permissions also apply to writes of any exported files and histories. Also, note that while a password for the BACnet user is technically not needed (for external BACnet access), you should assign one anyway, because of the write permissions typically assigned. Make it a "non-blank" password, and guard this password carefully.

Issue Which signal types can be connected to a UI on a Xenta I/O Modules? Product Line TAC Vista Environment Xenta 451A/452A, 421A/422A Cause UI is short for universal input, which means that these inputs are compatible with many different input types. Resolution Supported input signal types are: Thermistor: 1.8 KΩ at 25 °C or 10KΩ at 25 °C; Voltage: 0 to 10VDC; Current: 0 to 20mA; Digital Input. Refer to the following link about 1.8KΩ and 10KΩ thermistor compatibility: 1.8k Thermistor compatibility with Xenta controllers 10k Thermistor compatibility with Xenta controllers

Issue Error when trying to add exceptions to a schedule is seen when trying to "apply" the changes. Example: Personnel Manager Error saving data Communication Error Exception has been thrown by the target of an invocation. The personnel object was created Product Line Andover Continuum Environment Continuum Cause Too many old exceptions in the schedule. Sometimes RPC (Remote Procedure Call) errors happen on Cyberstation following the above error. Resolution Delete the old exceptions. This must be done manually for infinet schedules. 1.94 NOTE: If this issue is happening for 1.94, there is Hotfix for TPA CONT 12 0002.00 Schedule Exception Errors.zip that has been released for this issue. The V1.94 issue is also detailed in Technical bulletin: TPA-BOST-12-0002.00  

Issue Capturing packets from Zigbee Standard Security Network shows packets marked Bad FCS or Encrypted Payload Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Room Controller Cause Zigbee Standard Security Networks implement multiple keys to encrypt data for the Zigbee Network and each device Resolution This resolution assumes you have a Zigbee adapter that can capture packets in Wireshark.   Ensure zigbee_pc_keys are available in each profile you are going to use to analyze the Zigbee packets. The file location is generally: %AppData%\Roaming\Wireshark\profiles\<Profile Name>\zigbee_pc_keys   Open Wireshark and configure the Zigbee adapter NOTE: Please substitute your adapter name if not using the TI CC2531 adapter. Open Wireshark Click the gear next to the 'TI CC2531 802.15.4 packet sniffer' Select the known channel (11-26) and click Save Click on 'TI CC2531 802.15.4 packet sniffer' to start capturing Update formatting to resolve Bad FCS packets Go to Edit -> Preferences -> Protocols Select IEEE 802.15.4 Depending on your Wireshark version, check or "TI CC24XX FCS Format" or set FCS format = "TI CC24xx metadata" Add default link key for Zigbee Alliance Go to Edit -> Preferences -> Protocols Select ZigBee Set Security Level = AES-128 Encryption, 32-bit Integrity Protection Click Edit next to Pre-configured Keys Click + and Enter Wireshark Key from below, Byte Order = Normal, and Label Enter the Zigbee Alliance Default Link Key Key = 5A:69:67:42:65:65:41:6C:6C:69:61:6E:63:65:30:39 Key Value = 5A6967426565416C6C69616E63653039 Remove colons (:) for entry into Wireshark ByteOrder = Normal Label = ZigbeeAlliance09 Find and add Standard Network Key Ensure you have configured the default transport key (above). Use this display filter to find the request Key exchange: zbee.sec.decryption_key Find Standard Network Key Look in the Info column for the Transport Key and select it Expand Zigbee Application Support Layer Command Expand Command Frame: Transport Key to see Key Type: Standard Network Key and Key: shows the value Right-click on the key -> Copy -> Value Right-click on the Zigbee Network Layer Data -> Protocol Preferences -> Open Zigbee Network Layer Preferences Click Edit next to Pre-configured Keys Click + and paste under Key, leave Byte Order = Normal, and add Label. RECOMMENDED: Use Descriptive label because you will have Network Key per Zigbee Network, so includes Device, PAN ID, and NetworkKey, ie ASP087_12345_NetworkKey Find and add Trust Center Link Key PER device Ensure the following are configured: formatting, transport key, and Standard Network Key (above). Use this display filter to find the request Key exchange: zbee.sec.decryption_key Since this is per device, one can include the Network Address for the device. Example: If the network address of the device is 0x2074, the display filter would be: zbee.sec.decryption_key and zbee_nwk.addr == 0x2074 Find Trust Center Link Key per device Using the Info field, find the pair of Request Key and Transport Key. The Request Key will have Source = Device Network Address, and the Transport Key will have the Destination = Device Network Address. Click on the Transport Key packet Expand Zigbee Application Support Layer Command Expand Command Frame: Transport Key to see Key Type: Trust Center Link Key and Key: shows the value Right-click on the key -> Copy -> Value Right-click on the Zigbee Network Layer Data -> Protocol Preferences -> Open Zigbee Network Layer Preferences Click Edit next to Pre-configured Keys Click + and paste under Key, leave Byte Order = Normal, and add Label. RECOMMENDED: Use a Descriptive label because you will have a Key per device, so includes Device, Network Address, and Trust Center Link Key, ie TH907-01_0x2074_TCLK

Issue Creating Folder Structure to Organize Reports Environment SmartStruxure StruxureWare for Building Operation Report Server Cause A large number of reports may result in difficulty navigating the report tree.  The following processes allow you to sort the various created reports. Resolution Creating folders to store the saved reports.  Log into the SQL Report manager from the reports Server using the URL http://localhost/Reports   or  http://localhost/Reports_SQLEXPRESS     Open the folder you wish to add new folders to.  For this example I will use the Production reports folder.   Click "New Folder" Name the Folder and click OK NOTE: In order for the Folder to show up in the reports Server, it will have to have at least one object inside of it. You can move any report to the new folder by clicking on the drop down beside it and selecting "Move". Updating the StruxureWare reports Server to display the new folders  Connect to the StruxureWare Web Reports interface, using an account that is part of the Reports Administrators group. Click on Report Packs. At the bottom of the Screen click "Synchronize" This must be done to apply any changes made in the SQL Report Server Web interface to the StruxureWare Reports Server Saving a Reports parameters for quicker access.  You may wish to save a report to quickly run last months Trend Data. This type of saved report is referred to as a "Dashboard Report" Run the report you wish to save, using the desired parameters Above the report, click Save As In the Report name Field, type the Folder name and report name that you wish to use. NOTE you are limited to 30 characters for the report name. Be sure to check the "Dashboard report" option. Without this option checked you will be making a duplicate of the original report. The Dashboard Report option saves the parameters you have selected. Click "Save as"

Issue LOYTEC NIC-USB card shows offline in NL220 Cannot communicate to NIC-USB card when opening NL220 Product Line TAC Vista Environment NL220 NIC-USB Loytec Cause Proper setup of a NIC-USB in NL220 is required in order for the NIC-USB card to be able to communicate with NL220 or TAC Vista Server.  Resolution A tool called LConfig need to be installed on the computer before the configuration. Click here to download and install  the configuration tool (NIC - LOYTEC Network Interface Software 4.1.4). Connect the NIC-USB to the computer Use LConfig (Start/All Programs/LOYTEC Network Interface/Lconfig) to configure the NIC-USB Choose the USB tab Check "Enable USB Network Interfaces" Click "Test Device/Serial Number" Go to NL220. In the project open window, select the correct NIC-USB in the "Network interface" box. Click "OK"

Issue How to set up a MicroNet Mi for use on a Xenta 555 Product Line Satchwell MicroNet Environment MicroNet Mi Xenta 555 Cause Installation instruction for setting up MicroNet Mi with Xenta 555. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Cold start the MN50-Mi-ARC or MN-MI-100 with ARCnet card (MN-Mi). Unplug any RS 232 cables that are connected to PL3 or PL4. Energise the MN-MI and verify that the RUN LED flashes at about once per second. Set all bit switches to off. Place bit switch 8 to the on position and then return to OFF position. Place bit switch 1 to the ON position. Place bit switch 8 in ON position and then return to OFF position. The RUN, WINK and MODEM LEDs remain lit for about 1.5 seconds, and then the RUN LED should flash at about once per second. Note: This is different from the cold-start procedure for a controller, which requires you simply to toggle switch 8. Plug the RS 232 cables to PL3 or PL4. Connect the Xenta 555.

Issue Can not logon with the Mobile App Building Operation Technician Tool.  Logon screen appears but app closes after selecting Logon No objects are displaying in my Custom View folder or other locations  Can not view or acknowledge alarms My alarm display colors as set in Workstation are not displaying correctly in the mobile app  Product Line EcoStruxure Building Operation Environment Building Operation Technician Tool 1.0.0 / 1.1.0 Building Operation Enterprise Server and SmartX Server 1.9.3 and below Cause May be various cause that are not allowing the Mobile App to connect to the server (Enterprise or Automation Servers), including EcoStruxure Web Services (EWS) Configuration Setting, folder names, User permissions and Alarm configuration.  Please review the different options below for assistance. Resolution Please note: Mobile experience to be replaced with EcoStruxure™Building Operation v2.0 WebStation For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool   When logging into the Technician Tool it times out This has been seen before and was caused by the Windows Firewall. If you are able to ping back and forth between the enterprise server and iPad/iPhone, then it may be a firewall issue. You can either shut down the Windows Firewall or use Creating Windows Firewall rules to allow StruxureWare Building Operation to communicate on the TCP port to set up firewall rules.  Unable to connect to server or "Contact  technical support" message given When logging in to the Technician Tool, specify the HTTPS port in the SERVER field (EX: 192.168.10.20:446).   The mobile app uses the feature from Building Operation StruxureWare call EcoStruxure Web Services, as such a majority of issues can stem from this setting.  If you are having issues logging into the Enterprise Server or Automation Server using the Technician Tool check the following: Software installed on both the Enterprise and Automation Servers must be 1.3.0.938 or later? Ensure the EWS Server Configuration settings are enabled in the server. As a minimum Serve Value and Serve Alarm must be set to true Browse allows object to browsed if not set, no objects will be displayed Ensure the user has sufficient permission to log in and MUST be member of the default domain Values are not displaying in the Custom View folder or other locations Custom View folder must be located in the root directory of the Enterprise Server Check the EWS Configuration settings and ensure Browse is set to true - refer to item 2.2 above. In the EWS Configuration there is a tab labeled "Filter Hardware Folder"; Filters can be assigned By Path or By Object, check that the nominated folder or object has been filtered. Can not view or acknowledge alarms In the EWS Configuration settings ensure that the Alarm Acknowledge setting is set to true. Also check that the Alarm has no additional 'Enforcement', such as Cause / Action - these alarms can only be acknowledge through Workstation. My alarm display colors as set in Workstation are not displaying correctly in the mobile app Unfortunately the Alarm colors are hard coded within the Mobile App - this feature may be provided in a future release.  Date for this is currently unknown.

Issue Uninstall Process for Web Reports Product Line EcoStruxure Building Operation Environment SmartStruxure Web Reports Server StruxureWare for Building Operation Web Reports Server Cause After a re-install of webreports, certain features will not function if the original version was not completely removed. Resolution To uninstall WebReports: In Windows Control Panel, point to Programs and then select Uninstall a Program. Right-click StruxureWare Report Pack Installer and then click Uninstall. Right-click StruxureWare Reporting Agent and then click Uninstall. Right-click StruxureWare Reports Installation and then click Uninstall. Right-click StruxureWare WebReports and then click Uninstall. Right-click StruxureWare WebReports Service and then click Uninstall. In your Web browser, type the URL for SQL Server Reporting Services Report Manager. If you have installed SQL Server 2008 R2 Express, the URL is http://localhost/reports_sqlexpress Click Details View. Select the folders that contain the WebReports reports including Data Sources. Click Delete. Click OK. Click Close. Open Microsoft SQL Server Management Studio (type SQL in the Start menu Search box). Expand the Databases folder. Right-click StruxureWareReportsDB and then click Delete. In the Delete Object window, select StruxureWareReportsDB. Select Close existing connections. Click OK. Open Internet Information Services (IIS) Manager (type IIS in the Start menu Search box). In the Connections pane, expand Sites, expand Default Web Site, and then expand SchneiderElectric. Delete each virtual directory in the specified order: - Right-click WebReportsService and then click Remove. - Right-click WebReports and then click Remove. - Right-click SchneiderElectric and then click Remove. - In the Connections pane, select Application Pools. Right-click SchneiderElectric.WebReportsAppPool and then click Remove. Right-click SchneiderElectric.WebReportsServiceAppPool and then click Remove. Exit Internet Information Services (IIS) Manager. In SQL Server Reporting Services Report Manager (see previous steps), click Folder Settings. Select the NT AUTHORITY\IUSR check box and the [PC NAME] \appuser check box, and then click Delete. Exit SQL Server Reporting Services Report Manager. In Windows Control Panel, select System and Security, then select Administrative Tools. In Computer Management, expand Local Users and Groups and then select Users. Right-click appuser and click Delete, then follow any further prompts to complete the deletion. In Microsoft SQL Server Management Studio, expand Security and then expand Logins. Right-click the appuser account and then click Delete. In the Delete Object window, select appuser. Click OK. Click OK again. Right-click NT AUTHORITY\IUSR and delete it in the same way as you deleted the previous (appuser) account. Right-click [PC NAME] \appuser and delete it in the same way as you deleted the previous (appuser) account. Exit SQL Server Management Studio. In Windows Explorer, expand Program Files (x86) and then expand Schneider Electric. Right-click StruxureWare Reports Installation and then click Delete. Right-click StruxureWareReports and click Delete, then follow any further prompts to complete deletion.

Issue Receive error stating that a Menta "File object is locked by another application" when trying to open it for editing. Product Line TAC Vista Environment TAC Vista Menta Cause There are several potential causes of this error: The Menta (.mta) file is already open locally or on a remote machine. The current user does not have the appropriate authority to edit the file. Menta crashes while editing a file opened directly from the Server. Each subsequent attempt to launch the Menta editor from Workstation will result in this error. When a "standard" Menta file is being used and the user attempts to edit the Menta file locally. For more information about this scenario, please see "Read-only because object refers to a standard file" when editing Menta from Workstation. Resolution The following resolutions correspond to the causes listed above: If an instance of Menta already has the file open, whether on the local computer or on a remotely connected computer, then it must be closed before trying to open and edit that particular Menta file again. If the current Vista user has only "User" privileges or is otherwise limited from editing Menta then a user with the appropriate authority should log in to open the Menta file for editing. Shut down then restart Vista Server and Workstation if the error was caused by Menta crashing. See the link in Cause D above.

Issue The nvoEffectSetPt is different than the nviSetPoint The nvoEffectSetPt is different than the cooling or heating setpoint (SCPTsetPnts) Product Line EcoStruxure Building Operation, TAC Vista Environment Xenta 102-AX Cause The nvoEffectSetPt is calculated according to nviSetPoint, cooling or heating setpoints (SCPTsetPnts), nviStPointOffset, and thermostat offset. Resolution The nvoEffectSetPt is a SNVT network output in Xenta 102-AX and represents the current effective setpoint that the controller is utilizing in its control loop. nvoEffectSetPt can be configured to display in two different manners: Actual and Normalized. (As defined bynciVAVselctcCntl.oP.ESS (UCPTvavSelection)) Actual nvoEffectSetPt displays the setpoint that corresponds to the currently active application mode of the controller (occupied cooling, unoccupied cooling, standby cooling, occupied heating, unoccupied heating, and standby heating). Normalized nvoEffectSetPt displays the average of the cooling and heating setpoints for the currently active occupancy mode (occupied, unoccupied, standby). NOTE: Whether nvoEffectSetPt is set to Actual or Normalized only affects how the effective setpoint is displayed and does not affect how the application operates. The 102-AX application utilizes the setpoint that corresponds to the currently active mode (occupied cooling setpoint, etc.). In addition, the thermostat adjustment of the setpoint will not appear in any SNVT in Xenta 102-AX controller. This offset is captured in the Xenta 102-AX's memory, and although it is not displayed, it is utilized into the nvoEffectSetPt calculation. Also note that the below scenarios only apply to the occupied and standby modes since the unoccupied setpoints are unaffected by nviStPointOffset, nviSetPoint or by the thermostat offset. Scenario 1: nviSetpoint is unused 1.1 Actual nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the sum of one(1) of the four setpoints (occupied cooling, standby cooling, occupied heating and standby heating) plus the offsets (nviStPointOffset and thermostat offset). 1.2 Normalized nvoEffectSetPt calculation: In this scenario, the nvoEffectSetPt is the average of heating and cooling setpoints ( 1/2(Occupied Cooling Setpoint + Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint + Standby Heating Setpoint) ) plus the offsets (nviStPointOffset and thermostat offset).   Scenario 2: nviSetpoint is used 2.1 Actual nvoEffectSetPt calculation: In cooling mode, the nvoEffectSetPt is the nviSetPoint plus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint -Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ),  plus the offsets (nviStPointOffset and thermostat offset). In heating mode, the nvoEffectSetPt is the nviSetPoint minus half of the difference between cooling and heating setpoints ( 1/2(Occupied Cooling Setpoint - Occupied Heating Setpoint) or 1/2(Standby Cooling Setpoint - Standby Heating Setpoint) ), then plus the offsets (nviStPointOffset and thermostat offset). 2.2 Normalized nvoEffectSetPt calculation In this scenario, whether the application is in the cooling mode or the heating mode, the nvoEffectiveSetPt is the sum of the nviSetPoint and the offsets (nviStPointOffset and thermostat Offset). Therefore, when nviSetPoint is used and nvoEffectSetPt is to Normalized, the actual heating and cooling SCPT setpoints do not matter; only the difference between them is significant. For example, setting occupied cooling and heating setpoints to be 75°F (24°C) and 65 °F (18°C) will give the same resulting nvoEffectiveSetPt as setting occupied cooling and heating to be 45°F (7°C) and 35°F (1°C).   Example Occupied Cooling = 72°F (22°C), Occupied Heating = 68°F (20°C), nviSetPoint = 75°F (24°C), assuming the nviStPointOffset and thermostat offset are zero. nvoEffectSetPt in Occupied Cooling or Heating Mode   Scenario 1.1 Scenario 1.2 Scenario 2.1 Scenario 2.2 Cooling Mode 72°F (22°C) 70°F (21°C) 77°F (25°C) 75°F (24°C) Heating Mode 68°F (20°C) 70°F (21°C) 73°F (23°C) 75°F (24°C)

Issue What is a MIP? Environment I/NET site Cause What is a MIP board? Resolution The Memory Interface Processor (MIP) is a plug-in module that provides significant functional and speed enhancements to TAC products. It provides increased processor performance and enables 96 K of on-board RAM for I/NET-related processing. The MIP is installed by removing the process and other memory chip(s). (The MIP is not designed to be used with all or our products!) Refer to TCON101 and TCON123.