Export (0) Print
Expand All

3.4.4.6.8.1 Bad Parameter Error

If the client sends a request where any of the following is true:

  • The SOAP header (section 2.2.3.5) contains an empty, not present, invalid, null, or unknown Server element (section 3.1.4).

  • The SOAP header contains a Server element that specifies an AD LDS instance and the client is requesting to transfer (section 3.4.4.6.2.3.1) or seize (section 3.4.4.6.2.3.2) a FSMO role that the DC does not support.

Then the server MUST return a SOAP fault with a MoveADOperationMasterRoleFault fault subcode. The fault detail SHOULD be as specified in the following table.

Field

Value

[Code]

soapenv:Sender

[Subcode]

MoveADOperationMasterRoleFault

[Action]

http://schemas.microsoft.com/2008/1/ActiveDirectory/Data/fault

[Reason]

The operation failed because of a bad parameter.

[Detail]

<soapenv:Detail>
  <MoveADOperationMasterRoleFault
    xmlns="http://schemas.microsoft.com/2008/1/ActiveDirectory/CustomActions"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <ArgumentError>
      <Message>...</Message>
      <ParameterName>...</ParameterName>
      <ShortMessage>...</ShortMessage>
    </ArgumentError>
    <DirectoryError xsi:nil="true"></DirectoryError>
    <Error xsi:nil="true"></Error>
    <ShortError xsi:nil="true"></ShortError>
  </MoveADOperationMasterRoleFault>
</soapenv:Detail>
 
Show:
© 2015 Microsoft