Password Filter Install Constraint Violation Name Reference is Invalid
(Doc ID 438093.1)
Last updated on AUGUST 30, 2023
Applies to:
Oracle Internet Directory - Version 10.1.4 to 10.1.4 [Release 10gR3]Information in this document applies to any platform.
This problem can occur on any platform.
Symptoms
Constraint Violation
The server side error is "The name reference is invalid"
This is an issue with the 10.1.4 Microsoft Active Directory (AD) Password filter.
Background: Our domain that we are installing this on is <HOSTNAME> (dn
DC=<DOMAIN_NAME2>,dc=<DOMAIN_NAME1>,dc=net). However, there are other domains in the AD
Controller.
While installing the prepAD.ldif failed with the following error:
(Aug 29, 2006 10:32:16 AM), Install, com.oracle.installshield.adpwd.ldapModify,
dbg, <WINDOWS_SYSTEMS_FOLDER>\oracle\ADPasswordFilter\prepAD.ldif
(Aug 29, 2006 10:32:16 AM), Install, com.oracle.installshield.adpwd.ldapModify,
err, in LDAPOperation
(Aug 29, 2006 10:32:16 AM), Install, com.oracle.installshield.adpwd.ldapModify,
err, [LDAP: error code 19 - 000020B5: AtrErr: DSID-031522A8, #1:
0: 000020B5: DSID-031522A8, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att
9030e (objectCategory)
]
We subsequently tried to load that ldif file with ldifde (Windows command line)
and received the following errors:
Connecting to "<HOSTNAME>"
Logging in as current user using SSPI
Importing directory from file "prepad.ldif"
Loading entries
1: OU=<OU_NAME>,DC=<DOMAIN_NAME1>,DC=<DOMAIN_NAME1>,DC=com
Entry DN: OU=<OU_NAME>,DC=<DOMAIN_NAME2>,DC=<DOMAIN_NAME1>,DC=com
changetype: add
Attribute 0)
distinguishedName:OU=<OU_NAME>,DC=<DOMAIN_NAME2>,DC=<DOMAIN_NAME1>,DC=com
Attribute 1) instanceType:4
Attribute 2) name:<OU_NAME>
Attribute 3)
objectCategory:CN=Organizational-Unit,CN=Schema,CN=Configuration,DC=<DOMAIN_NAME1>,DC=com
Attribute 4) objectClass:organizationalUnit
Attribute 5) ou:<OU_NAME>
Add error on line 1: Constraint Violation
The server side error is "The name reference is invalid."
0 entries modified successfully.
An error has occurred in the program
ldapmodify produced a similar error.
The problem is that that the ldif file references the following object
category:CN=Organizational-Unit,CN=Schema,CN=Configuration,DC=<DOMAIN_NAME2>,DC=<DOMAIN_NAME1>,DC=com
when in actuality, our object category is:
CN=Organizational-Unit,CN=Schema,CN=Configuration,DC=<DOMAIN_NAME1>,DC=com
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |