Building Automation Knowledge Base

Issue What is the limit of the number of Controllers that can be in a Continuum System? Product Line Andover Continuum Environment Continuum Cause Want to know the theoretical and practical limits to how many controllers can be on one system. Resolution There are certainly some logical limits to how your Netcontrollers are addressed and identified in the system but for all intents and purposes you are only restricted by the IP Address. Netcontrollers Logically, you can have Netcontrollers addressed from 1 - 190 - so the maximum you can have in a "logical" Network is 190 Netcontrollers. However, the number of Networks you can have in a Continuum Database is only restricted by the Database itself - effectively infinite. See the article below on logical Networks. How many logical networks can be created on a Continuum system? This restriction is only for Netcontrollers defined within the Infinity side of the Continuum Database and does not apply to third-party BACnet controllers. Field Controllers (b3 / i2) There is a definite limit to the number of subnet (Infinet or MSTP) controllers that can be strung off of a given bCX or Netcontroller. As a general rule, each comm port can support up to a maximum of 127 subnet devices. Of course this does depend on the device being used, the amount of nodes it is enabled for, and the physical installation. The number of nodes purchased does correspond to the total number of i2 or MSTP controllers that can be on that bus. Example: If you have a bCX1 with 32 MSTP nodes this means that a total of 32 MSTP devices can be on this MSTP network and the following architecture is valid. bCX1 with bLink; (segment1) node1 to node16. (segment2) node17 to node32. If we look at a Netcontroller or Netcontroller II, these controllers have two RS-485 comm ports that can be used to support Infinet subnet controllers, up to 127 on each port and a maximum of 254 off the one controller. Now the controller would need to have both ports enabled for 127 nodes and considerations made for the amount of traffic this number of controllers would require. Similarly, the bCX1 (BACnet) will support up to 127 nodes. One thing to note is that this also includes repeaters if they are used to extend your network or star the MSTP. The general rule for the number of devices on an MSTP segment is a maximum of 32 nodes, this dependent on the network complying with MSTP installation guidelines for termination, distance, cable type, and that each node is a full load RS-485 transceiver. In the case of our BACnet controllers, they use a 1/4 load transceiver so given perfect network conditions it is possible to have 127 b3 devices on the same MSTP network segment. Even though this is possible, it is always good practice to use a b-Link repeater and a max of 32 devices per network segment - this also helps to segregate the devices for troubleshooting as well. Total Point Limits Other than with a Cyberstation with an I/O limited Security Key, I'm not aware of any limits to the number of points that can be created in a Continuum Database; this would be limited to the size and resources of the Continuum SQL Database. Consult the following article that has a spreadsheet to help estimate the size of your Continuum Database. It could also help to estimate your SQL requirements: Continuum Database Sizing and SQL Server selection

Issue Data Sync Service won't run after installation Product Line EcoStruxure Security Expert Environment Security Expert Server Cause Mismatch in authentication type during the installation of Security Expert Server and Security Expert Soap Service Resolution First completely uninstall the Security Expert Soap Service and Security Expert Server... Then reinstall Security Expert Server ensuring to UNTICK the box to hide advanced database configuration options When asked about Customize WCF TCP/IP Port, make note of your selection. Please note that using TLS 1.2 is the recommended method for authentication. Then reinstall the Security Expert Soap Service matching up the authentication type used for the Security Expert Server.

Issue The error "Failed to Invoke the Security Expert Suprema Component" is seen when attempting to register/enroll a user's biometric credential at a Security Expert Client Only machine.   Figure 1 - Suprema scan error   When doing a registration/enrollment from the Security Expert Server this error is not seen and the registration is successful. Product Line EcoStruxure Security Expert Environment Security Expert Suprema Biometric Reader Cause The Suprema.dll has not been properly registered on the local machine. Resolution First check in C:\Program Files (x86)\Schneider Electric\Security Expert folder and confirm that the three files Suprema.dll, BS_SDK.dll, and BS_SDK_V2.dll are all present. If they are not you will need to copy them over from a working installation of Security Expert Server Installation.   Now run the below commands via an Administrator authenticated command prompt session: For 64-bit machines cd C:\Windows\SysWOW64 regsvr32.exe “C:\Program Files (x86)\Schneider Electric\Security Expert\Suprema.dll” For 32-bit machines regsvr32.exe “C:\Program Files\Schneider Electric\Security Expert\Suprema.dll” You should get a pop-up saying the .dll was registered successfully. Close and re-open the Security Expert client and re-test enrolling a user's fingerprint.

Issue How to upload the application from a TAC Xenta 280/300/401 device? Environment TAC Xenta 280 TAC Xenta 281 TAC Xenta 282 TAC Xenta 283 TAC Xenta 300 TAC Xenta 301 TAC Xenta 302 TAC Xenta 401 TAC Menta Cause When the application file is generated and compiled, it does no longer contains any information about the layout, or the "yellow boxes". Therefore, it is not possible to extract a Menta file (.MTA) from the device. It is, however, possible to upload the compiled information, and download it to another device. This way, it is possible to replace a faulty device even if you no longer have access the original application. Resolution Always make sure that you have backup of your application files, as it is not possible to upload the graphical information from the device. To upload the complied application information from the device, you have to start TAC Menta, and connect to the actual device via a serial cable. In TAC Menta, select Options, and Simulate to go to simulate mode. Select Online. Select Upload. Select path and filename. The extension will be *.COD (compiled application file) Select Save, and the complied application file will be uploaded. It is not possible to open the *.COD file in edit mode in TAC Menta, you will always have to go to simulate mode before you can open up a stored *.COD file. To change TAC Menta from Tabular mode to normal mode, just press F5. This requires that you have open up an existing application file (*.MTA) or select to make a new application.

Issue Link test fails when selecting graphics folder path in Pinpoint Options. Internet Explorer throws the following error when a graphic is launched.   Environment WebClient IIS Server Web Pinpoint Pinpoint Graphics Cause When specifying the location of graphics files in WebClient, the share must be a virtual drive as IIS not use a physical drive. Resolution Use the virtual drive share name when configuring the graphic file location under WebClient in Pinpoint options.

Issue When attempting to run the WorkPlace Commissioning Tool using the BACnet-IP or BACnet-Ethernet protocols, the search stops immediately and the "sweeping flashlight" is not displayed.  No BACnet devices are found. Environment Windows 7 Professional operating system WorkPlace Tech Tool software version 5.7.4 through 5.7.7 and 5.8 Cause The WinPcap ethernet communications driver could not be started causing the network search to fail silently. During the installation of the WinPcap software, the installer presents an option to start the WinPcap driver at boot time.  Due to potential security concerns, it is suggested that this driver be configured not to start automatically when the computer is booted.  When the WinPcap driver has been installed in this mode and the user does not have system administrative rights, the driver cannot be started automatically when needed.  This issue and the required actions were documented in the WorkPlace Tech Tool 5.7.4 and 5.7.5 release notes. Resolution As published in the release notes document, there are two different ways the issue can be handled. Turn off Windows U.A.C. (Not recommended for security conscious users) Open the Windows control panel and select User Accounts.  If the control panel display is organized in the "Category" view mode, select "Add or Remove user accounts" then select the "Go to the main User Accounts page" link. Select "Change User Account Control Settings". Drag the displayed slider to the bottom position, "Never notify" then click [OK] to save the setting and exit.   Configure the three WorkPlace Tech Tool programs to run with administrative rights. (May not be allowed on some customer owned computers).  NOTE: When the WorkPlace Tech Tool programs have been configured in this manner, the User Account Control screen stating "Do you want to allow the following program to make changes to this computer" will be displayed each time one of these programs is run. It is necessary to click the [Yes] button to allow the program to run. From the Windows start menu or from the desktop select "Computer". Navigate to the folder "\Program Files\WorkPlace Tech" on the local disk C: (or the local disk where the WorkPlace Tech Tool software was installed. Right-click on the application WPCT (may be shown as WPCT.exe) and select Properties from the displayed list.  Click on the "Compatibility" tab then click the button [Change settings for all users].  In the "Privilege Level" section, check the box "Run this program as administrator".  Click [OK] to save the change and close the "All Users" compatibility options window.  Click the [OK] button to close the properties window. Right-click on the application WPFB (may be shown as WPFB.exe) and select Properties from the displayed list.  Click on the "Compatibility" tab then click the button [Change settings for all users].  In the "Privilege Level" section, check the box "Run this program as administrator".  Click [OK] to save the change and close the "All Users" compatibility options window.  Click the [OK] button to close the properties window. Right-click on the application WPTech (may be shown as WPTech.exe) and select Properties from the displayed list.  Click on the "Compatibility" tab then click the button [Change settings for all users].  In the "Privilege Level" section, check the box "Run this program as administrator".  Click [OK] to save the change and close the "All Users" compatibility options window.  Click the [OK] button to close the properties window. Close the Windows explorer window. In the event that a customer's security policy prohibits either of these methods of security permission control, the alternative is to uninstall the WinPcap program and reinstall it (by running the WorkPlace Tech Tool installer), configuring WinPcap to start automatically when the computer is booted.

Issue Start up of Continuum Workstation sees the below error. The Continuum Workstation may continue to start up if the OK button is pressed or may crash.   ContinuumServer.exe error An error occurred during initialization of Continuum Shared Memory by "ContinuumServer.exe". Please restart your system. If this problem persists, please contact technical support. Product Line Andover Continuum Environment Continuum v2.0 SP1 A Windows 32-bit Operating System Cause Beginning with the Andover Continuum 2.0 SP1 Release, Continuum applications now take advantage of the upper memory address space that is available natively on 64-bit Operating Systems (OSs). In order to access these memory addresses on 32-bit OSs, you must reconfigure your 32-bit OS to support applications that are Large Address Aware (LAA).  Resolution Enabled Large Address Aware (LAA). A Windows batch file is included as part of the Continuum 2.0 SP1 release that allows you to reconfigure your 32-bit OS to support applications that are LAA. You will need to ensure that Windows Firewall and Windows Defender are turned off and then run the "laa_update.bat" batch file as an administrator from the installation CD or zip folder.  See page 19 of the Cyberstation v2.0 SP1 Installation Guide for further details.

Issue Instructions listed in the webclient installation guide have been followed. Accessing Webclient pinpoint from any browser, the following error occurs when Webclient is installed on Windows Server 2008 "Unknown Error. Server:http://ServerNameDNWACserverFactory/WACSERVER Factory.soap" Environment Webclient Windows Server 2008 Cause The 1.92 Webclient installation instructions do no include all the instructions to configure Webclient Pinpoint for Windows Server 2008. This has been corrected in 1.93. Resolution The 1.92 Webclient installation instructions do not include all the steps needed to configure Webclient Pinpoint for use on Windows Server 2008. The complete set of instructions are included in the 1.93 release of Webclient. Click here for the 1.93 instructions for Server 2008 Click here for a sample web.config file

Issue A Niagara R2 UNC is installed in a remote location with internet service provided by Comcast. Until now, a static IP address was provided by Comcast allowing for a static IP address to be provided to the UNC. Comcast has now switched to dynamically assigned IP addresses. Each time the installed internet router is power-cycled, it will receive a different IP address. Can the UNC be enabled to support DHCP and continue to be remotely accessible? Product Line TAC IA Series Environment Niagara R2 Cause Comcast's changes in internet service policy Resolution Niagara R2 stations support DHCP but the IP address must be 'reserved' within the DHCP server. See the Niagara Networking and Connectivity Guide, page 3-23. In this application, there is no DHCP server. Enabling DHCP will not allow for remote connectivity to continue as it did. Review the requirements with Comcast to determine if they can provide a solution involving a reserved IP address for the installed router. This will allow the UNC to retain its static IP address and maintain remote connectivity. Alternatively, dynamic IP addressing can be "out-sourced" to a 3rd party company. See the Niagara Networking and Connectivity Guide, page 5-22. The company TZO and its website www.tzo.com has changed to www.dyn.com and their most often-used product is dyndns-pro (http://dyn.com/dns/dyndns-pro). There is a small annual service fee but it has worked successfully with Niagara R2 applications. There is also a free version available at http://free.domain.name/en.html?domain=dyndns-home.com.

Issue What do I need to order to upgrade Continuum or add a feature to Continuum Environment Continuum Security key keys dongle Cause How to upgrade versions on a Continuum Security Key (Dongle) How to enable a feature in Continuum   Resolution The security keys (USB Dongle) requires upgrading if going between versions (eg 1.8x to 1.9x), contact your local order intake/Upgrade/Repair for costs. (or adding a feature/option, eg. enabling "Add-On Reporting Modules")  The order must include the security key (USB Dongle) serial numbers, you will receive back upgrade "cookies", these are used to upgrade the dongles. Use Cyberkeywriter2 available on The Exchange Download Center to update the security keys (USB Dongle) The Continuum Cyberstation software can be downloaded from The Exchange Download Center and the site upgraded. You should also check the Compatibility Matrix and installation guide before installation (ensure the workstations hardware is capable of running the newer software) Check the compatibility matrix for SQL version requirements (LAN versions) All upgrades are handled through the Repair Department. Contact your local Order Entry / Repairs & Upgrades department. NOTE A LAN dongle can be used on a SU/SA (Single User Stand Alone) site for the main SQL PC, a LAN dongle is required for all other Cyberstations on a SU/SA site (max. 2 units) A Dongle enabled for 1.9x can be used on all sites with 1.9x and before (eg v1.94sp1, v1.82, v1.74)

Issue Looping script programs continuously loop around the code, but a fallthrough needs a trigger to start it running and will stop at the end. How is this configured. Environment Script programs set as Fallthrough in an AS or ES Up to Release 1.3 Cause Plain English used Triggers in points to start a program, these do not exist in an AS or ES Binary value, so what is used to start the program running? Resolution Once a script program has been written, checked and  saved as a Flow Type "Fallthru", you can then edit the bindings. In the bindings use the variable called "Restart" a binary value to bind to the triggering point/ value which should also be Binary. This object can then be triggered on the required event to start the program, which will then execute the code and stop at the end awaiting the next restart. When you Bind a Digital Value to a Scrip program, you may get an error message like the one here: By Default, a Digital Value has no Configuration Settings defined. Enter 0 and 1 for the binary states and then performing your binding to the Program alleviates the error message.  Note: This functionality operates for versions up to Release 1.3. From Release 1.4 the Restart attribute is read only showing the restart status from the program and does not allow a point / value to be bound to this flag. In Release 1.4 a looping program will need to be used checking the state of the trigger point and action accordingly.   Note: in newer releases e.g. 1.7, 1.8 and above, triggers are now supported and you can bind directly to the Trigger attribute of the program, each change of the bound point will trigger the script to run.

Issue How to print out alarms when they occur? Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause Dot Matrix printers are no longer commonly used and alarm printing has been replaced by features such as SMTP email and Sysman text messaging.  Building Operation does not have native support for alarm printing. Resolution If alarm printing is needed, then a third party file to printer utility such as File2Print (https://community.se.com/) is required to print Building Operation alarms sent using write to file notifications.

Issue What is the procedure on transferring Continuum from one PC to another PC? Product Line Andover Continuum Environment CyberStation SQL Cause Workstation hardware needs to be upgraded or replaced altogether Resolution Collect information from the existing machine Collect all IP address, DNS server and Windows Server IP information from the existing workstation. Run Continuum Database Initialization on the existing machine. Select Workstation and record the following information. Workstation Name Folder Name Device Node ID Network ID Data Source Name Database Name User Login ID Server Name. Verify that correct Database Passwords are known for both Andover97 user and sa accounts Start Continuum and run PinPoint. From the View menu select Options Record the folder path indicated under Graphics (Pin Files) and archive these files.  Record the folder path indicated under Background and archive these files.  If any customization has been done to the menu pages (i.e. hot spot) then the User Profile folder( C:\Program File\Continuum\UserProfile) should also be archived. Backup the Continuum Database Move the database backup and the contents of the archived folders described above to a secure external drive or a network folder (not on the workstation itself). Install CyberStation on the new machine Before removing the existing machine from the network, start the new Workstation without connecting it to the network. Configure the IP Address, DNS server and Windows Server IP address collected from the existing machine. Install CyberStation on the new Workstation PC Note: Do not forget to disable all Virus Protection and Firewalls.  When prompted run Database Initialization Use the information collected on the existing machine to initialize the StandAlone Database. Use the information collected on the existing machine to initialize the WorkStation. Start Continuum and verify that the CyberStation operates normally. Copy data collected from the existing workstation onto the new workstation. Copy Database backup file to the Backup folder under C:\Program Files\Microsoft SQL Server\ Copy contents of the archived Graphics folder to the same folder on the new workstation PC. Copy contents of the archived Background folder to the same folder on the new workstation PC. Copy contents of the archived User Profile folder to the same folder on the new workstation PC. Run PinPoint From the View Menu select Options Under Graphics (Pin Files) enter the folder path to where the Graphics files have just been copied (see above). Under Background enter the folder path to where the background image files (see above). Select the Check button and verify that a failure notice (a red "X") does not appear beside any item. Close PinPoint Restore the Continuum Database. On the new workstation, run SQL Server Management Studio Express. Navigate to the Continuum Database. Right click on the Continuum Database, select Restore Browse to the folder where the existing Database backup file was copied to.  When the restore has completed successfully. Change the DB Owner: Right clicking on the Continuum database Selecting new query. In the query window type SP_ChangeDBOwner Andover97 From the tool bar select Execute. The result window should return............Command(s) completed successfully Reset the passwords for Andover97 and SA Open Security from the main tree, Select Logins. Right click on Andover97 and select properties enter and retype new strong password password, retype the correct password. Repeat for SA password. Now restart the PC. Run Database Initialization Under StandAlone, update the database. Re-Launch Continuum CyberStation and verify that CyberStation is working properly. Shut down the new workstation. Swap the workstations Shutdown the existing workstation and remove it from the network. Connect the new workstation to the network Start the computer. Launch Continuum and verify all functions are operating as expected.

Issue Care should be taken when editing an Automation Server script program in a working system Environment Automation Server Script program Cause If a script program "Numeric Input",  "Numeric Output" or "Numeric Public" line is modified, but includes a syntax error or a reserved word, then saved, the binding for this line may be broken. As below  After editing the Numeric Input line using a reserved word, this line bindings are broken Resolution Always be extra careful when modifying scripts running live plant. In this case it would be better to add a new extra "Numeric Input", "Numeric Output" or "Numeric Public" line, rather than modifying an existing one. The binding below are not broken NOTE This issue was fixed in v1.7

Issue There appears to be a low battery on the control board. How can the NiCAD Battery be tested on the controller to see if it needs to be changed? Product Line TAC INET Environment I/NET Seven Cause Possible low battery on control board. Resolution There are some checks you can make regarding the battery condition. The battery has a design life of 7 years and sometimes lasts much longer. With power applied to a controller for at least 72 hours, take a DMM and measure the DC voltage across the battery. It should be in the neighborhood of 4.2-4.3 vDC. Remove power from the controller board and take the same measurement again. The beginning voltage should still be between 4.1-4.3 vDC and should start slowly tapering off (a tenth of a volt over a period of minutes would be normal). When the battery voltage reaches 3.6 vDC this is the threshold at which the battery can sustain the RAM memory. Any voltage below this value will subject the RAM memory to loss of data (+ - a tenth or two). If the initial voltage with power applied to the controller is less than 4.0 vDC after 72 hours, the battery may need replacing. If the battery voltage drops rapidly after power is removed from the controller, the battery needs replacing. If the controller memory inexplicably gets lost (not counting power surges, brownouts, etc.) and a station restore is needed, the battery may need replacing. Normally the above-mentioned tests will show that the battery has lost its storage capacity. The TAC part number for the White NiCAD battery that is on most of the I/Net Controllers is 01-2100-545. These batteries can no longer be ordered through the Customer Care department. For further battery info please reference Replacement I/NET Controller NICAD Battery info.  

Issue BACnet bCX MSTP network loses communication when a b-Link is added or removed Product Line Andover Continuum Environment MSTP b3 bCX4040  b-Link Cause The bCX MSTP circuitry is slightly different to the b-Link  MSTP circuitry , thus under some circumstances, other faults on the MSTP network can cause communication to change, when the network is connected via a b-Link Resolution If an MSTP network is installed correctly, then it will operate correctly at all speeds up to 76.8k (assuming all devices operated up to this speed) If the MSTP network is not stable up to 76.8k, or adding or removing a b-Link causing a loss of communication, then it is likely there is some fault on the network. (adding or removing the end of line termination resistors, is also a useful fault finding option) The bCX MSTP components are slightly different to the b-Link MSTP components, thus under some circumstances, other faults on the MSTP network can cause communication to be lost, when the network is connected via a b-Link Example This has been seen when third party variable speed drives (VSDs) were connected to a bCX MSTP network (these unit had switchable termination resistors that by default were in circuit) The communication was ok at a low speed (19200) connected directly to a bCX, but when the network was put on the secondary side of a b-Link, the communication failed. Once the termination resistors were switched out of circuit, the communication via the b-Link was fine. In the example above the VSDs were by ABB Related: How to change the Baud Rate of a field bus (Infinet or Bacnet MSTP) when there is an Infilink or B-link on the network

Issue See "mismatch xxxxxxxx" in the Continuum Error Listview. Product Line Andover Continuum Environment Continuum Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause An Error logging feature was added with 1.94 SP1. If the Continuum Error Listview has "mismatch xxxxxxxx" errors, then SP1 for Cyber has been installed, but the controllers are posting errors. Resolution Use the updates below or the most recent version and the errors will no longer post. A Cyberstation 1.94 service pack released to address accdataservices crashes and other issues. The list of corrected issues is the release notes. The files are available on https://ecobuilding.schneider-electric.com/ 

Issue DC1100 & DC1400 Optimiser / Compensator Controller Cold Start malfunction. Environment DC1100 Optimiser / Compensator Controller. DC1400 Optimiser / Compensator Controller Cause DC1100 & DC1400 Optimiser / Compensator malfunction preventing Cold Start procedure being undertaken.. Resolution 1.  Repeat DC1100 & DC1400 Controller Cold Start procedure. A manufacturing problem experienced with the DC1100 and DC1400 may result in difficulty applying the Cold Start procedure. Faults have been reported in respect of a number of DC1100 Controllers in particular, where difficulty has been experienced when applying the Cold Start procedure. The fault appears in those Controllers where the Enter and Exit Keys foul their respective cut-outs in the Top Cover Panel, thus preventing Cold Start from being achieved. This is due to a conflict in assembly tolerances that can cause the Keys to remain depressed after they have been pressed in, due to their being trapped by the cut-outs they should pass through. In such instances it may be necessary to undertake the Cold Start procedure a number of times before any trapped Key is released sufficiently to enable resetting of the Controller to be achieved. Actions are currently in hand to rectify this matter and the positioning of the cut-outs in the Top Cover Panel relative to the Key positions has been addressed from a design point of view. Examples of the Top Cover Panel incorporating newly dimensioned cut-outs are not due to be available for inclusion in production assemblies until Week Number 2010 45 at the earliest however. Consequently current production assemblies incorporating the existing Top Cover Panel will continue to be utilised in all newly manufactured Controllers for the moment at least. Similarly an opportunity will not arise until Week 2010 45 for any Controllers currently held in stock in S-E Sweden to be re-worked to include the new Top Cover Panel prior to their sale.

Issue Unable to connect to Access Expert as the Feenics Mercury Service stops and will not restart after a system reboot. Product Line Access Expert Environment Access Expert Premise Software (AX) v3 Cause If the Mercury service is failing to start the most common issues are: Service Administrator password was changed Feenics API is not running The OS (Windows) may still be performing some background activity that might slow down essential system functionalities Resolution Service Administrator password was changed: Update the password within these configuration files to match the new admin password c:\program files (x86)\feenics\web api\settings.conf c:\program files (x86)\feenics\mercury service\settings.conf Feenics API not running: Check the API by opening the Internet Information Services and checking to make sure the Feenics website is running. Make sure the default site is not running. You can also check the bindings on the website Port 80 and binding of '*' The OS (Windows) may still be performing some background activity that might slow down essential system functionalities: Open Windows Registry: Start -> Run -> regedit.exe File --> Export --> make a backup of the current registry Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ Right-click on the right page ---> New ---> DWORD call the new DWORD "AutoStartDelay"  Set AutoStartDelay in milliseconds (decimal). E.G. 240000 is 240 seconds.               

Issue Getting distribution file installation (no core software) error when attempting to commission the JACE-6E.  The error states "No core software was found that can be installed to the remote host." Environment I/A Series G3, JACE-6E, TRD-J-600E Cause Attempting to install an I/A Series G3 version that is not compatible with the JACE-6E platform (e.g. versions below 3.6.47). Workbench not set up to be an installation tool (required distribution files are not available within the Workbench environment). Resolution Attempting to install an I/A Series G3 version that is not compatible with the JACE-6E platform (e.g. versions below 3.6.47). The TRD-J-600E is compatible with I/A Series G3 version 3.6.47.1 or later. The I/A Series ENS with Workbench files are available for download from The Exchange Download Center. Workbench not set up to be an installation tool (required distribution files are not available within the Workbench environment). Re-install the I/A Series G3 software and enable the checkbox that configures Workbench to be an installation tool. The checkbox indicates "This instance of TAC I/A Series Enterprise Network Server will be used as an installation tool." The distribution files related to each of the platforms will be installed on the computer.