Building Automation Knowledge Base

Issue Performing database maintenance with Vista 4.5.0 Product Line TAC Vista Environment Vista 4.5.0 SQL Server Cause It is necessary to perform backups for two reasons, first to be able to recover the system in the event of a fatal error and second to be able to manage the size of the database. Resolution Vista has a means of backing up databases on a Vista Server.  It is necessary to perform backups for two reasons, first to be able to recover the system in the event of a fatal error and second to be able to manage the size of the database.  The Vista database probably won’t grow very much after the initial engineering activity but the event and trend log database grows as events are received in Vista.  In many installations maintaining an archive of event data is required so that is another reason for backing up the database.  This paper presents a way to accomplish the backing up of the Event and Trend database and creating an archive file. Before the backup process can be implemented it is first necessary to have a good estimate of the Event and Trend Log traffic anticipated for the installation.  In the Vista 4.3.0 Technical Product Information (TPI), Ref No: C88-1-D43, there is section entitled Strategies for Calculating and Controlling Database Size.  On page 5 the method for determining database size is explained and used in the following example: Right clicking on the $Backup_LDB object in the Server View brings up this dialog.   Note that this example has an Event and Trend database that has reached 1121 (MB) in size.  The default Size Alarm Limit is shown to be 1640 and if the database grows past that size, Vista may not operate reliably. The TPI states on page 4 that events contain on average 2Kb of data.  Combining that value with the expected traffic provides a reasonable estimate of the database expansion rate.  If the installation traffic estimate is 4000 Events and Trend samples per day, the database expands at the rate of 8Mb per day.  If the installation traffic estimate is 10,000, the database expands at the rate of 20Mb per day. A conservative approach would limit the size of the active database to half of the alarm limit.  That means the backup process must be done so that the size does not get to 820Mb.  At 10000 Events and Trend samples per day that value would be reached every 41 days.  Vista is designed to allow Event driven backup operations and the closest choice it offers to the 41 days is once a month so that is what will be chosen. The configuration of backup is done in Vista Workstation by opening the Properties of the Workstation object in the tree.  The first step is to select a location for the backup files to be saved.  In the example shown below it is the folder outlined in red.   The “Max number of files” limits the number of backups that are retained by Vista on the hard drive.  The number chosen here was two (2).  The procedure that is described further down will actually move backup files to new directories which could be a network drive or a CD/DVD rom.  (The latter option requires operator action so it might not be the most desirable especially since backups are usually done at off times when an operator might not be available)  Next the event that is to trigger the backup must be defined.  The configuration of when the backup is done is set on the Log Backup tab of the Vista Server Properties dialog.  In the example shown below the backup is scheduled to occur on the first of every month at 12:40AM. The selection of Event object is made from the options made available by the browse button.     The browse selection brings up the Select dialog from which the selection of Event type and properties is done.  In the following example the selection is Monthly.   Right clicking on the $Event_LDB object opens the properties dialog box to configure the Event_Month object.  The final configuration option is what to do with older records.  Vista will remove Events from the database if you so desire.  The removal does not shrink the database but does make space available for new events to be written without expanding the size of the database.  This is the key to keeping the database from exceeding the Alarm Limit. The Event Log tab provides a way to delete old records from the database.  In the example shown below records older than 30 Days will be deleted after the backup that was done be the Event_Month object has been completed.  This means that each month the backup should have the most recent 30 days of Events and Trend samples.   The final step that can be taken is to also copy the backup file to a server that is backed up or to a CD/DVD Rom. This operation creates an archive in which Event and Trend data is stored.  Windows task scheduler can be used to run a cmd at some time after the backup operation was scheduled.  For the above example schedule it to run a 1:00am on 1 st of each month.  If backing up to a network drive create a folder such as shown below.  J:\Engineering\Vista Event Log BU.  In order for the task scheduler to run it is necessary to setup a user account on the pc that is not related to any actual user.  I added a user to the User group named, vista xcopy dbmgr.  This will be the user account used by the task scheduler.  The Vista backup folder must have modify/write permissions for this user and the folder into which the backup is going to be copied must have Full control.   The command line for this example is shown below: C:\WINDOWS\SYSTEM32\xcopy.exe "C:\Program Files\TAC\TAC Vista 4.5.0\Db2\$bkp" "J:\Vista Event Log BU" /M The Windows task scheduler is configured in the Control Panel, Scheduled Tasks as shown below:   In the Run as: box enter the name of the new User created described above: vista (xcopy dbmgr) Schedule the task to run on the first of each month at 1:00AM.   The backup files can be restored to a Vista Server that is not performing actual site monitoring.  This method is only way the “archived” event and trend data can be viewed as of Vista revision 4.5.0.

Issue While attempting to import files to through WorkStation or libraries from the Script Editor, the program crashes with the error message below. It can even happen when doing mass create or mass change, or when adding columns to a list view. "StruxureWare Building Operation has stopped working" Environment Building Operation WorkStation Building Operation Script Editor Cause It has been identified that a program called "F-Secure Key" interferes with other installed programs, and can ultimately leed to other programs crashing. "F-Secure Key" hooks into the Microsoft dll "UIAutomationCore.dll" which is used to idenitfy and manipulate elements in the user interface. If "F-Secure Key" is installed, it can easily be identified, as you will see a blue circle with a key when logging in through WorkStation Resolution Uninstall all "F-Secure Key" related program from "Programs and Features" in the Control Panel on the PC

Issue An error occurred while installing DSS: MSDTC The content of the dialog box or windows event entry starts with: System.EnterpriseServices.RegistrationException: Unable to open COM+ 1.0 catalog to configure components. ----> System.Runtime.InteropServices.COMException (0x8004E00F): COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator Product Line TAC Vista Environment Vista Installation DSS Cause This happens when there is a problem with Microsoft Distributed Transaction Coordinator (MDTC) Resolution Go to Control Panel Administrative Tools – Services Check if MSDTC in running as a Service. The name that you should see in the service list is 'Distributed Transaction Coordinator' Make sure that this is Started, Automatic, Network Service (for XP and Win2003) Here is how to install it if it is not already running: Open cmd prompt Navigate to C:\Windows\%windir% Type "msdtc -install" which installs Msdtc. The service now appears under the 'Services' area. After installing follow the steps in Microsoft Technical Bulletin.

Issue An error occurred while installing DSS: MSDTC 2 Product Line TAC Vista Environment DSS Installation MSDTC Cause Users that get the following error message when installing Vista ‘Error occurred when installing DSS’ can be caused by the MSDTC (Distributed Transaction Coordinator) not being able to start. In the service list Distributed Transaction Coordinator (MSDTC) is not started and it fails when you try to start it. Resolution Check the windows event log. If you see the following error events logged in the Application log:  Event Type: Error Event Source: MSDTC Event Category: LOG Event ID: 4163 Description: MS DTC log file not found. After ensuring that all Resource Managers coordinated by MS DTC have no indoubt transactions, please run msdtc -resetlog to create the log file. Event Type: Error Event Source: MSDTC Event Category: TM Event ID: 4185 Description: MS DTC Transaction Manager start failed. LogInit returned error 0x5. Follow the steps in http://support.microsoft.com/kb/916926 to fix the problem. For other possible causes for this problem see: An error occurred while installing DSS: MSDTC An error occurred while installing DSS: The account already exists An error occurred while installing DSS:COM+ installation corrupt An error occurred while installing DSS: Cannot Start Service

Issue SNMP Flashing options for Netcontrollers and BCXs Product Line Andover Continuum Environment All Continuum master controllers Cause Documentation Resolution BCXs & Netcontrollers can be in 3 states: SNMP Standard is how all controllers are shipped by default. This means that the controller model and some other object info can be obtained via SNMP. SNMP Alarming Enabled means Standard SNMP as well as SNMP Alarming is enabled in order to send alarms to a network management system. This is a paid for option either initially when the controller is ordered or by contacting repair. To enable this option in the field, repair sends a file and instructions after payment. SNMP Disabled means that no SNMP information will come from the controller. Upgrading controllers with future firmware versions Depending on which SNMP option state the controller is in will determine the application flash that should be used going forward. Selecting the incorrect file can disable or re-enable SNMP options. Netcontroller v1.5300x SNMP Not Set means no SNMP options will be changed when upgrading firmware v1.5300x Standard SNMP means use with Standard SNMP (default) v1.5300x SNMP Alarming Enabled means use when SNMP Alarming is enabled (Not Set could be used also since it will not change the enabled option) v1.53 SNMP Disable means this will disable All SNMP traffic, Standard and Alarming BCX Use the default firmware upgrade after SNMP is enabled. If you use the BCX SNMP Disable flash files and then upgrade to a newer version of firmware, you will have to run the disable flash file again to disable SNMP. NOTE: The flash files used to disable SNMP are posted on The Exchange. Note2: If the flash file doesn't enable the options because it was sitting at resetting controller,  Reload the controller which will force a reset and then try the flash file again.

Issue Alarm Forward and Log settings with enhanced alarm logging causes unnecessary network traffic Product Line Andover Continuum Environment Continuum Workstation Cause There has been some confusion about whether to select forwarding and logging on the recipient editor located within the eventnotification editor. Resolution In 1.5 and later versions of Continuum, a new alarm engine was introduced. To use the new alarming engine, select the enhanced alarming check box located in the database initialization editor. The enhanced alarming feature will perform both the forwarding and logging of an alarm. If the enhanced alarming feature IS SELECTED, then the forwarding and logging of a specific PC will not need to be checked ***. If enhanced alarming IS NOT SELECTED, then you will need to specify a forwarding and logging workstation. **IMPORTANT: Intrinsic alarms of type Controller Status, Fault Status and Logon Status still need their corresponding Event Enrollment object configured for logging and/or forwarding as before. If enhanced alarming, forwarding and logging are selected, there will be no duplication of alarms, but will cause unnecessary traffic on the network. If all three are selected and are on a very busy network, you may experience workstations appearing as offline. This can be intermittent depending on the amount of network traffic generated on your site. To check the settings of your enhanced alarming features, open up the database initialization editor and select either the server or stand alone button to view your settings. If your setting is not selected and you want to use the new alarming engine then select the feature. Make sure you restart ALL workstations when you change this feature. In 1.7 and later versions of continuum there is also an enhanced alarm delivery selection. This selection uses Microsoft's Messaging Queuing Service to deliver alarms. This feature allows multiple workstations to share the load of delivery of alarms to the recipients of an eventnotification. Thus reducing the work load of just one workstation to handle the delivery. The enhanced alarm delivery feature, will be best utilized when working with multiple workstations.

Issue The properties of a BACnet or Infinet Schedule shows Next transition time as 2106-02-07 07:28:14. Where does this date come from? EBO BACnet schedule shown below Product Line EcoStruxure Building Operation, Andover Continuum Environment b3 BACnet Schedule Infinet Schedule Cause The reason it displays the date of 7 Feb /2106 is that there are no events in the controller for the current week. Resolution The next transition time is evaluated and will display the next transition time when the following week has an event scheduled.

Issue WebClient login screen has the webClient background, but no login fields   Product Line Andover Continuum Environment webClient Cause This typically happens when webclient has been installed prior to IIS, so .Net framework does not get registered with IIS. Resolution The resolution is to run the regiis.exe command as follows: From a DOS Command Prompt (as an admin) For Windows 2000 Professional it is: "c:\WinNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i" "c:\WinNT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i" For Windows XP Professional, Windows Server 2003 it is: "c:\windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i" "c:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i"   For Webclient 1.94 and above, .Net Framework 4 is used "c:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i" Once this command is run the normal login prompt will be presented.

Issue Satchwell VSF or VJF Valve Body controlled by Satchwell Spring Return Actuator requires replacement. Environment Satchwell VSF or VJF Valve Body installed in Water or Steam Control Valve applications. Cause Obsolescence of Satchwell VSF or VJF Control Valve Body. Resolution STEAM APPLICATION 1.  Replace Satchwell VSF or VJF Valve Body with S-E Two-Port Flanged Valve Body. Where an existing Satchwell VSF or VJF Valve Body is utilised in a STEAM application, then the VSF or VJF Valve Body should be replaced by a suitably sized S-E VGS211F Valve Body, thus enabling steam having a steam inlet pressure up to 1300 kPa and a temperature up to 200 deg C to be controlled. It should be noted however that the face-to-face dimension and overall dimensions of each S-E Valve Body will differ to those of the Satchwell VSF or VJF Valve Body. It should also be noted that the operation of the VGS211F Valve Spindle is the reverse of that of the VSF or VJF Valve Spindle. When the VGS211F Valve Spindle is UP, or in the fully extended position, then the Valve is OPEN. Similarly, when the VGS211F Valve Spindle is DOWN, or in the fully retracted position, then the Valve is CLOSED This will therefore result in the need to replace the existing Satchwell Actuator with the correct model of S-E M700 Actuator, in order to ensure the correct operation of the Valve Body in the event of electrical power failure. It is important that the above limitations are recognised when replacing a Satchwell VSF or VJF Valve Body with a S-E VGS211F Valve Body in retrofit projects. Such limitations do not apply to new projects where a new S-E VGS211F Valve Body and a new S-E  M700 Actuator are being selected, providing of course that an Actuator having the correct spring action in the event of electrical power failure is selected. N.B. Steam Control Valves are normally required to CLOSE in the event of electrical power failure. In the case of the S-E VGS211F therefore the S-E M700 SRSD Actuator should be selected. WATER APPLICATION 1.  Replace Satchwell VSF or VJF Valve Body with S-E Two-Port Flanged Valve Body. A number of alternative models of S-E Two-Port Flanged Valve Bodies are available to replace existing Satchwell VSF or VJF Two-Port Flanged Valve Bodies. It should be noted however that the face-to-face dimension and overall dimensions of each S-E Valve Body will differ to those of the Satchwell VSF or VJF Valve Body.  

Issue S-E L2SV Linkage Kit and S-E L7SV Linkage Kit compatibility with Satchwell Plug and Seat Valve Bodies. Environment Satchwell 1 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 2 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 3 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 7 series Plug and Seat 2-port and 3-port Valve Bodies. Cause Use the correct S-E Linkage Kit with Satchwell Plug and Seat Valve bodies. Resolution 1.  Observe specification number of Satchwell Plug and Seat Valve Body Generally where a Satchwell AL series Linear Actuator is fitted to a Satchwell plug and seat Valve Body, the Actuator may be replaced by an equivalent S-E Forta or MV15B series Linear Actuator and appropriate S-E Linkage Kit. It should be noted however that neither the S-E L2SV Linkage Kit nor the S-E L7SV Linkage Kit will enable an S-E Forta or MV15B series Linear Actuator to be mounted on a Satchwell 7 series MZ/MZF or a Satchwell 7 series VZ/VZF plug and seat Valve Body. The internal screw threads of the Neck Adaptors included in the S-E L2SV Linkage Kit (880 – 0124 – 000) and S-E L7SV (880 – 0126 - 000) Linkage Kit are compatible with the external screw threads on Satchwell 1, 2 & 3 series Valve Body necks only. The external screw threads on Satchwell 7 series Valve Body necks however differ to those on Satchwell 1, 2 & 3 series Valve Body necks. Consequently neither the S-E L2SV Linkage Kit nor the S-E L7SV Linkage Kit will enable an S-E Forta or MV15B series Linear Actuator to be mounted on a Satchwell 7 series Valve Body. A S-E Forta series Linear Actuator may be mounted on a Satchwell 7 series Valve Body however using Linkage Kit 880 – 0135 – 000.  No equivalent Linkage Kit is currently available for use with the MV15B series Linear Actuator. The Satchwell Valve Body series may be determined from the Valve Body specification number stamped on the Valve Body Identification Collar, where the single middle digit of the specification number denotes the series. In the case of a Satchwell 7 series Valve Body for instance the single middle digit of the specification number will be the number 7 (e.g. 626 – 7 – 402)

Issue Most readers do not support 24 VDC so there is risk of damaging the reader Product Line Access Expert Environment Mercury MR50 single reader board powered with 24 VDC and a card reader Cause Continuum hardware (ACXs and AC1s) typically have a jumper to configure 5 or 12 VDC for reader power. Mercury board MR52 can select 12 VDC for reader power with jumper J2 when it's powered with 24 VDC. The MR50 CANNOT be configured for 12 VDC reader power. If the MR50 is powered by 24VDC, it will automatically pass 24 VDC to the reader terminal board. CONNECTING A NON 24VDC READER IN THIS CONFIGURATION WILL DAMAGE THE READER. Resolution Readers that require different voltage or have high current requirements should be powered separately.

Issue TAC TRV-S series Butterfly Valve Body requires replacement. Product Line Field Devices Environment TAC TRV-S series Butterfly Valve Body installations. Cause Obsolescence of TAC TRV-S series Butterfly Valve Body. Resolution Replace TAC TRV-S series Butterfly Valve Body with S-E VF208W series Butterfly Valve Body. Replace TAC MB15 / MB30 Actuator with S-E MF20 / MF40 series Actuator as appropriate. It should be noted that where a TAC TRV-S series Butterfly Valve Body is to be replaced by a S-E VF208W series Butterfly Valve Body the TAC Actuator fitted to the TAC TRV-S Butterfly Valve Body will not be suitable for reuse on the S-E VF208W.Buttterfly Valve Body. TAC TRV-S series Butterfly Valves utilise TAC MB15 / MB30 series Actuators. TAC MB15 / MB30 Actuators are not suitable for use on S-E VF208W series Butterfly Valve Bodies. S-E VF208W series Butterfly Valve Bodies utilise S-E MF20 / MF40 series Actuators. S-E MF20 / MF40 series Actuators are suitable for use on TAC TRV-S series Butterfly Valve Bodies, but then no linkage kit should be mounted. MF20 datasheet MF40 datasheet  

Issue Remote Client Configuration Issues I.Net 2.31 and prior Product Line TAC INET Environment I/Net Seven version 2.xx with need for Remote Client configuration. 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.21 to 2.31 release. Resolution There are two different configurations for the Remote Client setup in I/Net Seven. Clicking the links below will open a PDF document which will show how the communication should be setup. This configuration is in the I/O Server under the current profile and can be found in the Workstation Options.   *IP Addresses are for demonstration purposes only.

Issue It is not possible to access graphics in a Xenta 5/7xx from a smart phone mobile app. Environment Xenta 511, 527, 711, 731 Smart Phones: Apple iPhone, iPad, Android Cause Graphics in a Xenta 5/7xx webserver render in the web environment using Java.  There is not currently a smart phone in the market that is works with Java applets. Resolution There is currently no supported mobile solution for viewing graphics in a Xenta web server. 

Issue How to add another TAC Vista server node into an existing server in TAC Workstation. Product Line TAC Vista Environment Vista Workstation Cause Multi-sever Vista system is the system which has more than one Vista Server in the network. One Vista Server will be assigned as the master and the rest will be assigned as slaves. The order of setting multi-sever system is very important in order to make the system work properly. Common mistakes are: Vista servers have different versions. Adding slave computers before adding the master computer. Using same names of Vista servers. Using dynamic IP address. Vista Server object names are the same. All folders and objects found at the root level of the servers must be changed to unique names before merging the databases. Resolution Before doing that, please back up all TAV Vista databases on all computers. All computers should run the same version of TAC Vista. Also make sure all your IP networks are functioning. In addition, all Vista Servers need to be the same version. (eg. Vista 5.1.3 server will not be able to communicate Vista 5.1.4 server when they are noded together.) All computers’ TAC Vista Servers need to have different names. The server name can be checked by opening your TAC Vista Server. By default, Server name is the computer name. If the sever name needs to be changed, please following the steps listed below: Go to TAC Vista Server Setup Go to Vista Database tab Under “Rename Vista Server to” text field, type the new name Click ok and start the Vista Server to make sure the name has been changed Choose one computer to be the Master and the rest of the computers will be Slaves. Start by shutting down all instances of TAC Vista Sever and TAC Vista Workstations. Add Slave Servers into the Master Server. Start the Master TAC Vista Sever, and then start its TAC Vista Workstation. Right click on the Vista Server object. Select New>Object>Node. Type $LAN.SlaveServerName. If the Slave Server name is different from its computer name, change the IP/DNS address in the property window. (Note: this step requires a static IP address) Right click on the Slave Server Node and select Properties. Type in the IP address in the IP address/DNS name field. Repeat steps a-e for any additional Slave Servers. Leave the Master Server on, and start the Slave Server. Follow steps 4 a-e for adding Master Server into Slave Server but use the Master Server’s server name and IP address this time. Then, right click on the TAC Server object in Slave Server computer, select Properties. Under the General tab, change the Network Master to the Master Server name. Then click OK. If you have multiple Slave Servers, add the Master Server into each of them. Shut down all instances of TAC Vista Workstation and TAC Vista Server. Restart the Master Server’s TAC Vista Server and its TAC Workstation first. Then start the Slave Servers’ TAC Vista Server and their TAC Workstation. You should be able to view the Slave Servers under Master Server. Note: Master Server can view all Slave Servers’ projects, and each Slave Server can view Master Server’s project. However, each Slave Server cannot see other Slave Servers unless you node Slave Servers to each other. Any change made in Slave Server’s TAC Workstation will be reflected in the Master Server’s TAC Workstation. Vice versa also works.

Issue Importing a .CSV file into Access Expert gives the following error: Product Line Access Expert Environment .CSV File Cause During the import the Excel doc holds the file open and causes a sharing violation in Access Expert. Resolution Close the Excel .CSV file during the import. This will happen with the sample file from Access Expert or one created manually with the appropriate fields.

Issue Integration to the Veris H80xx Entercept power meter with the Xenta 5/7/9xx and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Veris H80xx Entercept Power Meter Cause Integration instruction and programming example for integration to the Veris Entercept power meter. Resolution Please use the following .dev files as a starting point and a guide to the integration of a 100 amp or 200 amp Veris Entercept meter. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes to the modbus mapping or this supporting document for data scaling changes. If mapping for larger amp meters is needed, please contact product support.   100 AMP .dev file 200 AMP .dev file   To use these files in XBuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on the harddrive. In Xbuilder, right click on the Modbus Master device and choose Add Device Browse to the needed .dev file and click Open. Rename the newly added device to a unique name within the Modbus Master network.   Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template.  

Issue ACX5740 controller going on and offline when the WebClient Cyberstation is started Environment LAN System CyberStation 1.90 WebClient Cause Both the regular CyberStation and WebClient CyberStation were configured with the same ID information Resolution Reconfigure the WebClient CyberStation with unique ID information

Issue How to find a Vista 5 dongle ID if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista 5 Windows Command Window Cause The Dongle ID is required for locking TAC Vista licenses to a site dongle. Normally, the dongle ID can be found on the side of a Vista 5 licensing dongle. However, on older dongles, this number can rub off.  It is still possible to extract the dongle ID using the GetTACHLInfo.exe dongle utility software. Resolution On the Start menu, click Run. In the Run dialog box, type cmd Click OK. In the dialog box, go to the folder C:\Program Files\Schneider Electric\License Server (as default) NOTE: for TAC Vista 5.1.3 and prior, go to the folder C:\Program Files\TAC\License Server. Use command "cd.." for going to the parent directory and command "cd folderPath" for going to a child directory. Can also view items in the current directory by typing "dir". In the dialog box, type GetTACHLInfo (or GetTACHLInfo.exe) and press Return. The dongle ID is listed after "TAC_HL_ID=". Read Find a Vista IV dongle ID (PSU ID) for how to find Vista IV dongle ID.

Issue Which files can be backed up safely with an automatic/manual method. Environment Sigma (All) Cause Backing up a live Sigma system is not a recommend as copying ‘live open’ files can not guarantee the integrity of the data. Resolution For either backup method (automatic or manual) those files which could be potentially 'open' by Windows should not be backed up unless the Sigma server and clients have been shut down.  1. Those data locations that can be backup safely while the Sigma is running are those in which archive data is stored, namely; a.  C:\Sigma\Data\ArchivedAlarms b. C:\Sigma\Data\ArchivedLogs c. C:\Sigma\Data\ArchivedTransactions Removing the files from these locations should only be done as a space saving measure as Sigma can be configured to view these data files by the user. 2. For all other files the recommendation is to shut the system down (clients and server) before taking the backup. 3. Restoring data must only be performed after shutting down the system first.