Do you have a mapping defined for cardnumber? Is the corresponding LDAP field always populated and unique? If not, remove the mapping for it. It sounds like you don't have an accurate <mapping> for your LDAP schema. --Joe On Thu, Feb 19, 2009 at 12:13 PM, Barry Cannon <bc@interleaf.ie> wrote:
Hi All,
I am still battling through getting Koha talking to LDAP. I have managed to get so far but the latest problem is shown below in the apache logs. The problem is the cardnumber field is being completely ignored on the replication. Other LDAP attributes come across fine but we can only manage one sync and the rest fail with the error below. This is obviously because the cardnumber has to be unique and the next patron to import is also '' so duplication occurs.
Also, when a user logs into OPAC all the Parton Details attributes are blank.
[Thu Feb 19 12:55:15 2009] opac-user.pl: DBD::mysql::st execute failed: Duplicate entry ' ' for key 2 at /usr/share/koha/lib/C4/Members.pm line 769, <DATA> line 466.
AUTH_3: no results for userid='mmg', cardnumber=''.
[Thu Feb 19 12:55:15 2009] opac-user.pl: PARAM:LOOP:next_loop:hash pointer was expected but not found at /usr/local/lib/perl/5.8.8/HTML/Template/Pro.pm line 191, <DATA> line 466.
[Thu Feb 19 12:59:19 2009] opac-user.pl: DBD::mysql::st execute failed: Duplicate entry ' ' for key 2 at /usr/share/koha/lib/C4/Members.pm line 769, <DATA> line 466.
AUTH_3: no results for userid='mmg', cardnumber=''.
Can anyone help?
Regards
Barry Cannon
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha