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