Data Server Errors
These are errors returned by the LNS Data Server. The Data Server handles network variable
and message tag monitoring and control. These errors will appear in the format DS: #<Error
lcaErrDsBusy DS, #1
Could not get semaphore to perform Data Server operation.
lcaErrDsAlreadyStarted DS, #2
Cannot start Data Server, as it was already started.
lcaErrDsNoServer DS, #3
Invalid Data server handle passed in.
lcaErrDsOptionOutOfRange DS, #4
Invalid option passed in.
lcaErrDsNotImplemented DS, #5
Function not implemented.
lcaErrDsNotStarted DS, #6
Function unavailable until the Data Server has been started.
lcaErrDsCantActivate DS, #7
lcaErrDsCantDeactivate DS, #8
lcaErrDsIllegalObjectHandle DS, #9
Illegal object handle was passed in.
lcaErrDsReentry DS, #10
Tried to perform an exclusive operation, such as updating a particular network variable on a
node, that was already in progress.
lcaErrDsRegistrySetErr DS, #11
lcaErrDsAlreadyCreated DS, #12
Tried to create a Data Server when one already existed for this process.
lcaErrDsException DS, #13
A system exception was thrown.
lcaErrDsInvalidObjectType DS, #14
lcaErrDsUserCancel DS, #15
The operation specified was canceled interactively at the user interface.
lcaErrDsVersionIncompatibility DS, #16
Some of the DLLs used by the Data Server are older, incompatible versions.
lcaErrDsInitValidationError DS, #17
This indicates that the Data Server failed to initialize properly. This exception could be thrown if
your application specifies an invalid name or index number when retrieving an object from the
lcaErrDsUpdateRegistryFailure DS, #18
Could not update the Windows registry.
lcaErrDsNsCreateClientFailed DS, #19
Failed to create a Network Services client for data services.
lcaErrDsNsInitFailed DS, #20
Failed to initialize the Network Services Server.
lcaErrDsNsNotOpen DS, #21
Error on shutdown, when attempting to close the Network Services server, the server is not
lcaErrDsGetHandleFromNameFail DS, #22
Could not get the node handle from its name.
lcaErrDsInvokeNodeAddrFail DS, #23
Could not get the nodeâ€™s address on the network from the Network Services server.
lcaErrDsGetRegistryFailure DS, #24
Failed to retrieve an item from the Windows registry.
lcaErrDsSetRegistryFailure DS, #25
Failed to write an item to the Windows registry.
lcaErrDsInvalidRegKey DS, #26
Failed to set a Windows registry key because the new key passed in was invalid.
lcaErrDsInvalidNodeName DS, #27
An invalid node name was specified, or no name services provider was specified for the LNS.
lcaErrDsNodeDoesNotExist DS, #28
Node does not exist on this network, probably because it has not yet been configured with a
lcaErrDsNvDoesNotExist DS, #29
A network variable operation was attempted on an NV that does not exist.
lcaErrDsNvGetConnInfoFailed DS, #30
A Network Services call to get connection information for this network variable has failed.
lcaErrDsNvGetTypeInfoFailed DS, #31
A Network Services call to get type information for this network variable has failed.
lcaErrDsStartNvObjectFailed DS, #32
Could not start the network variable object.
lcaErrDsDeleteNvObjectFailed DS, #33
Could not delete the network variable object.
lcaErrDsNvSetObjDataFailed DS, #34
Failed to write data to the network variable object.
lcaErrDsDataFormatFailure DS, #35
An attempt to format the requested data has failed.
lcaErrDsCreateThreadFailure DS, #36
Could not create the thread to receive LONWORKS messages from the network.
lcaErrDsCreateEventFailure DS, #37
Could not create the event to signal arriving LONWORKS messages from the network.
lcaErrDsEventSignalTimeout DS, #38
Timed out waiting for a synchronizing event to be signaled by a LONWORKS network response.
lcaErrDsCannotForceDataRequest DS, #39
lcaErrDsNvIllegalRetry DS, #40
The number of retries specified for this network variable is out of range.
lcaErrDsNvIllegalInterval DS, #41
The interval specified for this network variable is illegal.
lcaErrDsInvalidDriverName DS, #42
The network interface driver specified does not exist.
lcaErrDsMismatchTypeSize DS, #43
The type specified is not the correct size to represent this network variable.
lcaErrDsFmtTypeNotFound DS, #44
The format type referenced does not exist.
lcaErrDsNvIllegalField DS, #45
The network variable field referenced does not exist.
lcaErrDsInvalidServerHandle DS, #46
The Data Server handle passed in is invalid.
lcaErrDsOptionIsReadOnly DS, #47
Option is read-only. The value may not be set.
lcaErrDsObjectNotStarted DS, #48
Failed because the object referenced must be started first.
lcaErrDsObjectIsAlreadyStarted DS, #49
Cannot start this object, as it is already started.
lcaErrDsSetInvalidServiceType DS, #50
Tried to set the service type to an invalid value.
lcaErrDsNiIsBusy DS, #51
Operation failed because the network interface was busy.
lcaErrDsNiOpenFailure DS, #52
Error opening the network interface.
lcaErrDsNiUnknown DS, #53
Error with the network interface.
lcaErrDsCantWriteRemoteNvOutput DS, #54
It is not possible to write a value to a remote output network variable.
lcaErrDsFormattingInternalError DS, #55
Error loading one of the SNVT or User type (.TYP) files.
lcaErrDsFmtFileLoadFailure DS, #56
Error loading one of the SNVT or User format (.FMT) files.
lcaErrDsBufferTooSmall DS, #57
The specified buffer is too small for the current operation.
lcaErrDsMsgSendFailure DS, #58
Failed to send the current message.
lcaErrDsNoDataAvailable DS, #59
No data is available for retrieval in the current operation.
lcaErrDsTypeFileNotFound DS, #60
The specifed type file could not be found.
lcaErrDsOptionIsMsgobjOnly DS, #61
The specified configuration option only applies to message objects.
lcaErrDsOptionIsNvOnly DS, #62
The specified configuration option only applies to network variable objects.
lcaErrDsNoResource DS, #63
System resources unavailable.
See KB 344.
lcaErrDsInvalidParamValue DS, #64
One or more of the passed parameters has an illegal value.
lcaErrDsMtagDoesNotExist DS, #65
The specified message does not exist.
lcaErrDsRegistryDataInvalid DS, #66
Invalid data was found in a Data Server registry entry.
lcaErrDsFmttypeHasNoFields DS, #67
The format type specified does not contain information about fields.
lcaErrDsEventSubscriptionFailed DS, #68
Failed to subscribe to the specified event.
lcaErrDsCantFindFormatCatalog DS, #69
The format catalog could not be found.
lcaErrDsCantFindStandardTypeFile DS, #70
The specified standard type file could not be found.
lcaErrDsEventDesubscriptionFailed DS, #71
Failed to unsubscribe to the specified event.
lcaErrDsInvalidVersion2TypeName DS, #72
An invalid Version2 format name was supplied. Version 2 type names must start with SNVT,
UNVT, SCPT or UCPT. Format names should be taken from the standard and user-defined
resource file catalogs located in the directory specified by the LdrfCatlalogPath property.
lcaErrDsInvalidWhenNvFieldInUse DS, #75
The requested operation must be performed on a network variable. It cannot be performed on
an individual network variable field.
lcaErrDsInvalidWhenNvFieldNotSpecified DS, #76
The requested operation must be performed on an individual network variable field. It cannot be
performed on a network variable.
lcaErrDsGetAppmanagerFailed DS, #77
Failed to specify the application manager.
lcaErrDsCantSetHostMsgOwner DS, #78
Fatal error occurred when attempting to become host message owner. Only one process can be
host message owner at any time.
lcaErrDsFmtIllegalBaseType DS, #79
Format specifier is not valid for the type/field.
lcaErrDsNetworkError DS, #200
Failed to communicate with target device.
You could see this error on the Monitor program (e.g., LonMaker Browser) if a device is
rebooting, there are network interface problems, there problems with routers or repeaters in
between the monitor program and the device, the channel bandwidth is overwhelmed, the
LonTalk channel is down or the device stopped.
LNS will throw DS 200 in many cases. The most common reasons for this error are high bandwidth
utilization (collisions that prevent communication) and physical network connectivity problems
(lack of terminators in twisted pair networks or other wiring problems).
In rare cases, a race condition has been identified in LNS 3.0. It occurs when actively polling
network variables at a high rate using a slow performance PC and a network interface with a layer
5 MIP (also known as an NSI interface). As a result of this problem, it is possible that LNS may
stop polling a network variable indefinitely.
To work around this problem use a layer 2 MIP interface. If this does not resolve the problem, it
may be necessary to upgrade to a faster PC or decrease the polling rate until reaching a work load
the PC can handle.
Examples of a Layer 5 MIP interface:
PCLTA-10 and PCLTA-20 running NSIPCLTA NI Application
PCC-10 interface using a NSIPCC NI Application
i.LON 10 and iLon100
U10/U20 when used with OpenLDV program
Examples of a Layer 2 MIP interface are:
PCLTA-10 and PCLTA-20 running PCL10VNI NI Application
PCC-10 interface using a PCC10VNI NI Application
iLon1000 communicating to the PC using a LonWorks/IP channel
U10/U20 when used with LonMaker/LNS/LonScanner
lcaErrDsTargetNodeFailure DS, #201
Target node responded with failure code.
lcaErrLnsDsUnexpected DS, #365
Unexpected failure. Contact customer support.
lcaErrLnsDsFailed DS, #366
Generic failure. Contact customer support.
lcaErrLnsDsOutOfMemory DS, #367
Memory allocation failure.
lcaErrLnsDsNotImpl DS, #368
lcaErrLnsDsPointer DS, #369
lcaErrLnsDsInvalidArg DS, #370
Invalid argument. One way this error can occur is if you call the Write method on a DataPoint
object obtained from a NetworkVariable or NvMonitorPoint object before reading or setting its
value with the FormattedValue property, the RawValue property, or the Value property. This
indicates that the DataPointâ€™s buffer is empty.
lcaErrLnsDsRange DS, #371
Argument supplied is out of valid range.
lcaErrLnsDsTimeout DS, #372
lcaErrLnsDsSizeTooSmall DS, #373
Size is too small.
lcaErrLnsDsInvalidObject DS, #374
Object not valid.
lcaErrLnsDsInvalidWindow DS, #375
lcaErrLnsDsInvalidOperation DS, #376
Operation not valid, or the operation was attempted on an invalid object.
lcaErrLnsDsQueueFull DS, #377
The message queue is full and the most recent message has been dropped.
lcaErrLnsDsQueueStopped DS, #378
The message queue was stopped by a client application and the most recent message has been
lcaErrLnsDsOutstandingRefs DS, #379
Outstanding object references still exist.
lcaErrLnsDsOutstandingClients DS, #380
Outstanding clients still exist.
lcaErrLnsDsOutstandingNetworks DS, #381
Outstanding networks still exist.
lcaErrLnsDsOutstandingVNIs DS, #382
Outstanding VNIs still exist.
lcaErrLnsDsOutstandingMonitorSets DS, #383
Outstanding monitor sets still exist.
lcaErrLnsDsNotFound DS, #384
Object not found.
lcaErrLnsDsClientNotFound DS, #385
Client not found.
lcaErrLnsDsNetworkNotFound DS, #386
Network not found.
lcaErrLnsDsVniNotFound DS, #387
VNI not found.
lcaErrLnsDsMonitorSetNotFound DS, #388
Monitor set not found.
lcaErrLnsDsMonitorPointNotFound DS, #389
Monitor point not found.
lcaErrLnsDsNodeNotFound DS, #390
Node not found.
lcaErrLnsDsNetworkVariableNotFound DS, #391
Network variable not found.
lcaErrLnsDsAppMessageNotFound DS, #392
Application message not found.
lcaErrLnsDsNotOpen DS, #393
Object must be opened before the requested operation can be performed.
lcaErrLnsDsNetworkNotOpen DS, #394
Network must be opened before the requested operation can be performed.
lcaErrLnsDsVniNotOpen DS, #395
VNI must be opened before the requested operation can be performed.
lcaErrLnsDsMonitorSetNotOpen DS, #396
Monitor set must be opened before the requested operation can be performed.
lcaErrLnsDsNotConnected DS, #397
The client must be connected to the server before the requested operation can be performed.
lcaErrLnsDsOpenFailed DS, #398
There was an error opening the object.
lcaErrLnsDsVniOpenFailed DS, #399
There was an error opening the VNI.
lcaErrLnsDsMonitorSetOpenFailed DS, #400
There was an error opening the monitor set.
lcaErrLnsDsCloseFailed DS, #401
There was an error closing the object.
lcaErrLnsDsVniCloseFailed DS, #402
There was an error closing the VNI.
lcaErrLnsDsThreadCreateFailed DS, #403
There was an error creating the thread.
lcaErrLnsDsNotTemporaryMonitorSet DS, #404
The requested operation can only be performed on temporary monitor sets.
lcaErrLnsDsNotTemporaryMonitorPoint DS, #405
The requested operation can only be performed on temporary monitor points.
lcaErrLnsDsLNSNotOpen DS, #406
LNS must be opened before the requested operation can be carried out.
lcaErrLnsDsLNSCreateClientFailed DS, #407
There was an error creating the LNS client.
lcaErrLnsDsLNSInitFailed DS, #408
There was an error initializing LNS.
lcaErrLnsDsLNSException DS, #409
Error occurred during an LNS operation.
lcaErrLnsDsReadFailed DS, #410
Network variable read failed.
lcaErrLnsDsWriteFailed DS, #411
Network variable write failed.
lcaErrLnsDsPollFailed DS, #412
Network variable poll failed.
lcaErrLnsDsSendFailed DS, #413
Application message transmission failed.
lcaErrLnsDsMsgRejected DS, #414
Application message rejected, as network management commands are restricted.
lcaErrLnsDsRequestFailed DS, #415
Application message request failed.
lcaErrLnsDsResponseFailed DS, #416
Application message response failed.
lcaErrLnsDsAddressNotAvailable DS, #417
The source node address is not available.
lcaErrLnsDsIllegalHexCharacter DS, #418
An illegal hexadecimal character was specified in the string.
lcaErrLnsDsTooManyClients DS, #419
There are too many clients connected to the server.
lcaErrLnsDsInvalidClientContext DS, #420
Invalid or no client context was supplied.
lcaErrLnsDsImplicitAddress DS, #421
The requested operation is not allowed, as the monitor point uses implicit addressing.
lcaErrLnsDsExplicitAddress DS, #422
The requested operation is not allowed, as the monitor point uses explicit addressing.
lcaErrLnsDsNotOwner DS, #423
The requested operation is not allowed, as the client is not the owner of the object or process
lcaErrLnsDsNoNameServicesManager DS, #424
Cannot look up the requested name, as there is no name service manager defined.
lcaErrLnsDsNameTooLong DS, #425
The name specified is too long.
lcaErrLnsDsCountMismatch DS, #426
Reference/Lock count mismatch. This could be caused by too many Release calls being made
by the application.
lcaErrLnsDsNotPermanentMonitorSet DS, #428
The requested operation can only be performed on a permanent monitor set.
lcaErrLnsDsNotPermanentMonitorPoint DS, #429
The requested operation can only be performed on a permanent monitor point.
lcaErrLnsDsException DS, #430
An unexpected exception occurred.
lcaErrLnsDsInitUpdateFailed DS, #431
A network variable could not be updated.