Issue Initialization errors when starting I/NET Seven 2.42 or higher Error: "You must install an instance of SQL 2008R2 (64bit) before completing the INET install" Product Line TAC INET Environment I/NET Seven 2.42 Windows Server 2008 64-bit Windows 7 64-bit SQL 2008 64-bit Windows 8 Cause I/NET 64-bit requires specific installation process in order to function on a 64-bit PC Resolution Installing SQL Download SQL2008 R2 Express 64 bit (SQLEXPR_x64_ENU.exe) from this location: http://www.microsoft.com/en-us/download/details.aspx?id=30438 Run SQLEXPR_x64_ENU.exe In the left hand section, select Installation In the Right and section, select New SQL Server stand-alone installation of add features to an existing installation. At the "Setup Support Rules" screen select OK At the "Product Key" screen, select Next At the "License Terms" screen, check accept and select "Next" At the "Setup Support Files" screen, select Install At the "Setup Support Rules" screen, select Next At the "Feature Selection" screen select: Database Engine Services, SQL Server Replication, Management Tools - Basic (If Present) and SQL Client Connectivity SDK. Leave the Shared feature directory as default. At the "Instance Configuration" screen, select the Default instance option, accept the default Instance ID, accept the Instance root directory default settings and select next. At the "Disk Space Requirements" screen, select Next At the "Server Configuration" screen, under SQL Server Database Engine set the Account name to NT AUTHORITY/SYSTEM, leave the password field blanks, and set the startup type to automatic. Under SQL Server Browser Service, set the Startup Type to Automatic At the Database Engine Configuration screen, set the Authentication Mode to "Mixed Mode", Define a strong password (example: @sql2008), in the Specify SQL Server administrators section click "Add Current User". Select Next. At the "Error and Usage Reporting" screen, select Next At the "Installation Rules" screen, select Next At the "Ready to Install" screen, select Install At the Installation Progress screen, when the setup process is complete, select Next At the "Complete" screen, select Close. SQL Configuration: In the Windows Start Menu, launch the SQL Server Configuration Manager In the Left hand section of the window, highlight SQL Server Services Verify that SQL Server Browser and SQL Server are Running In the left hand section of the window, expand SQL Server Network Configuration and highlight Protocols for MSSQLSERVER Enable Named pipes and TCP/IP Close the SQL Server Configuration Manager Restart the PC Installing SQL Server 2005 Backward Compatibility On the I/NET 2.42 or higher installation CD, look in Support\SQLBCM_64Bit and launch the SQLServer2005_BC_x64.msi file Follow all the prompts on each screen and accept all defaults. Install I/NET Seven 2.42 or higher Install I/NET Seven 2.42 or higher using the installation CD Follow prompts and use defaults When prompted for the SQL password, select "Windows Authentication" Restart the PC Open I/NET Configuration through the start menu. Modify the default Config profile or create a new profile. Close I/NET Configuration Start I/NET NOTE: If error occurs during SQL installation stating invoke or begin invoke failed, follow instructions at this link: http://support.microsoft.com/kb/975055 UPDATE: SQL2008 SP1 prevents the invoke failed error. It can be installed with the same instructions as above. Download it at this link: http://www.microsoft.com/en-us/download/details.aspx?id=25052

Issue Problems backing up a database after an upgrade to 2.13 Product Line TAC INET Environment I/NET Seven rev 2.13 Cause Problems backing up a database after an upgrade to 2.13 Resolution Shut down I/NET and I/O Server Start DB Create, select the option to Upgrade Database Force an upgrade to the database. Select Verify Database, to ensure that there are no differences. Start I/O Configuration, modify the active profile, hit the OK button, and don’t make any changes. Close it again. Start I/Net again and verify that all I/NET functions are normal. Shut down I/NET and I/O Server again. Start DB Create and verify that all the functions are available to you again.

  Issue After transitioning TAC INET Access to Security Expert, SP-C health status shows the message "Ring-loop failure at reader expander".   Product Line EcoStruxure Security Expert, TAC INET Environment  Security Expert SP-C   TAC INET Access Control Cause This message indicates that the ring-loop connection is not made.  For the ring-loop connection, the opposite end of the INET subLAN must be connected to Reader 2 on the SP-C. Resolution If an INET subLAN loop is not used, then  this message can be ignored. If an INET subLAN loop is used then this message indicates a break in the ring-loop.    1. Reference Guide I/NET Access Control Transition to EcoStruxure™ Security Expert (Hardware            Guidelines for Transitioning from I/NET Page 23)

Issue Checking if a port is open Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution It is possible to check if a port is open in a network by issuing the Telnet command. Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet. If a port is open, a blank screen will be seen after issuing the command: telnet [domainname or ip] [port] where [domainname or ip] is the domain name or IP address of the server being checked [port] is the port number the server application is listening on For example: telnet 192.168.0.20 9001 (to a closed port would display a connect failed message)   telnet 192.168.0.20 9003 (to an open port would display a blank screen)   To exit the Telnet session, type Ctrl + ] and then type "quit".   For how to enable Telnet in Windows 7 please see Enable Telnet Client on a Windows 7 PC

Issue How to use the Telnet command to troubleshoot network connectivity and check for blocked network ports. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, Pelco, EcoStruxure Building Expert, Access Expert, Security Expert Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet.  

Warning This article describes a feature that is not standard functionality within the Product Line.  It has been provided to allow customers the option to use this requirement.  Pay particular attention to the Prerequisites of the required programming. Issue Customer requires the functionality for Individuals  to double badge (present their credentials twice) to gain access. Product Line TAC INET Environment Access Control Cause Customer application requirement Resolution Prerequisites: LIMITATIONS: As this is not a standard access control feature within I/NET, it uses custom programming, which therefore reduces/limits the standard features within I/NET The description provided below must be set for ALL individuals with access to the door that requires double badging.  It does NOT cater to custom individual use.  It may be possible to provide additional programming to achieve this, but this is not detailed in this article. Door Automatic Time Schedules (ATS), if applied, can be overridden if the door reader is badged during the scheduled operation.  The functionality of this feature uses event-driven programming, which in its nature is single-shot programming and therefore relies on the following:  Requires reliable communication between SLI/MCI (779x) and the SCU (Door Controller).  The door reads from the SCU must be received by the SLI/MCI to activate the badge/read occurrence. Requires SLI/MCI (779x) CPU loading below 65%. LAN Load of this controller should be below 2%; anything above this can cause the operation to fail/be inconsistent.  Removes the standalone capability of the Door controller (SCU) POINTS The points required for each door that requires this functionality are Door Reader (Internal DO door point as required in I/NET)  Door Strike (External DO Point) must be programmed within the controller Door Intermediate (Internal DO Point). :: Scan Rate 1 second Door Read Count (Internal AO Point). :: Scan Rate 1 second I/NET Controller Summary Note: The address order, as shown in the screenshot above, is important for the overall operation.   That is Read Count must be at a lower address than all other points.  Next the Intermediate point.  The Strike and Reader addresses are fixed by I/NET but must be at a HIGHER address than the Read count and Intermediate points.    DOOR Intercard Interval (sec) should be set as low as possible.  This allows the card to be present within this time setting (minimum is 1 second) Door strike: Configuration of the door/reader must have this set to either. None: When a valid read is received, no action is sent to the strike Exit: Only when an Exit read to Request to exit (REX) is received by the door does it activate the strike.  Strike duration (sec): Should be set 1 second above the scan rate of the Intermediate / Read Count points above.  In this case, it is set to 2 seconds.  Note: this does not have any bearing on how long the strike remains "unlocked" Door editor Programming DOOR No additional programming is required for the door apart from the details provided in the above prerequisites.  ACCESS INITIATED CONTROL (AIC) Add an AIC that will trigger the Intermediate point on a "valid" reader entry for the nominated door. Select the Target point (DR1 Intermediate) Select either Use all individuals in the range which will trigger this action for all individuals.  Note: If selected Individuals are needed to activate this feature, then additional programming is required and not detailed in this article.    Select Reader entry to START the target point  Select which Doors are to trigger this action Access Initiated Control editor POINTS From the screenshots below, it can be seen that: Point DR1 Read Count has two extensions: Calculation (C)  Operation: The result of this calculation is displayed on the DR1 Read Count point.  The calculation adds the value of itself (P0) DR1 Read Count and point (P1) DR1 Intermediate point (where 0=OFF 1=ON), the result of which is then multiplied by the NOT (~) the value of (P2) Door Strike (where sec = 0 Unlk = 1). Result: DR1 Read Count is incremented by one on each valid read.  The counter is reset (zeroed) when the Door Strike is energized.        Event Definition (EV)   Operation: When the point DR1 Read Count crosses the value 1 (the value of 2 represents the double (2) badge), Sequence/Action #1 is triggered.  From the above Event Definition (EV), this runs Sequence/Action Num 1, which is shown below:  Operation: When triggered by the (EV) above, the Door Strike is immediately "Stop"  (Unlocked); after a 5-second delay, the Door Strike is "Start" (secured). Note: The delay of 5 seconds on line #2 determines how long the strike remains in the unlocked state.  Modifying this value will shorten or extend the unlocked state.     Point DR1 Intermediate has only one extension: Calculation (C)  SUMMARY OPERATION A valid card read is presented to the reader; this triggers AIC to turn point DR1 Intermediate to ON. This increments DR1 Read Count by 1 to the value of 1 via its Calculation (C) extension The additional card read repeats Steps 1 and 2 above;  DR1 Read Count value increments to a value of 2. Event Defintin (EV) high-value crossing (>1) triggers Event Sequence #1 Event Sequence #1 unlocks Door Strike 1 and, after a 5-second delay, relocks (secures) Door Strike 1 point. This relock (secure) of Door Strike 1 zeros the DR1 Read Count value via its Calculation (C) extension.  ATTACHMENTS - for reference showing the above details  I/NET Controller SAV file (DCU0201.zip) Backup InetDb (SQL.bak).  (InetDb_DoubleBadge.zip)  

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue I/NET transitioned User ID Credentials that have non-numerical characters (like a dash "-") cannot be modified in the Security Expert Client Product Line EcoStruxure Security Expert,TAC INET Environment Security Expert Controller Cause Security Expert Client does not allow User ID Credentials with non-numerical characters with a dash (-) to be modified Resolution Method 1: Delete the dash from the User ID Credential the first time you need to make any other edit to that user in SX. Click Save.   Method 2: Make a backup of the existing SX database in case you want to restore what you had. Use the latest version of the INET Database Transition Tool to re-transition ONLY Users. Note: Any adjustments you've made to the User's Access Levels in SX since the original transition from INET will be lost. You will need to make those adjustments again.

Issue I/NET Seven elevator control configuration and setup. (Traditional versus Extended elevator control) Product Line TAC INET Environment I/NET Seven Extended elevator control: DPU Firmware 3.20 or above. (DPU7920 with 48K MIP or SCU1284) Cause There are two types of elevator control that you can implement within TAC I/NET: Traditional Elevator Control – Tradition elevator control allows each elevator to support up to 62 floors. This type of control has been used for as long as elevators have been supported within TAC I/NET. Extended Elevator Control – Extended elevator control does away with floor mapping and allows you to assign floors directly to tenants. Using this type of elevator control, each elevator can support up to 79 floors. Resolution Elevators The Elevator control function will work with the access control parameters and personnel schedules to control access to banks of elevators. Activating () the elevator option in the Door Extension editor will cause the DPU to process each reader transaction as though it were an entry into an elevator cab. Note: An elevator DPU will support only one door reader. Changing a Door from elevator to non-elevator, or vice versa will cause the DPU to purge its database. In addition to supplying the above parameters at the door (DPU) level, it will also be necessary to supply the DPI/MCI with the information required to associate an elevator cab with the discrete output points that enable the floor relays, and the discrete input points that monitor the button selection. There will be an elevator extension on each door point in the DPI/MCI that is assigned as an elevator. After adding the extension to the point, you must define the Elevator parameters such as floor selection time, floor designation description, button enable point, and button selection point. Elevator Control Schemes There are two types of elevator control that you can implement within I/NET Seven: Traditional Elevator Control – Tradition elevator control allows each elevator to support up to 62 floors. This type of control has been used for as long as elevators have been supported within I/NET. Extended Elevator Control – Extended elevator control does away with floor mapping and allows you to assign floors directly to tenants. Using this type of elevator control, each elevator can support up to 79 floors. You can use either type of control, or a combination of both, to implement elevators within your system. By allowing you to mix both types of control, I/NET gives you the ability to begin using extended elevator control without reconfiguring your traditional elevator control system. The following sections describe each elevator control type. Traditional Elevator Control Traditional elevator control allows each elevator to support up to 62 floors. To implement this type of control, you assign the elevator door point to one or more tenants. You then create floor maps that associate floors with personnel schedules (see “Defining Floor Maps”, below). After performing these tasks, any individual (or group) assigned to the elevator can gain access to the floors that are associated with their personnel schedule Assigning the Elevator to Tenants Traditional elevator control requires you to assign the elevator to one or more tenants. Until you perform this task, the Floors button in the Elevator editor will not be available (i.e., it remains grey). Defining Floor Maps Floor maps are only necessary when configuring your I/NET system for traditional elevator control. Floor maps determine which floors are enabled during each schedule that a tenant defines for the elevator. For example: Tenant 1 has a personnel schedule named “24 Hour” defined for the elevator. This schedule provides 24-hour access, seven days a week. The elevator’s floor map associates the floor enable points for floors 1 and 2 with Tenant 1’s “24 Hour” schedule. This allows Tenant 1 individuals using the “24 Hour” schedule to select floor 1 or floor 2 at any time. Use the Floors button in the Elevator editor to create floor maps as follows: Choose a tenant. Select a schedule from up to 31 personnel schedules defined for the elevator. Select an entry from up to seven access intervals defined for the schedule. Assign floor enable points to the schedule’s access interval. Floor enable points cause the elevator buttons for those floors to be enabled for selection by the key/card holder. Up to 62 floor enable points can be assigned to each access interval. Any floor enable points beyond 62 are unavailable when using traditional elevator control. These higher floor enable points are only available for use with extended elevator control, as described below. Note: Extended elevator control is only available with the 7920 48k DPU. Repeat these steps as necessary to create floor maps for each of up to 31 personnel schedules assigned to the elevator by a tenant. Extended Elevator Control I/NET Seven now offers an alternative to the traditional elevator control just described. Enhancements to the I/NET system support up to 79 floors per elevator. Instead of assigning the elevator door point to the tenant, you can implement extended elevator control by assigning floors to the tenant. The DI/DO pairs that you add to an elevator from the Elevator editor are listed in the Tenant editor, much like normal door points. Select the floors that you wish to assign to the tenant. Implementing Elevator Control Note: Extended elevator control is only available with the 7920 48k DPU. Adding an elevator extension to the door point provides access to elevator-related features and editors within I/NET and allows floors to be assigned. Each floor assigned to an elevator must have an associated DO and DI point. The DO point enables the elevator button for the specific floor. The DI point provides feedback indicating whether the floor button has been selected. Preliminary Requirements Before defining an elevator, you must do the following: Define a door point as an elevator in the Door Extensions editor. Use the Resident I/O Points editor to define a floor enable point (DO) and a floor selection point (DI) for each floor that will be assigned to an elevator. Use the Personnel Schedules editor to define up to 31 schedules for the selected elevator door point. Adding an Elevator Extension Use the following procedure to add an elevator extension: Select Edit Controller Elevators from the main menu. The system displays the Resident I/O Points Editor. This screen lists the available door (elevator) points. Choose a point that does not have a Y in the EL column and select the Add button. The system displays the Elevators window. Enter a Floor selection time (sec) (1 to 255). This is the amount of time in seconds that the key/card user has to make a selection from the floor buttons in the elevator cab. The default is 5. Select Add. The system displays the Elevators - Floor Parameters window. This window allows you to define the floor index attached to this elevator extension. Enter the Floor index number (1 to 62). This is the line number in the list. Enter the Floor designation (up to two characters). This identifies the floor. For example, the first level of a basement could be represented as B1. For each elevator floor extension assigned to a point in the DPI/MCI, there must be an associated DO and DI point attached to the elevator extension. This association of DO and DI points produces closed-loop feedback allowing the controller to identify an elevator floor selection with each successful key/card reader access. In the Button enable field to choose a point from the drop-down list of all possible discrete output points in the controller  In the Button selection field, choose a point from the list of all possible discrete input points in the controller. Select OK. The system returns to the Elevators window. How you proceed from this point will depend upon the type of elevator control you are implementing. Use the appropriate steps below: Traditional Elevator Control: From the Elevators window, select Floors. The system displays the Tenant Selection window. Choose a tenant from the list and select the Select button. The system displays the Elevators - Floor Schedules window. Choose a schedule from the list and select the Select button. The system displays the Elevators - Access Intervals window. Choose an access interval from the list and select the Select button. The system displays the Elevators - Floor Map editor. Choose the DO points which enable the floor selection buttons for the appropriate floors. Points marked with "[X]" will enable their respective floor selection button in the elevator cab. When you have finished choosing the appropriate DO points, select OK. The system returns to the Elevators - Access Intervals window. You may continue assigning floors to access intervals, or you may back out of the elevator functions by selecting Close at each window. Extended Elevator Control (See also article Extended Elevator control (Step by step instructions) ) From the Tenant Editor, assign floors (i.e., door enable points) to the tenant. Assign floors to individuals and/or groups as necessary.

Issue Removing software from a PC may leave behind unused / old registry entries and folders from the removed software, this in some cases may prevent software re-installation Product Line Andover Continuum,EcoStruxure Building Operation,Satchwell BAS & Sigma,Satchwell MicroNet,TAC INET,TAC Vista Environment All supported Operating Systems Cause This is due to the windows uninstall program not fully removing all elements for the software. Some of this is due to windows thinking the the software may have been removed unintentionally and therefor all the previous settings will still be saved in case of  re-installation. For example, when SQL is uninstalled the program folders that contain the database will remain intact. This may be an issue if, for example, the software is removed due to a problem with the original installation. This is when a complete removal off all components and registry entries may be needed. Resolution The best solution for removing all the unused registry entries is to use a program designed to remove obsolete registry entries and temporary files. Some examples of these are: CCleaner, which will allow you to clean up your PC by removing past installation components. Revo Uninstaller  which is useful for removing redundant folders / files / Registry entries.   It may be useful to use both of these programs to ensure a complete cleanup. Revo Uninstaller can be used to remove unused software and then CCleaner to get rid of all the Temp files etc.  Finally remove the relevant folders from within the windows explorer, Example: C:\Program Files (x86)\Continuum Once done you should then be able to install a fresh clean copy of the application software. This solution is current in all versions of Windows including windows 10  

Issue Current information will be stored and updated in release notes and online documentation. Compatibility Matrix of Operating Systems, Video, Product Announcements, SQL Compatibility Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems and iBMS (intelligent Building Management System) Software Cause Compatibility, Firmware, Product Announcements Resolution Please see release documentation for current and recent products. For the Firmware compatibility matrix for: I/NET, it is available HERE or the EcoBuilding Download Center Continuum, click HERE Xenta Software Downloads HERE Vista, click HERE StruxureWare Building Operation, click HERE Product Announcements can be a great tool for discovering which products have been tested and are compatible with the different versions. These documents are available on the Extranet, but have been compiled here for ease of access: I/NET 2.40   Product Announcement 2.41   Product Announcement 2.41a Product Announcement 2.42   Product Announcement and Compatibility Matrix (page 5) 2.43   Product Announcement PA-00239 2.44a Software Available from Exchange Download Center 2.45   Software Available from Exchange Download Center 2.46 Software Available from Exchange Download Center 2.47 Software Available from Exchange Download Center 2.47a Software Available from Exchange Download Center 2.47b Software Available from Exchange Download Center 2.48 Software Available from Exchange Download Center Operating Systems and SQL Supported Video Compatibility Support Policy PA-00279 Software Support for TAC I/NET Continuum v1.92 Product Announcement v1.93 Product Announcement v1.94 Product Announcement PA-00210 1.94 SP1 Product Announcement PA-00273 1.9 - 2.1 Software, Firmware, & Video Compatibility Matrix Concerning IE10 and IE11 browser support  2.0 Feature Blast 2.0 + 2.01/ 2.02 Update Compatibility Matrix 2.0  Product Announcement PA-00353 2.0 CyberStation Installation Guide 2.0 WebClient Installation Guide 2.0 Software License and Ordering Activation Process 2.0 Software and Controller Upgrade Process Andover Continuum PA-00333 Support Policy PA-00272 for Andover Continuum Vista v5.1.5 Product Announcement v5.1.6 Technical Product Advisory v5.1.7 release note document, TAC Vista Compatibility Matrix, SNVT Matrix documents, and TPA-VSTA-11-0020.00 v5.1.7 Product Announcement x5.1.8 Release Note TAC Vista 5.1.8 and TAC Xenta 500/700/900 5.1.8 v5.1.9 Vista Compatibility Matrix SecurityIAS Product Announcement PA-00291 Product Announcement TAC Vista transition to SmartStruxure solution overview  Support Policy PA-00274 for TAC Vista Satchwell Sigma v4.05 SEB Release Notes v4.06 Release Notes v4.06 Release Note Supplement v4.07 Release Notes Satchwell Sigma Standard Edition Installation and User’s Guide Support Policy PA-00297 for Satchwell Sigma v4.08 Release Notes PA-00397 Sigma Version 4.08 Sigma server on a virtual machine Satchwell Micronet data sheet - MicroNet View 2.1 OS Compatibility - Micronet View PA-00228 Product Announcement Support Policy PA-00298 for Satchwell MicroNet PA-00228 Satchwell MicroNet End of Commercialization Announcement I/A Series PA-00163 I/A Series R2 & G3 Product Announcement PA-00114 Legacy Products Windows 7 Compatibility I/A Series R2 with Windows Compatibility Chart PA-00243 Software Product Update - Q2 2013 PA-00251 Hardware Product Update - Q2 2013 PA-00278 Software Product Update - Q3 2013 I/A Series (Niagara) R2 Windows Compatibility Matrix with additional detail I/A Series (Niagara) AX/G3/N4 Windows Compatibility Matrix with additional detail Support Policy PA-00280 R1 for TAC I/A Series StruxureWare Building Operation Please visit Maximum number using StruxureWare Building Operation (Scalability and Capacity) SmartStruxure Lite Please visit SmartStruxure Lite solutions

Issue Unable to connect Remote Client to Standalone Server ASTDIR error when attempting to configure I/NET is sometimes caused by not being logged in as an administrator. Product Line TAC INET Environment I/NET Seven Remote Client Workstation type Cause In most cases, the issue that blocks the remote client connection is port 50069. This must be opened between the two workstations, and use an admin-level I/NET password must be used to initiate communication as well as having to be logged in as an administrator on the local machine. Resolution Log in to Windows as an administrator-level user Make sure that the I/O server is not running Open I/NET Configuration Modify the active profile or create a new one Set TCP/IP settings as well as required reference hosts For Workstation type, select Remote Client or Remote Client (w/IO) When the authentication screen comes up, enter an I/NET operator name with full access. Enter the Host name of the standalone machine functioning as the server. (IP address can be used instead) Leave Authentication Type as default. Press OK Press OK and start I/NET For more information, see Remote Client Configuration Issues I/Net 2.31 and prior and Remote Client with I/O in the Workstation Type of the I/O Server 2.4 and later.

Issue Changing the MSDE SQL Server Sys Admin account password is not supported by the I/NET Seven DbCreate Utility. Users have been advised to uninstall and then reinstall MSDE to change the password. Product Line TAC INET Environment I/NET Seven MS SQL Server (MSDE) Cause Need to change password Resolution Use the Microsoft OSQL Utility to change the Sys Admin account (user name, SA). Developed for Course 2002 I/NET Seven Installation and Startup - MSDE SQL Server OSQL Utility; Rev. 1/4/2007, by: M. Myers, TAC-KSG How to change your INetDb SQL Server SA account password using the OSQL Utility: On the I/NET Seven host workstation computer, shut down I/NET Seven completely, including the I/NET Seven I/O Server. Open the command prompt window. Select Windows Start > Run. Type the command, cmd, in the Run window, Open the dialog entry space, and click on OK. Enter the text exactly as is between the quotations. Connect to the I/NET Seven MSDE instance using the sa account. At the operating system drive, command prompt (i.e. C:\>), type the following OSQL command and press ENTER: osql -U sa Enter the command text exactly as it appears, including a dash before the capital U, and the spaces after the l and the U. OSQL will reply with the following prompt: Password: At the Password: prompt, type in the current SQL Server sa account password, and press ENTER. If the log-on command is correct, OSQL will return a line prompt:1>. Type the following string command at the 1> line prompt and press ENTER: sp_password @old = ‘old password‘, @new = 'new password', @loginame = 'sa' Enter the old and new passwords and the SQL System Administrator account name, sa, in apostrophes. Be sure to type each space and comma in the command. OSQL will return a second line prompt: 2> Type the go command at the 2> line prompt and press ENTER: go OSQL will return the password changed message and the 1> line prompt: Password changed.1> To close OSQL, type Exit at the 1> prompt and press ENTER. The Command Prompt will appear: C:\>_ To close the Command Prompt window, type Exit at the command prompt and press ENTER.  

Issue Lost/Forgot/Modify the SysAdmin SQL default password created during the installation of TAC Vista 5.X.X in typical mode. Product Line TAC INET, TAC Vista Environment TAC Vista 5.x.x SQL 2005 Express Microsoft SQL Server Management Studio Express: (http://www.microsoft.com/download/en/details.aspx?id=8961) Local Admin rights Required. Cause Procedure if SQL Password is Lost/ Forgotten or Modification required. Resolution When you click on Microsoft SQL Server Management Studio Express, it will open the below page and require you to choose the way you want to log in: either by “Windows Authentication” or “SQL Server Authentication”. If you want to log in using Windows Authentication, choose this option and go in. (It uses the Windows login credentials). If you want to log in using SQL Server Authentication, choose this option and enter Login and password. If you want to change this Login and Password: Enter using the Windows Authentication Choose Security > Logins > Select the login ID Right click and go to Properties Change the password and re-login using the new password. Below is an example where the password for the login 'sa' has been changed:

Issue Troubleshooting I/NET installations and upgrades on multiple client workstations. Product Line TAC I/NET Environment I/NET Seven Multi-workstation Site Cause Options to investigate when unable to install I/NET Software on some PCs Resolution Difficulty loading I/NET Software onto a PC where the site has several PCs, and the software will load on one and not the other hardware. The steps below are intended to be used as a checklist and Compare the differences between working and non-working PCs: Is the memory the same? Is the OS the same or different? Is the OS Configured the same? Does it meet the minimum requirement for I/Net and its applications? TCON298 What are the permissions for the Logged in User? Does the user have full Admin-Rights to perform the applicable installation? Is I/Net being installed for the first time, or is it an upgrade? At what point during the installation does it fail on one versus the other? Are any error logs being generated during the process? Can any other software be installed? Are there any previously loaded applications using a SQL/MSDE DataBase? Has the IP/network/domain status changed? Going through the above steps will help rule out some possibilities.

Issue Xenta 527 Appears offline: Troubleshooting steps. Product Line TAC INET Environment I/NET Xenta 527 Xenta 527-NPR Cause Possible Causes: Ethernet Communication is down Ethernet Port is closed Device is configured incorrectly Device failure Resolution Ethernet Communication is down Using the command prompt, ping the device's IP and trace its route. "ping (Insert IP Address)" and "tracert (Inset IP Address)" Watch to see if the Domain server prints out the correct Hostname.  If the device is shown as offline, there may be an error with Firewall settings or Ethernet communication at the Host Workstation. Connect to the router via Internet Explorer If neither of these is possible, Communication is definitely down on the Workstation side. Next, check the Xenta Server side. Disconnect the Ethernet cable from the Device and plug it into a laptop. See if you are on the network.  Ethernet Port Is closed. If the above process shows that Ethernet communication between the Workstation and Router is valid, you may have the port closed. Use a crossover cable to connect a laptop to the device and see if you can connect to a controller ON THAT LINK in I/NET. Look for live values in Controller Summary.  If you can do this, and you can show that Ethernet communication between the two devices is working, then you most likely have a firewall on port 50069 Contact the building IT department Device is configured incorrectly If, in the above process, you cannot connect to I/NET while directly connected to the Router via an Ethernet crossover cable, the device may be configured incorrectly. Open the active I/NET configuration Profile. Ensure that TCP/IP is enabled Add the Router’s IP address to the Reference Host Table Restart the I/O server Check communication Connect to the 527 via HyperTerminal type setip and verify you have been using the correct IP address and hostname type inethost and add the Workstation’s IP address to the Reference host table. restart the 527 Communication should be restored. Device failure Observe the "Run" light on the device.  It should be solid green. Observe the TCP/IP port LED. If you are actively communicating, this should be blinking. If you are unable to connect to the device via a HyperTerminal Direct Connection or Internet explorer while directly connected, you may have a device failure Cycle Power on the device Connect via HyperTerminal (if you cannot do this, try using the failsafe mode. If that fails, replace the device) Type the command “format” to format the device type “setip” and enter the IP information Download and install the latest system file for the 527 you are using. Remember that the 527 and the 527-NPR use different install files. Configure the I/NET communication in HyperTerminal Other Troubleshooting Steps See if the communication error shows up on multiple computers and, if possible multiple locations. There may be an error with Firewall settings or Ethernet communication that only affects part of a large system Host Workstation. Use a different Ethernet port to connect the 527 or workstation to Direct connect to a controller on the controller LAN via TAP and see if any stations are offline.  It is theoretically possible that some form of electrical failure on the controller LAN has caused the 527 to appear offline.  If you cannot see the entire controller LAN from anyone on one device, you should troubleshoot Controller LAN communication. If this is a recurring issue for the site, please download and use the attached 527 offline response document for information gathering and troubleshooting.

Issue Error in Xenta 527 HyperTerminal     This error happens over and over (with different file sizes each time), and the controller essentially locks up and requires a restart to recover. Product Line TAC Vista, TAC INET Environment TAC Vista  below version 5.15 Xenta 527 using Controller LAN (RS-485) I/NET Cause Vista will poll I/NET for the past 1000 entries. Normal internal events consist of much less data than the I/NET events; 1000 I/NET events in one message make the message too large. The VSD Response too large error indicates Xentas max message size has been reached. TAC Vista ignores the error and repeatedly tries, leaving the Xenta 527 stuck in a loop. Resolution Polling I/NET for fewer events fixes this problem. The max number of events in one message has been adjusted down to 400. This change is included in TAC Vista revisions 5.1.5 HotFix 16 and later.

Issue This tool will help calculate the required M&B conversion coefficient for a given analog value in I/NET. Product Line TAC INET Environment All I/NET Controllers I/NET Resident Point Editor Cause Need to calculate an I/NET Conversion Coefficient (M&B) for a special sensor Resolution Click here to download an Excel spreadsheet that has several functions for calculating the correct M&B.

Issue Site may be migrating from I/NET to another access control system and would like to import the data. Product Line TAC I/NET Environment I/NET Seven SQL Management Studio Cause The site is migrating from I/Net to Continuum or another access control system. Resolution Open SQL Management Studio and create a New Query by clicking on the "New Query" button Run the script below: SELECT * FROM InetDb.dbo.IdWorksView Note:  This view only shows the Primary Group associated with each individual.     Select File>Save Results As... Save the file as a .csv to a location of your choosing

Issue When evaluating Inet Transition sites, a common error seen when uploading I/NET controllers under the  Inet Interface is an upload failure.  The Background Status and trace log will contain a changeset error as shown below: UploadDevice failed to process changeset on link: 93 station: 10, type index: 17 cannot continue upload Product Line EcoStruxure Building Operation, TAC INET Environment Ecostruxure Building Operation Inet Interface  Cause Understanding the ChangeSet Indices used by the developers will help pinpoint where the issue is originating from.  The message typically isolates the Link and Station but does not identify where within this controller the problem may lie.  Resolution The current list of ChangeSet Indices are listed below and attached Changeset_index.txt Index Affected 9 DCU passwords, States, Eng units, Conversion Coeff., Controls, Holidays, DDC history, Override access, Sunrise/Sunset 11 Points 15 Action message, DCU DDC, Event sequences 17 Calculation 19 Event extension 21 Extension general (can be one of: Runtime, Consumption, or Alarm inhibit - depends on DCU type) 23 ATS 25 ATC 27 Extension application (can be one of: Demand, ORB, ORBEM, UC, LZ, LC, Elevator - depends on DCU type) 29 Trend 31 Lookup table (raw data) 33 Demand load (raw data) 35 MCU 37 MR DDC 39 AIC sequence (raw data) 43 LCD page, Istat param, IAS (raw data) 45 Access control (raw data) Note: "raw data" indicates user cannot manipulate in EBO but it is uploaded and save in raw form to allow for a download/restore Working with the example shown in the Issue, the message indicates a changeset value of Index: 17.  Using the attached list, Index 17 indicates that the issue is within the Calculation Editor. Using the SAV file from the site and working offline within I/NET open this SAV file and check each of the editors, in this case, calculations. In most cases, it will either be an invalid character or invalid point address - which will be shown as 'blank' as seen below: Correcting this and updating the SAV file to the controller (Station Restore) will typically correct this issue. If the same error persists then please provide an Export of the Inet Interface and the SAV files of the controllers having this problem through your local support channel.   

Issue How to load up archived data in a report using Seven Reports Product Line TAC INET Environment I/NET Seven  SevenReports Archiving Cause Reports show nothing or have one blank page and fail to show data that meets the date window specified Resolution When using Seven Reports to view data, archived data can be viewed and put into a report.  From the Archives pull-down menu, Mount/Dismount the archive files. Files, by default, are stored in the c:\INET Seven Data\Arch folder. After mounting the needed reports (look at the date of the files in the archive folder), the report used must have the word ARCHIVE in the file name. This specifies that the reports will be pulled not from the current database but rather from the mounted files and on the dates specified. The reports should now be from the Archived files mounted. Archive Reports are located on the install CD under CD\Program Files\INET Seven\Reports To download, click on the link below and select to save the report to your hard disk in the c:\INET Seven Data\Reports folder:   I/NET Seven Release 2.20 and Prior files: ArchiveOverrideBillingSamples.rpt ArchiveRuntimeSamples.rpt ArchiveTransactionsDoors.rpt ArchiveTransactionsIndividuals.rpt ArchiveAnalogSamples.rpt ArchiveConsumptionSamples.rpt ArchiveDemandSamples.rpt ArchiveDiscreteSamples.rpt   I/NET Release 2.21 to current: ArchiveAnalogSamples_xi.rpt ArchiveConsumptionSamples_xi.rpt ArchiveDemandSamples_xi.rpt ArchiveDiscreteSamples_xi.rpt ArchiveOverrideBillingSamples_xi.rpt ArchiveRuntimeSamples_xi.rpt ArchiveTransactionsDoors_xi.rpt ArchiveTransactionsIndividuals_xi.rpt   Tip: In some instances, while the report is running and the data is being compiled, if you move the mouse or strike a key, the process starts all over. The solution is to start the report and wait for a few minutes if you have input a broad range of data to search and produce.