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 Migrating from LonMaker to NL220 Environment LonMaker NL220 Cause Changing LNS management tools. Resolution If both Lon Maker and NL220 reside on the PC: Migrating from LonMaker (or other LNS management tool) to NL220, all that is required is the LNS database.  NL220 will recognize the LNS Databases which have already been created in LonMaker. Open the database in NL220. There is no need to recommission online devices, so no credits need to be re-purchased.   If the LNS must be transferred onto a PC that only has NL220 installed: Take a copy of the Folder located in the directory Lm/Db/[name of project]/files Place this folder in C:\NLPrj\[name of project]\files Create a new Project in NL220 Name the project Select 'open an existing database' Browse to the Project path (C:\NLPrj\ ) Select OK. NOTE: Migrating from NL220 (or other LNS management tool) back to LonMaker is a little less seamless because LonMaker utilizes proprietary Visio drawings for viewing the network, and these are not native to the LNS database.  Viewing the network may be difficult with the automatically generated Visio drawings.

Issue Changes to public variables (PVR, PVI, PVB) in a Menta file on a live system are accepted by the database, but it seems that the actual controller is ignoring these changes, or not seeing them. Environment Vista Workstation More commonly a Vista Classic Network, though it does apply to LNS Cause In the upper left-hand corner of the Workstation, there is a drop-down menu to select either Engineering or Operating mode.  Engineering mode is used most often in a Vista Classic Network while adding or configuring new controllers.  While in engineering mode, changes can be made to database values, but these changes will not be propagated down into the controllers. Resolution Change back to Operating mode.

Issue Under user admin in a Xenta server you can change the content of the 3 frames that the user sees when logging in. If the user have changed the default frames for the root user in a Xenta server so that the tree navigation is not available you can't navigate back to user admin to reset the frames. Environment TAC Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause User have changed the frames so that the menu tree is no longer available Resolution Log on to the Xenta server with the root account. Type in https://xx.xx.xx.xx/wm/useradmin/ in the IE address field. This takes you directly to the useradmin page. Click on the root user. Under Frame Settings click on Use Default for the Menu frame.

Issue Error message: Insufficient object database authority to start the TAC Vista Server, when starting the TAC Vista Server. Environment Windows 7, Vista Server Cause TAC Vista Server thought the log in user does not have the full rights to view the TAC Vista Database. Resolution Before doing anything, please make sure you are logged in as an administrator.  Close Vista Server, then follow the steps below Go to TAC Vista Server Setup (Start/All Programs/Schneider Electric/TAC Vista Sever 5.1.X/Server Setup). Select "Authority" tab and click on the "Grant Access" button. You should get a success message. Start the Server again, you should not get the error message again. If it still doesn't work do the following:  Right click on the database folder. Unmark the "read only" check box. Click apply. Select  "Change this folder, subfolders and files".  

Issue After transferring an LNS database from NL220 or LonMaker into TAC Vista Workstation, all controllers are green (online) in Workstation. However, clicking on some programmable controllers results in an error message that states: "The blueprint is corrupted." Environment TAC Vista Workstation Xenta programmable controllers Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause The TAC Xenta group name was too long or contained spaces. (More than 20 characters)   Resolution Change the Xenta Group name to be less than 20 characters without any spaces.

Issue The xDriver profile selected does not exist, or the xDriver connection broker is not currently running. Environment LNS NL220 LonMaker Vista Cause Make sure that the profile you are using exists, and that the xDriver connection broker service has been started if you encounter this error. Resolution For more information on the xDriver connection broker, see the OpenLDV Programmer’s Guide, xDriver Supplement. http://downloads.echelon.com/support/documentation/manuals/devtools/078-0275-01C.pdf

Issue You attempted to create an object with a name that is already being used by an object of that type. Environment LNS NL220 LonMaker Vista Cause For example, the name assigned to all LonMarkObject objects must be unique. Therefore, if you use the Add method to create a LonMarkObject and specify a name that is already being used by another LonMarkObject, this exception will be thrown Resolution Name LonMarkObject as something unique.

Issue Could not initialize the LonTalk stack. Environment LNS NL220 LonMaker Vista Cause Could not initialize the LonTalk stack. Resolution First, close the LonMaker tool, then test your network interface using the LonWorks Plug 'n Play utility found in the Windows Control Panel. Once there, press the "Diagnostics" button and then press the "Test" button. If you get a "Failed" message similar to the following: ------------------------------------------------------------------------------ LonWorks® PCC10/PCLTA10/PCLTA20 Device Driver Version: 2.01 Card Type: PCLTA-20 / LMPA Driver Status:           Number of Free LTA Output Buffers-            Non-Priority: 0, Priority: 0           Loaded Image Size: 16384           Interrupt Count: 17333 ------ Network Interface Node Status ------ ** Failed ** ------------------------------------------------------------------------------ Then go back to the main LonWorks Plug 'n Play dialog and change your NI Application to something other than what is currently selected. Click on the "apply" button and do the test again. Don't forget to change it back to its original NI Application. Remember that the LonMaker tool can work with either the "NSI" or "VNI" NI Application images, although "VNI" is preferred due to higher performance. You may also want to try to "reset" and "restart" your network interface card and driver from the "Diagnostics" window. Once you stop getting the "Failed" message and see the network interface statistics, you should be able to open the network from the LonMaker tool. The following is an example of a successful "Test" result. Some of the counts may not be zero, but that should not be a problem unless it increases rapidly as you test again and again. If that happens, it can be due (most of the time) to one of three problems: wiring connections, excessive noise, or excessive traffic on the network. ------------------------------------------------------------------------------ LonWorks® PCC10/PCLTA10/PCLTA20 Device Driver Version: 2.01 Card Type: PCLTA-20 / LMPA Driver Status:           Loaded Image Size: 57344           Interrupt Count: 20345 ------ Network Interface Node Status ------ CRC Errors:                  [00000] TX Timeouts:                 [00000] Lost (APP) Messages:         [00000] Missed (NET) Messages:       [00000] Most recent error:           0 Reset Cause:                 External ------------------------------------------------------------------------------  

Issue The LonMaker tool has the incorrect NSI or "VNI" NI application images Environment LNS NL220 LonMaker Vista Cause The LonMaker tool only works with NSI or "VNI" NI application images, i.e., PCL10VNI or NSIPCLTA. Resolution Unable to change the state of the network interface. i.LON 100 or SmartServer: There are two types of RNIs, "Other" and "LonScanner". For LonMaker (or a LNS application), you must use the "Other" RNI. For LonScanner, you must use the "LonScanner" RNI. Check the interface setting in the LonWorks Interface Applet which is available in the Windows Control Panel. Select the RNI tab and double click the RNI you are using. If the interface setting is set incorrectly, change it to the correct one and press the Apply button. PCC-10 or PCLTAs: The LonMaker tool works with NSI or "VNI" NI application images, i.e., PCL10VNI or NSIPCLTA. To eliminate this error message, open the LonWorks Plug 'n Play utility from the Control Panel and check your NI Application. If it is "PCC10L7", it needs to be changed to PCL10VNI or NSIPCLTA. Hit Apply to change the image, then go ahead and open the network again.

Issue The network interface has already been opened with a different network driver.  Environment LNS LonMaker Vista Cause This error will be generated if you open a network that is already opened using a different network interface, LNS type, or database directory. Resolution Access the network properly.

Issue The Data Server failed to initialize properly. Environment LNS NL220 Vista Cause This exception could be thrown if your application specifies an invalid name or index number when retrieving an object from the LNS database. This error can occur when trying to monitor a variable with the DataServer of LNS 3.08.  Resolution It is a corrupted database error. The best thing to do is to come back to a previous backup of your database

Issue How to create a LNS database in NL220 and then bring it to Vista Workstation online Product Line TAC Vista Environment NL220 Cause In order to have a healthy LNS database, it is very important to create this database with proper steps in NL220. Resolution Preparation: Configure the Infrastructure Device Set up Vista Database path   Creating LNS Db in NL220 NL220: Add infrastructure device, nodes, etc. System plug-in: Assign Neuron ID (Optional), Menta file Back to NL220: SNVT binding   Bring LNS Db to Vista Db System plug-in: Network settings, Update TAC Network, create group bindings, add I/O modules, update the TAC Network again, check TAC Network, Update Vista Database   Bring Vista Db online NL220: Commission the Infrastructure Device System plug-in: Verify network settings, assign Neuron ID if needed, update TAC network and Vista database, download application and parameters Back to NL220: Commission and downloading all nodes besides I/O modules. Back to system plug-in: Change infrastructure setting, commence communication