7.38.2 Common StatusCodes

Table 178 defines the common StatusCodes for all Service results used in more than one service. It does not provide a complete list. These StatusCodes may also be used as operation level result code. OPC 10000-6 maps the symbolic names to a numeric value and provides a complete list of StatusCodes including codes defines in other parts.

Table 178 – Common Service Result Codes
Symbolic Id Description
GoodThe operation was successful.
Good_CompletesAsynchronouslyThe processing will complete asynchronously.
Good_SubscriptionTransferredThe Subscription was transferred to another session.

Bad_CertificateHostNameInvalid

The HostName used to connect to a Server does not match a HostName in the Certificate.
Bad_CertificateChainIncompleteThe Certificate chain is incomplete.
Bad_CertificateIssuerRevocationUnknownIt was not possible to determine if the Issuer Certificate has been revoked.
Bad_CertificateIssuerUseNotAllowed The Issuer Certificate may not be used for the requested operation.
Bad_CertificateIssuerTimeInvalidAn Issuer Certificate has expired or is not yet valid.
Bad_CertificateIssuerRevokedThe Issuer Certificate has been revoked.
Bad_CertificateInvalidThe Certificate provided as a parameter is not valid.
Bad_CertificateRevocationUnknownIt was not possible to determine if the Certificate has been revoked.
Bad_CertificateRevokedThe Certificate has been revoked.
Bad_CertificateTimeInvalidThe Certificate has expired or is not yet valid.
Bad_CertificateUriInvalidThe URI specified in the ApplicationDescription does not match the URI in the Certificate.
Bad_CertificateUntrustedThe Certificate is not trusted.
Bad_CertificateUseNotAllowedThe Certificate may not be used for the requested operation.
Bad_CommunicationErrorA low level communication error occurred.
Bad_DataTypeIdUnknownThe ExtensionObject cannot be (de)serialized because the data type id is not recognized.
Bad_DecodingErrorDecoding halted because of invalid data in the stream.
Bad_EncodingErrorEncoding halted because of invalid data in the objects being serialized.
Bad_EncodingLimitsExceededThe message encoding/decoding limits imposed by the Communication Stack have been exceeded.
Bad_IdentityTokenInvalidThe user identity token is not valid.
Bad_IdentityTokenRejectedThe user identity token is valid but the Server has rejected it.
Bad_InternalErrorAn internal error occurred as a result of a programming or configuration error.
Bad_InvalidArgument

One or more arguments are invalid.

Each service defines parameter-specific StatusCodes and these StatusCodes shall be used instead of this general error code. This error code shall be used only by the Communication Stack and in services where it is defined in the list of valid StatusCodes for the service.

Bad_InvalidStateThe operation cannot be completed because the object is closed, uninitialized or in some other invalid state.
Bad_InvalidTimestampThe timestamp is outside the range allowed by the Server.
Bad_LicenseExpiredThe UA Server requires a license to operate in general or to perform a service or operation, but existing license is expired
Bad_LicenseLimitsExceededThe UA Server has limits on number of allowed operations / objects, based on installed licenses, and these limits where exceeded.
Bad_LicenseNotAvailableThe UA Server does not have a license which is required to operate in general or to perform a service or operation.
Bad_NonceInvalidThe nonce does appear to be not a random value or it is not the correct length.
Bad_NothingToDo

No processing could be done because there was nothing to do.

For Service level results the code is used if the Client passed a list of operations with no elements.

Bad_OutOfMemoryNot enough memory to complete the operation.
Bad_RequestCancelledByClientThe request was cancelled by the Client.
Bad_RequestTooLargeThe request message size exceeds limits set by the Server.
Bad_ResponseTooLargeThe response message size exceeds limits set by the Client or Server.
Bad_RequestHeaderInvalidThe header for the request is missing or invalid.
Bad_ResourceUnavailableAn operating system resource is not available.
Bad_SecureChannelIdInvalidThe specified secure channel is no longer valid.
Bad_SecurityChecksFailedAn error occurred while verifying security.
Bad_SecurityPolicyRejectedThe security policy does not meet the requirements set by the Server.
Bad_ServerHaltedThe Server has stopped and cannot process any requests.
Bad_ServerNotConnectedThe operation could not complete because the Client is not connected to the Server.
Bad_ServerTooBusy

The Server does not have the resources to process the request at this time.

This can be caused by a general overload of the Server or an overload by the Client that receives the result code.

Bad_ServerUriInvalidThe Server URI is not valid.
Bad_ServiceUnsupportedThe Server does not support the requested service.
Bad_SessionIdInvalidThe Session id is not valid.
Bad_SessionClosedThe Session was closed by the Client.
Bad_SessionNotActivatedThe Session cannot be used because ActivateSession has not been called.
Bad_ShutdownThe operation was cancelled because the application is shutting down.
Bad_SubscriptionIdInvalid

The Subscription id is not valid.

The Subscription id is not known or is not valid in the context of the Session used to call the Subscription related Service.

Bad_TimeoutThe operation timed out.
Bad_TimestampsToReturnInvalidThe timestamps to return parameter is invalid.
Bad_TooManyOperationsThe request could not be processed because it specified too many operations.
Bad_UnexpectedErrorAn unexpected error occurred.
Bad_UnknownResponseAn unrecognized response was received from the Server.
Bad_UserAccessDeniedUser does not have permission to perform the requested operation.
Bad_ViewIdUnknownThe view id does not refer to a valid view Node.
Bad_ViewTimestampInvalidThe view timestamp is not available or not supported.
Bad_ViewParameterMismatchInvalidThe view parameters are not consistent with each other.
Bad_ViewVersionInvalidThe view version is not available or not supported.

Table 179 defines the common StatusCodes for all operation level results used in more than one service. It does not provide a complete list. OPC 10000-6 maps the symbolic names to a numeric value and provides a complete list of StatusCodes including codes defines in other parts. The common Service result codes can be also contained in the operation level.

Table 179 – Common Operation Level Result Codes
Symbolic Id Description
Good_ClampedThe value written was accepted but was clamped.
Good_OverloadSampling has slowed down due to resource limitations.
UncertainThe value is uncertain but no specific reason is known.
BadThe value is bad but no specific reason is known.
Bad_AttributeIdInvalidThe attribute is not supported for the specified node.
Bad_BrowseDirectionInvalidThe browse direction is not valid.
Bad_BrowseNameInvalidThe browse name is invalid.
Bad_ContentFilterInvalidThe content filter is not valid.
Bad_ContinuationPointInvalid

The continuation point provided is no longer valid.

This status is returned if the continuation point was deleted or the address space was changed between the browse calls.

Bad_DataEncodingInvalidThe data encoding is invalid.
Bad_DataEncodingUnsupportedThe Server does not support the requested data encoding for the node.
Bad_EventFilterInvalidThe event filter is not valid.
Bad_FilterNotAllowedA monitoring filter cannot be used in combination with the attribute specified.
Bad_FilterOperandInvalidThe operand used in a content filter is not valid.
Bad_HistoryOperationInvalidThe history details parameter is not valid.
Bad_HistoryOperationUnsupportedThe Server does not support the requested operation.
Bad_IndexRangeInvalidThe syntax of the index range parameter is invalid.
Bad_IndexRangeNoDataNo data exists within the range of indexes specified.
Bad_MonitoredItemFilterInvalidThe monitored item filter parameter is not valid.
Bad_MonitoredItemFilterUnsupportedThe Server does not support the requested monitored item filter.
Bad_MonitoredItemIdInvalidThe monitoring item id does not refer to a valid monitored item.
Bad_MonitoringModeInvalidThe monitoring mode is invalid.
Bad_NoCommunication

Communication with the data source is defined, but not established, and there is no last known value available.

This status/sub-status is used for cached values before the first value is received or for Write and Call if the communication is not established.

Bad_NoContinuationPointsThe operation could not be processed because all continuation points have been allocated.
Bad_NodeClassInvalidThe node class is not valid.
Bad_NodeIdInvalidThe syntax of the node id is not valid or refers to a node that is not valid for the operation.
Bad_NodeIdUnknownThe node id refers to a node that does not exist in the Server address space.
Bad_NoDeleteRightsThe Server will not allow the node to be deleted.
Bad_NodeNotInViewThe nodesToBrowse is not part of the view.
Bad_NotFoundA requested item was not found or a search operation ended without success.
Bad_NotImplementedRequested operation is not implemented.
Bad_NoValue

There is no value available.

This status is also used if a Variable is created and no default value or no initial value is available.

Bad_NotReadableThe access level does not allow reading or subscribing to the Node.
Bad_NotSupportedThe requested operation is not supported.
Bad_NotWritableThe access level does not allow writing to the Node.
Bad_ObjectDeletedThe Object cannot be used because it has been deleted.
Bad_OutOfRangeThe value was out of range.
Bad_ReferenceTypeIdInvalidThe reference type id does not refer to a valid reference type node.
Bad_SecurityModeInsufficient

The SecurityPolicy and/or MessageSecurityMode do not match the Server requirements to complete the operation.

For example, a user may have the right to receive the data but the data can only be transferred through an encrypted channel with an appropriate SecurityPolicy.

Bad_SourceNodeIdInvalidThe source node id does not refer to a valid node.
Bad_StructureMissingA mandatory structured parameter was missing or null.
Bad_TargetNodeIdInvalidThe target node id does not refer to a valid node.
Bad_TypeDefinitionInvalidThe type definition node id does not reference an appropriate type node.
Bad_TypeMismatchThe value supplied for the attribute is not of the same type as the attribute's value.
Bad_WaitingForInitialData

Waiting for the Server to obtain values from the underlying data source.

After creating a MonitoredItem or after setting the MonitoringMode from DISABLED to REPORTING or SAMPLING, it may take some time for the Server to actually obtain values for these items. In such cases the Server can send a Notification with this status prior to the Notification with the first value or status from the data source.