Building Automation Knowledge Base

Issue Need a wiring diagram of the breakout box connections between the Reader and the 7910 or 7920 DPU. Product Line TAC INET Environment I/NET site Cause Need a wiring diagram of the breakout box connections between the Reader and the 7910 or 7920 DPU. Resolution Recommend you look in TCON 112 (Readers) for illustrations the match your requirements. Check for TCON Number and Title Cross Reference (with links).

Issue Are there any documented guidelines for using large number in Access Control? Product Line TAC INET Environment I/NET Site Cause Are there any documented guidelines for using large number in Access Control? Resolution Begin by referencing TCON 300. All SLIs and DPUs must use I/NET Seven revision 1.x (or later) compatible binary software. All DPUs must have DIP switch 7 set to ON. Within a single tenant, you can assign a large key/card number directly to an individual, or translate the number using the Key/Card Translation table, but not both (i.e., you cannot have duplicate key/card numbers or individual numbers within a single tenant). Use compatible EPROMs in the DPUs Note: If you directly assign a key/card to an individual, and later translate the same key/card for another individual, only the translated key/card will be operational within I/NET. Other useful articles: SCU dip switch 6 for dual station addressing How to convert existing Idisc to large numbers (Hex) DPU memory allotment in a 7910A and a Non-mipped 7920

Issue Require Upgrade or Repair part number and pricing information Product Line Andover Continuum, TAC INET Environment Dongle / Security Key and Software upgrades Controller node count, X Driver or option upgrades Cause Part numbers are not listed for Upgrades or Repairs. Global Product Support do not provide pricing information. Resolution Repairs do not have part numbers, you should contact your local Order Entry department who will be able to provide an RMA form and pricing information.  (Note: An exception to this is if you are in Aus/NZ, repairs do have a part number. Repaired items are set-up in Pronto with the part number prefixed by “4-“. Process and form details for Aus/NZ repairs only.) Upgrades have now been allocated part numbers for all current products. The order forms and details of the new part numbers can be seen here. SAP and other quoting system have been updated with these upgrade part numbers. Contact your local Order Entry department to help you place an order and provide pricing information.

Issue Having trouble communicating to an NPR or other I/NET hosts over a slow/busy ethernet. Product Line TAC INET Environment Any Version of Windows OS and Any Version of I/NET Seven Cause You can make I/NET more tolerant of communication delays over the IP network by making the following change. Resolution Open regedit. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\CSI - Control Systems International\I/Net 2000\Configurations. Select your active profile. On the right side, right click and modify the DWORD value "EthernetTimeout" and click "Decimal". The default value is 500mS or half of one second. Increasing this value will determine how long I/NET waits for a response over the ethernet before it gives up. Raise it to 1000, 2000, 2500, etc. and see if it helps. For additional information please see NPR's giving you "Host Lost - Host Restore" messages.

Issue What are the limitations of the Xenta 527 when used with TAC Vista and I/NET. What do I need to consider when integrating I/NET with TAC Vista. Product Line TAC INET, TAC Vista Environment TAC I/NET TAC Vista 5.1.6 and above TAC XBuilder TAC Xenta Server 527 5.1.6 and above I2V Cause Integrating I/NET into Vista. Resolution Below are a few considerations associated with the Xenta 527 Server that may assist when integrating existing I/NET systems with TAC Vista: As in all case the latest versions of both hardware and software should be used on any integration project. The attached datasheet indicates that the TAC Xenta 527 Web Server has been tested with up to 1000 I/NET points, if you require to integrate more points than this it is then recommended to add additional Xenta Servers to cater for this.  You may also consider segregating your I/NET System to improve performance. Currently it is not possible to pick and choose which points are imported into the XBuilder project, it can only be limited to which SAV file (or controller) is imported . Note: Each I/NET point type, as shown below, creates the following number of TAC Vista objects - these include; Alarm, State, Value, Control, Test, Manual, Alarm_ack etc, and vary according to the point type used. I/NET Point Type Number of TAC Vista Objects created DO 14 AO 11 AI 10 PI 10 DI 11 DA 11     The impact to consider here is the time it takes when adding or modifying your Xbuilder Project. This usually means that importing a large number of SAV files will cause the Vista server to get extremely busy creating / importing all of these objects.  It is best to let the process complete before selecting any other window.  Note that the total number of objects created during the import of the I/NET points is not counted as part of the 'tested' 1000 point limit stated in the above datasheet. This is a separate consideration. Network performance can be affected when a large number of connection objects are in use (so direct transfers between I/NET and Vista). There is no documented limitation, but the recommendation is not to exceed 300 connection objects per Xenta 527 Server.  For information on what the effects a connection object on the I/NET controller LAN has and how to calculate this, refer to Connection Objects in Xenta Server effect on I/NET system. Engineering of any I/NET feature apart from Point Control, Trends, Time Schedule and Alarm Configuration can only be done using the I/NET Host Tool or via an I/NET workstation.  Access to these features are via the Xenta 527 web server feature, so pages appear as HTML pages within TAC Vista, this will have a different look and feel to both Vista and I/NET users.   Other Knowledge Base Articles as listed below are also available to assist on integrating I/NET and Vista: Unit conversions when integrating LON to I/NET Vista to I/NET Integration Tips    Decoding the I/NET signal "flags" attribute Viewing I/NET Point Names in Vista Workstation instead of Addresses User Defined Units on I2V integration were accidentally set incorrectly SQL Host not passing data to Xenta 527 Web Server

Issue Tables needed for linearizing a 10K thermistors for an I/Net 7716, 7718, 7728 and 7756 (upper board). Product Line TAC INET Environment 7716 7718 7728 7756 Cause Thermistors require the use of a look up table to linearize the data. Resolution Thermistor Inputs on PCU's 7716, 7718, 7728 and the upper board of a 7756 Enter the Temperature data in °C (First Column - 31 entries) Enter the corresponding resistance data in Ohms (Second column - 31 entries) Enter the dissipation constant in milliwatts per °C: 2 Low Temperature: -22.11°F (-30.06°C) High Temperature: 247.92°F (119.95°C) Point Value in °F: M=0.065942; b=-22.11377 Point Value in °C: M=0.03663447; b=-30.063207 Look Up Table: °C Ohms Current Self Htg Adj °C Adj °F VDC Counts Adj Cts 120 389 0.000481 0.045052 119.95 247.92 0.1872172 153 4095 100 680 0.000468 0.074521 99.93 211.87 0.3183521 261 3548 90 917 0.000458 0.096177 89.90 193.83 0.4199872 344 3275 80 1258 0.000444 0.12407 79.88 175.78 0.5587138 458 3001 70 1753 0.000425 0.158633 69.84 157.71 0.745767 611 2727 60 2489 0.0004 0.199471 59.80 139.64 0.9964769 816 2453 55 3045 0.000383 0.223671 54.78 130.60 1.1671138 956 2316 50 3602 0.000368 0.243359 49.76 121.56 1.32407 1084 2179 45 4368 0.000348 0.264484 44.74 112.52 1.5200445 1245 2042 40 5326 0.000326 0.283435 39.72 103.49 1.7375701 1423 1905 35 6691 0.0003 0.300218 34.70 94.46 2.0043736 1642 1768 30 8056 0.000277 0.308878 29.69 85.44 2.2308374 1827 1631 28 8777 0.000266 0.311174 27.69 81.84 2.3371678 1914 1576 26 9572 0.000255 0.312351 25.69 78.24 2.4453301 2003 1522 25 10000 0.00025 0.3125 24.69 76.44 2.5 2048 1495 24 10450 0.000244 0.312349 23.69 74.64 2.5550122 2093 1467 22 11420 0.000233 0.311127 21.69 71.04 2.665733 2183 1413 20 12490 0.000222 0.308669 19.69 67.44 2.7767897 2274 1358 18 13680 0.000211 0.304953 17.70 63.85 2.8885135 2366 1304 16 15000 0.0002 0.3 15.70 60.26 3 2457 1249 14 16470 0.000189 0.29383 13.71 56.67 3.1110691 2548 1195 12 18090 0.000178 0.286579 11.71 53.08 3.2200071 2637 1140 10 19900 0.000167 0.278241 9.72 49.50 3.3277592 2725 1086 8 21920 0.000157 0.268921 7.73 45.92 3.433584 2812 1032 6 24180 0.000146 0.258715 5.74 42.33 3.5371562 2897 977 0 32660 0.000117 0.224329 -0.22 31.60 3.8279419 3135 815 -4 36200 0.000108 0.211999 -4.21 24.42 3.9177486 3209 706 -10 55340 0.0000765 0.162028 -10.16 13.71 4.234772 3468 543 -14 69000 0.0000633 0.138199 -14.14 6.55 4.3670886 3577 435 -20 97130 0.0000467 0.105789 -20.11 -4.19 4.5332773 3713 272 -30 177200 0.0000267 0.063207 -30.06 -22.11 4.732906 3876 0 This spreadsheet is for a thermistor rated at 10,000 ohms at 25°C. Install a 10K Ohm Resistor in the "B" terminal (consult the TCON for the controller you are using for details) This look up table program is based on using 31 entries The data points do not have to be evenly spaced For the look up table to the 7756 lower board, see 10k Thermistor Look Up Table for an I/Net 7756 (lower board).

Issue Receiving "Deny Entry Sched." (Schedule) transaction message for all individuals on a single Interface (SLI). Receiving "Deny Entry Sel." (Select) transaction message for all individuals on a single Interface (SLI). Product Line TAC INET Environment I/NET Seven Traditional Elevator Control Cause In traditional elevator control, the Reader (Door Point) must have a schedule assigned for the Group / Individual to allow access to the Lift (reader) itself. Then in Floor Maps you can allocate access to the individual Floor Points. In the floor mapping you must also remember to allocate the associated floor points otherwise the Individual is not Scheduled to have access to the floor (Hence a Deny Entry Sched message is received). Recommendation is to migrate sites to Extended Elevator Control which makes this process much simpler. For details of this refer to Extended Elevator control (Step by step instructions). Resolution Under Access Elevators check that the Floor mapping is correctly set for each Floor DO point. If no DO 's are selected for that particular Tenant Schedule, the individual will receive a Denied Entry Sched when attempting to gain access to the floor. Deny Entry Sel (Selection) is received when the Elevator Reader is not selected for the Tenant / Group or Tenant / Individual. A schedule (Group or Personnel) must exists on the reader (door ) point for the Group or Individual in question. A list of all Event messages, and their descriptions, received in AMT is available in AMT Event message definitions.

Issue I/NET Physical Layer Issues, Lan Reconfigure, and/or Controllers going on or offline 1 at a time. Product Line TAC INET Environment I/NET Cause Physical Layer Issue Resolution Some or all of the following may indicate a physical layer issue. Abnormally large number of Lan Reconfigure messages Controllers going offline individually or in groups and sometimes all together Large numbers of Station Lost/Restore Messages Frequent problems connecting to controllers and data interruption To Troubleshoot a suspected Physical Layer error: Determine if this is a Controller LAN layer issue by direct connection to the Controller LAN using a tap.  If you continue to experience the same errors, as while connected via TCP/IP then the issue is on the Controller LAN Verify that you are using the correct wire gage (22 or 24) and that you controller LAN is less than 4000 feet for 24 AWG and less than 5000 feet for 22 AWG. Verify shield drain wire. Shield drain wire continuity must be maintained as the LAN cable passes through each controller. Shield drain wires from each controller LAN cable must be twisted together, insulated, and tied back such that wires do not come in contact with ground or any conductive surface within a controller. Shield drain wire must be directly connected to Electrical Service Earth Ground at only one end of the cable. The issue at this point can either be a wiring fault or a controller that is broken. Disconnect all controllers from the controller LAN by removing the LAN terminal strip from each controller Reconnect each controller one at a time and watch for the original errors. During this process a LAN Reconfigure is expected each time a device comes online While at each controller watch for any frayed wire, unusual/unneeded splices and if needed re-seat each wire into the terminal block When a controller is brought online and the error returns, examine that leg of the LAN wire for shorts or replace that section of wire Replace the suspect controller with a different device to ensure that the controller is not the source of the problem. (On critical systems you can plug in a spare controller at the location for testing without taking the existing controller offline) Typically if a controller is causing the error it will display alarms or LAN reconfigure on it's LEDs. Consult the TCON for the specific controller for more details (TCON Cross Reference available in TCON Number and Title Cross Reference (with links)). If it is not feasible to replace long sections of wire, or if it is determine that the controller LAN exceeds the specified length, then you may want to consider using Distributed Link Architecture.

Issue Does I/NET support dual NICs (Network Interface Cards)? Is it possible to change which network interface card I/NET uses? Dual Network Interface Cards (NIC) will not allow selection between the Networks, option is grayed out. Product Line TAC INET, EcoStruxure Building Operation Environment I/NET 2.40 and above Cause Requirement for I/NET to have dual NIC support and option to change which network interface card I/NET uses. Resolution A New feature released with I/NET Seven 2.40 now allows I/NET to support dual network interface cards (NIC). The intent is to allow I/NET and Video the capability of using different Ethernet networks. This option also allows which network I/NET (and / or Video) uses. These settings are changed via the Advanced WAN Configuration (Advanced IP button) via the I/NET Configuration Editor (see image below). Requirements: I/NET Configuration needs to have TCPIP enabled and hardware (Ethernet card) needs to be installed on PC, I/NET (or I/O Server) must be running to select the Advanced IP button (Advanced WAN Configuration). If the PC is configured with multiple network cards, the above shown drop-down lists will be active: I/NET network Video network Use the drop-downs to select a network card for each network. You can use the same card for both networks, or you can use a unique card for each network. By using two networks, you can separate I/NET traffic from video traffic and conserve bandwidth on each network. NOTE: If you have dual Network Interface Cards and you are not able to select between these networks (so they are grayed out) you must have the following minimum requirements configured for this option to be available in the I/NET Editor: A Physical connection to its connection media. (i.e. A connected network status. If you have a status indicating Limited or no connectivity you will not be able to select between Interface cards). Valid IP address and subnet mask Valid Gateway IP address. (If you have no gateway router on the network then select a valid IP address within the same IP range, usually the IP of the PC is the best option here.) If you are using wireless NIC and have issue to choose it, refer to Host number conflict on a computer with dual Network Interface Cards (NIC).

Issue Receiving the following error when attempting to navigate to the Xenta web interface. "TAC C503Boot/x.x.x.x not configured". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 511, 527, 555 Xenta Server 701, 721, 731 Cause Device web interface has stopped working or flash drive / hard disk has been corrupted on the Xenta Server. Resolution Attempt the following steps to resolve this problem: Try restarting the device and see if the unit comes back online, remember to wait 1-2 minutes for the unit to restart.  Check the RUN LED on the panel, if the LED is a solid green this indicates the device is running normally, and your access should be restored. If the LED is RED, solid or flashing this would indicate a problem with the device. Attempt to restore or upgrade the device to the latest firmware.    You can download the latest firmware version from the Schneider Electric Exchange. If this fails then then reference Xenta Server "Run" light is solid red with no communication via Ethernet.

Issue Problems receiving emails from Xenta 511/527 Product Line TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause Some email servers have been found to filter UTF-7 character encoding as spam. The Xenta products require this encoding to support Swedish characters, but this can be configured by manually editing some files. Resolution Use an FTP program (Internet Explorer) to connect to the Xenta you are trying to change and download the \sys\langstring.cfg file. Edit the file and modify the following lines to replace all instances of 7 with an 8: ALARM_CODE_1= =?utf-7?Q? ALARM_CODE_3=charset=UNICODE-1-1-UTF-7 Upload the edited file back to the Xenta device Cycle power The device will now use UTF-8 character encoding which is more commonly used in the United States. For more troubleshooting tips, see Troubleshooting sending emails from a Xenta Server.

Issue Where are the reports of fixed issues/bugs for the various product lines located? Product Line TAC Vista, TAC INET, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, EcoStruxure Building Operation, EcoStruxure Building Expert, Access Expert, Security Expert Environment Technical Product Announcements Cause TPAs contain information of changes made per version of the different product lines. A TPA may report enhancements and/or broken functionality. Resolution Navigate to Exchange Extranet to view all TAC Vista documents tagged as TPA. The documents will be listed in reverse chronological order. Log in to view these documents. See Register for The Exchange Download Center for more information on registration.

Issue 3:15am Time Sync error in AMT Product Line TAC INET Environment I/NET site with DCU Time Sync enabled Daylight Savings Time Cause Outdated SAV file No DST observed Enabled DCU Time Sync from Host PC Resolution Make sure versions of Bin Files are up to date with current revision of I/NET across all controllers. For how to do this read How to upgrade bin and SAV files in I/NET controllers.  Make sure SAV files are backed up and current. For how to do this read How to upgrade bin and SAV files in I/NET controllers. As the host workstation synchronizes the daylight savings time settings in a controller, it will also check for the existence of a corresponding SAV file. If a SAV file for the controller is found, the host workstation processes it as follows SAV file is current If the controller's SAV file is current, the host automatically updates it with the daylight savings settings from this editor. This ensures that if you later restore the controller using this SAV file, the correct daylight savings time settings will be downloaded. SAV file is old If the controller's SAV file is out-of-date, the host does not change it. In this case, you can manually update the controller's SAV file or use the Automatic DCU Save function in order to create an up-to-date SAV file for the controller. Refer to Station Save and Restore for more information.  Beginning with I/NET revision 2.41, I/NET allows the DCU Time Sync and no observance of DST.  Work around is to remove DCU Time Sync if your time zone does not observe DST.

Issue Video of DigitalSentry system can't be seen in I/NET. Alarm of Endura system, for example Motion Detection or Video Server Offline can't be shown in AMT. Product Line Pelco, TAC INET Environment I/NET 2.41 Cause The possible cause is that when installing SarixSDK of I/NET 2.41, there will be an error: Error 1904. Module C:\Program Files\Pelco\Common Files\IntegralPelco4600 dll fail to register. HRESULT-2147220473. Resolution The possible resolution is to uninstall the SarixSDK, delete the Pelco folder in Program Files folder and reinstall the SarixSDK. The error should disappear during the installation. And then video and alarm should be able to appear in I/NET. For more issue about video that can't be seen in I/NET, refer to Video in Endura/Digital Sentry System Can't be Shown in I/NET.

Issue The I/Net Seven Help button goes to Windows Help instead of I/Net Help Product Line TAC INET Environment I/Net Seven Software versions 2.40, 2.40A, 2.41, 2.42 and above. Windows 7 (32Bit & 64 Bit), Server 2008R2 (32 Bit), Server 2008R2 (64 Bit)       Note: In Windows 10 (64 Bit) the Online Function was removed by Micrsoft Cause There are some Windows Downloads, from the Microsoft Web site, that needs to be manually installed on the PC.    Resolution Go to TCON Number and Title Cross Reference (with links) and download TCON 298 (Dated 4/12) Chapter 1, Page 2 see the note in the middle of that page for the required windows download to solve this issue. Also if you look in the readme.txt file in any of the I/Net 2.4X release you will see this comment: 9. If installing I/NET on Windows 7, Windows Server 2008R2 or Windows Server 2008R2 64 bit the following must be done to allow I/NET online help to work.  I/NET Seven's online help is a 32-bit ".hlp" file. In order to view I/NET Seven online help on Windows Vista, Windows 7 or Windows Server 2008, you must first download "WinHlp32.exe" from Microsoft and install it on your workstation. Note: there are different downloads for 32 bit and 64 bit OS's WinHlp32 downloads.   Links to download WinHlp32.exe: Windows 8.1 : http://www.microsoft.com/en-US/download/details.aspx?id=40899 Windows 8 : http://www.microsoft.com/en-US/download/details.aspx?id=35449 Windows 7 : http://www.microsoft.com/en-US/download/details.aspx?id=91 Windows Server 2008 : http://www.microsoft.com/en-US/download/details.aspx?id=19771 Windows Server 2008 R2 : http://www.microsoft.com/en-US/download/details.aspx?id=4424 Windows Vista : http://www.microsoft.com/en-US/download/details.aspx?id=5143

Issue Downgrade SQL 2008 to SQL 2005 Restore from SQL 2008 to prior version. Product Line Andover Continuum, TAC INET, TAC Vista Environment SQL 2008 used by Building Management Software Cause Have database loaded on one machine using SQL 2008 and would like to move or change to SQL 2005 Resolution Golden Rule: A SQL 2008 database cannot be downgraded or restored to a SQL 2005 version. It is not possible to downgrade a database or a database backup. The SQL schema will not allow it.  For your current version of SQL: C:\Program Files\Microsoft SQL Server \80, \90, \100 Folders are the client tools. 80 = SQL Server 2000 90 = SQL Server 2005 100 = SQL Server 2008 How ever, it is not a rule. Since 2008 creates both 80, 90. The only way to find what versions are installed (besides regedit) is by the Sql Server Configuration manager.    For other SQL options related to I/NET, please visit SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL.

Issue Invalid or phantom Links, Hosts and IP's in Netcon.  This symptom exists when you penetrate Network Configuration and there are Links and NPRs that you have no clue as to who they are or where they came from. Product Line TAC INET Environment I/NET NPR-2000 Xenta 527 Cause This can happen is if a laptop was used to connect to the system from a different Network or from the outside. Once connected, its IP address and any link it shares are broadcasted to the other devices like PCs and NPR’s, thus populating the table with entries that do not belong or are non-existent for this location or system. It can also happen if you install an NPR/527 or replace  one with a unit that has been used elsewhere. If that use NPR/527 is being used as a reference host, it will infect the system with every IP address and Link in its routing tables. Resolution At this point there is no way to get it out of the tables except to Telnet into all devices, remove the IP tables and rebuild them from scratch. This may be a cumbersome process depending on the amount of devices that make up the system (PCs, Laptops and NPR’s). All of these would need to be set back to 0 reference host while the cleanup is being done. To get this cleaned up, follow the steps to start a Telnet session:   Go to Start > Run and type Telnet then hit Enter. Type open at the end of the prompt, hit the space bar and then put in the IP Address of the NPR/PC and hit Enter. A logon prompt will come up, type csi and hit enter Now type LA, this lists all the entries in the table. Type delall and hit enter. This clears out all the IP’s of the other devices. This would have to be done on all the devices. Once completed, start I/NET to verify that those are gone and then start referencing other PC’s, Laptops and NPR’s to get the system back online again. Note: The proper way to use a Service/Maintenance laptop that is used for multiple customer sites is to direct connect to the NPR to see the controllers of the other links that exist at the site. However, before starting I/NET on the service/maintenance PC, open Windows Explorer, C:\Program Files\Inet Seven and delete the XXX.dat files. These get rebuilt when I/O Server restarts, it also clears out all entries in the routing tables. See .DAT files.  You may also create a different configuration profile for each site. This will also keep the tables separate.

Issue Effects of leap year with schedules and BMS Product Line Andover Continuum, TAC INET Environment I/NET Site Continuum Site Time, calendar, Gregorian Calendar Cause Leap year adjustment in calendar Resolution I/NET: I/NET will not be affected by Leap Year occurrence if DST and Time Sync is correct in the host computer. For Time Sync errors, please refer to Time Sync Error, Daylight Saving setup, please refer to Configuring Daylight Savings Time. Continuum: Continuum will not be affected by Leap Year occurrence to controllers or scheduling if the Cyberstation has the correct time. There have been no incidents in the past with regards to leap year. Leap year is no different than some months having 30 days, others having 31. More information on time sync of controllers check Time sync controllers to workstations. To sync Continuum to an external time clock read Synchronize Continuum system to external time clock.

Issue DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2 'Cannot open backup device ' C:\Users\Administrator\Desktop\20120919'. Operating System Error 5( Access is denied). [Microsoft][ODBC SQL Server Driver] [SQL Server] BACKUP DATABASE is terminating abnormally' Product Line TAC INET Environment I/NET loaded on Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2 Cause The cause is insufficient rights to perform this function based upon a local policy of not allowing users to see the 'C' drive. Resolution Although when Using a Network Administrator account or Administrator for the local machine, you cannot open backup to either the local machine 'C' drive or a network share, you should be able to backup to a thumb drive.  Go to local disk properties - security tab Users do not have permissions to modify or write to the 'C' drive. Windows UAC may over ride the administrator permissions. Check your permissions and make sure you have rights to a folder and perform the backup. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.  

Issue The order of installation is dependent upon the SQL versions installed with Vista and I/NET. I/NET DBCreate does not open after installation is complete.  DBCreate application is not shown even though under Task Manager processes the application is active. Product Line TAC INET, TAC Vista Environment SQL MSDE Express Vista and I/NET Installed on the same PC Cause Vista and I/NET both use SQL databases for purposes of event and trend logging.  They must be installed in the correct order to coexist within the shared SQL installation. It can be confusing to know which software should be installed first on a certain installation because it is completely dependent upon both the I/NET versions and Vista versions.  Later versions are compliant with SQL 2005 Express while earlier versions must use SQL MSDE. Resolution If a previous installation has failed, it is best to start "fresh" before attempting a re-install. Removal of Vista instructions located here: How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Removal of I/NET instructions located here: Procedure for uninstalling I/NET Seven on a stand-alone host Empty Recycle Bin to remove evidence of previous installations.    Use the following guidelines to determine in which order to install I/NET and Vista: If the I/NET version is prior to 2.2.1, then I/NET must be installed before Vista, regardless of the Vista version. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 4.3.0 through 5.0.0, and the I/NET version is 2.2.1 or higher, then Vista must be installed before I/NET. These versions of Vista use TAC Config and SQL MSDE. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 5.0.1 through to 5.1.6, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET. These versions of Vista use SQL 2005 Express.  I/NET versions 2.2.1 and higher have an option to install SQL 2005 Express. When prompted during the I/NET installation, allow a new SQL instance on the existing SQL 2005 Express that was installed with Vista.   If the Vista version is 5.1.7 and above, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET The default installation of this version of Vista uses SQL 2008 R2 Express.  When prompted during the I/NET installation, select Default Instance of either MSDE or SQL 2005. (Note that if installing on Windows7 operating system, MSDE option is grayed out and cannot be selected, as it is not supported on Windows7)..   If the Vista version is 5.1.7, and the I/NET version is 2.4.0 or higher, you can choose either one to be installed first. If Vista is installed first, by default Vista will install SQL 2008 R2 Express SP1. But I/NET 2.4x fails to recognize the instance installed by Vista, while also fails to create a default instance. So after installed Vista, manually create a default instance for I/NET, and then install I/NET. Refer to Item 1 in How to Troubleshoot on DBCreate on how to create it; If I/NET is installed first, you can choose Custom Installation for SQL during the installation of Vista. You need to manually enter the SQL instance name, SQL username and password when installing I/NET SQL. If you don't know the instance name, there is a quicker way to identify it: Open DBCreate of I/NET, and you can see the SQL server name for I/NET. Just copy and paste it here. Then you can finish the installation. For Vista IV installation, the correct procedure can be found here: TAC Vista IV and Peripheral Software Installation Outline