Building Automation Knowledge Base

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 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 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 Infinity controller error: Type not valid for this IO channel Product Line Andover Continuum Environment Continuum Cyberstation Cause ElecType mismatch between what is in the database and the field controller hardware. An example of this problem would be offline creating a voltage output on a DO-4.  It will save to the DB since it is a valid InfinityOutput configuration.   Although when attempting to do a Send to Controller the controller knows that point type is not valid on the specific IOU module hardware. This can also happen when an object is imported into Continuum because the database error checking is less strict than when creating the object online. Resolution Go into offline editing Check the point configuration If it does not match the field hardware, then correct it, save it, go to online mode and reload.

Issue Import Export table and alarm delivery troubleshooting procedures for CX, Infinet controllers, and Cyberstation Environment CX Infinet controllers Cyberstation Cause The below troubleshooting outline can be used when trying to determine why point values are not being transferred from one controller to another. Also there is a section to troubleshoot why alarms are not being delivered correctly from the controllers. Resolution Programming import export problems: Open point editors for the source and destination points, verify whether or not the point value is being transferred. If the values are not being transferred then verify the program that is transferring the values is enabled and active. If the program is disabled then go to the runtime tab and determine why the program is disabled. If the program is not disabled then manually run the program, if it is a fall through, and see if the values update. If the values update when manually running the program then the problem is not an import/export problem but a programming problem. If everything with the programming side of things checks out then get a dumb terminal dump of the source and destination controllers. Use the command “Dump All” at the R prompt through dumb terminal. Look at the Import/Export entries in the source controller’s dump file and see if the Import/Export entry is in the dump file in the Import/Export section of the dump file. The format of the entry should look similar to the below. If the Import/Export entry is in the dump file then the problem is not an import/export problem but more than likely a communications problem. Verify the integrity of the Infinet bus and see if there are any problems there. If the bus integrity looks good then the problem could possibly be an intermittent communications problem. If the transfer of these point values are critical then one recommendation would be to add a “Point refresh” program that runs at certain intervals. If the import/export entry is not in the controller dump file then try selecting the first option, “Do not reload attached objects”, in the “Send to Controller” options and reload the controller. What this will do is resend just the Import/Export table down to the controller. Check to see if the point is now sharing correctly via the point editors. If so then the problem was a corrupt Import/Export entry in the controller. If the problem still exists then go to the next step. If the problem is still there then get another dumb terminal dump of the source and destination controllers and verify whether or not the Import/Export entries are in the controller. If the entries are there then review step 5. If the Import/Export entries are not there then run the Import/Export fix up utility against the database and repeat steps 6 through 8. If after going back to steps 6 through 8 the entry is still not there then backup the database and send it to TSD with all the specifics on the points that are not sharing, controller names that owns the points, and programs that transfer the point values. Open the point transfer program and re-save it. Go back to step 7 only.   Alarm Import/Export problems. The below describes how to check to see if an alarm delivery problem is Import/Export table related. Did the alarm get logged into the database? If the alarm did get logged then this is not an Import/Export problem. If the point is still in alarm does the point editor reflect that the point is in alarm? If not then this is not an Import/Export problem. If the point is in alarm and it is not logged check the NewAlarmCount system variable on the CX level controller. If the value of NewAlarmCount is NOT zero then this is not an Import/Export problem. If the point is in alarm and the NewAlarmCount system variable in the CX is zero and the alarm is not logged then this could be an Import/Export problem. If you disable the point and cycle it out of alarm and then back into alarm does the alarm come in? If the alarm comes in then this is more than likely a communications problem and not an Import/Export problem. Check the Continuum error log and see if there are any errors being posted for the delivery if this alarm. Run the ACCTrace utility, from the workstation that is supposed to be logging the alarm, when cycling the point in and out of alarm. Send trace file to TSD for review. To determine which workstation is logging the alarms use the below calculation: The Netcontroller will take it’s own AccNetid and mask it with 63 stripping off the 2 high bits of it’s id leaving a result in the range of 1 to 63. For those of you who are binary mask challenged, NetControllers with Ids between 1 and 63, result is their ID NetControllers with Ids between 64 and 127, result is their ID - 64 (ID range of 0 to 63) NetControllers with Ids between 128 and 190, result is their ID - 128 (ID range of 0 to 62) That result is then added to 190 and that is the ID of the first Workstation to get the Alarm and Log it in the Database. If there is no Workstation with that ID (or the workstation with that ID is offline), the NetController will send the alarm to the Workstation with the next highest ID above the one calculated by the ratcheting algorithm. If no Workstation Ids are higher than the one calculated, the routine will loop around and use the lowest Workstation ID to send to first. Do a dumb terminal dump of the controller that is having the problem. The command to dump it is “Dump All”. Capture this dump file to a text file and check the Import/Export table section of the dump file. The Import/Export section of the dump file should have an entry for the points that have alarms attached to them. The format of the entry is: pointname  to Alarm. If the Import/Export entry is in the dump file then the problem is not an import/export problem but more than likely a communications problem. Verify the integrity of the Infinet bus and see if there are any problems there. If the bus integrity looks good then the problem could possibly be an intermittent communications problem. If the transfer of these point values are critical then one recommendation would be to add a “Point refresh” program that runs at certain intervals. Using the calculation above to determine which workstation is logging the alarm verify that workstation exists in the database. If that workstation does exist in the database make sure that that workstation is pointing to the correct database. We have run into situations where one workstation switches between databases using the same workstation ACCNet ID and IP Address. Doing this will cause problems with alarm and Access Event delivery. If you are doing this kind of installation you must have a unique ACCNet ID and IP address for each database. If the import/export entry is not in the controller dump file then try selecting the first option, “Do not reload attached objects”, in the “Send to Controller” options and reload the controller. What this will do is resend just the Import/Export table down to the controller, it does not reset the controller. Go back and retest the point and see if it goes into alarm and delivers the alarm correctly. If so then the Import/Export entry for the point was corrupted in the controller. If the alarm still is not logged or delivered do step 8 again. If the Import/Export entries are not there then run the Import/Export fix up utility against the database and do steps 10 and 11 again. If the alarm is still not logged then backup the database and send it to TSD with all the specifics on the points that are not sending the alarms. Please include the controller names that owns the point and also what alarm link is not working correctly. Edit the point, remove the alarm attachment and save the point. Then re-edit the point, re-attach the alarm and resave the point. Check and verify that the alarm functions as it should.

Issue A Niagara G3 server station was running well for a long time.  Then in a matter of a couple of days, the station began failing to run.  The error listed in the Application Director Output is:   ERROR [java.lang.OutOfMemoryError: GC overhead limit exceeded 13:46:17 20-Mar-14 EDTjava.lang.OutOfMemoryError: GC overhead limit exceeded][sys.leasejava.lang.OutOfMemoryError: GC overhead limit exceeded] Error in run Product Line TAC IA Series Environment I/A Series G3 Enterprise Server Cause There is not enough memory allocated to the Java Virtual Machine (JVM). The email service is keeping a very large outbox because the network email server's IP address was changed. Resolution Increase the Java Virtual Machine (JVM) memory allocation Using a text editor, open the nre.properties file (located in the niagara 'lib' subfolder on the server hard drive). Locate the line: java.options=-Xmx256M. Change it to java.options=-Xmx512M. Empty the outbox file (i.e. delete it) and/or update the email server's IP address.

Issue Cant login to webstation Loginpage for webstation Environment Vista webstation Cause Mostly  caused by that another process is using the same port as webstation do Resolution Run the command netstat -aonb | find ":80" in the command prompt to see what process PID is taking the port 80, If Vista is using another port change 80 to what port you use. A common scenario is that it is the TAC Vista SmartStruxure interface that is taking the port, and that after a reboot, the interface starts up before the IIS. Change the port used in the interface to something else

Issue How many time schedules (time objects, TSCH, TSCHI) can be added to TAC Xenta programmable devices? Environment TAC Xenta 301, 302, 401, 281, 282, 283 TAC Xenta 527, 511, 711, 721, 731, 701 Menta Cause The limits for schedules are not clearly documented for all types of TAC Xenta controllers. Resolution The TAC Xenta 7xx can handle 50 time objects with 50 week and 50 holiday schedules in each. The limit for the TAC Xenta 28x controllers are one TSCH block with max 16 week/holiday charts. There is no fixed limit of TSCH blocks you can add to a TAC Xenta 30x/40x. The limit is the available memory in the controller. The more times you allow for (max. week/holiday charts) in each block, the more memory it uses.

Issue Should we upgrade to the latest revision for the SCU 1284 If we do not upgrade the SCU will I/NET work properly. Product Line TAC I/NET Environment I/NET Seven Security Control Unit (SCU) 1200 series firmware 3.2x and above Cause The recommendation is to always upgrade to the latest revision. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Resolution I/NET Seven is backward compatible with all previous hardware firmware revisions of the SCU. The recommendation is to always upgrade to the latest revision to enable all of I/NET's features and fixes included in these revisions. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. If you have any additional concerns then please contact Product Support. The following table lists the release firmware revisions and associated fixes and new features: Rev Date DCN Changes 3.21 05/06 5593 Add support for SCU tamper to the SCU1200 and SCU1280 3.22 01/07 5610 Start adding intrusion alarm support to SCUs Add issue level support to SCU1284 Fix defect where deleting last tenant from DPU causes incorrect schedules Add door code 3.23 08/07 5627 Fix defect where changing a door to "unselect" did not prevent access through door 3.24 10/07 5631 Expand individual count from 24,000 to 32,000 per tenant 3.25 07/08 5657 Implement various changes to intrusion alarm system that were identified during EN50131 certification 3.26 01/10 5677 Fix corrupt reader LED due to OP5 monitoring board Fixes to SCU1284 expansion board for IAS power monitoring 3.27 07/11 5717 Make AMT show person who commanded PIN functions 3.28 12/12 5739 Fix for bad card read on reader number 4 with internal AO at bit offset 04 3.29 08/13 5745 Fix so that a change of date from one month to the next will work correctly when using special days 3.30 10/14   Support for 130-bit Wiegand card New event named “Key reassignment” 3.31 12/14 5754 Support for 86-bit Wiegand card For DPU range of controllers refer to I/NET Door Processing Unit (DPU) 7910A / 7920A EPROM Feature matrix.

Issue I have to replace a faulty Xenta 301 but found that the existing Xenta 301 was system version 1. The system consists of about 12 Xenta controllers sitting on a Menta only network using .nwc,ndb network configuration tool. Environment TAC Xenta 300 TAC Menta Cause New devices are delivered with version 3. Resolution As TAC Xenta system program version 1 and version 3 can not work on the same network, downgrade the new device to replace the faulty one. Download TAC Xenta 300 system program version 1.17 Use Download Wizard as normal to download the system program, however, going from version 3 to version 1, do NOT keep old application in the Download Wizard. Select Clear Application. Download the Menta application and network configuration manually via the serial cable. You could use the actual TAC Menta versions to do this.

Issue ALARM blocks can be added to an SBO Function Block application, but it is not possible to set delay, priority or alarm text parameters from within the Function Block Editor.  Also, the preceding block is assigned an auto-generated name and public status, if it did not already have a name. Environment SBO 1.5.0 and earlier. Function Block Editor Cause When an alarm block is added to a Function Block program an alarm object is automatically created in the SBO System Tree, below the FB program object.  By default, the alarm object is not visible until the filter 'Show non-presentation objects' is set The public block preceding the alarm block is required so that the alarm object in the System Tree can have a Monitored Variable reference.  The 'Function Block Editor and Menta Editor Difference Guide 04-15010-01' states that 'The function block programs still need the ALARM blocks, but the blocks only serve as inputs and outputs to the alarm functions..'.  This is misleading as you do not need to explicitly create an external alarm object - all the usual alarm properties are available in the automatically generated alarm object, once it is made visible. Resolution Set the System Tree filter to 'Show non-presentation objects'.  Then set the required alarm properties in the displayed alarm object below the FB program object.

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 create a new database or purge a full SQL (i.e. it has hit the limit of 2G) Product Line TAC Vista Environment TAC Vista 4.X Cause Log data has filled the 2GB limit of the SQL database. Resolution How to purge a full SQL (if you've hit the limit of 2G) Before deleting the database or creating a new one: Check the $queues/insertevents and $queues/insertlogvalues folders in the Vista database. This folder may contain "queued" files waiting to be written into the SQL database. If these queues have significant amount of data stored as a result of the SQL being full, you may delete these files if the data is not needed. If the data is needed, it will be written to the new SQL Database when Vista starts. In some cases, the $queue folders may be so large that even creating a new database won't allow the Vista Server to run. If this is the case and the $queued items are not needed, delete them from their directories. If you find that there is an abundant amount of queued files it may be easier to delete them using DOS. This can be done by navigating using the "cd" and "cd.." command prompts to c:\TAC\Vista\VistaDb\$queues. There you will find \insertevents and \insertlogvalues. You can clear both directories using the "del" command. It is recommended to stop the SQL Server and DSS Writer before attempting to delete any queued files. You can stop the SQL Server by double-clicking on the icon in the task bar and choosing to "Stop". You can locate the DSS Writer by right-clicking on My Computer and selecting "Manage". Navigate to "Services and Applications\Services" directory and look for "TAC DSS Writer Service". Right click on this service and select Stop. If the data is not needed: Simply go to ...Microsoft SQL Server/MSSQL$TACVISTA/Data and delete the old database. Before doing so, you may need to stop the SQL Server.  Then following steps in "If the data is needed" section below. If the data is needed: The simplest way to get a fresh DB is to create one. This is done using TAC Vista SQL Setup which can be downloaded from the Buildings Business Extranet: Global. Make sure that you download the SQL Setup for your Vista product version. In the Vista SQL Setup program, select your SQL Server - pcname\TACVISTA, Chose Windows Authentication if Vista is managing the Database (recommended in the Vista Install), "Login", enter the name of the database (perhaps "NEWtacdatalog" to be created, and select the login pcname\TACA_pcname, and "Create". This will create a new database to which you can now point the Vista Server. In Vista Server Setup, under the SQL Tab, change the database to this newly created database, click "OK". You can keep the old database to export for viewing or if you plan on upgrading to SQL Enterprise and merging the data in the future.   NOTE: Sometimes when this is done without first detaching or deleting the database from the SQL, the DSSwriter or TACA user stops working. Detach/Delete the database with SQL Management Studio Express and reinstall the system to solve this.  

Issue The Save to Flash exclamation point (bang) on a Controller object, does not go away even after a valid save to flash is performed on the controller. Product Line Andover Continuum Environment Continuum Controllers Cause An InfinityNumeric with its Setpoint attribute set is changing value frequently. With this Setpoint attribute set, every time the object changes value, the controller sees that the change needs to be applied to the flash as well. This changes the ObjectStatus of the Controller Device object to indicate a Save To Flash is required by  showing the exclamation point (bang) on the controller. Resolution Check if you have any InfinityNumeric points with the "Setpoint" flag set that update frequently. In ContinuumExplorer, under the controller object, right-click the InfinityNumeric default class folder and select "View". This will launch the object class listview for this controller. Add the Setpoint attribute by selecting View -> List View Configuration. Select columns tab, click "Add Column". Select the Attribute field in your new column and from the drop down select "Setpoint". Apply your Changes and refresh the ListView. The InfinityNumerics that have the Setpoint value of True are the ones you want to look at closely to determine which ones are changing value frequently and if they really need to be configured as a Setpoint.  Also, refer to Save to Flash exclamation point indicates that the controller 'requires flash backup'.

Issue A TGML Graphic is added or imported into Vista. Then when you right click on the TGML Graphic and select " Open Bindings Window" a blank bindings window is opened. None of the objects defined in the TGML Graphic appear in the binding list to be bound to objects in the Vista database. Environment Vista 5.1.7 Cause The TGML Graphic is named with .(dot) characters in the name. E.G. VAV1.1.7 Resolution Do not use dots, dashes or hyphens in the naming convention for any Vista objects. Either eliminate it altogether, or use underscores (_) instead. To correct this issue after the TGML Graphic has been added  with the incorrect naming convention, is: Edit the TGML Graphic and save it out of the database. Delete the TGML Graphic with the name including the . (dot) character. Add a new TGML Graphic using the correct naming convention E.G. VAV1_1_7 Open the TGML Graphic that was saved out of the database and save into the new TGML Graphic you created with the correct naming convention. Note: Renaming the TGML Graphic object from VAV1.1.7 to VAV1_1_7 in the Vista database does not fix the problem.

Issue webClient schedules getting error 'request for permission of type' system.security.permissions Product Line Andover Continuum Environment webClient Cause Require to run the Caspol commands. Resolution Run the Caspol commands, here is a batch file that runs these commands without typing them in. Click Here to download the batch file   Rename the caspolwebclient.txt to .bat Run the batch file at each WS that needs to access webclient schedules. Below are the actual commands: 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 In some configurations, you may need to add the IIS computer into Internet Explorer as a trusted site for each browser. Internet Explorer > Internet Options > Security > Click trusted Sites > Click Sites Type in http://yourservername/webclient and click Add (Ex. http://tacweb/webclient) Deselect the checkbox for Require server verification (https:) for all sites in this zone. Click OK and Ok Close Internet Explorer and access webclient See Removal of MS KB2858725 Dot Net 4.5.1 causes issues with Web Servers IIS Functions if this is for 1.94 SP1 - Uninstalling KB2858725 * It may be necessary to give specific permissions in the registry if you are seeing system.permissions.UIPermission, mscorlib Make a backup of the From Windows, Start> Run> Regedt32.exe Expand the hives(folders) to HKEY_CLASSES_ROOT\CLSID\{00B01B2E-B1FE-33A6-AD40-57DE8358DC7D}\InprocServer32\2.0.0.0 Right Click on 2.0.0.0 and select export, name the file and save. (This file can be used to restore the original settings of this branch)  Right click on this folder again and select permissions, select Users and add Full Control See below for snapshots

Issue Copying objects from one MP-X device to another results in a validation error. "Property value '<object type>' already assigned"     Product Line MPx series EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Cause The Object ID is already used within the destination device Resolution This functions as design. To resolve this:   Manually enter the Object ID when creating files that may be copied to other MP-X devices. One may choose to use blocks of IDs up to 64,999.   2. Utilize the import/export function within EBO which will import the BACnet objects using the next available Instance IDs.

Issue What is Remote Client with I/O in the Workstation Type in the I/O Server? Product Line TAC INET Environment I/Net Seven version 2.4x with need for Remote Client configuration using a Remote SQL Server. Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause Remote Client changes with I/Net Seven version 2.4x  Resolution The new option of Remote Client with I/O for the Workstation Type begins with 2.4x version of I/Net Seven. This option is for a SQL Server which is not located on the Filemaster or Standalone but rather a separate Server. The Remote Client with I/O must be running for other standard Remote Clients to get the features such as AMT, Trends, and Network Functions. Network Functions can be found in I/Net on the pull down menu Edit/Host Computer/Network Functions. The configuration is in the I/O Server under the current profile and can be found in the Workstation Options.  HINT: Exit the I/O Server (and I/net) and select Start/Programs/I/Net/I/Net Configuration to be able to setup the Remote Client. Remote Client is not show unless you exit I/O Server. Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Remote Client with I/O. I/Net version 2.4x Remote Client with I/O Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Filemaster, Equalized Client, or Remote Client. I/Net version 2.4x Filemaster, Equalized Client, or Remote Client Suggestions for further info: To install the SQL, go to Installing I/NET Seven on a 64-bit operating system. For more on how to set up that Remote Client with I/O to use that SQL database, see Unable to connect Remote Client to Standalone Server. 

Issue The Wonderware Temporary License is out of date. How can a new one be obtained? Environment WonderWare Cause Since Schneider Electric (Rockford) is no longer a Wonderware OEM software distributor, demo licenses can no longer be provided. Resolution The 30-day temporary Wonderware demo mode license is available to the Wonderware SI selling the Wonderware software.

Issue Digital Sentry and Endura VMS systems have specific cameras and firmware that are supported by the Continuum Integration Product Line Andover Continuum Environment Continuum Digital Sentry Endura 2.0 Cause In the past the video compatibility matrix was very specific about what vms firmware versions and cameras were tested and supported by Continuum. As of 2.02 and above, Continuum is relying on Pelco's testing of specific cameras with either Digital Sentry or Endura and this article lists those specific links. Only the Digital Sentry link was in the 2.02 Video Compatibility Matrix. Resolution Video Matrix for 2.02 - Download Here Pelco cameras supported by Digital Sentry v7.15 : http://partnerfirst.pelco.com/content/digital-sentry#sthash.ZkEtYiZd.w16va5xk.dpbs Pelco cameras supported by Endura 2.0: http://partnerfirst.pelco.com/content/endura#sthash.ii8IYPqC.dpbs Pelco support indicates that the camera compatibility lists are for specific models, not for a certain series of camera. i.e. IME22 doesn't mean the IME22x is supported.