Issue Upgrading from EBO 2.0.x to 3.0.x causes I/NET to become incompatible. After upgrading to 3.x the I/NET controllers do not come online. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure Building Operation (version 3.0.1 and later) I/NET Seven Software (version 2.44 and above) Cause I/NET Seven Software is built using a 32-bit interface. Starting with EBO 3.0.1, EcoStruxure requires the use of a 64-bit interface. Resolution For INET seven to operate with EcoStruxure Building Operation 3.0.1 it is necessary to obtain a 64-bit DLL from the Exchange and install it in the INET installation prior to the upgrade. Search for INET IPortAPI64 - Software on Exchange.  Download the IPortAPI64_EBO.dll. Unzip the DLL and copy the DLL to the same folder as the 32bit INET install, by default this will be C:\Program Files (x86)\INET Seven folder. Note: if INET was installed in a different folder this can be found by examining the Windows registry key ”INETSevenPath” at HKLM\SOFTWARE\WOW6432Node\CSI - Control Systems International\I/Net 2000/Configurations. Install EcoStruxure Building Operation 3.0.1 When the ES restarts the InetPlugIn will connect to InetIoSrv via the 64-bit IPortAPI64_EBO.dll.

Issue After transitioning an INET security system to Security Expert, SCU1200 and SCU1280 controllers do not come online Product Line Security Expert, TAC INET Environment Security Expert Controller (SP-C) I/NET SCU1200 I/NET SCU1280 Cause The INET-to-Security Expert transition brings each SCU1200/1280 into Security Expert as an Input Expander but there is a known issue that causes the devices to remain offline. R&D is working on a fix. Resolution The workaround for bringing a SCU1200/1280 controller online in Security Expert is to create a Reader Expander and then edit the inputs and outputs associated with the SCU1200/1280 to point to the Reader Expander you’ve just created.   Important:  Create a backup of your Security Expert database before proceeding with the instructions that follow.   For a transitioned SCU1200/1280, create a Reader Expander as follows: In Security Expert, navigate to Expanders > Reader Expanders. Choose a Controller from the drop-down list. Click the Add icon. Define a Name for the expander.  The transition tool would create a name like SCU1200 <703503> for the expander.  In this example, the SCU’s link address is 70, its station address is 35, and its point address is 3. When manually defining the name of the new expander, you may wish to use this naming convention to keep the system uniform. Set the Physical Address of the expander.  This address should be 1 higher than the point address of the SCU.  So, for SCU1200 <703503>, the point address is 3 (703503) and so the physical address of the expander should be set to 4. Set Port 1 Network Type to “Third Party Generic”. Set Port 2 Network Type to “Third Party Generic”. Expand the Commands section and enter the following commands:       PortOne=INET       HardwareType=INET Navigate to the Reader 1/2 tabs and perform the following steps: Set Reader 1/2 Keypad Type to “None”. Uncheck Allow Reading Opened/unlocked. Uncheck Display Card Detail when Invalid. Navigate to the Reader 1/2 Options tabs and perform the following steps: Uncheck Door Sense Enabled. Uncheck REX Enabled. Uncheck Invert REX Input R1/2. Uncheck Always Allow REX R1/2. Save the expander. When presented with the Configure Module wizard, perform the following steps: Set Inputs to 0. Set Outputs to 0. Uncheck Add Trouble Inputs. Uncheck Add Doors. Click Add Now.   Edit the inputs associated with a transitioned SCU1200/1280 as follows: In Security Expert, navigate to Programming > Inputs. For each input associated with the SCU1200/1280, change the Module Type to “Reader (RD)”. Save the input.   Edit the outputs associated with a transitioned SCU1200/1280 as follows: In Security Expert, navigate to Programming > Outputs. For each output associated with the SCU1200/1280, change the Module Type to “Reader (RD)”. Save the output.   When you have finished with all of the steps above, perform a Module Update on the Reader Expander.  Repeat these steps as necessary for other SCU1200/1280 devices.  Once you have verified all SCU1200s/1280s are working properly, you can delete the Input Expanders that were created by the transition tool since they are now unnecessary.

Issue How to run I/NET Seven Software as a local user Customer does not WIndows User logged in with Local Administrator rights to run I/NET Seven Software  Product Line TAC INET Environment Windows 7 Windows 10 I/NET Seven Rev 2.41 and above  Cause The IT department requires that I/NET Seven runs using a Windows "User Group" instead of the usual "Local Admin" Resolution   Define the Windows User Account Temporarily log into the PC with the desired User account using “Local Admin/Administrator” rights. Turn off the “User Account Control: (UAC) following the directions defined in this article Windows 7/10 User Account Control Settings  If this is not done then every time you try to enter an I/Net editor, using the “User” Group you will be asked to login as a “Local Admin” Change the User account back to the "User" Group I/NET Seven Feature Matrix: Review the following table showing all the editors both the “Local Administrator” and the “User” can access with their “Windows” Rights. Note: **The I/Net Editor “DbCreate Functions”. If you log into "DbCreate with the "SQL Server Authentication" then these items will be "Y". If you do not give the "Windows User" the SQL Username and Password then these items will be "NO"   User Account I/NET Seven Operation Administrator  User Install I/NET Y NO Remove I/NET Y NO Upgrade I/NET Y NO I/NET Configuration Y Y       DBCreate Functions     Create db Y Y ** Import I/Net 2X Y Y ** Verify existing db Y Y ** Remove existing db Y Y ** Backup db Y Y ** Restore db Y Y ** Import Docutrend Archive Y Y ** Upgrade db Y Y **       Seven Reports     View Y Y Run Y Y Configure Y Y Save Y Y Print Report Y Y Mount Archive Y Y View Archive Y Y Run Archive  Y Y Print Archive Report Y Y       Archive Configuration     Event Archive Configuration Y Y Run Y Y Trend Archive Configuration Y Y Run Y Y View  Y Y       I/O Server Configuration     Promote Filemaster Y NO Demote Filemaster Y NO Promote Client Y NO Demote Client Y NO  

Issue Importing Infinet devices into AS-P fails with the following error "Invalid Data Error: Invalid_Data (0x10000) in module Coml(11). "Invalid cast from null": CreateObjectRequest".  Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Cause Infinet devices have a space character within their names Resolution Remove the space character and use an underscore in its place.

Issue Some helpful basic IP commands. Product Line Other Environment Computer with IP NIC or Network Cause Need for basic IP configuration or IP address Resolution Go to start, click run and type in "cmd". This takes you to the command prompt. Type in: "ping xxx.xxx.xxx.xxx" to see if your device is online and its response time. Make sure you put the space between "ping" and "xxx". "ipconfig" and hit enter to get the info of the computer you are currently using. You'll get the IP address, subnet mask and the gateway. "ipconfig/all" and hit enter to get more info on the machine your using. It will give you all the above and then some including the DNS server addresses. "tracert xxx.xxx.xxx.xxx" and hit enter and you can see the servers that you are going through to get to your destination. This can be used when connecting to a Loytec or a iLon and the IP address is being presented to the L-IP or iLon is unknown. Connecting through a firewall/gateway/NAT server, you are not presenting the PC's address - when you do the tracert you will go through your gateway and the next address will be the IP you are presenting- Use this in the iLon as the LNS server address.

Issue Unable to open graphics that are on a shared network drive Product Line INet, Continuum, Access Expert, Security Expert Environment Windows 10 Chrome Windows IE Cause A registry setting is overridden or needs to be reset that was not previously not there. Resolution This is a Microsoft Issue. Here is a link that describes the resolution: https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command

Issue Complexity of SQL and which version is compatible  Product Line TAC INET Environment TAC I/NET Seven and congruent Windows Operating System. File Master, Filemaster, EqualizedClient, Compatibility, SQL, SQL 2008, Full SQL, SQL 2005, SQL2008, SQL2005, SQL Express, Express SQL, MSDE, 2.31, 2.40, 2.40a, 2.41, Server, XP, Windows 7, 7, 32-bit, 64-bit, Microsoft SQL, Service Pack, SP Cause Filemaster and either Equalized Client or Remote Client is desired. Problem is to know which versions of SQL are compatible. Resolution Below is a handy chart designed to help in determining what versions of SQL are compatible in I/NET Seven. Pertains to MSDE, SQL Express, SQL 2000, 2005, 2008. File Equalization Chart       Note: 1. Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, 2008, or 2008 2. It is strongly recommended that you defragment the PC’s hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. 3. The use of any edition of Microsoft SQL Server 2005, 2008, or 2008 R2 will require that the PC have at least 2 GB of RAM. 4. No Express edition of Microsoft SQL Server can be used on a TAC I/NET Seven filemaster. Golden Rule: You cannot move the db or downgrade from I/NET db SQL 2008 to I/NET db SQL 2005, see Downgrade SQL 2008 to SQL 2005, What version is used? 

Issue What is Remote Client with I/O in the Workstation Type in the I/O Server? Product Line TAC INET Environment I/Net Seven version 2.4x with need for Remote Client configuration using a Remote SQL Server. Equalization, FileMaster, File Master, Equalized Client, Remote Client, Equalize, FM, EQ, RC, MSDE, Express, Full SQL, SQL, TCP/IP, Connection Cause Remote Client changes with I/Net Seven version 2.4x  Resolution The new option of Remote Client with I/O for the Workstation Type begins with 2.4x version of I/Net Seven. This option is for a SQL Server which is not located on the Filemaster or Standalone but rather a separate Server. The Remote Client with I/O must be running for other standard Remote Clients to get the features such as AMT, Trends, and Network Functions. Network Functions can be found in I/Net on the pull down menu Edit/Host Computer/Network Functions. The configuration is in the I/O Server under the current profile and can be found in the Workstation Options.  HINT: Exit the I/O Server (and I/net) and select Start/Programs/I/Net/I/Net Configuration to be able to setup the Remote Client. Remote Client is not show unless you exit I/O Server. Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Remote Client with I/O. I/Net version 2.4x Remote Client with I/O Clicking the link below will open a pdf document which will show how the communication should be setup if selecting Filemaster, Equalized Client, or Remote Client. I/Net version 2.4x Filemaster, Equalized Client, or Remote Client Suggestions for further info: To install the SQL, go to Installing I/NET Seven on a 64-bit operating system. For more on how to set up that Remote Client with I/O to use that SQL database, see Unable to connect Remote Client to Standalone Server. 

Issue Seven Reports Error "CRPaige library CRPaig80.DLL cannot be found". Product Line TAC INET Environment I/NET site with Windows OS Cause Missing CRPaig80.DLL error message Resolution CRPaig80.DLL can be found on the original I/NET Seven installation CD (cd-drive:\program files\inet seven). Copy CRPaig80.DLL to the root I/NET Seven folder (c:\program files\inet seven). Click Here to download a zipped copy of the CRPaig80.DLL

Issue How do the 7793 and 7798 handle retries?  Improving I/NET sublan communications Excessive MCU Lost messages in AMT Command Error messages in AMT Product Line TAC INET Environment I/NET sublan 7793, 7798 Cause If there are issues on the physical layer of the network, this will effect the reliability of I/NET communications. However, these risks can be lessened with some best practices. Resolution Best Practices and Troubleshooting measures to improve sublan communications: Ground the 24V line coming into MRs and ASCs Connect ground to the earth ground terminal of DPUs and SCUs. Bond the shield of the LAN cable all the way through the network, not landing it on any controller anywhere and then tie it to earth ground in one location. (see diagram)   SubLAN Communication Explained: The first packet to any sublan device goes out on the primary channel, terminals 1 and 2 of the sublan connector on the 93/98. If the device doesn't respond in time, a second packet is sent out on the alternate channel, terminals 4 and 5. If there is still no reply, a third packet goes out on the primary Finally, if there is still no reply, that device is marked as lost which generates an "MCU Lost" message. Optional Configuration for only using Terminals 1 and 2:  If you are using only Terminals 1 and 2 you could be missing 33% of it's retry capacity. If you follow wiring guides and best practices the device will answer on the first packet every time, however if you have not followed the guide all it takes is a little noise to make the retries necessary. If you are unable to use a loop configuration, or want to avoid the extra potential for noise and EMI, in stall a jumper on the sublan connector from terminal 1 to 4 and from terminal 2 to 5 The allows you to get the extra retry, without the extra cable This will also function if you have some controllers on channel A and some on Channel B The SLI doesn’t have to be at the end of line on sublan communication  

Issue Sunrise/Sunset does function correctly in I/NET Seven rev 2.16 Sunrise/Sunset workaround in I/NET Seven 2.16 Product Line TAC INET Environment I/NET Seven rev 2.16 Cause Currently there are some issues with Sunrise and Sunset working correctly in I/NET Seven rev 2.16. The follow steps are given as a work around to solve these issues. Resolution There are two different ways to make this work correctly: Add some starts between the Sunrise and Sunset. It is important that these starts do not have any days of the week defined.   Use a Cycle between the Sunrise and Sunset. It is important that this Cycle does not have any days of the week defined.  

Issue After upgrade of Xbuilder or opening a project built on another computer generating the project causes a "File not found:" error message.   Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment XBuilder Cause Find the alarm or event page that is causing this problem and view the reference field to identify the cause of the problem.   XBuilder was upgraded and the xmle files from the previous version are no longer present. XBuilder installation directory was on a different drive on the computer the project was last used on. Resolution In Xbuilder, right click on all the Alarm and Event pages, select Change reference, and browse in the new path to the referenced file.  

Issue 3 State Event Sequence to control certain Access Control Doors Product Line TAC INET Environment I/NET site Cause Three State control requirement Resolution   When using the Door Points ("08" & "09") with event sequences, the following actions will occur: A “Start” command is equal to the “Secure Mode” of the door A “Stop” command is equal to the “Unlock Mode” of the door A “Lock Door” command is equal to the “Lock Mode” of the door

Issue How do I properly acknowledge and purge a "Force Door" alarm in AMT. Product Line TAC INET Environment I/NET Access Control Cause The return to normal condition (Door Normal) "Message Type" must have the same "Message Type" as the alarm cause (Forced Door).  This is the same condition as for DOTL (Door Open Too Long) alarms.  For I/NET to clear both these alarms. the Message Types must match within the Door editor. Resolution You have to properly configure the Door editor before you can properly remove this from AMT. In order to acknowledge and purge a "Force Door" alarm you must have the "Force Door" entry set to "Alarm." The "Door Normal" should also be set to "Alarm."  

Issue Can I use the Xenta 527 on an old I/NET 2000 system? Product Line TAC INET Environment I/NET 2000 Cause Adding a Xenta 527 to an I/NET 2000 network. Resolution Yes you can, provided you set the Xenta 527 up to be compatible with I/NET 2000.   With the Xenta programming cable (P/N 3-781-0128-0) inserted in port "B" of the Xenta 527, go into Windows Hyper-Terminal and make the following changes for the Xenta 527 to operate in an Inet 2000 program.     Please be aware that I/NET 2000 is no longer a supported product and this mode should be used at your own risk.  

Issue USB Prox enrollment reader for I/NET Seven Environment I/NET Seven Cause I/NET supports the use on an Enrollment reader via the Hosts PC Serial port, most PC's no longer have serial ports.  One solution is to use a USB supported reader which can be sourced by the supplier listed in the resolution  Resolution The USB enrollment reader is made by RF Ideas. It is very easy to program for use in the I/NET Seven System. After you program certain steps it becomes a "Plug and Play" device at the job site. To set up this USB reader please consult this whitepaper.

Issue The "Transactions Individual" report in Seven Reports does not sort the transactions by Date and Time. Product Line TAC INET Environment I/NET Seven Seven Reports Cause The "Transactions Individual" report is not sorted by Date and Time Resolution The "Transactions Individual" report is not sorted by Date and Time for a reason. I was determined by TAC, that the customer needs to design the method by which they want this report to be presented. This White Paper will define how to go about setting the Sort process by the Date and Time Option. Start Seven Reports and open the “Transactions Individuals” report Once the report is fully developed on the screen. Choose the “Design” tab In any of the blank white area do a “Right Mouse” Click In the “Popup” window selects the “Report” Option In the next “Popup” window selects the “Sort Records…” Option In the next “Popup” window you need scroll the left window unit you find the “RptEvents.DateTime” Option. Then Select the “Add” button the place the “RptEvent.DateTime” Option in the right window. After you do Step 6 this is what you will see in the right window You need to highlight the “RptEvent.DateTime” function. Then select either “Ascending” or “Descending” sort order.  In the “Ascending Mode” the “Oldest Date” is on the top of the list and the most “Recent Date” is at the bottom of the list.  In the “Descending Mode” the most “Recent Date” is on the top of the list and the “Oldest Date” is at the bottom of the list. I selected the “Descending” Mode as the way I wanted to sort the Date and Times. You also need to select the “OK” button to finish the setup process. You need to close out of this report. Select “Yes” button to save the changes you made in the “Canned” report. Remember to rename you newly created report to something other than the Original “Canned” report name.

Issue   Error message: "Failed to run DcuXml.exe" when importing I/NET .sav files into XBuilder Product Line TAC INET, TAC Vista Environment XBuilder 1.6.0 Cause When XBuilder imports I/NET save files, it does a simple batch of all of the save files for the import process. It creates a path for the import into XBuilder. A typical path might look like this: C:\TAC XBuilder Projects\MyProjectName\Files\INET\dcu0102,dcu0103,dcu0104 This example shows the import of 3 I/NET save files with a character length of 72 for the batch process. This process is limited to 2048 characters. Importing 15-20 save files will cause a crash.   Resolution To squeeze a few more save files into XBuilder, shrink that path as much as possible. For example: Rename the default "TAC XBuilder Projects" folder to something shorter. Rename the project to something shorter. Move .sav files to another location, even temporarily to the C:\ drive root to eliminate extra path data. Example:  C:\XBPrj\MyPrj\Files\INET\dcu0102.sav.  This path shrinks the directory at the front end to allow for more save files on the backend.

Issue Importing I/NET 2000 Graphics into I/NET Seven Product Line TAC INET Environment I/NET Seven Cause Have you upgraded from I/NET 2000 to I/NET Seven and the graphics at the site has either stopped working, don’t come up with the correct back ground or bitmaps and the size is all wrong? Resolution There are a few things that you need to verify after the upgrade. Verify that the path for both symbols and bitmaps that was used in I/Net 2000 is the same for I/NET Seven. If this is not done then the pages when opened in I/Net Seven would come up with a blank background or without a bitmap and or symbols. To find the original path (if unknown): Open the Graphics Editor Select File> Open to edit the graphics page  Select View > Page Properties In the Backdrop area (shown below) is the original path of the background bitmap.   If you only have a few graphics then you can edit and modify this for each of the graphic pages  Alternatively make sure all the bitmaps used are still located in the path defined here. All folders with Bitmaps and Symbols are all the same, even if you have to create a new I/Net 2000 folder on the new PC. If you were using 800 X 600 on the original pages, then you’d have to change the resolution on the new PC to the same. If this is not done, then the pages will show smaller and the points would be distorted.

Issue There is a possible corruption of the SQL Database and the DCUxxxx.sav files when upgrading I/NET Seven from Rev 1.xx to I/NET Seven rev 2.13 and above Product Line TAC INET Environment I/NET site 1.xx Cause Corruption of the SQL Database and the DCUxxxx.sav files Resolution If you do a fresh install of Inet Seven 2.13 and above and restore an Inet Seven rev 1.xx SQL DB. There is a possibility of having the SQL Database and the DCUxxxx.sav files getting corrupt if you do not properly save the NETCON file. The example below is an Inet Seven rev 1.06 SQL database that was restored to a fresh install of Inet Seven rev 2.14. This is what the NETCON file looks like; if you do a station restore at this point you will corrupt the system. Look at step 2 for the correct way to handle this. Taking the above example and changing it to look like the one below will prevent the corruption from occurring in the Inet Database and DCUxxxx.sav files. Please NOTE this issue will be corrected in Inet Seven rev 2.16 and above. Note: Remember while you are in the NETCON editor; penetrate each station in the MCU summary page. Edit and Save each DPU entry so that the “Type” is correct DPU type (7910, or 7920). Also, save the revision of something close, such as 3.03 or 3.04 for the 7910 & 7920. Make sure that there are no “*”, “Blank spaces” or “0.00” displayed when you are done. Also make sure you “SAVE” NETCON all the way down to the door level.