Share via

3.4.4.1.8.1 Bad Parameter Error

  • Article

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, unknown, or null Server element (section 3.1.4).

  • The request contains an empty, not present, or null DistinguishedName element.

  • The request contains an empty or not present FeatureId element.

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

Field

Value

[Code]

soapenv:Sender

[Subcode]

ChangeOptionalFeatureFault

[Action]

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

[Reason]

The operation failed because of a bad parameter.

[Detail]

 
 <soapenv:Detail>
     <ChangeOptionalFeatureFault
       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>
     </ChangeOptionalFeatureFault>
 </soapenv:Detail>