Lon - NS Error Codes

NS Error Codes

Network Service Errors

A network services error occurs when the LNS Server is unable to successfully complete a

service. These errors will appear in the format NS: #<Error Number>.

 

lcaErrNsCancel NS, #1

The service and the associated transaction were cancelled. This error occurs when an internal

error occurs, such as the LNS engine restarting.

 

lcaErrNsNodeHasNoAppl NS, #5

The device was discovered to be applicationless, or not associated with a program. If you

encounter this error, load the application into the device. For host-based nodes, ensure that the

host application is running.

 

lcaErrNsBadManagerId NS, #6

The current manager ID does not correspond to a known manager. This is an internal error and

should be reported to customer support.

 

lcaErrNsResourceProblem NS, #7

A problem occurred in resource allocation. This is an internal error and should be reported to

customer support.

See KB528.

 

lcaErrNsInterfaceFailure NS, #8

The host was unable to communicate with the NSI. This may be due to problems communicating

with the LNS engine, or with the network interface. If you encounter this error, ensure that the

LNS engine process is running, and that the network interface is functioning properly.

See KB469.

 

lcaErrNsBadClient NS, #9

The specified server (or the current server) is undefined. This is an internal error and should be

reported to customer support.

 

lcaErrNsBadServer NS, #10

The specified server (or the current server) is undefined.

 

lcaErrNsNoClient NS, #11

No client is currently defined. This is an internal error and should be reported to customer

support.

 

lcaErrNsNoTxInProgress NS, #12

There is no transaction defined for the client. This warning can be expected when cancelling a

method that is not part of an explicit transaction.

 

lcaErrNsLNSNotFound NS, #13

The NSI has not been configured to communicate with the LNS. This error may occur when

opening the database with the remote database collection if the clients NSD is not properly

configured. To reconfigure the client’s NSD, open the database remotely using the Networks

collection.

 

lcaErrNsClientBlocked NS, #14

The client is already involved in a service request. You should invoke only one service per client.

This includes all requests to start or commit transactions. When a client has already launched a

service, wait until the current service completes before you invoke a new service. This is an

internal error and should be reported to customer support.

 

lcaErrNsTxInProgress NS, #15

The client is already involved in a transaction. End the client's current transaction by calling

CancelTransaction method, or wait for the transaction to complete and call the

CommitTransaction method, before starting a new transaction for that client.

You should avoid starting multiple transactions on a single network database within a single

application.

 

lcaErrNsNotImplemented NS, #16

The specified service or option is not implemented by the specified server. This error could

indicate a bad service parameter. This is an internal error and should be reported to customer

support.

 

lcaErrNsErrorInfo NS, #17

The service failed. When you encounter this error, a service-specific error status is available in

the LastError property of the System object.

 

lcaErrLNServiceFailure NS, #18

The requested service failed. This is an internal error, and should be reported to customer

support.

 

lcaErrNsMsgRejectedByNode NS, #19

A node returned a negative response to a command from LNS. This could be due to a LonTalk

authentication failure. It may also result from an inconsistency between the program interface

defined in the database and what the node actually supports.

See KB576.

 

lcaErrNsPrematureRelease NS, #20

This is an internal error and should be reported to customer support.

 

lcaErrNsRootBusy NS, #21

A transaction is still in progress. This is an internal error and should be reported to customer

support.

 

lcaErrNsRootDoesNotExist NS, #22

The service depends on a transaction that does not exist. This is an internal error and should be

reported to customer support.

 

lcaErrNsNoFreeRootTransactions NS, #23

This is an internal error and should be reported to customer support.

 

lcaErrNsCantFindObject NS, #24

One of the objects needed to complete the service is not in the database of the LNS.

 

lcaErrNsDuplicateObject NS, #25

An attempt was made to add an object that already exists.

 

lcaErrNsCommError NS, #26

The LNS cannot communicate with the node. This may be because the Neuron ID referenced by

the application is invalid or does not exist, the LNS or the node is not physically attached to the

media, the LNS is not configured (because the MgmtMode property was not set to

lcaMgmtModePropagateConfigUpdates after the database was initially created), problems

with the physical media, or the LNS timers (set using the RetryCount and TxTimer properties of

the System object) are too low.

See KB 149.

 

lcaErrNsOperationError NS, #27

The node failed to go online, offline or to reset when requested to do so. This may be due to a

problem in the implementation of the device.

 

lcaErrNsUnsupportedInfo NS, #28

The requested information is not available from an application node. For example, transceiver

status, SI/SD data, and network variable names are not always stored in the node.

LonMaker Turbo SP1 has some fixes

 

lcaErrNsOutOfRange NS, #29

The value assigned to a property or parameter is either out of range, or invalid.

 

lcaErrNsEventFailure NS, #30

The generation of an event failed. This is an internal error and should be reported to customer

support.

 

lcaErrNsDeferConfigUpdatesMgmntMode NS, #31

The requested service cannot be provided in the current management mode. When you

encounter this error, set the system management mode tolcaMgmtModePropagateConfigUpdates (0), and try the operation again. You can changethe system management mode by writing to the MgmtMode property of the System object.

 

lcaErrLNSubscriptionDblimit NS, #32

The LNS's event subscription table is full. This is an internal error, and should be reported to

customer support.

 

lcaErrLNSequence NS, #33

A record from a binary external interface file or binary application image file was received out of

sequence. If you encounter the error, the XFB or APB file may be corrupted.

 

lcaErrLNSegmentation NS, #34

Segmentation is not supported, or there is a problem with segment order. This is an internal

error, and should be reported to customer support.

 

lcaErrNsChecksum NS, #35

A checksum error occurred while transferring the binary external interface or binary application

image file to the LNS. If you encounter the error, the XFB or APB file may be corrupted.

 

lcaErrLNSessionError NS, #36

Invalid session handle or a session error. Make sure that sessions are begun and ended in pairs,

and are always part of an explicit transaction.

See KB 149.

 

lcaErrNsNoNeuronId NS, #37

An operation requiring a Neuron ID was attempted on a device with no Neuron ID. 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.

 

lcaErrNsProgramidMismatch NS, #38

Program IDs do not match. This may occur if there is an incorrect or out-of-date program

version.

 

lcaErrNsObjectInUse NS, #39

A requested operation can't complete because the object involved in the operation is in use. For

example, you may not be able to delete a node because that node is still included in

connections.

 

lcaErrNsNodeHasNoSiData NS, #40

The node has no SI (self-information) data, when required.

 

lcaErrNsDbError NS, #41

An internal database error occurred. This is an internal error, and should be reported to

customer support.

See KB469.

 

lcaErrNsOutOfJournal NS, #42

No more memory is available for journaling. This is an internal error, and should be reported to

customer support.

 

lcaErrNsOutOfMemory NS, #43

No more memory is available for allocation.

 

lcaErrNsBadParms NS, #44

Invalid parameter values.

See KB636.

 

lcaErrNsNetworkHasInstalledNodes NS, #46

Attempt to add the LNS failed because application nodes have already been defined or added.

You must install the LNS before the other nodes. This is an internal error, and should be

reported to customer support.

 

lcaErrNsDbImportExport NS, #47

Requested operation can't proceed because a database import or export is currently in progress.

 

lcaErrNsProgramNotFound NS, #48

Could not find the program definition required to execute the service.

 

lcaErrNsIntegrityError NS, #49

Internal integrity error. This is an internal error, and should be reported to customer support.

 

lcaErrNsDblimit NS, #50

An unspecified database limit was exceeded.

See KB190.

 

lcaErrNsNodeNotFound NS, #51

Cannot find the node.

 

lcaErrNsDuplicateNode NS, #52

An attempt was made to add a node that is already defined.

 

lcaErrNsNodeDbLimit NS, #53

The node limit has been exceeded.

 

lcaErrNsDuplicateProgram NS, #54

The program template is already defined.

 

lcaErrNsProgramDblimit NS, #55

This is an internal error, and should be reported to customer support.

 

lcaErrNsNvmtNotFound NS, #56

The network variable or message tag cannot be found.

 

lcaErrNsNvmtDbLimit NS, #57

This is an internal error, and should be reported to customer support.

 

lcaErrNsChannelNotFound NS, #58

The channel cannot be found.

 

lcaErrNsProgramIntfMismatch NS, #59

The new program interface does not match the previously defined program interface; i.e., the

number of network variables, message tags, or the structure of self identification data is

inconsistent even though the program IDs match. This error may also be thrown if the

SelfDocConsistency property of a DeviceTemplate object is set to a value that conflicts with the

configurations of the devices using that template.

Check if you are using the correct XIF file for the device. You can do one of the following:

1. Delete the device and the device template, and re-add/commission the device again using the

correct XIF file. 2. Delete the device and the device template, and re-add/commission the device

again using "Upload from Device" for external interface.

 

lcaErrNsProgramIntfUnsupported NS, #60

The program interface does not support the requested action.

 

lcaErrNsMsgError NS, #61

There was a failure in the messaging sub-system. This is an internal error, and should be

reported to customer support.

 

lcaErrNsCancelError NS, #62

An error occurred while canceling a transaction or service. This is an internal error, and should

be reported to customer support.

 

lcaErrNsNothingToCancel NS, #63

There was no service or transaction to cancel

 

lcaErrNsNodeNotInstalled NS, #64

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.

 

lcaErrNsAuthViolation NS, #65

Authentication rules were violated.

 

lcaErrNsChannelDblimit NS, #66

The network channel limit (currently 1000) has been reached.

 

lcaErrLNSubnetDblimit NS, #67

The network subnet limit (currently 255) has been reached.

See KB190.

 

lcaErrLNSubnetNotFound NS, #68

The specified subnet ID was not found. Subnet IDs must be created automatically by the LNS

or defined manually using the Add method of the Subnets collection object.

 

lcaErrNsRouterDblimit NS, #69

The network router limit (currently 32766) has been reached.

 

lcaErrNsRouterNotFound NS, #70

The specified router handle does not exist.

 

lcaErrNsTimerRange NS, #71

The timer value computed for a connection or for the LNS Object Server to communicate with a

node exceeds the range supported by LONWORKS devices. This is an internal error, and should

be reported to customer support.

 

lcaErrNsWrongChannel NS, #72

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 placed. 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

 

lcaErrNsInsufficientRouters NS, #73

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. 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

 

lcaErrNsNoSessionInProgress NS, #74

The EndSession method of the System object was called before a corresponding BeginSession

was called. Make sure that a session is open before you call EndSession.

 

lcaErrNsTopologyPhysicalLoop NS, #75

The attempted router operation would have created a loop in the physical network topology.

 

lcaErrNsTopologyLogicalLoop NS, #76

The attempted router operation would have created a loop in the logical network topology.

Normally, loops are initially detected as physical loops. However, it is possible to add a

permanent repeater or bridge, so that a logical loop exists even though a physical loop does not.

 

lcaErrNsTopologySubnetViolation NS, #77

An attempt was made to define a device with a subnet that is incompatible with the devices

channel, due to router constraints. To resolve this error, either leave the subnet undefined (so

LNS will define it) when you define the device, or make sure that the selected subnet is not in

use on other logical channels.

 

lcaErrNsRouterMustBePermanent NS, #78

An attempt was made to illegally add a non-permanent router, or to change the class of a

permanent router to non-permanent. Once a permanent router has been added to the

topology, it cannot be changed to a non-permanent router, even by removing and then readding

it.

 

lcaErrNsCantDetermineChannel NS, #79

An attempt was made to register or add a device without a specified channel handle, and the

system was not able to automatically determine the channel on which the device resides. This

error will occur if the channel the device resides on is connected to any other channel by

repeaters or permanent bridges. Also, this error will occur if the channel is not currently

configured in the system.

 

lcaErrNsRedundantRoutersMustBeConfigured NS, #80

An attempt was made to add a redundant router that was not of the configured class, to change

the class of a redundant router to the non-configured class, or to add a redundant router to an

existing non-redundant, non-configured class router.

 

lcaErrNsCantDetermineXcvrId NS, #81

A channel was defined with a wildcard transceiver ID, but the transceiver ID could not be

automatically determined by the system.

 

lcaErrNsRouterCantBePermanent NS, #82

An attempt was made to change a non-permanent router to a permanent router by writing to

the ClassId property of the Router object. A router can be changed in this way only by being

moved.

 

lcaErrNsObjectLocked NS, #83

An attempt was made to change a locked object. This is an internal error, and should be

reported to customer support.

 

lcaErrNsInvalidContext NS, #84

An attempt was made to invoke a service from an event handler that was called directly from a

background task. This is an internal error, and should be reported to customer support.

 

lcaErrLNServerNotFound NS, #85

The specified server could not be found. The server ID may be invalid. This is an internal error,

and should be reported to customer support.

 

lcaErrNsNodeStateError NS, #86

The node was in the wrong state for the attempted operation. To resolve this error, try setting

the State property of the node’s AppDevice object to lcaStateCnfgOnline.

 

lcaErrNsLmobjNotFound NS, #87

The specified LonMark object could not be found.

 

lcaErrNsLmobjDbLimit NS, #88

The LonMark object limit has been exceeded.

 

lcaErrNsInvalidSidata NS, #89

The self-documentation information was invalid (e.g., improper LonMark definitions).

 

lcaErrLNServiceCommError NS, #90

A communications error occurred between the client and the server.

 

lcaErrNsRequestNotAllowed NS, #91

The requested service has been disabled. This error is usually the result of a remote full client

performing an operation that has been disabled by the server.

 

lcaErrNsCpNotFound NS, #92

The specified configuration property does not exist.

 

lcaErrNsCpDbLimit NS, #93

The configuration property database limit has been exceeded.

 

lcaErrNsCpRangeNotFound NS, #94

The specified configuration property range does not exist.

 

lcaErrNsCpRangeDblimit NS, #95

The configuration property range database limit has been exceeded.

 

lcaErrNsConnectionError NS, #96

Connection rebinding failed for a set of moved nodes. Possible causes are: no more address

table slots, no more groups, or broadcast violation.

 

lcaErrNsFileLookupError NS, #97

An error occurred during a file operation, probably due to an out of range file index.

 

lcaErrNsFileIoError NS, #98

The file operation target failed to read/write a file.

 

lcaErrNsFileTimeoutError NS, #99

The target timed out during a file transfer operation.

 

lcaErrNsFileWindowError NS, #100

The target received a packet out of order during a file transfer operation.

 

lcaErrNsFileAuthError NS, #101

File transfer failed due to incorrect authentication.

 

lcaErrNsFileAccessUnavail NS, #102

Random file access is not implemented on the target.

 

lcaErrNsFileOpenFailure NS, #103

The target failed an open file operation.

 

lcaErrNsFileSeekInvalid NS, #104

The target failed a file seek operation.

 

lcaErrNsCantModifyConstCp NS, #105

An attempt was made to modify a constant configuration property.

 

lcaErrNsCpDefaultsNotFound NS, #106

Default configuration parameters have not been uploaded to the database. To correct this, you

should set default values from the current values in the device using the UploadConfigProperties

method of the AppDevice object. Use the lcaConfigPropOptSetDefaults and

 

lcaConfigPropOptLoadUnknown upload options when you call the method. To avoid this error in

other databases, import a program template with a XIF containing CP default values.

 

lcaErrNsCantFindConnection NS, #107

The requested connection was not found.

 

lcaErrNsLmobjMemNotFound NS, #108

The requested LonMark object member was not found. You will encounter this error if you try to

use the UnassignNetworkVariable method to remove a network variable from a LonMarkObject,

but the network variable was not previously assigned to the LonMarkObject. You can use the

AssignNetworkVariable method to assign a network variable to a LonMarkObject.

 

lcaErrLNStaleFileHandle NS, #109

An attempt was made to use a stale file transfer handle. This is an internal error, and should be

reported to customer support.

 

lcaErrNsFileLimitReached NS, #110

The file transfer handle limit has been reached.

 

lcaErrNsFileContention NS, #111

A file could not be accessed due to contention with the initiator. You can avoid this error by not

performing file transfers with devices that are already engaged in file transfers with other

devices.

 

lcaErrNsAccessExpired NS, #112

The LNS demonstration software has expired. A new copy must be obtained.

 

lcaErrNsCpValueNotFound NS, #113

A value could not be found for the specified configuration parameter. 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.

 

lcaErrNsNodeReset NS, #114

An operation failure occurred due to an unexpected node reset.

 

lcaErrNsManagerNotAllowed NS, #115

The specified services are not allowed by the manager. This is an internal error, and should be

reported to customer support.

 

lcaErrNsUnsupportedService NS, #116

Service attempted to reboot a node that is not a 3150.

 

lcaErrNsLabelNotFound NS, #117

The requested label could not be found.

 

lcaErrNsDuplicateLabel NS, #118

An object with this label already exists.

 

lcaErrNsNoRecoveryInProgress NS, #119

There is no database recovery in progress for the recovery status service.

 

lcaErrNsCantModifyProgramIntf NS, #120

The service attempted to modify a read-only program interface.

 

lcaErrNsCantModifyNvType NS, #121

The service attempted to modify a read-only network variable type.

 

lcaErrNsNvNotLmobjMember NS, #122

The network variable is not a member of a LonMark object.

 

lcaErrNsHostResourceProblem NS, #123

There is a resource problem in the API or application.

 

lcaErrNsTxAlreadyCanceled NS, #124

The specified transaction was already canceled.

 

lcaErrNsFirmwareVersionMismatch NS, #125

The device contains an incompatible firmware version. 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.

 

lcaErrNsUnimplementedCategory NS, #126

The service encountered an unimplemented category or category operation. This is an internal

error, and should be reported to customer support.

 

lcaErrNsUnimplementedProperty NS, #127

The service encountered an unimplemented property or property operation. This is an internal

error, and should be reported to customer support.

 

lcaErrNsDisallowedInMipMode NS, #128

The specified service or operation is disallowed because the interface is not an NSI. This is an

internal error, and should be reported to customer support.

 

lcaErrNsDisallowedInTxHandler NS, #129

The specified service or operation is disallowed in the transaction notification handler. This is an

internal error, and should be reported to customer support.

 

lcaErrNsLNSNotInitialized NS, #130

The NsInit() function either was not called or failed. This is an internal error, and should be

reported to customer support.

 

lcaErrNsLNSEngineNotFound NS, #131

The LNS Win32 engine was not found. If you encounter this error, you should verify that LNS is

installed properly on your machine.

 

lcaErrNsInvalidNsi NS, #132

The network interface is not a valid NSI mip.

 

lcaErrNsFileHeaderError NS, #133

The file which was accessed had an invalid header

 

lcaErrNsDbVersionError NS, #134

Returned when the LNS encounters a database (or non-volatile data) with the wrong version

number.

 

lcaErrNsNoNetworkInterface NS, #135

Returned when an attempt is made set the MgmtMode property to

 

lcaMgmtModePropagateConfigUpdates (0) without selecting a network interface.

 

lcaErrNsNsiInuse NS, #136

Returned when an attempt is made to remove an NSI that is being used by other processes.

 

lcaErrNsDialingFailure NS, #137

Failed to call host. Probably due to busy, no answer, or recent failure.

 

lcaErrNsNetworkInterfaceState NS, #138

Local network interface is in the wrong state (e.g. unconfigured). 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.

See KB190.

 

lcaErrNsNetworkInterfaceConfig NS, #139

Local interface is not properly configured or updated. When you encounter this error, set the

MgmtMode property of the System object to lcaMgmtModePropagateConfigUpdates (0).

and recommission the network interface, if necessary.

 

lcaErrNsNetworkInterfaceInUse NS, #140

Network interface is currently in use.

 

lcaErrNsInvalidNeuronId NS, #141

The specified neuron ID is illegal. This error is reported if a Neuron ID containing zeroes in the

middle 4 bytes is specified. Neuron Chips that use this format are defective and should be

returned.

 

lcaErrNsDialupDataUninitialized NS, #142

Device not configured to dialup to host upon LNS communication.

 

lcaErrNsCannotStartAppl NS, #143

Dialup NSI was unable to start host application or LNS after connection.

 

lcaErrNsCapacityLimit NS, #144

License capacity or credit limit reached. This error will occur when all the credits in the license,

including deficit credits, have been used. For more information on licensing, see Chapter 13 of

the LNS Programmer’s Guide.

 

lcaErrNsCpNvLengthUnknown NS, #145

Length of configuration NV implementing a CP is unknown.

 

lcaErrNsInvalidErrorContext NS, #146

An update error had been reported prior to updating the nodes. This is an internal error and

should be reported to customer support.

 

lcaErrNsLicenseViolation NS, #147

LNS license access failure. 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 (LNSeng.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

PC’s 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 Programmer’s Guide.

For solution see KB540.

 

lcaErrNsLicenseExpired NS, #148

LNS license time limit has expired. This error will occur if you are using a trial license and the

number of days allocated to the license have expired, or if you are using a trial license and set

the PC clock back.

For more information on licensing, see Chapter 13 of the LNS Programmer’s Guide.

 

lcaErrNsConflictWithCurrentNetwork NS, #149

This error will be generated if you open a network that is already opened using a different

network interface, LNS type, or database directory.

 

lcaErrNsConflictWithAnotherNetwork NS, #150

This error will be generated if you open a network that specifies the same database directory as

another currently opened network.

 

lcaErrNsBatchOptionNotImplemented NS, #151

The batch service option combination specified is not implemented. This is an internal error,

and should be reported to customer support.

 

lcaErrNsBatchNoResult NS, #152

Access to specified batch result is not possible, since it does not exist. This is an internal error,

and should be reported to customer support.

 

lcaErrNsLicenseFeatureDisabled NS, #153

Feature has not been enabled in the license.

 

lcaErrNsDemoLicenseDisallowed NS, #154

Full license already exists. Demo license not allowed.

 

lcaErrNsVnodeIndexMismatch NS, #155

Virtual node index mismatch

 

lcaErrNsNiVniOpenFailure NS, #156

Unable to open NI layer or VNI

 

lcaErrNsVniMsgError NS, #157

VNI messaging error

 

lcaErrNsMaxDbOpened NS, #158

Exceeded the maximum number of databases

 

lcaErrNsEventsNotInitialized NS, #159

Event sub-system not initialized.

 

lcaErrNsMcsNotFound NS, #160

Monitor set cannot be found.

 

lcaErrNsMcsDblimit NS, #161

Max number of monitor points exceeded.

 

lcaErrNsMcpNotFound NS, #162

Monitor point cannot be found.

 

lcaErrNsMcpDblimit NS, #163

Max number of monitor points exceeded.

 

lcaErrNsNvmtInUse NS, #164

The network variable or monitor point is in use and cannot be used for current service.

 

lcaErrNsDbConversionInProgress NS, #165

The engine is in the process of converting a database. Internal

 

lcaErrNsIllegalMcpTarget NS, #166

Monitoring of specified target is not allowed.

 

lcaErrNsCantModifyNvName NS, #167

Can't modify network variable name.

 

lcaErrNsDbconvAccessFailure NS, #168

Unable to read/write old or new record during conversion

 

lcaErrNsUpgradeDisable NS, #169

Program interface upgrade has been disabled.

 

lcaErrNsUpgradeInfoNotFound NS, #170

No upgrade change info available for node.

 

lcaErrNsLNSUpgradeRequired NS, #171

LNS program ID changed. Requires upgrade or revert back to old interface.

 

lcaErrNsEngineNotInitialized NS, #172

LNS/NSI engine initialization has not completed. This is an internal error, and should be

reported to customer support.

 

lcaErrNsNiNoWinsockDll NS, #173

LNS attempted to use IP without the winsock.dll file installed.

 

lcaErrNsNiCantOpenIpLink NS, #174

An LNS network interface failed to open an IP connection.

 

lcaErrNsNiInvalidIpAddress NS, #175

An LNS network interface uses an IP address not defined on this PC.

 

lcaErrNsNsiNotConfigured NS, #176

NSI needs to be added or re-commissioned.

 

lcaErrNsNiDeviceOpenFailure NS, #177

NI device driver open failure.

 

lcaErrNsBadLength NS, #178

Invalid length of parameter, data, service, or message.

 

lcaErrNsBadName NS, #179

Invalid name length, characters, or usage.

 

lcaErrNsBadDomain NS, #180

Invalid domain length, index, or usage.

 

lcaErrNsInsufficientRtrsForMnc NS, #181

No routers exist to complete logical path needed for monitoring and control.

 

lcaErrNsInsufficientRtrsForNsi NS, #182

No routers exist to complete logical path needed for NSI and control. This exception will be

thrown if you attempt to remove a router and the operation fails because it would break

communication between the LNS Server and a remote Full client.

 

lcaErrNs96BitAuthNotSupported NS, #183

This error will be generated if you attempt to use 96-bit authentication on a device that does not

support it.

 

lcaErrNsNeuronModelMismatch NS, #184

Neuron model version mismatch. 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 device’s system

image. In this case, you need to upgrade the device’s system image. Some devices support the

LoadEx method, which automatically upgrades the system image before loading the application

image if there are compatibility problems.

 

lcaErrLNSysimageFileFormatError NS, #185

System image or upgrade image file format is invalid. Verify that LNS has been installed

correctly.

 

lcaErrLNSysimageCannotBeWritten NS, #186

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. 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.

 

lcaErrLNSysimageUpgradeMemoryFailur NS, #187

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.

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.

 

lcaErrLNSysimageUpgradeFailed NS, #188

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. If you encounter this error, try invoking the LoadEx method again,

or loading the previous system image back into the device.

 

lcaErrNs16BitUserErrorCode NS, #189

The user defined error code is too big. This is an internal error, and should be reported to

customer support.

 

lcaErrNs16BitWarningCode NS, #190

The LNS warning code is too big. This is an internal error, and should be reported to customer

support.

 

lcaErrNs16BitErrorCode NS, #191

The LNS error code is too big. This is an internal error, and should be reported to customer

support.

 

lcaErrNsFlexDomainAuthNotSupported NS, #256

An attempt was made to leave a device authenticated but without a domain, and that device

does not support flex domain authentication.

 

lcaErrNsCantModifyBoundNvType NS, #257

Cannot modify the network variable type of a network variable when it is bound.

 

lcaErrNsCantModifyMonitoredNvType NS, #258

Cannot modify network variable type of a network variable when it is being monitored.

 

lcaErrNsRegCannotOpenReg NS, #259

Cannot open the LNS registry.

 

lcaErrNsRegUnknown NS, #260

Unknown LNS registry error.

 

lcaErrNsRegConfigFileNotFound NS, #261

The LNS registry backup file cannot be found.

 

lcaErrNsRegCannotUpdateConfigFile NS, #262

Cannot update the LNS registry backup file.

 

lcaErrNsUnsupportedFileDirectoryVer NS, #263

The device contains a version of the file directory that is unsupported.

 

lcaErrNsBadsiHdrSize NS, #264

Invalid self-identification data header size.

 

lcaErrNsBadsiCapacityExceedsLimits NS, #265

Capacity defined by self-identification data exceeds supported limits.

 

lcaErrNsBadsiCountExceedsCapacity NS, #266

Resource count exceeds capacity limits in self-identification data.

 

lcaErrNsLmsdObjectRange NS, #267

Invalid object range in the LonMark portion of a network variable self-documentation string.

When specifying a range of objects, the lowest object index must appear before the highest

object index.

 

lcaErrNsLmsdObjectMemberNumber NS, #268

Invalid object member in the LonMark portion of a network variable self-documentation string.

The member number must be between 1 and 32767.

 

lcaErrNsLmsdObjectArray NS, #269

The LonMark portion of a network variable self-documentation string indicates that elements of

the network variable are to be used as members of an object array. However, the network

variable array has fewer members than the object array.

 

lcaErrNsLmsdVersion NS, #270

Unsupported LonMark version number in the node self-documentation string.

 

lcaErrNsLmsdExpectedObjHdr NS, #271

Expected LonMark object header in node self-documentation string.

 

lcaErrNsLmsdObjectNameTooLong NS, #272

The LonMark Object name in the node self-documentation string exceeds 16 characters.

 

lcaErrNsCpsdOwnerType NS, #273

Invalid CP owner type in header portion of the CP self-documentation string. The header must

indicate whether the CP is owned by the device, one or more objects, or one or more network

variables.

 

lcaErrNsCpsdMismatchedRangeTypes NS, #274

Mismatched CP range types in the CP self-documentation string. Both the low and high range

values must have the same type.

 

lcaErrNsCpsdDisableWithoutNodeobj NS, #275

The CP Self-documentation of one or more CPs indicate that the object must be disabled in

order to set the CP, but no node object is defined. Without a node object, it is not possible to

disable an object.

 

lcaErrNsCpsdFileCpWithoutFtp NS, #276

A CP template file is defined in the external interface file for a device, but the device does not

support FTP or direct memory access.

 

lcaErrNsCpsdCpRange NS, #277

The CP Self-documentation includes a range of objects or network variables, with the first index

in the range being greater than the second. CP ranges must be specified from lowest to highest.

 

lcaErrNsCpsdDistributedArraySize NS, #278

The CP Self-documentation indicates that a CP array should be distributed among range of

network variables or objects, but the CP array size does not match the owner’s range.

 

lcaErrNsCpsdTemplateVersion NS, #279

The version of the CP template is unsupported.

 

lcaErrNsGroupDblimit NS, #280

The number of LonTalk groups has been exceeded. There is a limit of 255 LONtalk groups per

domain. In some case you may form connections using subnet or domain broadcast, to limit the

use of groups. You may also limit the use of groups by using network variable aliases. These

options are specified in the connection description template used when forming connections.

 

lcaErrNsNodeidDblimit NS, #281

Number of LonTalk node IDs exceeded. There are 127 LONtalk node Ids per subnet. LNS will

allocate a new subnet, as needed, if the application does not specify the subnet to be used.

 

lcaErrNsLNSEngineInitTimeout NS, #282

The application timed out starting the LNS engine process (LNSEng.Exe). This could be an

indication that LNS is not installed properly. If you encounter this error, you should try

rebooting your PC, or re-installing LNS.

 

lcaErrNsDmtNotFound NS, #283

The dynamic message tag cannot be found.

 

lcaErrNsDmtDblimit NS, #284

The maximum number of dynamic message tags has been exceeded. A single device can

support up to 65,534 dynamic message tags, including internally defined message tags created

for use with message points. You can add and remove message tags from a device with the Add

and Remove methods of the MessageTags collection.

 

lcaErrNsLmobjNotDynamic NS, #285

The specified LonMarkObject is not dynamic. 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.

You can determine if a LonMarkObject is dynamic or not by reading its IsDynamic property.

 

lcaErrNsLmobjNvNotDynamic NS, #286

The specified network variable is not dynamic. 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.

You can determine if a network variable is dynamic or not by reading its IsDynamic property.

 

lcaErrNsLmobjInUse NS, #287

The specified LonMarkObject is in use, and at least one of its member network variables is

bound. 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.

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.

 

lcaErrNsApplReadWriteProtected NS, #288

This exception will be thrown if you call the Load method to load a new application into a device,

but the device’s current application is read/write protected.

 

lcaErrNsEngineIsSuspended NS, #289

The engine is currently suspended. This is an internal error, and should be reported to customer

support.

 

lcaErrNsNotSupportedFromRemoteClient NS, #290

The operation is not supported from a remote full client. This is an internal error, and should be

reported to customer support.

 

lcaErrNsUnexpectedLink NS, #291

The link between the parent and the child record was unexpected. This error usually indicates

that the LNS database has been corrupted. If you encounter this error, you should use the

Validate method to run a database validation, and consider switching to a backup database.

 

lcaErrNsUnsupportedProgramCapability NS, #292

The program defines capabilities that are not supported by LNS. This error will be thrown when

you call the Import method to import a device’s XIF file, and the XIF file (or the device’s selfdocumentation)

indicates that it supports dynamic function blocks or dynamic function block

members, but does not specify the EXTCAP_SUPPRESS_DYN_FB_DEF and

EXTACP_SUPPRESS_DYN_FB_MBR_DEF flags. LNS 3.20 does not support downloading function

blocks or function block membership to a device, any so any device that supports these

operations needs to have an alternate way to define these dynamic function blocks and function

block members. They must indicate that via the EXTCAP flags mentioned above.

 

lcaErrNsInvalidCpAttribute NS, #293

The LONMARK organization does not allow modifiable device-specific configuration properties to

be stored in files accessed via FTP on devices that support only sequential access. If you

attempt to set the DeviceSpecificAttribute property to True on such a configuration property, this

exception will be thrown.

 

lcaErrNsNotAllowedInASession NS, #294

The operation is not allowed as part of a session. You can use sessions to group together

properties and methods that must be performed together to avoid immediate error conditions.

You can start a session with the BeginSession method, and close it with the EndSession method.

You should note that the only network operations you can perform within sessions are those

related to changes in the physical topology of your network. These operations include moving

devices and routers, adding and removing routers, and setting the class of routers. For more

information, see the online help for the BeginSession method.

 

lcaErrNsInvalidCpFileSize NS, #295

The configuration property value file size reported by the device does not agree with the size

defined by the definitions in the configuration property template file. Note that if the device

template was imported from an external interface file, the configuration property template file

comes from the external interface file. Otherwise, the configuration property template file is

loaded from the device.

 

lcaErrNsWarningFirst NS, #4030

A symbol denoting the beginning of the error number range reserved for warning codes.

 

lcaErrNsUpdateCommError NS, #4030

The database updates were successful, but one or more nodes were not updated because the

LNS was unable to communicate with them. 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.

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.

 

lcaErrNsUpdateFuncError NS, #4031

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. This usually means

that there is a configuration mismatch between the node and the LNS's 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.

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.

 

lcaErrNsNeuronStateChangeFail NS, #4032

The LNS's database updates were successful, but one or more nodes were not updated because

the node(s) failed to make a necessary state transition. 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 nonzero

value, and you can force a retry with the RetryUpdates method.

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.

 

lcaErrNsNodeUpdateDisallowed NS, #4033

The database updates were successful, but one or more nodes could not be updated because

they are in the wrong state. 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. 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 a node is applicationless, you must reload the application using the AppDevice.load method.

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.

 

lcaErrNsUpdateFileXferError NS, #4034

The database updates were successful, but an update error occurred. 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. You can keep

track of which devices are up to date using commissioning events and by reading the

CommissionStatus property of each AppDevice object.

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. Most

file update errors map to this status during an update.

 

lcaErrNsUpdateWhenUncnfg NS, #4035

The database updates were successful, but one or more nodes could not be updated because

they are not configured. You should ensure that all applicable devices are configured when this

error occurs. 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.

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.

 

lcaErrNsUpdateWhenAppless NS, #4036

The database updates were successful, but one or more nodes could not be updated because

they are applicationless. You can load a node’s application by calling the Load method on the

AppDevice object associated with the node. 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.

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.

 

lcaErrNsUpdateCpFileTooShort NS, #4037

The database updates were successful, but one or more devices was not updated because a

configuration property file in the device is shorter than specified in the database. This is usually

due to an inconsistency between the device’s configuration property template file and its data

file. The configuration property template file should be the same for all devices of a given type.

If you encounter this type of error, check to make sure that the device is using the appropriate

external interface file. 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.

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.

 

lcaErrNsUpdateCpFailure NS, #4038

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.

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.

 

lcaErrNsUpdatesDeferred NS, #4039

The database updates were successful, but the configuration properties on one or more devices

could not be updated because the MgmtMode is currently set to

lcaMgmtModeDeferConfigUpdates (1). You can update all the devices on the network with

all pending updates by setting the MgmtMode property to lcaMgmtModePropagateConfigUpdates (0).You can also update a single device with its pending device-only configuration changes while theMgmtMode property is still set to lcaMgmtModeDeferConfigUpdates (1) with the

PropagateDeviceConfigUpdates method.

 

lcaErrNsWarningLast NS, #4089

A symbol denoting the end of the error number range reserved for warning codes. 

 

Add Feedback