Grouper Users - Open Discussion List

[Tom Zeller <>]

You are running 2.x, correct ?

Run with -printRequests or -logSpml and increase the logging level in
log4j.properties :

 # LDAPPC[NG]
 log4j.logger.edu.internet2.middleware.ldappc = DEBUG
 # vt-ldap, used by LDAPPC[NG]
 log4j.logger.edu.vt.middleware.ldap = DEBUG

We need the request to understand the failure response.

On Fri, Nov 4, 2011 at 12:03 PM, Klug, Lawrence 
<>
 wrote:
> Hi,
>
>
>
> We’re getting  into LDAP errors when running sync or buldSync operations –
> they seem to be related to schema or constrain violations.  Can anyone
> suggest a strategy for fixing?
>
>
>
> Thanks,
>
>
>
> Lawrence
>
>
>
> <ldappc:syncResponse>
>
>     <modifyResponse xmlns='urn:oasis:names:tc:SPML:2:0' status='failure'
> requestID='2011/11/04-09:46:31.263_Q4VPCJ0Q' error='customError'>
>
>       <errorMessage>[LDAP: error code 67 - Not Allowed On
> RDN]</errorMessage>
>
>     </modifyResponse>
>
>     <ldappc:id ID='etc:sysadmingroup'/>
>
>   </ldappc:syncResponse>
>
>
>
>   <ldappc:syncResponse>
>
>     <modifyResponse xmlns='urn:oasis:names:tc:SPML:2:0' status='failure'
> requestID='2011/11/04-09:46:31.275_Q4VPCJ0V' error='customError'>
>
>       <errorMessage>[LDAP: error code 19 - Constraint violation in
> modifications]</errorMessage>
>
>     </modifyResponse>
>
>     <ldappc:id
> ID='urn:mace:ucla.edu:ppid:person:037C906A66444DFBAA8C4DB08035D62E'/>
>
>   </ldappc:syncResponse>
>
>
>
> Lawrence Klug
>
> UCLA Middleware Services
>
> Office: 310 825-2061
>
> Cell: 818 667-2386
>
>