Posts

Showing posts from July, 2018

DDL sql execution error while upgrading from Moodle 3.4 to Moodle 3.5.1+ (SOLVED).

Here is the solution to  DDL sql execution error  ,while upgrading the Moodle 3.4 to Moodle 3.5.1+. The following is the copy of the error. Upgrading to new version search_simpledb DDL sql execution error More information about this error × Debug info:  Table 'mdl_search_simpledb_index' already exists CREATE TABLE mdl_search_simpledb_index ( id BIGINT(10) NOT NULL auto_increment, docid VARCHAR(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', itemid BIGINT(10) NOT NULL, title LONGTEXT COLLATE utf8mb4_unicode_ci, content LONGTEXT COLLATE utf8mb4_unicode_ci, contextid BIGINT(10) NOT NULL, areaid VARCHAR(255) COLLATE utf8mb4_unicode_ci NOT NULL DEFAULT '', type TINYINT(1) NOT NULL, courseid BIGINT(10) NOT NULL, owneruserid BIGINT(10), modified BIGINT(10) NOT NULL, userid BIGINT(10), description1 LONGTEXT COLLATE utf8mb4_unicode_ci, description2 LONGTEXT COLLATE utf8mb4_unicode_ci, CONSTRAINT PRIMARY KEY (id) , KEY mdl_searsimpinde_o

Auto increment problem in Koha. How to fix the Koha auto increment problem? When you check-in a book if you get error message "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 about page and search for the "data problems" section". Then the issue is with Koha auto increment.

Image
 How to fix the Koha auto increment problem? When you check-in a book if you get error message "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 about page and search for the "data problems" section". Then the issue is with Koha auto increment. Check the detailed information regarding the issue in Koha, go to About Koha -> System Information. You will see the issue as in the screenshot below: Fix or solution to the issue: First clean up the incorrect data records. To do this first log on to the koha server and then log into the mysql:            sudo mysql -u root -p (Note: koha_library = Database Name)           use koha_library;   Now delete all the data that is corrupted from respective database tables with the delete command. The IDs of the corrupted items can be copied from the System Information : MariaDB[koha_library]> DELETE FROM deletedbiblio WH

ACTION_FAILED:OU_INVALID: Solution for GoogleApps bulk user upload issue, username@domainname.com:ACTION_FAILED:OU_INVALID. This error is because you have not specified the Org Unit Path properly.

To upload bulk users to GoogleApps, you will require a following required fileds, other fields are optional:-               First Name               Last Name               Email Address               Password               Org Unit Path What is 'Org Unit Path'? This field was not their earlier. This is the path to place users in an organizational unit. For example if your domain has different organization unit like , staff, students, guest etc.. then the Org Unit Path would be just :  /