Re: [Koha] Error returning a book

2017-08-22 Thread Luis Moises Rojas
Data problems Some of your tables have problems with their auto_increment values which may lead to data loss. *You should not ignore this warning*. The problem is that InnoDB does not keep auto_increment across SQL server restarts (it is only set in memory). So on server startup the

Re: [Koha] Error returning a book

2017-08-22 Thread vinod mishra
Is it still showing any number in about page? if so than you may delete it and try again. With Regards, Vinod Kumar Mishra, Assistant Librarian, Biju Patnaik Central Library (BPCL), NIT Rourkela, Sundergadh-769008, Odisha, India. Mob:91+9439420860 Website: http://mishravk.com/ ORCID ID:

Re: [Koha] Error returning a book

2017-08-22 Thread Luis Moises Rojas
First, thanks to all of you. We have done everything https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix says: But will still have the error: The message is The item has not been checked in due to a configuration issue in your system. You must ask an administrator to take a look at the

Re: [Koha] Error returning a book

2017-08-22 Thread Chrispin Simasiku Sitali
Furthermore, thanks to Joy Nelson, use the following; You will need direct access to the database to correct this. Login to mysql (or mariadb) and run the following query: delete from deletedborrowers where borrowernumber in (52,78); The above query will take care of those duplicated ids. Also

Re: [Koha] Error returning a book

2017-08-22 Thread Luis Moises Rojas
Is this error the same: Some of your tables have problems with their auto_increment values which may lead to data loss. *You should not ignore this warning*. The problem is that InnoDB does not keep auto_increment across SQL server restarts (it is only set in memory). So on server startup the

Re: [Koha] Error returning a book

2017-08-22 Thread Luis Moises Rojas
Hi Chrispin: Do we have to deleted manually? Libre de virus. www.avast.com

Re: [Koha] Error returning a book

2017-08-22 Thread Chrispin Simasiku Sitali
Its because of duplicate ids in your database. Please log in as administrator (Staff Client of course) and go to About Koha. You will find a list of errors. Those duplicate ids need to be deleted Sitali CS On 22 August 2017 at 17:49, Luis Moises Rojas wrote: > Hello