3.4.4.3.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 request contains a null or not present NtdsSettingsDN element.
The request contains an NtdsSettingsDN element containing at least one empty or null element.
The server!serverReference attribute on the parent of the nTDSDSA object specified by the GetADDomainControllerRequest/NtdsSettingsDN (section 3.4.4.3.2.3) input parameter element is not present or cannot be read due to the client lacking access rights to read the attribute. See sections 3.4.4.3.3.1.2, 3.4.4.3.3.1.5, 3.4.4.3.3.2.1, 3.4.4.3.3.2.3, 3.4.4.3.3.2.7, 3.4.4.3.3.2.8, 3.4.4.3.3.2.9, and 3.4.4.3.3.2.10.
No crossRef objects satisfy the requirements given in section 3.4.4.3.3.2.4 for populating the Forest element.
Then the server MUST return a SOAP fault with a GetADDomainControllerFault fault subcode. The fault detail SHOULD be as specified in the following table.
Field |
Value |
---|---|
[Code] |
soapenv:Sender |
[Subcode] |
GetADDomainControllerFault |
[Action] |
http://schemas.microsoft.com/2008/1/ActiveDirectory/Data/fault |
[Reason] |
The operation failed because of a bad parameter. |
[Detail] |
|