Building Automation Knowledge Base

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 What does it mean when a TAC controller is said to have a Universal Input? Environment Xenta Programmable Controllers Xenta I/O modules Cause Universal typically means all types; however, this definition does not apply to TAC Xenta controllers. Resolution With respect to TAC Xenta controllers, the term "Universal" means more than one type of input. It is important that the project planner review the data sheet to determine the exact definition for "Universal" as it applies to any TAC Xenta device.

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 When attempting to login to the hosted instance, the below error is received indicating that the user is already logged in. Product Line EcoStruxure Access Expert Environment V2 Hosted Instance Cause There are two things that can cause this- A user can only be logged into a single instance at any given time. The user may currently be logged into a different instance. The user did not correctly log out of the instance they are attempting to access, and therefore is still logged in.  Resolution Take the following steps to resolve each of the two causes: Ensure that the user is not logged into any other instances. When closing out the web browser it is necessary to log the user out, as opposed to just closing the web browser. Failure to log out prior to closing the browser will result in this error.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Creating a report that shows which visitor is being visited Product Line EcoStruxure Security Expert Environment Security Expert Controller Cause The standard visitor report does not record who at the site is being visited Resolution This video demonstrates how to create a visitor report that includes which users have been visited in the Security Expert System.   The advanced Visitor Report is created in 4 main steps: 1. Create an Access level for each user who receives visitors 2. Assign this Access level to the user's visitor tab 3. Create (or use existing) User report with the new "access level" column selected 4. Configure and run the user report   Creating Access levels 1. In Security Expert client, go to Users|Users a-Select a user who receives visitors (ex: John Doe) b-Go to the Visitor tab c-Check the "User supports visitors" box d-Click the ellipsis (3 dots) to open the Access Level window e-Click Add button f-Name it '[User]'s Visitors' (ex: John Doe's Visitors) g-In the configuration section, configure the access level required for the user's visitors h-Save and repeat for each user who normally receives visitors. Close the window and go back to the User table.   Assign Access level 2. Select "John Doe's Visitors" for Visitor access level -Save changes   Create User Report 3. Go to Report|Setup|User -Create (or use existing) report for visitors -Go to the Columns tab -Click Add and choose "Access Level" User Field -Save report setup   Configure User Report 4. Return to the general tab and expand the "Default user report filter" section. Press "edit in report view" and edit your desired layout -Save report view   The next time you run the visitor report it will print who's being visited in the "Access level 1" column

Issue Want to be able to run the SE7200 in floor heating and chilled beam simultaneously. Environment SE7200 Cause running simultaneous applications. Resolution Unfortunately the SE7200 will only handle 1 main application per controller due to its limited I/O.

Issue Need an example on how to program a required action where a Door Switch activation triggers alarm sounder to turn on and stay on until a Key Switch is closed. Product Line EcoStruxure Security Expert Environment Security Expert Cause Require a programming example. Resolution There may be a number of ways of doing this, one solution is to have a Door Switch trigger an alarm in the Door's Area which triggers an Alarm Output to turn on. A Key Switch Input is linked to another Automation Area that will disarm the Door's Area which turns off the Alarm Output.   In this example we will use the following objects: Input        Door_Switch_Input Input        Key_Switch_Input Output        v_Alarm_Output        (a virtual output for this test) Area        Door_Opened_Area Area        Area_Automation Input Type        KeySwitch_InputType   Setup 1. Create an Output, in my example this is virtual output v_Alarm_Output. 2. If not already created create the Area your Door is located, in my example I created Door_Opened_Area.   3. On the CONFIGURATION tab set the alarm timings to 0. 4. On the OUTPUTS tab set the Alarm Memory Output to your alarm output. 5. create the Area that will be used as an automation area to reset the door alarm. In my example I created Area_Automation for this purpose.   6. On the CONFIGURATION tab set the alarm timings to 0. 7. Create a new Input Type, in my example this is KeySwitch_InputType. On the GENERAL tab set the Control Area to the area with your door switch in it. (Door_Opened_Area) 8. On the OPTIONS (1) tab, under MISCELLANEOUS OPTIONS, set the Disarm Control Area On Input Restore and Arm Control Area On Input Alarm options. 9. If not already created, create your door switch input. In my example this is Door_Switch_Input.   10. On the AREAS AND INPUT TYPES tab set the Area to your door area and the Input Type to Instant. 11. If not already created, create your key switch input. In my example this is Key_Switch_Input.   12. On the AREAS AND INPUT TYPES tab set the Area to your automation area and the Input Type to the input type you created earlier (KeySwitch_InputType). 13. Go to a Status Page view with these two Areas listed and disarm then arm each of them. This needs to be done after any change to the Area or objects within it (such as inputs) so they will function properly with the new changes.   Notes: KeySwitch = Closed -> Alarm disarmed (Area_Automation) KeySwitch = Open -> Alarm armed (Area_Automation) To disable alarm and reset area, KeySwitch must be Closed and then Opened. DoorSwitch needs to be closed for Alarm to be re-enabled with KeySwitch.   Usage 1. Armed normal state. 2. Door Alarmed. Door_Switch opens triggering alarm in Door_Opened_Area triggering v_Alarm_Output to turn On. 3. Alarm silenced by Key_Switch. Key_Switch is Closed triggering Door_Opened_Area to be disarmed and v_Alarm_Output to turn Off . Key_Switch is Opened triggering Door_Opened_Area to re-arm. 4. Alarm will not re-trigger again until Door_Switch is closed and Area re-armed.

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 What is the part number for the battery in a Network 8000 GCM? Environment Network 8000 GCM-84000 series, GCM-86000 series, LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK. Network 8000 LCMs. Cause Need to replace a discharged  battery in a GCM or an LCM. Resolution The part number for the replacement battery is E17-129. NOTE:  The E17-131 is a functional replacement for the E17-129 which is now obsolete.  The E17-131 can be found on iPortal   For a GCM-86000 series, LNC-100, SIM-CCN, SIM-MTECH, SIM-TRANE, and SIM-YORK, replace the battery according to F-25895, GCM-861X0 Series Global Control Module Installation Instructions, "Battery", "To Enable Battery", "To Replace Battery", and "Checkout" sections. For a GCM-84000 series or an LCM, replace the battery according to F-23116, "LCM / GCM Battery Installation Instructions".

Issue Sensors required Environment DC1400 sensors Cause What sensors does the DC1400 optimiser/compensator require? Resolution Old        Description                                                                       New Part Number Spec DRT3454    ROOM SENSOR                                                      STR600/004604100 DOT0002   OUTDOOR SENSOR                                               STO600/5126060000 DWT0001  IMMERSION SENSOR                                              STP660/5126080000 (NO POCKET SUPPLIED) DST0001   STRAP ON SENSOR                                                STC600/5126070000 Pockets available: DWA0001    BRASS POCKET ADAPTOR                                 9121058000 DWA0002    IMMERSION STAINLESS POCKET 120MM           9121060000 DWA0003    IMMERSION BRASS POCKET 200MM                  9121062000 DWA0004    IMMERSION STAINLESS POCKET 200MM           9121064000 DWA0005    IMMERSION BRASS POCKET 120MM                  9121066000

Issue After an install of webclient 1.80/1.81 on Windows Server 2003 you receive the following error opening webpinpoint graphics: Could not find pin file at specified URL. Please contact your system administrator. Environment webpinpoint 1.80/1.81 Cause .PIN and .EMF file extensions have not been registered in the IIS MIME Types (for webClient Pinpoint graphics). Also, an IP conflict with another PC can cause this.   Resolution Webpinpoint is installed properly when first opening a graphic, you can browse to the NewGraphicsFiles folder through Internet Explorer and the web folder tab in Cyberstation pinpoint options resolves properly without Red Xs. To fix this, follow the instructions on Pg 32 in the Webclient 1.80/1.81 Installation Guide as follows Registering File Extensions for Server 2003 after IIS Installation: If you have a Windows Server 2003 system, you must also register the .PIN and .EMF file extensions in the IIS MIME Types (for webClient Pinpoint graphics). After IIS installation, follow this procedure: From the Control Panel, double click and open Administrative Tools. The Administrative Tools dialog appears. Double click and open Internet Information Services (IIS) Manager. The Internet Information Services (IIS) Manager dialog appears. In the tree, right click on the machine name, and select Properties from the popup menu. Click the MIME Types button. The MIME Types dialog appears. Click the NEW button. The MIME Types dialog appears with 2 empty fields In the Extension field, enter: .pin and in the MIME type field, enter: pinfiles/plain. Click Ok Click the NEW button again, but in the Extension field, enter: .emf and in the MIME type field, enter: image/emf Click OK three times back through the dialogs. Restart your machine and open webpinpoint

Issue Which CD Keys can be used with which version of I/NET Seven Software? Product Line TAC INET Environment I/NET Seven - all revisions. Cause Need to know which CD Key can be used with which version of I/NET CD Resolution The I/NET CD Key is comprised of User Name Site Name Key; provided in the format XXXX-XXXX-XXXX-XXXX-XXXX. The key provided above is a 20 character key, segregated into five 4 character sets.  The second set of four characters (shown in bold and underlined above) and using the table below, will help identify which version of I/NET Seven Software works with which CD-Key:   I/NET Seven Version CD Key I/NET Seven 1.xx XXXX-D71R-XXXX-XXXX-XXXX I/NET Seven 2.00 to 2.31 (Excluding 2.30) XXXX-E71R-XXXX-XXXX-XXXX I/NET Seven 2.30 (Only) XXXX-F71R-XXXX-XXXX-XXXX I/NET Seven 2.4x XXXX-F71R-XXXX-XXXX-XXXX

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.

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 can I clone an MPM? How can I upload config.db to an MPM? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause Unable to upload config.db to an MPM Resolution An MPM can be cloned from Building Expert by exporting default.db from one MPM and importing it to another (using the "Export Database" and "import Database" buttons) Note: Allow MPM a few minutes before attempting to access Building Expert. MPM will reboot automatically and install Database files. If it is necessary to clone the system configuration objects as well, refer to the procedure below: This procedure show you how to upload the Database to an MPM. To download a backup of the database, refer to MPM database information. Power up the MPM and ensure either its IP address can be pinged or Building Expert is accessible. In address bar of browser, enter 10.50.80.3/test.html. (assuming IP address of MPM is set to default) In Remote Path field of File Upload section, enter config.db. Click Browse and Navigate to the backup config.db file and select it. Click Submit Query. Wait for {“success”: true} to show before you proceed. Note: Uploading the config.db file first does not cause the MPM to reboot; which is why it is uploaded first On Browser, click to return to previous page. In Remote Path field of File Upload section, enter default.db. Click Browse and Navigate to the backup default.db file and select it. Click Submit Query. Wait for {“success”: true} to show before you proceed. Allow MPM a few minutes before attempting to access Building Expert. MPM will reboot automatically and install Database files. Note: MPM must not powered off during this time In address bar, enter 10.50.80.3 to connect to Building Expert and validate Database upgrade is correct.

Issue Where can additional information on the SPW100 series differential pressure switches be found. Environment SPW100, SPW102, SPW104,SPW106, SPW108, SPW110, SPW114 Cause Only the Schneider Electric datasheet and CE declaration are posted on the Extranet, no installation documents are available. Resolution Attached are the OEM suppliers datasheet and installation guide along with the Schneider Electric documents. Download here.

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.