Asynchronous Service Operation Status of Done with Error Link Enabled
The status for a service operation typically displays Error in the Service Operations Monitor when the system cannot create a publication or subscription contract or if there is some other framework error (for example a SQL error).
However, there are situations when the system displays a status of Done for an operation instance, publication contract, or subscription contract, yet also displays an Error link indicating that it encountered a problem during processing.
This can occur when:
-
Attempting to publish a service operation that contains segmented messages to a node that is not segment aware.
-
The routing on a publication contract is inactive.
-
There is no service operation handler for a subscription contract.
-
And so on.
The system sets the status for an operation instance, publication contract, or subscription contract to Done when it has successfully created the instance or contract. In each of the cases described in the list, the system encounters an error after it has evaluated the transaction and has successfully created the operation instance or contract. The system therefore displays an Error link that you can use to access the corresponding error message. The system does not send the service operation until the error is corrected.
The following table lists the pages where you can access an Error link should any of these situations occur:
| Type | Error Link Location |
|---|---|
|
Operation instance |
Asynchronous Services – Operation Instances page. ( and click the Operation Instances tab.) |
|
Publication contract |
Asynchronous Details page. (.) |
|
Subscription contract |
Asynchronous Details page. (.) |