The aggregate configuration is not valid for specified node.
The aggregate value could not be derived due to invalid data inputs.
The requested number of Aggregates does not match the requested number of NodeIds.
The requested Aggregate is not support by the server.
An equivalent rule already exists.
The signature generated with the client certificate is missing or invalid.
The client did not specify all of the input arguments for the method.
The attribute is not supported for the specified Node.
No data found to provide upper or lower bound value.
The server cannot retrieve a bound for the variable.
The browse direction is not valid.
The browse name is not unique among nodes that share the same relationship with the parent.
The browse name is invalid.
The certificate chain is incomplete.
The HostName used to connect to a server does not match a HostName in the certificate.
The certificate provided as a parameter is not valid.
It was not possible to determine if the issuer certificate has been revoked.
The issuer certificate has been revoked.
An issuer certificate has expired or is not yet valid.
The issuer certificate may not be used for the requested operation.
The certificate does not meet the requirements of the security policy.
It was not possible to determine if the certificate has been revoked.
The certificate has been revoked.
The certificate has expired or is not yet valid.
The certificate is not trusted.
The URI specified in the ApplicationDescription does not match the URI in the certificate.
The certificate may not be used for the requested operation.
A low level communication error occurred.
This condition has already been disabled.
This condition has already been enabled.
The condition has already been shelved.
The condition branch has already been acknowledged.
The condition branch has already been confirmed.
Property not available, this condition is disabled.
The condition is not currently shelved.
There is a problem with the configuration that affects the usefulness of the value.
The network connection has been closed.
Could not establish a network connection to remote server.
The content filter is not valid.
The continuation point provide is longer valid.
The data encoding is invalid.
The server does not support the requested data encoding for the node.
Data is missing due to collection started/stopped/lost.
The extension object cannot be (de)serialized because the data type id is not recognized.
Expected data is unavailable for the requested time range due to an un-mounted volume, an off-line archive or tape, or similar reason for temporary unavailability.
The deadband filter is not valid.
Decoding halted because of invalid data in the stream.
A dependent value has been changed but the change has not been applied to the device. The quality of the dominant variable is Bad.
There has been a failure in the device/data source that generates the value that has affected the value.
The dialog condition is not active.
The response is not valid for the dialog.
The server has disconnected from the client.
No DiscoveryUrl was specified.
The related EngineeringUnit has been changed but this change has not been applied to the device. The Variable Value is still dependent on the previous unit but its status is currently Bad.
The reference type between the nodes is already defined.
It is delivered with a Variable value when Variable has changed but the value is not legal.
It is delivered with a dependent Variable value when a dominant Variable has changed, the value is not legal and the change has not been applied.
It is delivered with a dependent Variable value when a dominant or dependent Variable has changed, the value is not legal and the change has not been applied.
Encoding halted because of invalid data in the objects being serialized.
The message encoding/decoding limits imposed by the stack have been exceeded.
Cannot move beyond end of the stream.
The data or event was not successfully inserted because a matching entry exists.
The event filter is not valid.
The specified event id is not recognized.
The event cannot be acknowledged.
The stream did not return all data requested (possibly because it is a non-blocking stream).
The referenced element is not a valid element in the content filter.
The referenced literal is not a valid value.
A monitoring filter cannot be used in combination with the attribute specified.
The number of operands provided for the filter operator was less then expected for the operand provided.
The operand used in a content filter is not valid.
An unrecognized operator was provided in a filter.
A valid operator was provided, but the server does not provide support for this filter operator.
The history details parameter is not valid.
The server does not support the requested operation.
The server does not support changing the user identity assigned to the session.
The user identity token is not valid.
The user identity token is valid but the server has rejected it.
The syntax of the index range parameter is invalid.
No data exists within the range of indexes specified.
It is delivered with a Variable value when a source Variable has changed but the value is not legal.
The client of the current session does not support one or more Profiles that are necessary for the subscription.
An internal error occurred as a result of a programming or configuration error.
One or more arguments are invalid.
The server does not allow this type of self reference on this node.
The operation cannot be completed because the object is closed, uninitialized or in some other invalid state.
The timestamp is outside the range allowed by the server.
The defined timestamp to return was invalid.
The server requires a license to operate in general or to perform a service or operation, but existing license is expired.
The server has limits on number of allowed operations / objects, based on installed licenses, and these limits where exceeded.
The server does not have a license which is required to operate in general or to perform a service or operation.
The max age parameter is invalid.
The operation could not be finished because all available connections are in use.
The requested notification message is no longer available.
The method id does not refer to a method for the specified object.
The monitored item filter parameter is not valid.
The server does not support the requested monitored item filter.
The monitoring item id does not refer to a valid monitored item.
The monitoring mode is invalid.
Communication with the data source is defined, but not established, and there is no last known value available.
The operation could not be processed because all continuation points have been allocated.
No data exists for the requested time range or event filter.
No data is currently available for reading from a non-blocking stream.
The server will not allow the node to be deleted.
The data or event was not successfully updated because no matching entry exists.
The requested operation has no match to return.
There is no subscription available for this session.
The client did not provide at least one software certificate that is valid and meets the profile requirements for the server.
The node attributes are not valid for the node class.
The node class is not valid.
The requested node id is already used by another node.
The syntax of the node id is not valid.
The requested node id was reject because it was either invalid or server does not allow node ids to be specified by the client.
The node id refers to a node that does not exist in the server address space.
The node is not part of the view.
The nonce does appear to be not a random value or it is not the correct length.
The variable should receive its value from another variable, but has never been configured to do so.
The executable attribute does not allow the execution of the method.
A requested item was not found or a search operation ended without success.
Requested operation is not implemented.
The access level does not allow reading or subscribing to the Node.
The requested operation is not supported.
The provided Nodeid was not a type definition nodeid.
The access level does not allow writing to the Node.
There was nothing to do because the client passed a list of operations with no elements.
The number was not accepted because of a numeric overflow.
The object cannot be used because it has been deleted.
The asynchronous operation was abandoned by the caller.
Not enough memory to complete the operation.
The value was out of range.
It is delivered with a dependent Variable value when a dominant Variable has changed and the value is not legal.
It is delivered with a dependent Variable value when a dominant or dependent Variable has changed and the value is not legal.
The source of the data is not operational.
The parent node id does not to refer to a valid node.
The applications do not have compatible protocol versions.
The requested operation requires too many resources in the server.
The reference type is not valid for a reference to a remote server.
The reference could not be created because it violates constraints imposed by the data model.
The reference type id does not refer to a valid reference type node.
This Condition refresh failed, a Condition refresh operation is already in progress.
The request was cancelled by the client.
The request was cancelled by the client with the Cancel service.
The header for the request is missing or invalid.
The request could not be sent because of a network interruption.
The request was rejected by the server because it did not meet the criteria set by the server.
The request has not been processed by the server yet.
Timeout occurred while processing the request.
The request message size exceeds limits set by the server.
The security token request type is not valid.
An operating system resource is not available.
The response message size exceeds limits set by the client.
The secure channel has been closed.
The specified secure channel is no longer valid.
The token has expired or is not recognized.
An error occurred verifying security.
The operation is not permitted over the current secure channel.
The security mode does not meet the requirements set by the server.
The security policy does not meet the requirements set by the server.
The semaphore file specified by the client is not valid.
There has been a failure in the sensor from which the value is derived by the device/data source.
The sequence number is not valid.
The sequence number is unknown to the server.
The server has stopped and cannot process any requests.
The server index is not valid.
No ServerName was specified.
The operation could not complete because the client is not connected to the server.
The ServerUri is not a valid URI.
The server does not support the requested service.
The session was closed by the client.
The session id is not valid.
The session cannot be used because ActivateSession has not been called.
The shelving time not within an acceptable range.
The operation was cancelled because the application is shutting down.
The source node id does not reference a valid node.
The sub-state machine is not currently active.
A mandatory structured parameter was missing or null.
The subscription id is not valid.
A value had an invalid syntax.
The target node id does not reference a valid node.
The server does not recognize the QueryString specified.
An internal error occurred.
The size of the message chunk specified in the header is too large.
The type of the message specified in the header invalid.
There are not enough resources to process the request.
The SecureChannelId and/or TokenId are not currently in use.
The server cannot process the request because it is too busy.
The device identity needs a ticket before it can be accepted.
The device identity needs a ticket before it can be accepted.
The operation timed out.
The client requested history using a timestamp format the server does not support (i.e requested ServerTimestamp when server only supports SourceTimestamp).
The timestamps to return parameter is invalid.
Too many arguments were provided.
The requested operation has too many matches to return.
The request could not be processed because there are too many monitored items in the subscription.
The request could not be processed because it specified too many operations.
The server has reached the maximum number of queued publish requests.
The server has reached its maximum number of sessions.
The server has reached its maximum number of subscriptions.
The type definition node id does not reference an appropriate type node.
The value supplied for the attribute is not of the same type as the attribute's value.
An unexpected error occurred.
An unrecognized response was received from the server.
User does not have permission to perform the requested operation.
The user token signature is missing or invalid.
The view id does not refer to a valid view node.
The view parameters are not consistent with each other.
The view timestamp is not available or not supported.
The view version is not available or not supported.
Waiting for the server to obtain values from the underlying data source.
The asynchronous operation is waiting for a response.
Non blocking behaviour is required and the operation would block.
The server does not support writing the combination of value, status and timestamps provided.
The operation succeeded.
The operation is not finished and needs to be called again.
The value is accurate, and the signal source supports cascade handshaking.
The value source supports cascade handshaking and the value has been Initialized based on an initialization request from a cascade secondary.
The value source supports cascade handshaking and is requesting initialization of a cascade primary.
The value source supports cascade handshaking, however, the source’s current state does not allow for cascade.
The value source supports cascade handshaking, however, the source has not selected the corresponding cascade primary for use.
The value written was accepted but was clamped.
The communication layer has raised an event.
The processing will complete asynchronously.
The request specifies fields which are not valid for the EventType or cannot be saved by the historian.
A dependent value has been changed but the change has not been applied to the device.
The value does not come from the real source and has been edited by the server.
It is delivered with a dominant Variable value when a dependent Variable has changed but the change has not been applied.
It is delivered with a dependent Variable value when a dominant Variable has changed but the change has not been applied.
It is delivered with a dependent Variable value when a dominant or dependent Variable has changed but change has not been applied.
The data or event was successfully inserted into the historical database.
The data or event field was successfully replaced in the historical database.
There is a fault state condition active in the value source.
A fault state condition is being requested of the destination.
The value has been overridden.
The data or event field was successfully replaced in the historical database.
No data exists for the requested time range or event filter.
A non-critical timeout occurred.
Sampling has slowed down due to resource limitations.
There was an error in execution of these post-actions.
The server should have followed a reference to a node in a remote server but did not. The result set may be incomplete.
The Server does not support retransmission queue and acknowledgement of sequence numbers is not available.
The system is shutting down.
The subscription was transferred to another session.
The operation was uncertain.
The value may not be accurate due to a configuration issue.
The value is derived from multiple values and has less than the required number of Good values.
A dependent value has been changed but the change has not been applied to the device. The quality of the dominant variable is uncertain.
The related EngineeringUnit has been changed but the Variable Value is still provided based on the previous unit.
The value is outside of the range of values defined for this parameter.
The value is an initial value for a variable that normally receives its value from another variable.
Whatever was updating this value has stopped doing so.
Communication to the data source has failed. The variable value is the last value that had a good quality.
The list of references may not be complete because the underlying system is not available.
The server was not able to delete all target references.
One of the references to follow in the relative path references to a node in the address space in another server.
The value may not be accurate due to a sensor calibration fault.
The value is at one of the sensor limits.
The value is simulated.
The value is derived from multiple sources and has less than the required number of Good sources.
The value is an operational value that was manually overwritten.
The value may not be accurate because the transducer is in manual mode.
Generated using TypeDoc
The operation failed.