Building Automation Knowledge Base

Issue When starting Vista software (other than Vista Server) an error appears stating that the license has expired. lc_checkout failed: Feature has expired. Feature: Menta.View Expire date: 31-May-2011 License path: C:\Program Files\Schneider Electric\License Files\Demo_5_1_31_may_2011.lic FLEXnet Licensing error:-10,32 For further information, refer to the FLEXnet Licensing documentation, available at "acresso.com". Product Line TAC Vista Environment Vista Workstation Menta TGML Editor Vista Webstation Cause The temporary trial license for Vista has an expiration. If Vista returns an error stating that the license is expired this may be due to one or more of the following reasons: The temporary license file being used has indeed expired Vista was pointed to a temporary license file that has now expired rather than being pointed to the license files folder The computer date is set incorrectly Resolution Start by checking to see that the computer date is set correctly. If it is set to a future date beyond the expiration date of the temporary license file this will prevent Vista from starting up. Check to verify that the temporary license file being used has not expired by opening Windows Explorer and browsing to the following folder: C:\Program Files\Schneider Electric\License Files or C:\Program Files\TAC\License Files if this is an older installation. The expiration date of the file is part of name of the file. For example, Demo_5_1_31_aug_2011 expires on the 31st of August, 2011. The terminal services licenses need to be updated every two weeks and the expiration date can also be found in the file name in a week-of-the-year format. The easiest way to find the exact date is to open the license file in a text editor  and the expiration date can be found in the first line. For example, the first line of the license file Demo+TS_OK_5_1_valid_through_week32_2011 is: "FEATURE Vista.Workstation taclic 5.1 14-aug-2011 uncounted \" therefore this license expires on the 14th of August 2011. If the exact license file rather than the license location was specified during installation, Vista may not be able to find a new temporary license file once the old one expires. The location where Vista looks for the license should be cleared out by following the steps in the resolution of Switching from the Demo license to the site License in Vista 5.1.7 or older. Once the registry value has been cleared Vista will ask where the license is found the next time it is started up.

Issue Drayton Theta ll ES4 Optimiser Controller requires replacement. Product Line Field Devices, Satchwell Sigma Environment Stand alone discreet Drayton Optimiser Controller Theta ll ES4 Cause Obsolescence of Drayton Theta ll ES4 Optimiser Controller. Resolution Please note that the Satchwell SVT controller is no longer available, and that the only possible replacement is the DC1400. Please refer to What is the replacement for the SVT controller range? for more details.  Replace Drayton Theta ll ES4 Optimiser Controller with Satchwell SVT Optimiser Controller.  N.B.  Two models of the Satchwell SVT Optimiser Controller are available :-  SVT 4201 with Analogue Timeswitch  SVT 4251 with Digital Timeswitch, Details of the Satchwell SVT Optimiser Controllers may be viewed here. It should also be noted that the associated Drayton Theta ll ES4 Optimiser Controller Sensors are obsolete.  These Sensors are not compatible with the Satchwell SVT Optimiser Controllers and must therefore be replaced.  Unlike the Drayton Theta ll ES4 Optimiser Controller, which requires the installation of both an Outside Air Temperature Sensor and an Inside Air Temperature Sensor, the Satchwell SVT Optimiser Controllers require the installation of a Inside Air Temperature Sensor only.  A STR 614 Inside Air Temperature Sensor is packed with the Satchwell SVT Optimiser Controller when supplied new :-   Details of the STR 614 Room Temperature Sensor may be viewed here.

Issue Error message in Vista System Plug-in: LNS System access failure, (Subsystem: NS,#147) lcaErrNsLicenseViolation 147 LNS license access failure. Product Line TAC Vista Environment LonMaker, NL220 LNS Network Cause Feedback from Echelon on this error message. A variety of conditions may cause this error. Some relate directly to internal licensing components. For example, the license DLLs may not have installed properly, the files that identifies the license (nsseng.exe for the LNS Server, lonmaker.DSL for LonMaker) do not exist, or the Crypkey licensing components (crypserv.exe and ckldrv.sys) are not running properly. You can resolve these problems by deleting the files that may be causing problems, and re-installing LNS. The license DLLs, as well as the crypserv.exe and ckldrv.sys files, can be found in the Windows 'LNS Licenses' folder, and the Crypkey files can be found in the Windows 'system32' folder. Note that you must stop the 'CrypkeyLicense' service and 'NetworkX' driver before deleting the Crypkey files. Certain conditions on the PC operating the license may also cause this error. For example, if the PCs file system is corrupted or low on space, or if the license files have been manually deleted, tampered with in any way, or moved by some disk-defragmentation utilities, this error will occur. You can resolve these situations by ordering a replacement license key. If the PC clock is set back to a time before the creation of the license or before the last time credits were purchased, this error will occur. In some cases, this can be resolved by rebooting the PC. Otherwise, it may be necessary to order a replacement key. The error may occur if the license has been transferred out of the PC, manually terminated, or if there are zero maximum credits. In this case, you need to purchase additional credits for the license. For more information on licensing, see Chapter 13 of the LNS Programmers Guide. Resolution It is very likely that you have corrupted LNS Credits. To determine if this is the case and how to solve it please reference Corrupted LNS Credits.  

Issue How to protect an OAT sensor from the sun? Product Line Field Devices Environment Outside Air sensors, Outdoor Temperature Sensor STO100 System Vista, Xenta STO200 System I/NET STO500 System Continuum STO600 System Satchwell STO600D System Drayton STO300 Outdoor temperature transmitter ETO100, ETO200, ETO500, ETO800 Cause Direct solar heating will affect the outside temperature reading. Resolution We do not supply sun shields for an Outside Air Sensors as there should never be a requirement to fit one. The Outside Air Temperature sensor for a building should always be fitted to the North side of the building where it will not be in direct sunlight (or the South side in the southern hemisphere). The temperature on the East, South or West sides of any building will always be higher than the North side (in the northern hemisphere) and give inaccurate readings if the sensor is mounted there. Also any sort of sunshade will also act as a shield to retain the heat also giving an erroneously high reading. For sites like weather stations where the measurements are to be taken in a field installation a Stevenson screen could be used, these are available from specialist instrument suppliers. A web search should provide local suppliers. Also see Recommended locations for Temperature Sensors, Valves, and Actuators for further details on sensor location.

Issue Problems installing Vista Webstation 5.1.5 or newer Product Line TAC Vista Environment Vista Webapps (Webstation) 5.1.5 Windows 2008 Server 32-bit or 64-bit. Cause In order to install TAC Vista Webstation successfully on Windows Server 2008, there are a number of steps and prerequisites to be checked. Resolution In order to install TAC Vista Webstation successfully on Windows Server 2008 it has to be done in the following order: PC Preparation – Only if you can not access the Run as administrator context-menu! Log in as an administrator and create a new administrator group (eg. VistaAdmin) and add a user to this group. By doing this you will be able to access the Run as administrator context menu later on (users added to the Windows administrator group do not always receive full administrator rights). Install IIS 7 and ASP.net Start the Server Manager (Right-click on Computer in the start-menu or the Computer desktop icon if running classic start-menu and select Manage). Right-click Roles and click Add roles. In the dialogue that opens up click Next and then select Web Server (IIS). In the dialogue that follows click Add Required Features. Click Next (twice). On the select Role services page select ASP.net. In the dialogue window that appears click Add Required Role Services. Click Next and then click Install. NOTE FOR WINDOWS 7 USERS! Whilst Windows 7 is not officially supported for running Webstation it may be used in a test environment. It's important to note that the IIS and ASP.net installation is slightly different - the user is not asked to add roles, the user is asked to add windows features (see screenshot below). Ensure .net framework 4.0 is installed Open Server Manager and select Features. Scroll down and ensure .net framework 4.0 is installed. If not: Open Internet Explorer. From the menu select Tools\Windows Update (Safety\Windows Update in IE8) Run windows update and install .net framework 4.0 Install TAC Vista Server and any hotfixes Install TAC Vista Webstation and any hotfixes As administrator, register ASP.Net version 4.0 Click on start and then All programs\Accessories. Right-click on Command Prompt and select Runs as administrator. If using 32-bit: Open explorer and locate the %SystemRoot%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis. If using 64-bit: Open explorer and locate the %SystemRoot%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis. Ensuring that the directory is set to C:\ copy the file path into command prompt and the add the following text : aspnet_regiis.exe -i -enable Press Enter Confirm the installation was successful Click on start and then type inetmgr in the search box. This will open IIS manager. Expand the hierarchical menu on the left and then expand the Sites folder. Expand Default Web Sites and select Webstation Right-click on webstation and select manage application > Advanced Settings. In the Application Pool field it should say SE ASP.NET v4.0 Classic All that is left now is ISAPI, CGI (see "HTTP Error 404.2 - Not found. The page you are requesting cannot be served because of the ISAPI and CGI Restriction List settings on the web server") and DCOM settings (see TAC Vista Installation Manual or Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET). License problem: Webstation - No license Available

Issue Advice on the configuration of a Sigma DNN (Distributed Network Node) when connecting it to a "Flat" Ethernet network. The DNN provides a communications route to Sigma controllers connected to an Ethernet or ARCnet sublan. Product Line Satchwell Sigma Environment Sigma Ethernet network Ethernet or ARCnet subnets Cause General configuration advice. Resolution A "Flat" Ethernet network is a network that does not contain any subnets, for instance a network who's address is 10.158.0.0 Mask 255.255.0.0 will contain network addresses 10.158.0.1 to 10.158.255.254. On this type of network the DNN will only require an IP address and Subnet Mask to be entered. This information and details of the DNN's "Default Server" are added to the device using the SDCU (Sigma Device Configuration Utility). If the DNN has RIP (Routing Information Protocol) enabled then it will broadcast the route to the sublan onto the network, if RIP is not enabled, then a persistent route must be added to the Sigma server. Please refer to Persistent routing on the Sigma server for more information.  To modify the DNN RIP settings, use the Pocket Terminal programme. RIP is enabled by default. To disable RIP on port 5 of the DNN. Start the Pocket Terminal programme. Enter RIPD 5 and select send. To enable RIP on port 5 of the DNN. Start the Pocket Terminal programme. Enter RIPE 5 and select send. To review the status of RIP Enter RIPS and select send

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 Services for assistance. Issue There is no clear guidance on how to handle the SNMP settings for TAC Xenta Servers Product Line TAC Vista Environment TAC Xenta Server TAC XBuilder SNMP Cause Previously the SNMP feature has not been widely used and has not been a security concern. There are two types or flavors of SNMP. One is for browsing a device to get information about it (SNMP Agent), and the other is to automatically send alarms from a given device to a central alarm system (SNMP Alarm Trap). Now according to reports from the field, IT departments are starting to get concerned about the SNMP feature in Xenta Servers. A general overview of how SNMP can be used maliciously for intrusion can be studied here. Normally the IT department requests that: The default community string is changed SNMP is disabled Here is an example of what you see when you browse a Xenta Server (having the correct Xenta Server mib file) using a SNMP browser such as "MIB Browser" from iReasoning Here is an example of alarms received from a Xenta Server via SNMP Resolution All (or most) SNMP settings are changed through TAC XBuilder First step is to change the default community name. If the community name is either "private" or "public" (the latter is default), it can be browsed without knowing the name. You simply change the name in "Community Name" and "Trap Community Name". Download all project files to the Xenta Server afterwards. Now when you try to browse the Xenta Server from the SNMP agent without first defining the community name, you will not be able to retrieve data. Next, we can disable the SNMP Alarm Trap. Download all project files to the Xenta Server afterwards. After that, alarms will not be sent to the IP address configured. Following here are advanced steps to change the ports used for SNMP (161 and 162) If the settings described above are not enough, we can change the port number used for SNMP. This is however a little more complicated. You need to connect to the Xenta Server using FTP (Note that the FTP access may be disabled, refer to Disable FTP in the Xenta 5/7/9xx Controllers if unsure how to enable this), and fetch the following file: /sys/system/snmp.cfg Open the file in Notepad Change the two port number as below - you can choose other port numbers, but it is crucial that they are not the same as any other ports used by the Xenta Server. Upload the changed file to the same location on the Xenta Server Download the project from TAC XBuilder, choosing to download all files You now get this message Here you must click "Target system" or the changed settings are overwritten Note that the port numbers defined in XBuilder have not changed yet Save the project and close XBuilder Open the project again You will now see that the port numbers have the value you defined in the file earlier Now when you try browsing the Xenta Server with a SNMP tool, you can no longer connect on the default port 161

Issue If the PC is shut down or rebooted, Vista Server can be configured to run automatically on startup of the PC. This is not the same as running Vista Server as a service (for information on that, please see Registering/Unregistering TAC Vista Server as a Windows service). The server still runs as an application, but starts once at Windows Startup. Product Line TAC Vista Environment Microsoft Windows Vista Server Cause In the event of a power loss or reboot, the Vista Server will start automatically for the user, which enables trending and event logging, without requiring a manual start of the application. Resolution These instructions are tailored to the Windows 7 environment, but the process is very similar in all Windows versions (add a shortcut to the application to the Windows Startup folder): Open Windows Explorer and navigate to C:\Program Files\Schneider Electric\TAC Vista 5.1.X In that folder, locate Tacos.exe Right-click on Tacos.exe and select Send to > Desktop (create shortcut) This will place a shortcut on the desktop to be used in a later step. Click on Start > All Programs Locate the folder called Startup Right-click on Startup and select Open all users This will open a Windows Explorer window to the appropriate folder Drag and drop the Tacos.exe shortcut from the Desktop to this folder

Issue MFC errors when starting or running Cyberstation or Webclient Product Line Andover Continuum Environment Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Windows 10 Windows Server 2012 Cause Microsoft Function Class (MFC) errors are typically caused by missing, damaged or altered files that an application is looking for and is having problems using. Resolution There can be a number of reason why MFC errors are being received. Here are a few causes related to Cyberstation startup. Check the Continuum compatibility matrix. If you are using a version of Windows Operating System that has not been qualified for a specific version (i.e. Windows XP SP2 with 1.93) then this can cause MFC errors. Viruses and Malware can also affect MFC files. Be sure to run both types of scans on Cyberstation, but this should be done after the Cyberstation or Webclient PC has been installed. If these types of products are active during an install, they can flag some of the files that would normally get installed as suspect and cause problems with the operation of Cyberstation even if it appeared that the installation was successful. Removing Continuum, rebooting, running scans and then disabling the active scans at the time of the Cyberstation install will often resolve these issues. Windows XP, Vista and Windows7 have restore points that you can sometimes go back to in order to restore to a point earlier where the MFC errors were not happening. As a last resort, you may need to reformat the hard drive on the PC, reinstall the Windows Operating System including the appropriate service packs and hotfixes and then install Cyberstation or Webclient. Links to other MFC related articles: MFC errors on Continuum startup after moving a database to another PC MFC error on Continuum startup or Continuum won't start on HP PC Running a listview is giving a MFC error

Issue When Vista Server is running as a service how do you restore backup files? Product Line TAC Vista Environment Vista 4.x.x Vista 5.x.x Cause The Vista Server program will not allow you to restore a backup when running as a service. Depending on the nature of the backup it might have to be deregistered as a service to do the restore. Resolution Vista backup is a zip file of the database directory Open Services from the Windows Control Panel. Stop the Vista Server service (TACOS.exe) Unzip the database backup into an empty directory of your choice. Start Vista Server Setup and browse to the directory the database was restored to in the Database folder path of the Vista Database tab. Click Ok. Start the Vista Server service (TACOS.exe) Vista backup is a full Vista backup (FVB) file Unregister Vista Server as a service, see Registering/Unregistering TAC Vista Server as a Windows service. Start Vista Server as a program. Login to the Vista Server program. Use the File\Restore Database option. Browse to the FVB file. Browse to a new folder. Click Ok. Close Vista Server. Start Vista Server Setup and browse to the directory the database was restored to in the Database folder path of the Vista Database tab. Click OK. Start Vista Server as a program. Ensure the database was upgraded. Stop Vista Server. Register Vista Server as a service, see Registering/Unregistering TAC Vista Server as a Windows service.

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

Issue TAC Vista to SmartStruxure Interface does not connect in non-English Operation System Environment TAC Vista SmartStruxure Solution TAC Vista SmartStruxure Interface 1.0 TAC Vista 5.1.8 non-English Operation System Cause The Format setting to non-English will cause this issue. Resolution In the Windows Control Panel, select Region and Language. On the formats tab change the format to English. Click Apply. Vista 5.1.9 will fix this. For how to create Vista interface in SmartStruxure, refer to How to Create TAC Vista Interface to SmartStruxure.

Issue How to set up extended logging. Product Line Andover Continuum Environment Continuum Cyberstation Extended Log Cause Configuration of extended logging. Resolution Sample configuration for extended logging. This example would create enough entries for a 24 hour period. Create an Infinity Numeric Select the logs tab Number of entries (96) Type will be LogInstantaneous (Stores the current value of this point at the beginning of every interval) Interval will be 15 minutes (15 minutes in a 24 hour period is 96 which is what we set for the Number of entries) By default the Workstations are setup for 5 minute checks to the controllers to see if there are extended logs to enter into the database. For more in-depth configuration of extended logging, please review Extended Logs in the Continuum Online help system.  For performance and load balancing please see Extended Logging gaps, performance and load balancing.

Issue Sporadic values in Vista or Vista Graphics show up as red X or "Invalid Value" Product Line TAC Vista Environment Vista Workstation Classic Environment Cause Vista is designed to only have one instance of Vista Server running per system.  If two Vista Servers are polling the same equipment, data will not be read correctly. Resolution Configure all machines as a Remote Workstation with the instructions below. The remote Workstation will be networked to the Vista Server you would like to remotely view. To allow for correct communication DCOM setting will also need to be set. See Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET for the utility to complete this process. Shut down all Vista programs, including Vista Server Start Vista Workstation You will see this log in screen: Click on "Options" to display this screen Change "[Local Server]" to the IP address of the machine with Vista Server running Enter your username and password and select OK 

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

Issue IT departments want to install just the client software without attaching to the webclient server and want to know if there is a way to accomplish this. Product Line Andover Continuum Environment webClient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Webclient deploys activex controls using several .cab file from the C:\program files\redist folder on the webclient server. These files must be delivered to the browser PCs with admin privileges on the client PC in order for webclient and webpinpoint to work. Here is a list of the .cab files and ActiveX controls that get installed AccWebUtils.cab - AccDotNetBootstrap Control, Crypto Class (Used for  regular webclient use) WebclientPinpointSetup.cab - PPBrowserMgr Control (WebPinpoint) WebclientVideo.cab - TACVideoControl.VideoControl (Viewing Video layouts) ** The other piece that doesn't get installed are the permissions for the caspol commands that must be set for zones in order to run schedules. See webClient schedules getting error 'request for permission of type' system.security.permissions or .net control error on Webclient reports related to webclient schedules and running the caspol commands 1.94 SP1 requires that Microsoft VC++ 2005 Redistributable SP1 x86 to be installed for webpinpoint, it prompts to install when accessing a graphic the first time Resolution There is no client side webClient PC installation. The method for delivering the necessary activex controls and files are triggered by the browser PCs access to the webclient server PC and then the files are delivered to the client.  Some IT departments use Microsoft  SMS or Active directory to deploy software in a locked down environment. To deploy webclient to these types of browser PCs, they would have to logon with Admin privileges to perform the one time install of these files. The only other method if the IT group has InstallShield or WISE package creation software would be to capture the browser PC installation and use the produced .msi file for client delivery. This is informational only and has not been tested by Schneider Electric.

Issue How to find a Vista 5 dongle ID if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista 5 Windows Command Window Cause The Dongle ID is required for locking TAC Vista licenses to a site dongle. Normally, the dongle ID can be found on the side of a Vista 5 licensing dongle. However, on older dongles, this number can rub off.  It is still possible to extract the dongle ID using the GetTACHLInfo.exe dongle utility software. Resolution On the Start menu, click Run. In the Run dialog box, type cmd Click OK. In the dialog box, go to the folder C:\Program Files\Schneider Electric\License Server (as default) NOTE: for TAC Vista 5.1.3 and prior, go to the folder C:\Program Files\TAC\License Server. Use command "cd.." for going to the parent directory and command "cd folderPath" for going to a child directory. Can also view items in the current directory by typing "dir". In the dialog box, type GetTACHLInfo (or GetTACHLInfo.exe) and press Return. The dongle ID is listed after "TAC_HL_ID=". Read Find a Vista IV dongle ID (PSU ID) for how to find Vista IV dongle ID.

Issue Using a 4-20 mA sensor on a Xenta 451A or 452A Product Line TAC Vista Environment Xenta 451A Xenta 452A Cause There is only enough power onboard a Xenta 451A or 452A for one 4-20mA.  Resolution Wire each sensor, using an external power supply for cases where there is more than 1 4-20mA sensor. Create an AI in the Menta file Bind the object to the 451A Select the correct Terminal Ref Choose the 4..20mA sensor If using this device as a stand alone LON module chose the 4-20 mA option for the nci NOTE: only Xenta devices ending in "A" have truly Universal Inputs.  For complete details on input configuration, see Configuring inputs on Xenta 421A or Xenta 451A when using the controller as a stand alone Lonworks node.

Issue Node reset messages are received at the Sigma server on a regular basis. Product Line Satchwell Sigma Environment Sigma software - all releases. Sigma firmware - all versions. Cause Messages designed to be sent to a server are being sent to a device node. Resolution The BAS 2800+ system allows Controllers and Terminals to have the same numbers allocated. In Sigma this is not possible as all device numbers are unique. Should a reference to a terminal accidently be left in a controller configuration, then the controller may send messages to this device number, the receiving controller will then reset. There are two ways to locate the source of the messages being sent to the resetting controller, they are: Use SigView to display all of the object data for a controller, and then search the data for the node number of the resetting controller. You will be looking for entries such as T(resetting node number). OR Disconnect the controller from the network, and then connect a laptop, configured with the controller IP Address, and running WireShark to record all network messages. Allow WireShark to run for a period greater than the time between controller node resets. Filter the WireShark messages to review only messages sent to the IP Address of the resetting node. Check what the source IP address of these messages is, and then use SigView to review this controllers data. A typical Wireshark display is shown below, in this case the trace is filtered on the "Source" IP Address. For more information on using WireShark, please review Using WireShark to analyse communications on an Ethernet network.

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