Building Automation Knowledge Base

Issue MSDE to Full SQL database Product Line TAC INET Environment I/NET site currently using MSDE and wanting to convert to Full SQL database Cause The size of a site may have grown beyond the limits imposed by the existing SQL database.  The site may want more information available in the database thus pushing beyond the size of the current database limits. SQL and version compatibility for Filemaster, Equalized Client, Remote Client, Limitations of SQL: For information on your current SQL compatibility Resolution Here is a list of articles which may be useful with installations of I/NET: Installing I/NET Seven on a 64-bit operating system Equalize Client in Windows 7 64-bit with I/NET 2.42 or higher SQL 2008 and Windows 7 SQL 2008 Install Tips Installing 2008 SQL R2 Express for 2.42 Also: The Windows 7 HAS to be the professional version to work with I/NET. The Home Edition will not work. Assuming the site is using File Equalization it requires FULL SQL 2005 on the 32Bit and Full SQL 2008 R2 on the 64Bit on the File Master. The other PCs can have the express version of SQL, but the Express has to be the same version. If database size is expected to get above 4Gig, then full SQL would be needed on the FileMaster as well as each Equalized Client There is really no way to make a comprehensive list of every single step required at every site. Site knowledge is key but this list may be beneficial. It is assumed the site has a Filemaster (FM) and several Equalized Clients (EQ). Make a backup of db, then make a second backup. Copy those onto another location for safekeeping. Make sure all firmware at site is at correct revision Save archive information on each computer Make note of each pc for I/O configuration information Bring each EQ computer to a stand alone state including Filemaster Make backup of each pc’s db and archive info, graphics pages, etc for safe keeping Discover what database is on each EQ and FM. I assume the FM has MSDE, which all the others would have as well. From FM uninstall I/NET Remove all the I/NET folders from FM Remove SQL on FM Install Full SQL on FM Install I/NET and use Full SQL instance on FM Create blank database on FM Check that db from SQL Management Studio Express Restore db from backup on FM Repeat steps 8 – 13 on each of the StandAlones except using SQL Express In I/O configuration, point each StandAlone at FM which makes them EQs Setup your archiving config for site Go through each link in Network Configuration and check for communication Go to AMT and check messages

Issue Various problems with converted TGML graphics Bindings of the I/NET objects within Building Operations have wrong and / or illegal point address. Environment I/NET integration with SmartStruxure Cause Improper preparation before converting graphics may cause nuisance issues. Resolution Ensure the following is done when converting a sites I/NET graphics to TGML Before converting the graphics to TGML Ensure all save files are current Ensure the I/NET network configuration is current Before importing the graphics to StruxureWare Ensure that all affected controllers are imported.  Do not change any names or descriptions before importing graphics Upload any controller which indicates it is required. This will ensure that point names for graphic bindings are correct. In the INET Interface path box, enter the path to where the INET interface is located in WorkStation. This setting affects the bindings that get defined for objects in the resulting TGML file(s). If you accepted the default name when you created the I/NET interface in WorkStation, this path is typically /Server 1/INET Interface/.  Make sure this matches the installed system details.   Click Here to get more detail from the Online Web Help. Check out the I/Net Transition: Graphics Conversion video on the Community website.

Issue NPR Connectivity over the Internet Product Line TAC INET Environment I/NET NetPlus Router (NPR) Series 2000 Cause In most cases when communication occurs over the Internet, firewalls are in place to block non typical ports.  I/NET utilizes Ports 50069 (set by default).  These ports usually need to be configured within routers to allow I/NET to communicate correctly. Resolution Receiving messages from one I/NET System to another over the Internet through an NPR that is behind a Firewall. In order to accomplish this there are several steps that need to be done. Configure the NPR with a static IP Address. Set the Host Masking to send and receive messages (this will not be available when directly connected). Remove the NPR from behind the firewall and connect outside the firewall. Connected directly to the Internet. Set the Host Masking so that it can receive messages. Once communications have been established, You can now replace the NPR back behind the firewall. Also refer to Which ports must be open on a commercial router in order to communicate with an NPR over a WAN? which discusses ports utilized by I/NET. For cases where you are using the Xenta Server 527 NetPlus Router (NPR) refer to TCP/IP Ports used by the I/NET system: UDP Port Settings.

Issue How to integrate I/NET with Pelco Analog Matrix in order to implement some features, such as: Switch specific camera image to specific monitor. Switch specific camera to specific preset and display it on specific monitor. Product Line TAC INET Environment I/NET Pelco CCTV system Pelco Matrix Cause In some projects there is demand for access control system to integrate with analog CCTV system to do the alarm interaction. I/NET can integrate with Pelco CCTV system with ASCII code communication. Resolution I/NET communicates with Pelco analog CCTV system through ASCII code. There are two kinds of communication port for Pelco matrix, which are RS232 and RS485/422. For RS232 port for matrix, an RS232 to RS 232 cable is needed. If there are no COM ports for computer, an USB to RS232 converter is needed. For RS485/422 port for matrix, an RS232 to RS485/RS422 converter or USB to RS485/422 converter is needed. Connect the I/NET server to Pelco matrix through this converter, and the steps below should be followed: Open the I/O Configuration of I/NET, and choose the port for text output port and baud rate for the port communicating. In the AMT, choose Edit--->Text Library, and click Add. Choose a point for alarm interaction, and the status of the point to activate the interaction: alarm, acknowledge, return to normal (RTN) and acknowledged/return to normal (RTN). In the text area, enter the ASCII code for matrix. For the two applications of the alarm interaction, different ASCII code should used: 1Ma1#a, which means switching 1# camera image to 1# monitor 1Ma7#a1\\a, which means switching 7# camera to 1# preset and display it on 1# monitor. Here "\a" is an escape sequences for I/NET, so we need one more "\". Then the integration with I/NET and Pelco CCTV system is finished. When the specific point goes into alarm, then the specific camera can be switched to specific preset and displayed on specific monitor. For more applications of the integration with Pelco analog matrix, refer to the documentation for the Pelco ASCII Protocol Manual. And for more information about how to set text output in I/NET, refer to Text Output through RS-232 Port in I/NET.

Issue DBCreate unable to run after installation. If installing I/NET on new PCs or upgrading to 2.42 and DBCreate does not start after selecting it from Programs > I/NET > DBCreate. Product Line TAC INET Environment SQL 2008 Server 2008 Windows 7 Windows XP Cause The SQL Browser needs to be enabled in the Services to get it to run. Resolution Run the SQL 2005 Backward Compatibility 64-bit option or 32-bit based on the OS. Restart I/NET Configuration Editor Modify the active profile and click on the Connections button. Verify that the database shown is the correct one that is being connected to and click on the okay button. Start I/NET again and verify that you can login and start the program again. See Initialization Error when starting I/NET for information that may also be helpful.

Issue Host conflict window always pops up, and cleaning routing table doesn't help. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause Host conflict is a normal issue happening in I/NET. It is usually caused by the duplicated host ID setting on different servers, or an engineer laptop is inserted into the network with the same host ID setting with some server. And the routing table will be messed up since all the IP related information will be recorded in the routing table and it will be distributed to all the network devices, including all the servers and NPRs. The usual solution is to clear all the routing tables on all the network devices, . Refer to How to Remove the Routing Tables in a Device or PC about how to clear the routing tables. But if the routing table is cross referred, like Server 1 adding NPR 1 and NPR 2 as reference hosts, while NPR1 adding Server 1 and NPR 2 as reference host, the routing table will never be cleaned out since when you clean the routing table for Server 1, NPR1 and NPR 2 will still try to send their wrong routing table to Server 1. Unless all the network devices are disconnected and the routing tables are cleaned one by one, or disable the 50069 port for the whole network, which is used by the communication between network devices, there is no other way to clean them out. And these two method are not applicable sometimes. Resolution If the routing table can be managed well, such kind of issue will never happen. The best practice on adding reference host and creating routing table is: On the servers: Choose one server as the master reference host. All the other servers add this server as reference host. Don't add NPR as reference host. All the NPRs can be added into the master server by clicking on the NPR button in I/NET configuration and added one by one manually. By this way, the master server can build its own routing table without impacted by other devices. And this one is the only routing table in the whole network. On NPRs. If NPR doesn't need to talk to other NPRs, like transferring indirect points, there is no need to add reference host for NPR. If indirect points are needed, just add the master server as the reference host. Then this NPR will be able to see all the other NPRs based on the routing table on the master server. If the master server is not equipped with UPS, or not always promises to be online, another master NPR can be chosen as a secondary reference host. Add this NPR as a reference host to all the servers and other NPRs. Under this scenario. if the routing table needs to be cleaned, only the master server and the secondary reference host need to be cleaned. It will be more easier to clean all the routing table and get rid of the host conflict error.

Issue Unable to create a backup of an I/NET Seven Database using DBCreate, gets a backup failed error. Product Line TAC INET Environment Windows XP, Windows Vista OS, with SQL 2000, 2003 and 2005. Cause Functionality of the host pc and the database seems to be inconsistent. Resolution Option 1: Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy INetDb.mdf and INetDb_log.ldf to an alternate locations (located in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data) Restart all SQL Services. Launch DBCreate and remove the existing I/NET Seven Database. Create a new I/NET Seven Database. Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy the saved INetDb.mdf and INetDb_log.ldf over the newly created files. Restart all SQL Services. Launch DBCreate and attempt a backup. Option 2 (If Option 1 does not work) Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy INetDb.mdf and INetDb_log.ldf to an alternate locations (located in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data) Uninstall and Reinstall I/NET Seven. Stop all of the SQL Services (SQL Server, SQL Agent, SQL Distributed Coordinator) Copy the saved INetDb.mdf and INetDb_log.ldf over the newly created files. Restart all SQL Services. Launch DBCreate and attempt a backup. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue When I/NET is running under Windows 7, there will be a display issue about alignment. The font size has been changed to smaller - 100%, but still no use.  Product Line EcoStruxure Building Operation, TAC INET Environment Windows 7 Cause Be sure to try I/NET Seven Windows fields not aligning correctly on workstation's display to change the font size first to see whether it can help. If not, continue to the next information. I/NET used the default MS Sans Serif font to display everything. But something has changed in Windows 7 about the font display.  Research showed that many users with high resolution monitors (particularly LCD flat screens) were running the monitors at lower resolutions than the native resolution of the screen. This was usually because at the native resolution, the fonts were becoming too small to read, so the users would decrease the resolution. Windows includes a facility to increase font and window sizes while keeping the screen at the native resolution.  This is a much better method of increasing the font size as it can produce much smoother images by using many more, smaller pixels. The really significant issue is, unlike CRT monitors, flat-panel LCD monitors have a fixed pixel size, or "resolution", and that when users change to a lower resolution (in order to increase text size) the system has to re-sample the lower-resolution display image into its fixed resolution causing a significant degradation in display quality: not just text looks worse, everything looks worse. A change was made for Windows 7, to set the screen resolution to the monitor's native resolution and if the screen is over a certain resolution to default the font size 120 DPI (dots per inch). This is approximately 125% of normal 96 DPI (100%). When the system defaults to 125% DPI it also adjusts the MS Sans Serif font to be bigger.  If the user then decides to set the DPI back to 100%, then TrueType fonts, which are scalable, adjust as expected. But the bitmap MS Sans Serif font does not: it remains at the larger size, hence this issue. This problem does not occur if Windows 7 keeps DPI at 100% when it is first installed. So anyway, when the default font size is Medium - 125% instead of smaller - 100%, probably the solution below is needed to solve it. Resolution Go to the Registry Editor, and find HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts. Find the entry MS Sans Serif 8,10,12,14,18,24. The original value is set to SSERIFF.FON on a system which started at 125% DPI. Set to SSERIFE.FON on a system which started at 100% DPI.  Notice that one character of the file name changes from F to E. Restart the computer, and make sure the font size is set to smaller - 100%. Refer to I/NET Seven Windows fields not aligning correctly on workstation's display about how to set font size. Then it should go back to work.

Issue Alarms being generated in I/Net are not showing up on the Enterprise Server. Product Line EcoStruxure Building Operation, TAC INET Environment SmartStruxure Integration with I/Net Alarms Cause Alarms generated in I/Net are not populating on the Alarms Window on the ES, all masking are set on both the AMT Configuration and Host Masks. When the point goes into Alarm, it populates the Alarm Window type, whether it is Priority or Critical with said point address. However, it does not show up on the Alarms page because the bin files on the controller needs to be updated to the latest version of software and all points need to be saved prior to integrating with SmartStruxure. Resolution When integrating with SmartStruxure, all controllers are supposed to be updated with the latest version of software as well as sav files, per Resetting a 7793 Controller and PCU (Applies to 7793, 7716, 7728, 7756). Once completed, recheck the points by putting them in Test mode so that they can generate the Alarm condition and it should show up in the ES Alarm now.

Issue No Messages Received in AMT from specific Link or Site Product Line TAC INET Environment I/NET Seven Xenta 527-NPR Xenta 527 Web Server NPR2000 Cause There are many causes outlined in AMT not receiving Data which show reason why AMT may not be receiving data. In some cases the issues is not due to programmatic issues but network Errors. I/NET uses UDP port 50069 to broadcast data from NPRs and Xenta 527s to any listening host device. While this does give the flexibility to have multiple hosts receive the same packet, it prevents the proof of delivery that a TCP packet provides. You can read more about UDP at this link. http://en.wikipedia.org/wiki/User_Datagram_Protocol Resolution  To prove a network error, use the following methods: Verify everything listed in AMT not receiving Data If feasible, repeat those steps above direct connected to the Xenta 527 via crossover cable. Ensure Window Firewall is disabled on the local PC when performing this task. Once you have a PC that will receive Messages while direct connected, re-connect the 527 to the network and use the same PC to connect to try to 527 over the network. If AMT works or fails based on being on or off of the network, then this is a networking issue. The PC, Domain Server, or Internet Service provider are all capable of blocking I/NET communication. This can be done by either blocking traffic going out of the PC(s) to the NPR/527(s), or it can block traffic from the NPR/527(s) to the PC. On a PC Windows Firewall these are referred to as outbound rule and inbound rule respectively. Please note the following conditions when certain parts of the network traffic are blocked. Traffic Blocked on traffic from NPR to PC Traffic Blocked on Traffic from PC to NPR Both Blocked You can connect to controllers in I/NET, values will update and you can control points You cannot connect to controllers in I/NET, values will not update and you cannot control points You cannot connect to controllers in I/NET, values will not update and you cannot control points AMT does not receive data from the blocked Link or Site AMT does not receive data AMT does not receive data   To Correct a PC Windows Firewall Issue: You will be able to prove a windows firewall issue by turning off the PC firewall for a few minutes and testing AMT. If traffic resumes, this is the cause. Open Windows Control Panel If needed, change "View By" from Category to Small Icons Click on Windows Firewall Select Advanced Settings Click on Inbound Rules Click on New Rule in the Actions Pane Select Program and click Next Browse to the InetIoSrv.exe application on your PC. Click Next Select the Action to Allow the connection and click Next   Set the Rule to apply to all locations. Click Next Name the Program and Click Finish. AMT Should begin to receive data. If not, repeat step 1 to verify this is a PC firewall issue and contact Product Support for additional assistance. If the data is being blocked by the network and not the PC Firewall: Contact your network administrator and explain that the Xenta 527 or NPR 2000 must be able to broadcast UDP data on UDP port 50069. This path must be open on every hop between the device and the PC. Verify that both the PC and device are on the same Windows Domain. Typically, UDP traffic will not travel outside of the Domain. If you are unable to get network blocked removed, you may be forced to put all I/NET devices and PC's on a single subnet.

Issue This is a guideline to do air balance settings (airflow calibration) on a VAV ASC using a I/STAT or M/STAT. Product Line TAC INET Environment MR-VAV-AX MR-VAV-X1 MR-VAV-X2 Cause The air balance company needs a procedure to properly set up the MR-VAV-AX products for the air balance settings. Resolution Understand the cooling setpoint is 75°F, and the heating setpoint is 70°F. This information is important in knowing which state the system is trying to control. While in the PP mode of the I/STAT, it is important to verify the setpoint is 75°F. This allows Test & Balance to set the temperature to: 77°F for maximum cooling 72°F for minimum cooling with no fan 68°F for heating mode - minimum primary airflow with fan To verify the current setpoint, use the Select key and scroll up to Set Temp. The I/STAT will display the current setpoint. For testing purposes as described in Step 1, if the temperature setpoint is not 75°F, press the + or - key to raise or lower the setpoint to 75°F. In order to enter the Service Mode, press the Service key. Enter the I/STAT password 183. Press the + or - key to see the left most digit change accordingly. Press the + key to scroll to 1 and press Enter. The cursor on the I/STAT will move to the center digit. Press the - key to 8 and press Enter. Now the cursor will move to the right most digit. Press the + key to 3 and press Enter. You are now in the Service Mode. While in the Service Mode, the Service key is the escape key and the Enter key will allow the controller to accept your desired changes. The first step in the calibration process is to make sure the controller is at the Factory Calibration Setting (FCS). Press the Select keys to scroll to Airflow Parameters (AP) and press Enter. CLF is displayed on the I/STAT. Press the Select keys to scroll to FCS, press Enter. The I/STAT will display NO. Press the + key to change the display to YES and press Enter. Press the Service key to back up one screen. To verify duct diameter (dd) press the Select key and scroll to Unit Parameters (UP). The I/STAT will display the current duct diameter as 10.0 (default of 10 inches) unless the value has already been changed. Press the + or - key to raise or lower the value, and the Select keys to move between the right most and center digit. Sample: 8 inch box is displayed as "08.0" Press the Enter key to allow the changes to take place. Press the Service key to back up one screen. To verify Cooling Low Flow (CLF) and Cooling High Flow (CHF) setpoints, press the Select keys to scroll to Airflow Parameters (AP) and press Enter. CLF is displayed on the I/STAT. Press Enter, the I/STAT will display the current value. Note that CFM is displayed as KCFM, for example 0.50 = 500 CFM. If the values are correct, press Enter. If the values need to be changed, use the + and - keys to change the values and the Select keys to move the cursor from the left most digit to the right most digit. Once you have the desired value displayed, press Enter. The I/STAT is now displaying CLF. Press the Select keys to scroll to CHF and press Enter. If the values are correct, press Enter. If the values need to be changed, use the +, -, and Select keys to change the CHF to the desired value then press Enter. CHF is displayed on the I/STAT. Press the Select keys to scroll down to Calibrate Primary Low (CPL), press Enter. The VAV controller will modulate the damper to maintain its design CLF. The I/STAT is currently displaying the CFM the controller is reading. Note that during this process, the CFM value may go to -0.1, 0.0, etc.; the controller is calibrating itself to the 100% actual closed position. Once the CFM comes within 10% of the CLF setpoint, the ON/OFF LED will turn on. While the LED is on, the controller is not modulating the damper and the controller has the damper in a fixed position for approximately 60 to 90 seconds. (Do not attempt to enter any values at this point. When the LED goes off, the controller takes back control of the damper and will modulate it to maintain CLF.) Once the airflow has stabilized and the I/STAT is displaying the CLF CFM, measure the airflow and input the actual value (do this as soon as possible because once the + or - key has been pressed, it freezes the damper into a fixed position to allow enough time to enter the actual value and to minimize chances of the actual CFM changing), into the I/STAT using the +, -, Select and finally the Enter key as described in Step 8. Important: Even if the current reading is correct, press Enter. The I/STAT will display Calibrate Primary High (CPH), press Enter. The VAV controller will modulate the damper to maintain its design CHF. Again, once the CFM comes within 10% of the CHF setpoint the controller's ON/OFF LED will come on and the controller will perform as described in Step 9. When the LED goes off, the controller takes back control of the damper and will modulate it to maintain CHF. Once the airflow has stabilized and the I/STAT is displaying the CHF CFM, measure the airflow and input the actual value (again, do this as soon as possible) into the I/STAT using the +, -, and Select and finally the Enter key as described in Step 8. Important: Even if the current reading is correct, press Enter. The I/STAT should be displaying CLF. Once the low and highs have been calibrated, press the Service key. Press the Select key to scroll to Operational Parameters (oP), press Enter. Press the Select key again to scroll to Prove Performance (PP). This mode will place the program's Room Temperature in a test state. The I/STAT display will toggle between the current CFM and the room temperature. This step will allow the balance engineer to verify proper operation of the VAV controller to maintain the design maximum and minimum airflow. Press the + and - keys to increase or decrease the room temperature in order to manipulate the system to control between cooling and heating as described in Step 1. Once the VAV has controlled the damper to design minimum CFM, the balance engineer can adjust the fan (if applicable) to design airflow. Important: If at any time during the calibration process, (not during Prove Performance (PP)) a mistake is made, make sure that the controller is reset back to the Factory Calibrated Settings (FCS), (see Step 4) and restart the calibration process. Also, if the VAV box does not control the CFM within the maximum allowable percentage, normally within 10%, go back to Step 4 and restart the calibration process. For further information see the following: TCON126 (Micro Regulator Controllers and I/STAT) TCON147 (ASC MR-VAV-AX) TCON155 (ASC MR-VAV-X1) TCON165 (ASC MR-VAV-X2) Go to TCON Number and Title Cross Reference (with links) and download the TCONS above.

Issue It may be desirable to change the default name of an NPR as it appears in I/NET (ie XentaXB2435) to something more descriptive. Product Line TAC INET Environment I/NET I/O Server Config Xenta 527, Xenta 527-NPR, Xenta 731, Xenta 913 Cause I/NET generates a unique default name for each NPR. While the default name differentiates the NPRs it may be helpful to have a descriptive and relevant name for each NPR. Resolution Open the I/NET IO Server Config. Select the IP Port connection of the NPR to be changed and select Modify to open the Configuration Profile. Click on NP Routers to open the NetPlus Routers Summary. Select the router that you want to change and click Modify to open the NetPlus Router Configuration. Enter a new name for the NetPlus Router and click OK. The NPR will now re-initialize and will have the new name. If you are still having issues, see How to change the name of a 527 Link or DLA site.

Issue What are the limitations of using ID Works with I/NET Seven? Can a "begin time" or an "end time" be assigned to a temporary card from ID Works (Card Access Control Data Entry)? Can an individual’s record be made a "DPU Resident" from ID Works? (I/NET Seven 1.0x) What is the format of the CardID entry in the ID Works system? Can assign PIN numbers be used with an ID Works system? Product Line TAC INET Environment I/NET Seven ID Works  -  For details of what version of Datacard ID Works Software integrates correctly with I/NET Seven refer to Datacard ID Works Software versions for integrating with I/NET Seven.  Cause I/NET Seven provides support for Datacard ID Works identification software. I/NET Seven provides a database view specifically designed for use with ID Works. This view contains tenant and individual data used by the ID Works Video Badging application. It allows you to add individuals, assign key/cards, edit individual parameters, or even delete individuals.  The limitations described below are imposed anytime that you use ID Works to modify your I/NET Seven access control system. Resolution The limitations described below are imposed anytime that you use ID Works to modify your I/NET Seven access control system. ID Works does not allow you to add or modify multiple cards for a single individual. ID Works does not allow you to remove a card from an individual without deleting the individual record in I/NET Seven. You cannot disable an individual’s card without disabling the individual in the I/NET Seven. You cannot create a new group or a new tenant from within ID Works. You cannot assign a begin time or an end time to a temporary card from ID Works – only dates can be entered. I/NET Seven will use a default time of 00:00 (Midnight) on the dates specified. If you need to change this default time, it requires you to go into I/NET Seven > Access > Individuals editor. You cannot make an individual’s record be DPU resident from ID Works. You cannot assign a decimal card number to an individual from within ID Works. The format for this entry has to be a hexadecimal number. You cannot set and individual’s APB scheme (i.e., hard, soft, or graced antipassback) from within ID Works. You cannot assign a PIN to an individual from within ID Works. These can be access via the I/NET individual editor. For further information refer to TCON301 Chapter 5.

Issue How can I determine what version of SQL I/NET is using? What version of SQL is installed on the I/NET PC? Product Line TAC INET Environment I/NET Seven 2.10 and above For previous versions of I/NET refer to How to determine the SQL version you are running with I/Net Seven. Cause To find out what version of SQL is installed and used by I/NET Seven site PC. Resolution A new feature was introduced in I/NET Seven Revision 2.10 that allows you to view both the I/NET revision and SQL revision installed.  To view this all I/NET applications and the IO Server must be shutdown before performing the following steps: Start DBCreate >Start> All Programs> INet>DBCreate Login screen is shown, select either Windows login or enter the SQL Server Authentication details and click OK Right-click on the Title area shown in red below:   After Right-clicking, select from the menu options About...   The About DBCreate screen will then be shown and you can see both the I/NET Seven Version and SQL Versions as shown and highlight below: For I/NET Revisions prior to 2.10 then refer to How to determine the SQL version you are running with I/Net Seven on how to view what version of SQL is installed.      

Issue DBCreate database restore fails with error message: "The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally." Product Line TAC INET Environment I/NET Seven SQL Server 2000 all editions and SQL 2005 all editions Cause It is not possible to restore a SQL Database which was backed up using SQL 2005 back into a SQL 2000 database. Resolution The simplest method to rectify this problem would be to uninstall I/NET and SQL (Refer to Procedure for uninstalling I/NET Seven on a stand-alone host on how to do this) and then re-install I/NET using SQL 2005. The second method would be to upgrade the installed MSDE Default instance to SQL 2005 Express. There is a published white paper from Microsoft on this and is attached here: MSDEtoSQLExpress.doc.  Refer to the steps on page 11 to 14. The SQLExpress installation file is available on the I/NET CD under the folder SQLExpress\.SQLEXPR32.EXE. After performing these steps its advisable to run up DBCreate and upgrade the SQL database.

Issue In order to make page links between different I/NET graphic folders work fine, the same folder structure needs to be created manually in EcoStruxure / SmartStruxure. Refer to Converting I/NET graphics to TGML using the "Create Source Tree" option to realize this. Product Line EcoStruxure Building Operation, TAC INET Environment EcoStruxure / SmartStruxure 1.4 or higher I/NET Cause The I/NET graphic folder structure will not be created automatically before SmartStruxure 1.4.0. Resolution Starting in version 1.4.0, there was a new feature called Data import for I/NET graphic. Using this feature, all the converted I/NET graphic folders structure can be imported at one time without any need for manual work. Here are the steps to make it work: Convert the I/NET graphics according to Converting I/NET graphics to TGML using the "Create Source Tree" option, but do not create the folder structure manually in EcoStruxure / SmartStruxure. Create the default Inet Graphics folder by right clicking on I/NET Interface-->New. Right click on Data Import and choose the root folder of all of the I/NET graphics. Click OK. Data importer will check all the file names and bindings. If any error happens, check and fix it before importing again. (Currently apostrophe is not supported in SmartStruxure. Change the name and relative link and do it again. It may be fixed in later version) Check whether all the bindings and links work fine. Important: Currently this feature doesn't support export/import in SmartStruxure. It will fail to import if any sub folders are contained under INET interface. This may be fixed in later version. The workaround is to still create the whole structure according to Converting I/NET graphics to TGML using the "Create Source Tree" option.

Issue Need help with programming Need help to make graphic Installation questions Forum Environment BMS Security Video Cause A great way of getting help with various application programming and graphic making is to spread knowledge between all the great technician out there. A forum exist for this and people worldwide that works with SE Solution share their knowledge here. Resolution Please enter the forum by the link below. http://community.se.com/welcome

Issue HID PIN Pad reader for I/NET Part NumberHID PIN Pad reader for I/NET Part Number Product Line TAC INET Environment I/NET Access Control Cause HID PIN Pad reader for I/NET and which part number to use? Resolution iPortal shows several PIN pad readers from HID (HID-6136CKD000214 HID-6136CKD000009) but only one works with I/NET.  Here is a pdf document which helps to explain which part number works with I/NET. The 09 means the 8 bit blast which is required for compatibility.  Want to use Pin Pad only without using the proxcard? The RK40  will do Prox only or Prox + Pin but not Pin only. See Essex Pin Pad Reader programming for Pin Only or for higher security Pin Only see Code-Guard Scramble Pin Pad Reader Programming.

Issue DVR incorporated with I/NET Seven and Pelco Integral or Digital Sentry Product Line Pelco, TAC INET Environment I/Net Seven Pelco Integral or Digital Sentry DVR CCTV Cause Send back a Integral DVR and it comes back as a Digital Sentry or confusion revisions of I/NET Seven and Pelco Integral of Digital Sentry Resolution This chart to clarifies which versions of I/NET Seven are compatible with which Pelco DVRs: For the latest products (after 2.31 revision) please visit Software and Firmware compatibility matrix for older versions of the traditional product lines which has the most recent Pelco compatibility.

Issue What if an NPR 2000 goes away and never comes back even after cycling power to it? Product Line TAC INET Environment I/NET site Cause Cold starting an NPR 2000 is a common troubleshooting technique to clear up a number of communication problems that may arise. Resolution If said NPR stops communicating and doesn't come back no matter what, you should cold start it and do a software restore. (See that procedure in How to cold start an NPR 2000.)