Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Expand Minimize

2.2.1.5.17 Types of DFS Replication Errors

This section specifies errors that the server SHOULD choose to detect and return to the client as part of the error XML element. The server MAY also choose to ignore any error condition that is described in this section. The server MUST send a RefID that is defined in one of the following Error Parameters tables.

Some of the error conditions that are specified in this section are specific to the underlying DFSR implementation, and might therefore be inapplicable to other implementations of DFS Replication. If an error is different in another implementation of the DFS Replication service, such an error condition may be mapped to an implementation-specific error. The recommended way is to append the error code to the method name without any processing. If the error condition is inapplicable, the server SHOULD NOT include this error in the health report.<22>

Some of the errors described in this section include implementation-specific information about a failure in the form of an implementation-specific error code and an implementation-specific error string. The implementation MUST use these parameters to provide more information about the error.<23>

When the server detects any of the errors that are described in this section, it MUST add a new error element to the server element. The error element MUST have an id field that contains the value that is specified in the Error ID section for that error. The format of the error element is specified in section 2.2.1.5.16.

For each error message, the server MUST supply the listed number of parameters. For each parameter, the server MUST add the errorReferences element to the error element. The value of each parameter MUST be an XML string and SHOULD<24> correspond to that provided in the subsections of Types of DFS Replication Error, as specified in section 2.2.1.5.17. The client MUST NOT make any assumptions about the format of the data within the strings.

Show:
© 2015 Microsoft