Building Automation Knowledge Base

Issue When launching NLCredits Generator, you get the following error : THE OBJECT WAS NOT FOUND. (SUBSYSTEM: LNS, #6)  An object has been requested by name or index that could not be found in the databases.  Typically, this would be a request from a LNS collection object with a bad name or index. Environment NL220 Vista LNS Cause An object has been requested by name or index that could not be found in the databases.  Typically, this would be a request from a LNS collection object with a bad name or index. It should be noted that this error can also occur in some implicit assignments. For example, if the network interface to be used has not been explicitly assigned to the appropriate property, LNS will continue using the network interface previously assigned to the ActiveRemoteNI or NetworkInterface property, respectively. In such a scenario, this exception could occur even though no explicit assignment has been made, indicating that an implicit assignment maps to an unavailable object. A monitor set may be created while offnet (System.MgmtMode is set to lcaOffNet); however, a monitor set cannot be opened while offnet. Furthermore, attempts to query the MonitorSet.IsOpen property will get the error "The object is not found (Subsystem: LNS, #6)" when offnet Resolution Launch NL220 and check if there is a project with a name only composed by alphanumerical characters (for instance, something like 82807E44116C482). Delete the project if you find it. Go to C:\NLPrj and manually delete the directory of the project you've deleted in NL220.

Issue An unexpected error occurred. Environment LonMaker Vista LNS Cause An unexpected error occurred. Resolution Please contact Echelon technical support on LonSupport@Echelon.com

Issue A query to an LNS collection object has been made using an invalid index number. The range of valid indices starts with 1 and ends with the current item count. Environment LonMaker NL220 Vista LNS Cause When launching the plug-in of a device. Resolution In NL220, go to the "Plug-Ins" menu dropdown If the option exists, Verify that the option "Simple string command" is deactivated. If not, uncheck it and try to relaunch the plug-in. *Note this option has been removed in more current versions of NL220, there may not be an option represented.

Issue When opening ZBuilder "Invalid OLE collection index(Subsystem: LNS, #15)" pops up a hundred times – seems to be one for each configuration value.  Exmucpt, exmappop, etc.  Environment Zbuilder Vista LNS Cause unknown Resolution Restoring a LonMaker backup should fix the issue.

Issue An attempt has been made to create a database that already exists. The database path should be changed to point to a different location. Environment LonMaker Vista LNS   Cause Can not defrag a database in LonMaker.  While opening an LNS database or explicitly defragmenting a database using the CompactDb method of the Network and ObjectServer objects or the Defragment Database function in LonMaker it is possible to receive: Error opening LCA database. The database already exists. (Subsystem: LNS, #21)[DB #-2035]. The error indicates that a prior attempt to defragment the database was not complete. This is likely to happen when an application is killed using Task Manager during the defrag process. Resolution To resolve the error, first delete the objects.reo file from the database directory and defragment again. Larger databases may take minutes to defragment and may leave a single threaded application unresponsive during the process. Database directory by default is c:\lm\db\< NetworkName > Therefore, if your network name was "MyNetwork," then look for c:\lm\db\MyNetwork\objects.reo Do not kill the application. It is possible to use the Task Manager as an indicator. While defragmenting, watch the CPU utilization indicator to identify completion of the defrag operation if the software performing this call does not return a completion message to your screen. http://www.echelon.com/support/kb/solution.asp?solutionID=109

Issue An unexpected database error occurred. Please take a note of the full error message, and contact technical support at LonSupport@Echelon.com Product Line TAC Vista Environment LonMaker NL220 Vista LNS Cause Microsoft TCP/IP Networking is normally installed during Windows operating system installation but it is an optional component if a network interface card (such as an Ethernet adapter) is not installed in the PC. Microsoft TCP/IP Networking is included on the Windows installation CD of all Windows operating systems that LNS 3 runs on. Depending upon the operating system that you are using (Windows XP, Windows 2000, or Windows 98), the Microsoft TCP/IP Networking component may be named slightly differently. Consult the Windows documentation for further information on how to install the Microsoft TCP/IP Networking component. Resolution You can find the same information in the "Known Problems and Workarounds" section in LNS3.0 service pack's readme file. Echelon support article 143

Issue Microsoft TCP/IP Networking must be installed on your PC or a LNS #25, [DB #2524] error is reported. Environment LonMaker NL220 Vista LNS Cause Microsoft TCP/IP Networking must be installed on your PC . Resolution Microsoft TCP/IP Networking is normally installed during Windows operating system installation but it is an optional component if a network interface card (such as an Ethernet adapter) is not installed in the PC. Microsoft TCP/IP Networking is included on the Windows installation CD of all Windows operating systems that LNS 3 runs on. Depending upon the operating system that you are using (Windows XP, Windows 2000, or Windows 98), the Microsoft TCP/IP Networking component may be named slightly differently. Consult the Windows documentation for further information on how to install the Microsoft TCP/IP Networking component. You can find the same information in the "Known Problems and Workarounds" section in LNS3.0 service pack's readme file. See also Echelon support article 143

Issue The System object associated with this network database is invalid. Environment LonMaker NL220 Vista LNS Cause Undetermined Resolution To resolve this, the network database must be rebuilt from scratch.

Issue When importing an I/NET network into a Vista Workstation, the point names are available, but only after you drill down to the link, station, point, bit offset, and view the point type.  This can be cumbersome when trying to bind graphics or navigate the network. Product Line TAC Vista Environment Vista Workstation 5.1.1 and above I/NET Shortcut wizard Cause This is how the I/NET network is structured in I/NET. Resolution Right-click on the I/NET network Select "Create I/NET shortcuts..." A folder is created with nested folders for individual controllers, but each shortcut point is renamed with the I/NET point name instead of the address.

Issue What is the proper installation process to install TAC Vista WebApps on Windows 7. Environment Vista 5.1.4 to Vista 5.1.9 Windows 7 Cause TAC Vista 5.1.4 Web Apps does not support Windows 7 for customer installations. It is supported for test environments only. Since Windows 7 and Server 2008 are very similar in design the steps detailed for Windows Server 2008. Resolution Install IIS 7 with IIS 6 Management Compatibility Specifically add the "IIS Metabase and IIS 6 configuration compatibility" feature. Install TAC Vista Server As Administrator, Run the ASP.NET IIS Registration Tool (aspnet_regiis.exe) for ASP.NET version 2.0 %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiise.exe -i Install TAC Vista Webstation As Administrator, Migrate the ASP.NET application configuration to IIS7. Go to the Webstation/Screenmate settings in IIS Select "Advanced settings" under "Manage Application". Change Application Pool from "DefaultAppPool" to "Classic .NET AppPool". Open Dcomcnfg. On "My Computer", "Launch and Activation Permissions", click "Edit Defaults". Add the "Network Service" account and grant "Local Launch" and "Local Activation".

Issue A call to the RecoverFromNetwork method has been made, using a previously used network database. Environment LonMaker NL220 Vista LNS   Cause A call to the RecoverFromNetwork method has been made, using a previously used network database. Resolution For the recovery process, a newly created network database is required. Run the LNS Database Recovery Wizard: If you are recovering through a PCC-10, PCLTA-10 or PCLTA-20, use the LonWorks Plug 'n Play Control Panel to select the NSI NI Application. Otherwise, error "NS #138 (Local interface is in the wrong state (unconfigured)" is reported, then "NS #67 system is not open)", then "LNS #55". Finally, the LNS Database Recovery Wizard only gives you the option to cancel the recovery. see also Echerlon support article 190

Issue An unspecified database limit was exceeded. Environment LonMaker NL220 Vista LNS Cause You will get this LNS error when the maximum number of devices within a network (32385) is exceeded. Resolution Run the LNS Database Recovery Wizard: If you are recovering through a PCC-10, PCLTA-10 or PCLTA-20, use the LonWorks Plug 'n Play Control Panel to select the NSI NI Application. Otherwise, error "NS #138 (Local interface is in the wrong state (unconfigured)" is reported, then "NS #67 system is not open)", then "LNS #55". Finally, the LNS Database Recovery Wizard only gives you the option to cancel the recovery. see also https://echelon.force.com/support/s/search/All/Home/190?tabset-95728=2

Issue Local network interface is in the wrong state (e.g. unconfigured).  Environment LonMaker NL220 Vista LNS Cause Local network interface is in the wrong state (e.g. unconfigured). Resolution When you encounter this error, set the network management mode to lcaMgmtModePropagateConfigUpdates (0) by writing to the MgmtMode property of the System object. Then, re-commission the network interface, if necessary Run the LNS Database Recovery Wizard: If you are recovering through a PCC-10, PCLTA-10 or PCLTA-20, use the LonWorks Plug 'n Play Control Panel to select the NSI NI Application. Otherwise, error "NS #138 (Local interface is in the wrong state (unconfigured)" is reported, then "NS #67 system is not open)", then "LNS #55". Finally, the LNS Database Recovery Wizard only gives you the option to cancel the recovery. see also Echelon support article 190

Issue The database has an invalid version. Note that LNS databases can be upgraded using the CompactDb method, but also note that LNS databases are not backwards compatible. Once updated to version N+1, the database will not be accessible for a version N client any more. Environment LonMaker NL220 Vista LNS Cause Invalid database version.  If you are running LonMaker 3.1 with a non-Turbo LNS Server and somebody who is running LonMaker 3.1 with a Turbo LNS Server has edited the database and sent you a backup, you will not be able to open the database until your PC has been upgraded. The global database is not open. (Subsystem: LNS, #64) and Invalid database version. (Subsystem: LNS, #81)[DB #-2038] errors occur if you try to open a database with an older version of LNS. Resolution Right click on the title bar of the design window and select About. This will tell you your LNS server version on the machine in question has. It must be the same or greater than the database you attempt to open.

Issue The string passed contains one of more characters that are invalid in the current environment. Environment LonMaker NL220 Vista LNS Cause File names must follow style conventions taken from the Windows operating system on the PC running an application. Resolution When writing to the Name property of any object, use of the forward slash (/), back slash (\), period (.), and colon (:) characters will cause this exception to be thrown.

Issue The Neuron ID assigned is already being used by another device in the network. Environment LonMaker NL220 Vista LNS Cause The Neuron ID assigned is already being used by another device in the network. Resolution If you are typing in the Neuron ID manually, check to make sure a device actually does have that neuron ID already.  If you are service pinning and you are certain that no other device is using that Neuron ID, then it may be a “phantom node” that will come to the surface by attempting a resynch.  You can then delete that phantom node and proceed.

Issue The remote client fails to connect to the LNS Server. Environment LonMaker NL220 Vista LNS Cause When using LNS 3.8 to make a client/server application : - LNS server is launched on the server - when opening the database on the client, you get the error.   It is a port problem. Resolution Lightweight clients use port 2540 to talk to the server and LNS applications also require ports 6001 and 6002. You can check the port usage on your PC by launching netstat -a in a command prompt ; you will get the list of the ports used. netstat -bn will also give you a list of ports being used.  It can occur if the LNS Server has not been started on the server PC and the client attempts to connect.  Or if the network is not connected and onnet ready to receive remote clients.

Issue An IP remote client did not receive expected data in time. The connection might be lost. Environment LonMaker Vista LNS Cause Trying to download to controllers and Vista receives an invalid address error.  The LonMaker database had a de-serialization error found when it tried to check the monitor sets.   De-serialization error after attempting a drawing resynch.  Resolution  Restore an old backup of the LonMaker database or the NL-220 database. If the error still occurs additional assistance will be needed from Echelon to try to find a solution.

Issue There is no communication with the LNS Server. Environment NL220 Vista LNS Cause LNS server was shut down on the remote server prior to closing the drawing.  Resolution Close the drawing prior to shutting down the LNS server

Issue WorkPlace Tech Tool 5.7.4 causes Visio to crash when attempting to open some MNL-800 applications.   The problem occurs with MNL-800 applications that were created with WorkPlace Tech version 4.x where the application does not use the hardware schedule function.  Environment WorkPlace Tech Tool version 5.7.4 MNL-800 application file created with WorkPlace Tech Tool version 4.x Hardware schedule has never been enabled using an earlier version of WorkPlace Tech Tool version 5.x Cause Required hardware tag "DayOfWk" missing (normally shown on left tag rail, if unused in the application). Resolution This problem is automatically repaired in WPT version 5.7.5 or newer. While we recommend upgrading WPT to 5.7.5 or newer, you can continue to run WPT 5.7.4 and  correct the problem by taking the file to a computer running WorkPlace Tech version 5.7.3 and following this procedure: Open the existing file in the existing project (or in a new project). Run the Hardware Wizard and click [Next] twice to display the Time & Schedule page. Check the box  "Enable the built-in schedule" then click [Finish] to update the application file with the schedule reference tags. Run the Hardware Wizard a second time and click [Next] twice to display the Time & Schedule page. Un-check the box "Enable the built-in schedule" then click [Finish] to update the application file removing the unused schedule reference tags. Close the application.  This will save the changes to the application file.  If prompted to convert the drawing, do not convert it. The saved application file will be usable in WorkPlace Tech Tool version 5.7.4