From Dolibarr ERP CRM Wiki
Revision as of 09:25, 2 October 2018 by Yves.brungard (talk | contribs) (mix of collations)
Jump to navigation Jump to search

This page will list all the common technical problems you can run into.

If you run into a problem, the first step is to activate the Syslog module, then to redo the steps that leads you to a bug, and then check the log file residing at /documents/dolibarr.log

Dolibarr ask my login or password each time I click on a new link

You PHP system to store Dolibarr session is probably no more working.

Go into home - system info - php

What value do you have for parameter "session.save_handler" ?

If it is files, take a look at parameter "session.save_path". Its value is a directory path. Check your web server can read and write into this directory. Check also there is enough free space onto disk.

I can't approve a proposal/invoice/order/any other module

When you approve a document, Dolibarr will rename the folders and all the documents that belonged to the temporary document into the final one.

In most cases, the validation problems arise when Dolibarr tries to rename, and can be caused by:

  • A wrong permission for the /documents/ folder, so that Dolibarr can't rename the folder. If that's the case, you should have in your syslog something like:
ERROR user fiche Interfaces::run_triggers action=ORDER_SUPPLIER_VALIDATE Files found: 6, Files launched: 5, Done: 0, Failed: 1
ERROR user fiche CommandeFournisseur::valid 
DEBUG user fiche ROLLBACK Transaction
  • A wrong custom numerotation system: if you use illegal characters for the filesystem (like "/"), this will crash whenever you'll try to validate your document since it won't be able to use this illegal character in the renaming. Try to disable your current custom numerotation system and enable the default one temporarily to see if this fixes the issue.

I encounter a DB_ERROR message

Run the /install/repair.php page. This page can takes several minutes to run. Don't forget to run a backup first.

What repair can do :

  • Run repair SQL file.
  • Search list of fields declared and list of fields created into databases, then create fields missing
  • Clean data into ecm_directories table
  • Move logos to correct new directory
  • Rebuild thumbs for product files
  • Check and clean linked elements
  • Check orphelins menus
  • Run purge of directory
  • Check and clean linked elements
  • Clean data into const when files of module were removed without being

To operate, the page should be opened with at least one command:

  • /install/repair.php?standard=confirmed
  • /install/repair.php?clean_linked_elements=confirmed
  • /install/repair.php?restore_thirdparties_logos=confirmed
  • /install/repair.php?clean_menus=confirmed
  • /install/repair.php?clean_orphelin_dir=confirmed
  • /install/repair.php?clean_product_stock_batch=confirmed
  • /install/repair.php?set_empty_time_spent_amount=confirmed
  • /install/repair.php?rebuild_product_thumbs=confirmed
  • /install/repair.php?force_disable_of_modules_not_found=confirmed
  • /install/repair.php?clean_perm_table=confirmed
  • /install/repair.php?force_utf8_on_tables=confirmed for Mysql only, when Illegal mix of collations (utf8_general_ci,IMPLICIT) and (utf8_unicode_ci,IMPLICIT) for operation '='

My problem is not in the list

If the solution for your problem couldn't be found in this page, please keep in a safe place a maximum of detailed informations (like the dolibarr log, php version, database type and version, dolibarr's version, Apache's log...), and seek help at the following organisms: