Issue An operation requiring a Neuron ID was attempted on a device with no Neuron ID.  Subsystem; NS #37 Environment LNS LonMaker Vista NL220 Cause For example, if you invoke the Wink method on a device whose Neuron ID has not been set in the LNS database, this exception will be thrown.  In some other cases, this exception may be thrown if a device’s Neuron Id has been set in the LNS database, but the device has not been commissioned.  For example, if you read the SelfDocumentation property of a device before that device has been commissioned, this exception will be thrown, regardless of whether or not the device’s Neuron ID is set. Resolution Make sure the Neuron ID has been set and the device is commissioned.

Issue Requested operation can't proceed because a database import or export is currently in progress. Environment LNS LonMaker Vista NL220 Cause Requested operation can't proceed because a database import or export is currently in progress. Resolution Wait for the import or export to complete.

Issue These errors are internal to Echelon LonMaker and require the assistance of Echelon Technical Support. Environment LNS LonMaker Vista NL220 LonSupport@Echelon.com 1-800-258-4LON or 1-800-258-4566 Cause NS #9 lcaErrNsBadClient NS #11 lcaErrNsNoClient NS #14 lcaErrNsClientBlocked NS #16 lcaErrNsNotImplemented NS #18 lcaErrNsServiceFailure NS #20 lcaErrNsPrematureRelease NS #21 lcaErrNsRootBus NS #22 lcaErrNsRootDoesNotExist NS #23 lcaErrNsNoFreeRootTransactions NS #30 lcaErrNsEventFailure NS #32 lcaErrNsSubscriptionDblimit NS #34 lcaErrNsSegmentation NS #41 lcaErrNsDbError NS #42 lcaErrNsOutOfJournal NS #46 lcaErrNsNetworkHasInstalledNodes NS #49 lcaErrNsIntegrityError NS #55 lcaErrNsProgramDblimit NS #57 lcaErrNsNvmtDbLimit NS #61 lcaErrNsMsgError NS #62 lcaErrNsCancelError NS #71 lcaErrNsTimerRange NS #83 lcaErrNsObjectLocked NS #84 lcaErrNsInvalidContext NS #85 lcaErrNsServerNotFound NS #109 lcaErrNsStaleFileHandle NS #115 lcaErrNsManagerNotAllowed NS #126 lcaErrNsUnimplementedCategory NS #127 lcaErrNsUnimplementedProperty NS #128 lcaErrNsDisallowedInMipMode NS #129 lcaErrNsDisallowedInTxHandler NS #130 lcaErrNsNssNotInitialized NS #146 lcaErrNsInvalidErrorContext NS #151 lcaErrNsBatchOptionNotImplemented NS #152 lcaErrNsBatchNoResult NS #172 lcaErrNsEngineNotInitialized NS #189 lcaErrNs16BitUserErrorCode NS #190 lcaErrNs16BitWarningCode NS #191 lcaErrNs16BitErrorCode NS #289 lcaErrNsEngineIsSuspended NS #290 lcaErrNsNotSupportedFromRemoteClient NS #4031 lcaErrNsUpdateFuncError NI #24 lcaErrNiObsolete NI #27 lcaErrNiUnimplemented LNS #5 lcaErrUninitializedDb LNS #35 lcaErrGeneric LNS #36 lcaErrDbServer LNS #39 lcaErrWrongWriteDataSize LNS #40 lcaErrInvalidFormat LNS #54 lcaErrCantCopyLNSDirectory LNS #70 lcaErrCantRecoverReadOnlyFile LNS #71 lcaErrStringIsEmpty LNS #73 lcaErrInvalidProgramType LNS #97 lcaErrInvalidRmcObject LNS #98 lcaErrInvalidRmcServer LNS #99 lcaErrInvalidRmcClient LNS #101 lcaErrInvalidRmcMethod LNS #123 lcaErrInvalidPropChangeEvent LNS #133 lcaErrInternalErrBadExceptionCode LNS #134 lcaErrInternalErrBadHresultExceptionCode LNS #135 lcaErrInternalErrBadVNIDataServer LNS #136 lcaErrInternalErrBadNsdHandle LNS #137 lcaErrInternalErrStartTransaction DS #365 lcaErrLnsDsUnexpected DS #366 lcaErrLnsDsFailed Resolution These are internal errors and should be reported to Echelon's customer support. Contact Echelon at 1-800-258-4LON (258-4566) or LonSupport@Echelon.com.

Issue How can I tell what device the alarm is coming from in the b0warlog.log file? The  b0warlog.log or "Warning Log" file does not reference individual devices therefore is difficult to see where the alarm happened. Environment Vista Alarms Cause A lot of  warnings are due to a mismatch in the Vista database and a device on the field. For instance, if you have a Xenta Server alarm that doesn't exist in the Vista database. Resolution You could see if the Xenta/Xenta Server is marked in Vista, look for the asterisk (*), to give you a clue where it came from.   An alternative way to do it is to use testclt program: Start testclt.exe from the root directory of you Vista installation. Login Go to File-Dbg Write alrproc Click Add Choose the Time radio button Click Poke Click Close Wait for the warning to happen in the b0warlog.log Open b0dbglog.logfile in notepad and search for "your error" Just above the line found you should see which alarm object that sent the alarm Example: (Searching for Error:81) Tue Nov 23 13:26:02 2010 :alrproc  >> ProcessAlarmEvent EventId:TGML_test-731-Lon-XG-Xenta401-$NETMON.offline EventType:1 Pri:9 Txt:Xenta group offline Tue Nov 23 13:26:02 2010 :alrproc  >> ValidateDataSpec Id:TGML_test-731-Lon-XG-Xenta401-$NETMON ObjType:EE_MESS Tue Nov 23 13:26:02 2010 :alrproc  >> Processed Error:81  

Issue Error: NS#64 lcaErrNsNotInstalled Environment LNS LonMaker Vista NL220 Cause An operation on a node was requested that requires the node to be configured, but the node is not configured. When you encounter this error, make sure that the device in question has been configured. Resolution Some operation on a device was requested and that operation requires the node to have been installed, but the device has not been added yet. Add the device.

Issue The network subnet limit (currently 255) has been reached. Environment LNS LonMaker Vista NL220 Cause The network subnet limit (currently 255) has been reached. 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.  

Issue An attempt was made to add, commission, move, or replace a device that is on the wrong channel.  A device is considered to be on the wrong channel when a configured, learning, or non-permanent bridge class router exists between the device and the channel on which it is to be place.  When you encounter this error, place the device or router on the correct channel, or define the device or router without a channel and have LNS determine the channel automatically. Environment LNS LonMaker Vista NL220 Cause This usually occurs when the device is defined on the wrong channel.  Resolution Moving the device in the LonMaker drawing to the correct channel will usually clear the error.  Also check to make sure that the Network Interface is on the correct channel.  Sometimes the incorrect channel is just relative to the Network Interface. Look to see if your Network Interface is on the same channel that you are physically connected to.  Move your Network Interface to the correct channel and attempt to commission again If devices have moved recently, it may be necessary to change the routers to Repeater mode.  As a general rule of thumb, it is always best to leave routers in Repeater mode until the conclusion of the commissioning process – just in case some devices need to be moved.  After everything is commissioned and online, then switch the router (or each port of the router) to Configured mode.

Issue An attempt was made to create a connection between nodes on different channels, but no routers were available to complete a logical path between the channels. Environment LNS LonMaker Vista NL220 Cause This error can occur when attempting to remove or move a router which has connections across it, or a router which connects an NSI to either the LNS or another NSI Resolution Lon Maker will not allow the disconnection of a router if the logical path to the device is broken. To combat this you must be creative by adding temporary routers, moving the devices to the new temporary channel, which will create a new path to the devices. the old Routers can then be removed/replaced and the devices can now be returned. Delete any temporary routers/channels.

Issue A value could not be found for the specified configuration parameter. Environment LonMaker NL220 Vista LNS Cause This exception will be thrown if you use the GetDataPoint method to create a data point with the lcaDataSourceOptionsDatabaseOnly (2) option set, and then attempt to read the value of the data point, but the value does not exist in the LNS database. Resolution You need to make sure to add your resources to the resource catalog BEFORE importing the XIF to LNS. Once the XIF is imported, adding the resources later will not make them appear. You will need to delete the device template (LonMaker|DeviceTemplates|Delete).  Run ldrfcat and add the directory with your resources in it (usually in \LonWorks\Types\User\MfgName\...) Refresh the catalog and re-import the XIF.

Issue There is a resource problem in the API or application. Environment LonMaker NL220 Vista LNS ZBuilder Cause This may be a compatibility issue observed when launching ZBuilder from LonMaker.  Resolution Zbuilder may work many times after LonMaker is started, but eventually produce this error.  Once the error was produced, it would reoccur every successive attempt.  To launch Zbuilder successfully, LonMaker had to be restarted.  When checking versions, it was discovered that there was ZBuilder 5.0.3 installed and ZBuilder part of the 5.1.0 ToolPack installed.

Issue Host resource allocation problem. Subsystem NS,  #123 lcaErrNsHostResourceProblem.  There is a resource problem in the API or application. Environment LonMaker NL220 LNS Cause NS #123 is a generic LNS resource allocation error (could be memory). This error has been encountered while attempting to re-bind a few SNVTs that had been lost.  When attempting to re-bind, the following error message appeared: 'NS #123: Host resource allocation problem.'    This error has been encountered while attempting to service pin a replaced Xenta programmable.  After a failed download, the service pin resulted in the following error message: 'NS #123: Host resource allocation problem.'    Resolution If there is another LNS application (e.g. LNS DDE Server) running in the background, you may want to shut down other LNS applications and try again.  In some cases, restoring a backup resolved the issue.

Issue This error will be generated if you attempt to load a new application image into a device with the Load method, and the system image (firmware version) used by the device is incompatible with the new application image.  Some devices support the LoadEx method, which will upgrade the system image to a compatible version when this error occurs.  Environment LonMaker NL220 Vista LNS Cause The device contains an incompatible firmware version. You have a mismatch between the old firmware and new firmware. The old firmware was built (linked) to an older version of the system firmware (Echelon's OS) that's either in the Neuron chip (3120 type) or external flash (3150 type). Resolution The solution is to either: Rebuild your application image (the one you're trying to download) and select the older system image version in the project properties. Update the system (and application) image by reprogramming the flash. That's only possible for a 3150 based product.   Xenta 102-AX upgrade to 2.1.6 caused this error and didn’t allow the new firmware to download.  This particular Xenta 102-AX had previously been loaded incorrectly and rendered applicationless.  This is why it is very important to always know what you are doing prior to loading a new firmware.

Issue Returned when an attempt is made to set the MgmtMode property to lcaMgmtModePropagateConfigUpdates (0) without selecting a network interface. Environment LonMaker NL220 Vista LNS Cause After restoring an NL220 backup file and opening the project using the "Default" network interface, you may receive NS #135. Trying to re-open the network and manually chose the correct network interface, instead of "Default", the same the same error occurs.  Resolution Open the smart channel window and then click on the IP channel, Attached, and Test All.  This resolves the offline network interface. In the NL main window, chose Tools, Attached to Network, and the network status should return to ONNET.   If the Attached and Test All buttons are grayed out then try rebooting the server and connecting the NL220 database again. This may be due to all NIC ports being locked out by another program like Vista.

Issue LNS license access failure.  Environment Cause 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 identify the license, nsseng.exe for the LNS Server for example.  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. Resolution Open a DOS command prompt window (Start > Run > cmd) Type "checklic nsseng.exe" and press Enter Take a screenshot Open LNS License Wizard (Start > Programs > Echelon LNS Utilities > LNS Server License Wizard) Take a screenshot Send Echelon both screenshots in order to define the problem and determine how to advise you to fix it.

Issue LNS license time limit has expired. Environment LonMaker NL220 Vista LNS Cause This error will occur if you are using a trial license and the number of days allocated to the license has expired, or if you are using a trial license and set the PC clock back. Resolution For more information on licensing, see Chapter 13 of the LNS Programmers Guide. All the LNS deficit credits have been used. You have to recredit LNS.

Issue Error: Subsystem NS, #149 lcaErrNsConflictWithCurrentNetwork This error will be generated if you open a network that is already opened using a different network interface, LNS type, or database directory. Environment LonMaker NL220 Vista LNS Cause After restoring a LonMaker database, or upgrading a LonMaker system, each LNS database has to be opened before the Vista server is started or you get this error. Same as with LonMaker, if you start the NL220 stand alone, and then start Vista, the LNS server will not be conflicted.  If switching between LonWorks Interface types (example:  RNI to PCLTA) you may receive this error when trying to open the LonMaker drawing.   Cannot run LNS Database Validation Tool with the database open (Start > Programs > Echelon LNS Utilities > LNS Database Validation Tool 3.2). Resolution Shut down the Vista Server. If Vista Server is set to run as a service (Control Panel > Administrative Tools > Services > TACOS) manually stop the service. Open each LNS database network attached and onnet.  Restart the server. If this error occurred from switching LonWorks Interface types, rebooting the PC should clear the error.

Issue Monitor point cannot be found. Environment Echelon LonMaker NL220 Vista LNS Cause When trying to resynchronize, you may get this error. Resolution  A monitor point is a member of a monitor set.  They are created when you right click on a SNVT in the LonMaker drawing and choose “Monitor.”  If a monitor point can no longer be found, then it can be cleaned out of the monitor set to eliminate this error. Navigate to LonMaker > Network Service Devices.  Click on the NSD Name for your network, which highlights the Monitor Sets button.  Click it. Expand the view to find Echelon LonMaker Monitor Sets.  These are the monitor points created manually by monitoring a point in the drawing.  They are optional and unnecessary.  Right click on Echelon LonMaker Monitor Sets and select Delete. Select "Done".  Select "Done".  LonMaker > Resynchronize.  Try it again.  This time check Sync drawing to database (fix-up drawing).  Also, check Sync monitor sets between drawing and database. It should resynchronize successfully now.  In the future instead of right clicking on a SNVT binding and selecting monitor value, use get value.  This will momentarily show you the LON value without creating monitor sets, which can later cause this error.

Issue No routers exist to complete logical path needed for monitoring and control. Environment LonMaker NL220 Vista LNS Cause When initially creating a multi-port router, the internal L-IP FT-1250 channel was designated as an existing FT-10 channel.  The drawing was built and then couldn’t be commissioned due to the physical topology not matching the drawing. Resolution With no logical path for the controllers and you attempt to move them to another channel, you must first  correctly define the router in the Visio drawing.

Issue Neuron model version mismatch.  Environment LonMaker NL220 Vista LNS Cause This error will be generated if you attempt to use the Load method to load an application image into a device that is incompatible with the devices system image.  Resolution In this case, you need to upgrade the devices system image.  Some devices support the LoadEx method, which automatically upgrades the system image before loading the application image if there are compatibility problems.

Issue New system image cannot be written Environment LonMaker NL220 Vista LNS Cause This error will be generated if you invoke the LoadEx method on a device, but the system image cannot be written, probably because it is not stored in flash memory.  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.