Issue New system image memory fails during upgrade. Environment LonMaker NL220 Vista LNS Cause This error will be generated if there is a failure to write the new system image the device after the LoadEx method has been invoked. These failures usually occur because the device does not have flash memory in the required location to hold the new image during the download process. Resolution The old system image will remain intact if this error is thrown.  However, the device will remain applicationless.  You should load a new application image into the device with the Load or LoadEx methods in this case.

Issue New system image failed to upgrade. Environment LonMaker NL220 Vista LNS Cause This error will be generated when you invoke the LoadEx method on a device, and the new system image is successfully transferred to the device, but the switch from an old system image to a new system image fails.  Resolution  If you encounter this error, try invoking the LoadEx method again, or loading the previous system image back into the device.

Issue The application timed out starting the LNS engine process (NssEng.Exe).  Environment LonMaker NL220 Vista LNS Cause This could be an indication that LNS is not installed properly.  Resolution If you encounter this error, you should try the following steps in order. Restart the "Echelon LNS Server" service Rebooting the PC Re-installing LNS

Issue The specified LonMarkObject is not dynamic. Environment LonMaker NL220 Vista LNS Cause This exception may be thrown if you attempt to assign a network variable to a static LonMarkObject with the AssignNetworkVariable method, unassign a network variable from a static LonMarkObject with the UnassignNetworkVariable method, or delete a static LonMarkObject with the Remove method. Resolution You can determine if a LonMarkObject is dynamic or not by reading its IsDynamic property.

Issue The specified network variable is not dynamic. Environment LonMaker NL220 Vista LNS Cause This exception may be thrown if you attempt to assign a static network variable to a LonMarkObject with the AssignNetworkVariable method, unassign a static network variable from a LonMarkObject with the UnassignNetworkVariable method, or delete a static network variable with the Remove method. Resolution You can determine if a network variable is dynamic or not by reading its IsDynamic property.

Issue The specified LonMarkObject is in use, and at least one of its member network variables is bound. Environment LonMaker NL220 Vista LNS Cause This error may be thrown if you use the Remove or RemoveByIndex methods to delete a LonMarkObject with the lcaLonMarkObjectRemoveNVs (1) option set as the removalFlags element, and that LonMarkObject contains bound network variables. Resolution The bound network variables must be disconnected before the LonMarkObject can be deleted. You can disconnect the network variables by specifying the lcaLonMarkObjectRemoveAndDisconnectNVs (3) option as the removalFlags element when you call the Remove or RemoveByIndex methods

Issue The link between the parent and the child record was unexpected. Environment LonMaker NL220 Vista LNS Cause This error usually indicates that the LNS database has been corrupted. Resolution If you encounter this error, you should use the Validate method to run a database validation, and consider switching to a backup database.

Issue The database updates were successful, but one or more nodes were not updated because the node(s) rejected the update, for example due to an authentication failure.  A device encountered an operational or messaging error while its configuration was being updated. Environment LonMaker NL220 Vista LNS Cause This usually means that there is a configuration mismatch between the node and the LNS database.  The LNS will continue to try to update the nodes in the background if the UpdateInterval property of the System object is set to a non-zero value, and you can force a retry with the RetryUpdates method. This seems to have two origins – either in the LNS tool which commissioning or creating group bindings, etc., or in the System Plug-in while trying to download a programmable controller.  It has been observed when creating group bindings when most of the controllers were offline in an onnet connected network. It has been observed while creating and downloading a network in NL220.  All of the correct steps of creating a node, importing a Menta file, updating the network, and downloading were followed.  During a download, an error occurs: “A device encountered an operational or messaging error while its configuration was being updated” (Subsystem: NS, #4031).  After which an additional dummy device was created and inherited the neuron ID of the controller originally being downloaded. It has been observed on an engineering PC using a NIC USB running under Windows Vista which had been reverted to Windows XP.   Commissioning a router in a brand new NL220 Smart Channel results in this error.  Resolution This error occurs because LonMaker/LNS does not receive the device's response in a timely manner during the commissioning process. A new property (AppDevice::Delay) was introduced in LNS Turbo to resolve this issue. This Delay value will be added to any delays calculated by LNS based on the network topology. When this property contains the default value of 0, LNS will not calculate an extra delay for the device. For earlier versions of LNS, the workaround is to increase the channel delay.  Please note that this solution will affect all devices on that channel. Also note that the AppDevice::Delay property is not exposed in the LonMaker Turbo Edition. To modify this property, you must use another LNS application, such as the LNS Object Browser (lnsobjectbrowser.exe located in your LonWorks\bin folder). You can keep track of which devices are up to date using commissioning events, and by reading the CommissionStatus property of each AppDevice object.  If you are receiving persistent update failures on a device, you should re-commission the device with the Commission method. In some cases, switching to a PC using an Echelon LTA cleared the problem. It has been observed that in NL220, an incorrect Device Template was assigned to the Controller during the commission process. The workaround was found by deleting the controller, updating Vista, and then deleting the offending template (in this case Lonm401 assigned to a Xenta 282). The controller then was able to be added with the correct Template. In another case, the controller had to be decommissioned, the controller had to be deleted (including the IO modules if they exist), the TAC network tree inside the system plug-in was deleted, and then the Vista database was updated. A new controller was then added to the page and the commissioning process was started over. All bindings are lost in this process. 

Issue The database updates were successful, but the configuration properties on one or more devices could not be updated as a result of invalid configuration property definitions.  The LNS will continue to try to update the nodes in the background if the UpdateInterval property of the System object is set to a non-zero value, and you can force a retry with the RetryUpdates method. Environment LonMaker NL220 Vista LNS Cause You can keep track of which devices are up to date using commissioning events, and by reading the CommissionStatus property of each AppDevice object.  If you are receiving persistent update failures on a device, you should re-commission the device with the Commission method. This error can occur while running LNS TE with NL220. This error is likely due to the device implementation. It could occur if the CP definitions were incorrect for example or if the device implements changeable-type NVs and the type change was rejected by the device. Resolution The best is to get a protocol analyser log of the CP download. 

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