3.4.4.2.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.

• The domainDNS!wellKnownObjects attribute on the domain NC root object is not present or cannot be read due to the client lacking access rights to read the attribute.  See sections 3.4.4.2.3.1.4, 3.4.4.2.3.1.5, 3.4.4.2.3.1.8, 3.4.4.2.3.1.17, 3.4.4.2.3.1.18, 3.4.4.2.3.2.1, 3.4.4.2.3.2.4, and 3.4.4.2.3.2.10.

• No crossRef objects satisfy the requirements given in sections 3.4.4.2.3.1.9, 3.4.4.2.3.1.13, and 3.4.4.2.3.2.3 for populating the Forest, NetBIOSName, and DNSRoot elements.

• If, during the processing of the request, the server fails to populate the ObjectClass or ObjectTypes elements of the ActiveDirectoryPartiton as per the processing rules documented in sections 3.4.4.2.3.2.6 and 3.4.4.2.3.2.8.

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

Field	Value
[Code]	soapenv:Sender
[Subcode]	GetADDomainFault
[Action]	http://schemas.microsoft.com/2008/1/ActiveDirectory/Data/fault
[Reason]	The operation failed because of a bad parameter.
[Detail]	<soapenv:Detail>    <GetADDomainFault      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>    </GetADDomainFault>  </soapenv:Detail>