Building Automation Knowledge Base

Issue Edit > Host Computer > Software Restore results in pop-up error "No entries in data base" Product Line TAC INET Environment I/NET Seven host Cause The network configuration does not have any entries saved in the database. Resolution Go to Edit > Host Computer > Network Configuration In the Link Summary window, find the correct Link. If the Cnf column has a plus sign (+) in it, then this link is not saved. If the correct link is not shown, reference Error: "No Entries in Database" for more information. Highlight the correct link and press "Save" With the correct link highlighted, click "Penetrate" Any controller with a + in the Cnf column has not been saved. Click "Save All" Hit "Close" on the Station Summary and "Close" on the Link Summary. There are now entries in your database. The software restores should now show the correct options. For instructions on performing a software restore, see How to upgrade bin and SAV files in I/NET controllers

Issue A Deny Entry Tenant Message is given instead of a valid card read. Product Line TAC INET Environment I/NET Seven AMT Cause The Deny Entry Tenant message is delivered when the credential read is not known to the controller for any of the following reasons: The door being read is not part of the individuals tenant. The SLI does not have the correct database Card Translation is incorrectly enabled/disabled in the door editor There is a hardware error with the Card reader. Resolution General Steps: Determine if the issue only happens to a single individual or a group or all cards. Select Access>Tenant. Verify that the door has been added to the correct tenant(s) Select Edit>Individuals and browse to the card(or a test card) in question. Verify that the card has the been added to the door correctly. Follow the directions in How to force a download of card data to force a download. If this fixes the issue, go to the "SLI does not have the correct database section" In AMT, select window options and add the message column to the window Find a Deny entry tenant message and see if the message column matches up with Hex card number for the badge that was read. If all you get is a scrambled number, There is probably a hardware error. Verify Card Translation is Enabled (this section assumes you are using large card number format) Select Access>Doors Modify the door in question Check the box next to "Card Translation". If this option is not available you will need to flip Dip switch 7 on the SCU Compare this setting to a few other doors on the system. Thy should all have the same setting Hardware Error The easiest way to prove a hardware error is to plug a spare card reader directly into the DPU or SCU. If the problem is immediately solved replace the field reader. If not, try unplugging other readers on the controller and see if the problem goes away for that reader. It is possible that the controllers power supply is no sufficient to power the reader. Use an external power supply instead. Various known fixes for SLI database Errors: Take the SLI to it's boot state and restore bin file and database files from the Server If you are using I/NET 2.15-2.21, upgrade to 2.31 Insufficient memory: The SLI will allocate memory for all possible individuals in a tenant regardless if they are used or not. For example, if the site has only 500 cards, but the tenant is set to 32000 individuals, this will use the same controller memory as a site with 25000 individuals.  Reducing the number of individuals allocated in the tenant has been shown to clear up Denied Entry Tenant messages. System traffic: In I/NET 2.31 and above, the filemaster or server will indicate when badge data is being downloaded on a status bar in the bottom right hand corner of the screen. If this indicator is constantly showing downloads, it is due to poor system communication causing constant polling of the database.  Follow these steps to fix this issue. Turn Automatic DPU restore off on all links and wait for the download messages to stop. (this is done by selecting Edit>Host Computer>Network Configuration, then modifying each link) Wait for the automatic downloads already requested to finish. Re-enable Automatic DPU restore on each link, one at a time. Wait for the system to finish individual downloads before moving on. When you find a link that take an excessive amount of time (compared to others) to finish downloading, troubleshoot that links controller LAN wire.

Issue If using TAC Informer (Product development within Australia / New Zealand region), product has no further support and now longer works with I/NET Seven 2.40 or higher.  Receive either of the following errors: * I/Net Alarms     'Alarms' I/Net connect failed - I/O Server create failed OR * I/Net Alarms     'Alarms' failed to start - I/O Server create failed Alternatives with sending SMS alarms with I/NET Emailing alarm solutions for I/NET  Product Line TAC INET Environment I/NET Seven 2.4x or above TAC Informer (Pager TAP) - Product sold within Australia / New Zealand region. Cause Application developed by Australia (support for this product ended in 2005) now does not work with I/NET 2.40 or above. There are a few alternatives and possible workarounds, but this product is no longer supported. Resolution There are couple of alternatives: Currently the TAC Informer software will work with 2.31 or lower, so you can use these versions of I/NET Seven software. It may be possible that loading the I/NET 2000 compatibility files from the I/NET Seven CD may allow connection to the current INetIoSrv.exe file. The steps for this are as follows: Copy DbSrv2K.exe and INetIoSrv2K.exe from the CD “Support \ INET2000_Backward_Compatibility” directory into I/Net Seven's Program Files directory. From a DOS command and from the C:\Program Files\Inet Seven\ folder; Register both programs from the command line: DbSrv2K /regserver INetIoSrv2K /regserver Note: If you need to unregister these files use the following syntax: /unregserver  Alternatively it is recommended to use the email feature within Xenta 527 Web Server (Refer to Troubleshooting sending emails from a Xenta Server) which can then be configured with a third party mobile message service provided by Redcoal (www.redcoal.net).  They provide a set of simple Desktop applications which allow SMS to be sent via desktop application or via email.  Click Here for further information.  Customer will require to setup an account and charges do apply. Note: This provider only operates in Australia.  Third alternative is to use a solution provided by a company called NotePage, product name is PageGate - Refer to PageGate I/NET Seven Programming Instructions for further information.  Benjamin Roswall has developed a tool which is available on the community: TAC INET Notifier.  The program will look for alarm events in the SQL database, and process then according to the settings. The program has its own alarms list, and if the service is stopped, it will save the alarm list so that only new alarm events are processed when the program comes back online. For emails you just need to know your SMTP server configuration, and for SMS it uses the SysManSMS program that has a SMTP to SMS feature. Also, the program can write to a text file, and SysManSMS can then look for this text file. Please note Schneider Electric do not endorse this product but provide this option as a workable solution. All support issues related to these products should be directed to the developers / providers of the respective software.

Issue There is a beeper inside some of the card readers. In some cases when alarms happen, such as Door Forced or Door Open Too Long, the beeper can be activated with a sound to deliver alarms. Product Line TAC INET Environment I/NET Cause In some cases this application is needed. Resolution Open the Door parameter in I/NET. Set the relative alarm message. For example, set the Door Open Too Long or Door Forced to Alarm.   Click the "Sounder" button Change the polarity to "Low". Set the relative beeper type and condition. For example, when the Door Open Too Long or Door Forced happens, the beeper activates continuously. For more issues about beeper in I/NET, refer to Reader beeps continually when connected to the door controller.

Issue AMT message stop coming through after re-installation of I/NET Product Line TAC INET Environment I/NET Seven all revisions. Cause If you re-install I/NET from a clean install.  That is you have uninstalled I/NET initially, AMT masking is cleared from the Host PC. Resolution Go to AMT Configuration (Edit > Configuration) Select the correct distribution group and mask settings for the site They must match the source points so that you receive the correct alarms and messages for that Host PC. For further information refer to TCON 299 - Chapter 6 "Message / Alarm and Printer Masks" If this still does not resolve your issue then refer to article AMT not receiving Data for additional items to check.

Issue When restoring I/NET database backup from another server in DBcreate, it shows an error: Error dropping PRIMARY KEY 'PK_DvrServers': Could not allocate space for object 'sys.sysserefs'.'clust' in database 'InetDb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET SQL Server Cause Each SQL express version has its own database size limit. Refer to SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL. If the database size limit is reached, I/NET database will fail to update. The backup of the database will be fine, but when trying to restore onto another computer, it will also fail. Resolution 1. If the original I/NET server is still running, try to enable archive function to shrink the database in I/NET. And also follow Archiving and SQL database size keeps growing to set the database cap. 2. If the original I/NET server can't run, or the original database has been deleted, try to use SQL server version with higher size limit or full version SQL server which hasn't physical size limit. Like try to restore the backup from SQL 2005 Express (4GB limit) to SQL 2008 R2 Express (10 GB limit) or Full version of SQL 2005/2008. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue A 7791 is used specifically for what? Product Line TAC INET Environment I/NET Site Cause A 7791 is used on security/access control installations. Resolution It is the interface for Door Processing Units (DPUs). (TCON209, 1-20) TCON Number and Title Cross Reference (with links) is TCON information. Explain and define I/NET Ethernet, C-LAN, and Sub-LAN communication is a chart to explain further.

Issue The card reader beeps continually when connected to the door controller with the Sounder cable connected. Product Line TAC INET Environment I/NET Cause There may be several causes for this situation: The door which this reader belongs to isn't configured. The polarity setting of the reader beeper isn't correct. This reader port is damaged due to certain cause. Resolution The following steps need to be followed: For cause 1, configure the door and reader in Door parameter. For cause 2, click "Sounder" button in the Door parameter window and change the "Polarity" setting correctly. Usually change from "High" to "Low". For cause 3, send the door controller to repair. For how to set up a beeper in I/NET, refer to How to use the Beeper of the Card Reader in I/NET.

Issue What are the new features that are available in the 3.xx firmware version of the DPU. Should we upgrade to the latest EPROM revision for the DPU 7910A / 7920A If we do not upgrade the EPROM will I/NET work properly. 7910 / 7920 DPU Transactions not showing up in AMT - including Disabled / Deny Entry Sel / Deny Entry Schd (Schedule) 7910 / 7920 DPU Door Editor changes not downloaded to controller. Editor changes revert back to None. Product Line TAC INET Environment I/NET Seven DPU 7910A / 7920A 2.23 and above. Cause The recommendation is to always upgrade to the latest revision. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Note: The implications are that if you choose to leave the EPROMs at the earlier revision, and you enable the new features which are a "Global" setting (for example User defined PIN) then the DPUs with the unsupported firmware will not accept these changes even though you have defined this at the Host. If you require these features then you MUST upgrade the DPU which require these features and / or fixes. Resolution I/NET Seven is backward compatible with all previous hardware firmware revisions of the DPU. The recommendation is too always upgrade to the latest revision to enable all of I/NET's features and fixes included in these revisions. In some cases this is not always possible. Please review the information below to determine if these features and fixes are required for your installation. Note: The implications are that if you choose to leave the EPROMs at the earlier revision, and you enable the new features which are a "Global" setting (for example User defined PIN) then the DPUs with the unsupported firmware will not accept these changes even though you have defined this at the Host. If you require these features then you MUST upgrade the DPU which require these features and / or fixes. If you have any additional concerns then please contact Product Support. Below are the New Features introduced in firmware revision 3.00: This release contains changes to support a real time clock and the ability to report messages with seconds. The DPU now supports generating an alarm for a card read of a card that has been disabled. The DPU now supports the use of User defined PIN numbers. The DPU now supports soft and graced APB. The DPU has been modified to handle the new user defined Duress scheme. The DPU now has the capability of generating a Reader Tamper Alarm by configuring a two bit DA at bit offset 4 for door 1 and 5 for door 2. Click Here to review the changes for EPROM firmware revisions 2.23 through to 3.04 for both the DPU 7910A and DPU 7920A. For SCU range of controllers refer to I/NET Security Control Unit (SCU) firmware releases. 

Issue Expanding a system with a 7798B and unable to connect to other controllers. Product Line TAC INET Environment All versions of I/NET Cause There is no expansion card to connect the LAN Controllers together. Resolution The 7798B requires a CLX Expansion Card to be plugged into the slot to allow it to communicate to other controllers. The part number for this is LAN EXPANSION OPTION FOR RS-485, CLX. See Additional information on CLX LAN Expansion Option for RS-485 for more information on the CLX part. Take the device off the wall, unplug all wires including power. Insert the CLX card into the slot on board, be careful not bend any pins while doing this. Connect the wires again in their respective terminal with the LAN wire connecting to the CLX card, Sublan to those devices and power. Put the device back on the wall, set up accordingly and it should be communicating to the controllers now.

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

Issue When there are dual NICs on the computer, you will get host number conflicting error. The IP address causes this conflict is just the local IP address. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET prior to Version 2.44a Win 7 or higher OS Cause When there are two NICs on the computer, I/NET needs to know which NIC is used for communication. I/NET support for dual Network Interface Cards (NIC) can be used for dual NIC configuration for I/NET. But under Win 7 and higher OS, wireless NIC can't be recognized in I/NET, which makes it impossible to choose wireless NIC to be used for I/NET. In the I/NET configuration, it just shows 0.0.0.0. Resolution I/NET will fix this issue in the new release. For I/NET prior to version 2.44a, there are two workarounds for this issue currently: Refer to I/NET support for dual Network Interface Cards (NIC) to choose onboard NIC to be used for I/NET communication. Disable onboard NIC or just disconnect it from the network. Then you will see the option for choose NIC for I/NET communication will be grayed out. That will force I/NET to communicate with wireless NIC. Remember to reboot I/NET I/O server after this to make it take effect. 

Issue When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Product Line TAC INET, TAC Vista Environment I/NET XBuilder I/NET Host Tool Cause When a specific application request exceeds the standard capability of I/NET it is sometimes possible to use XBuilder to expand possible applications. Resolution This is a sample access control application to demonstrate the possibility. Minimum requirements for this are :Xenta 527 Web Server. If you wish to use Menta Programming, use a Xenta 731 or Xenta 913. Application: Customer Requests an Audible Buzzer be triggered when a door is forced open, but not shut off until the alarm has been acknowledged. Create a DO point to controller your buzzer/light/alarm indicator (buzzer DO) Create an internal AO point to function as a translator (logic AO) Add a Calc to the buzzer DO: ~(P0=C0) where P0 is the logic AO and C0 is 80 Perform a Station save In XBuilder, create a project for the 527 Web Server Insert or re-insert the I/NET network Add a connection object Drag the Flags attribute of the Doors DO point to the "from" part of the connection object Drag the Value attribute of the logic AO point to the "to part of the connection object Generate the Project and Send to Target. The response time of the buzzer coming on or going off is dependent on the Scan interval of the buzzer DO.  The reason it works is that the flag attribute of the Door point will equal exactly 80 if you have an alarm flag and the point is still in alarm (the alarm has a value of 64 and unack has a value of 16 totaling 80. See Decoding the I/NET signal "flags" attribute for more information). The door point will stay in alarm until it is acknowledged so this will stay at 80 until someone acknowledges the alarm, or puts the point in Manual/Test.  The Buzzer will not activate if the point is in Manual or Test The above solution will trigger off any alarm specified from the door editor (Door Open To Long, Door Forced, Bad Card read, etc).  Turn off the other possible alarms, or create an addition internal point labeled Door Forced.  The Door DO point can trigger an event sequence based on Forced door to control the additional point. If you do this the calc will need to be modified to ~((P0=C0)|(P0=C1)|(P0=C2))  C0=16 C1-64 C2=80. This will allow for the buzzer to be on until the point has been acknowledged and return to normal

Issue When using SQL 2008 or SQL 2008 R2, I/NET will crash randomly. Referring to the system Event Log, you can see a SQL error happened just before I/NET crashed, called "There is insufficient system memory in resource pool 'internal' to run this query." Product Line EcoStruxure Building Operation,TAC INET Environment I/NET SmartStruxure Cause According to Microsoft Knowledge Base, this problem occurs for all the following reasons: There is a bug in the code that is used to evaluate how many rowsets are required to perform a sorting operation. Therefore, the code greatly overestimates the numbers of rowsets. The required grant estimate in full-text is 64 pages for each rowset that is required to sort. There is a large request that blocks the system from using the memory that is reserved for the full-text query. Resolution Install the newest SP to the SQL 2008 or SQL 2008 R2 being used. Download Microsoft SQL Server 2008 SP3 Express Edition or Microsoft SQL Server 2008 R2 SP2  Express Edition from the Microsoft website. If this doesn't help, please follow Create Error Log for I/NET to turn on the error log for I/NET and then send the log in to your local country product support group for further troubleshooting.

Issue No Trends are showing up in the Data/Enquiry Editor when a point is selected. Product Line TAC INET Environment Xenta 527-NPR Webserver 5.1.6 Cause Changes in the Xenta 527 firmware in version 5.1.6 and later have resulted in some problems I/NET trend data displaying in the Xenta 527-NPR. Resolution To resolve this, the best option is to downgrade the Xenta 527 to version 5.1.5, per Download an .MOT file into a Xenta Programmable controller and restart the device and I/NET again.

Issue Operating System Selection when using SQL Server Product Line TAC INET Environment I/NET Seven Site Cause Making decisions on operating system selection while using SQL Server 2000 Resolution If your site has grown beyond the capabilities of the Microsoft SQL Desktop Engine (MSDE) as discussed in Customer Advisory CA-2004-04 then you need to decide upon an operating system to use when you upgrade to SQL Server 2000. SQL Server 2000 Enterprise Edition and Standard Edition can run on the following operating systems: Windows Server 2003, Standard Edition Windows Server 2003, Enterprise Edition Windows Server 2003, Datacenter Edition Windows® 2000 Server Windows 2000 Advanced Server Windows 2000 Datacenter Server Source: http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.mspx An option to consider based on the needs of the customer is whether Windows Small Business Server 2003 Premium Edition can meet their needs. This version sells at almost the same cost as SQL Server 2000 (5 CALs), however it includes much more. Windows Small Business Server 2003, Premium Edition includes the following components: Microsoft Windows Server 2003 Microsoft Exchange Server 2003, Standard Edition Microsoft Shared Fax Services Microsoft Office Outlook 2003 Microsoft Windows SharePoint Services 2.0 Health Monitor 2.1 Remote Web Workplace Microsoft Internet Security and Acceleration Server 2000, Standard Edition with Service Pack 1 (SP1) Microsoft SQL Server 2000, Standard Edition with Service Pack 3a (SP3a) Microsoft Office FrontPage 2003 It is important to note that there are some restrictions built into this version of Windows Server 2003. These restrictions limit it to only a single domain solution and can only expand up to 75 users or device connections. Windows Small Business Server restrictions Windows Small Business Server provides a cost-effective suite of programs for small businesses that have 75 or fewer users or devices. To help you prevent unapproved network installations and to help you protect your networks against viruses and other attacks, Microsoft has placed the following restrictions on the use of Windows Small Business Server: You must install all the component server programs in Windows Small Business Server on a single computer. No component may be installed on a separate computer. If you want to run one or more of the component services on a computer other than the Windows Small Business Server-based computer, the other computer requires separate licenses. You can connect a maximum of 75 users or devices to a Windows Small Business Server-based network. This requirement limits the number of users or workstations that can access one or more of the component server programs. Windows Small Business Server is a single-domain solution that is not intended to be integrated with other Windows-based domains. You are not permitted to establish explicit trusts to other Microsoft Windows NT-based domains or to Active Directory directory service domains. Also, Windows Small Business Server does not let you create child domains. The computer that is running Windows Small Business Server must have all operations master roles and must be at the root of the Active Directory forest. The following features that are available in earlier versions of Small Business Server are not available in Windows Small Business Server: Microsoft Shared Modem Service Microsoft Terminal Server Windows Small Business Server supports up to two physical CPUs and up to four virtual CPUs with hyperthreading. Note: Earlier versions of Windows Small Business Server support up to four physical CPUs. You can have other domain controllers and member servers in your Windows Small Business Server-based network. However, the computer that is running Windows Small Business Server must be set up as the root domain controller of an Active Directory forest. This requirement may prevent the computer that is running Windows Small Business Server from serving as a corporate branch office server or as a department server of a large organization that is based on Active Directory or on Microsoft Windows NT 4.0. You cannot add Windows Small Business Server to an existing domain. You must install a Windows Small Business Server-based domain and then add additional domain controllers or member servers to the domain. When you run Exchange 2003 on a Windows Small Business Server-based network, Exchange 2003 cannot be part of a larger Exchange 2003 organization. Because Windows Small Business Server is installed at the root of the Active Directory forest, you cannot install Exchange 2003 components that belong to an existing Exchange 2003 organization. Source: http://support.microsoft.com/default.aspx?scid=kb;en-us;842690 Windows Small Business Server 2003 Premium Edition is a good solution for jobs where the controls contractor will be managing the server operating system that is the core of the BMS.  Many customers today will allow controls contractors to utilize their IP infrastructure but want the system managed and maintained by that same controls contractor.  This software allows that contractor to provide a turn key installation and include all PC hardware and software.  Windows Small Business Server 2003 Premium Edition is also a very cost effective solution for jobs where the specification requires a server operating system or a full version of SQL server that the contractor must provide.  It is recommended that if Windows Small Business Server 2003 Premium Edition is used, any software that is not needed on the server is disabled (i.e. Exchange Server, Fax Services, SharePoint Services).  In conclusion, Windows Small Business Server 2003 Premium Edition is a cost effective way to provide SQL Server at a site if all criteria are met.  Update: If using I/NET 2.40 and above, please check this compatibility matrix for Operating Systems when using SQL Server For other compatibility issues, see Software and Firmware compatibility matrix for older versions of I/NET, Vista, Andover Continuum, Satchwell Sigma, I/A Series, and StruxureWare Building Operation.

Issue Ordering, installing, wiring of CLX LAN Expansion board. Product Line TAC INET Environment I/SITE 7798 CLX Cause There is not any CLX-specific installation guides or manuals. This article is intended to give some basic information about the expansion board and its use. Resolution Part number: CLX Part name: LAN Expansion Option for RS-485 Part description: I/SITE Expansion Board - adds controller LAN communications to network other controllers to 7728 & 7798 - RS-485 CE/EMC Compliant Comments: Plugs on to 7798 base unit, RS-485: 19,200 or 9600 baud, SDLC, token-passing. Wiring: Terminals 1 and 2 on the CLX are Controller LAN +,- respectively. For more information on installing the CLX expansion, see CLX Expansion Card for 7798B .

Issue Essex Pin Pad Reader Programming in I/Net Seven. Product Line TAC INET Environment Any Windows OS Version and I/Net Seven Version Cause Need to program an Essex Pin Pad reader in I/Net Seven. Resolution Here is the link to programming the Essex Pin Pad Reader Essex Pin Pad requires the site is not using Large Numbers The Essex Pin Pad is for site which wish to use Pin only for entry. Not Pox Card + Pin or Prox only. For information on a Prox card access which includes Pin Pad see HID PIN Pad reader for I/NET Part Number. For a higher security Pin Only option comparable to the Essex see Code-Guard Scramble Pin Pad Reader Programming.

Issue Installing I/NET on a PC using MSDE and MSDE won't start. Product Line TAC INET Environment I/NET Version 2.40 and above Windows 7 MSDE Cause MSDE does not run on Windows 7. Resolution If the user has attempted this, more than likely the OS has corrupted SQL. There are a couple of things that can be done as described in Verify in Windows Registry all items are deleted after uninstall of I/NET Seven and MS SQL. However to return the PC to its original state the best bet would be to reinstall the OS, or a backup prior to the installation of I/NET.

Issue All or a group of Analog Inputs on my Controller (DCU 7700) are reading high (flooding), in alarm and / or displayed as "OLD'. Product Line TAC INET Environment I/NET All model series DCU 77xx Cause The inputs on a DCU 7700 are 1-5 Volt DC inputs. If the voltage of an input goes above 5 Volts DC the voltage will flood across the other inputs and they will all go out of range or OLD. Resolution To diagnose the problem sensor perform the following: Measure all inputs (Between terminal 9 and the respective input terminal) one at a time and identify the input that is the highest voltage (above 5 Volts.) Disconnect this input and then place your meter between terminal 9 and the identified input terminal. The excess voltage will slowly drain away and all the other points will come back into normal operating range. If the voltage does not drop repeat the above steps. Replace / Repair the fault sensor(s). Also refer to Analog inputs are reading too high or too low on a 7780.