3.3.4.4.8.4 Bad Naming Context Error
Article
10/30/2020
2 minutes to read
Is this page helpful?
In this article
If the client sends a request with the PartitionDN element
specifying a nonexistent NC , then
the server MUST return a SOAP fault with a GetADPrincipalGroupMembershipFault
fault subcode. The fault detail SHOULD be as specified in the following table.
Field
Value
[Code]
soapenv:Sender
[Subcode]
GetADPrincipalGroupMembershipFault
[Action]
http://schemas.microsoft.com/2008/1/ActiveDirectory/Data/fault
[Reason]
Active Directory
returned an error processing the operation.
[Detail]
<soapenv:Detail>
<GetADPrincipalGroupMembershipFault
xmlns="http://schemas.microsoft.com/2008/1/ActiveDirectory/CustomActions"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ArgumentError xsi:nil="true"></ArgumentError>
<DirectoryError>
<ErrorCode>-2147016656</ErrorCode>
<ExtendedErrorMessage>...</ExtendedErrorMessage>
<MatchedDN>...</MatchedDN>
<Message>...</Message>
<Referral xmlns:b=http://schema.microsoft.com/2003/10/Serialization/Arrays></Referral>
<ShortMessage>...</ShortMessage>
<Win32ErrorCode>-2147016656</Win32Errorcode>
</DirectoryError>
<Error i:nil="true"></Error>
<ShortError i:nil="true"></ShortError>
</GetADPrincipalGroupMembershipFault>
</soapenv:Detail>