Error 500: Error while rebuilding database. See log file for details.

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • MediaBerg
    replied
    Works! Great Maximus. Thanks!!!!

    Leave a comment:


  • MediaBerg
    replied
    Do you mean this one?
    And is this solution just for company (Firma) or all others entities as well?

    Leave a comment:


  • Maximus
    replied
    I am pretty sure that this error is caused by bad changes in custom. Try to check this "Column 'description' cannot be part of FULLTEXT". Did you customized it? Check your JSON syntax.

    Leave a comment:


  • MediaBerg
    replied
    I've tried to create a view custom fields in the company section. #Admin/fieldManager/scope=Account. ( Administration » Entität Manager » Firma » Felder)

    Add mainly textboxes.

    Some of them work. All others not. Always the same error Error 500: Error while rebuilding database. See log file for details.

    I installed espo on a shared server
    Error messages whilst setup:
    max_execution_time 30 Fail (180 is recommended)
    max_input_time 60 Fail (180 is recommended)
    memory_limit 128M Fail (256M is recommended)
    all other success.

    Leave a comment:


  • Maximus
    replied
    Have you created some custom fields or change something in Espo directories before you faced this error? Do you use Espo on the cloud?

    Leave a comment:


  • MediaBerg
    replied
    Hi Maximus,

    thanks for your quick reply. Do have a hint for a not database-geek?

    Thanks,
    Andreas

    Leave a comment:


  • Maximus
    replied
    Hello,
    hope this will be helpful https://stackoverflow.com/questions/...fulltext-index

    Leave a comment:


  • MediaBerg
    replied
    Hi Tanya,

    same problem with version 5.5.6.

    Here is the log:
    [2019-03-05 08:30:41] Espo.ALERT: Rebuild database fault: PDOException: SQLSTATE[HY000]: General error: 1283 Column 'description' cannot be part of FULLTEXT index in/mywebsitename.de/crm/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php:699 Stack trace: #0/mywebsitename.de/crm/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(699): PDO->query('CREATE FULLTEXT...') #1/mywebsitename.de/crm/application/Espo/Core/Utils/Database/Schema/Schema.php(196): Doctrine\DBAL\Connection->executeQuery('CREATE FULLTEXT...') #2/mywebsitename.de/crm/application/Espo/Core/DataManager.php(95): Espo\Core\Utils\Database\Schema\Schema->rebuild('Account') #3/mywebsitename.de/crm/application/Espo/Core/DataManager.php(62): Espo\Core\DataManager->rebuildDatabase('Account') #4/mywebsitename.de/crm/application/Espo/Controllers/FieldManager.php(71): Espo\Core\DataManager->rebuild('Account') #5/mywebsitename.de/crm/application/Espo/Core/ControllerManager.php(143): Espo\Controllers\FieldManager->postActionCreate(Array, Object(stdClass), Object(Slim\Http\Request), Object(Slim\Http\Response)) #6/mywebsitename.de/crm/application/Espo/Core/ControllerManager.php(159): Espo\Core\ControllerManager->processRequest(Object(Espo\Controllers\FieldManag er), 'create', Array, Object(stdClass), Object(Slim\Http\Request), Object(Slim\Http\Response)) #7/mywebsitename.de/crm/application/Espo/Core/Application.php(281): Espo\Core\ControllerManager->process('FieldManager', 'create', Array, '{"type":"varcha...', Object(Slim\Http\Request), Object(Slim\Http\Response)) #8 [internal function]: Espo\Core\Application->Espo\Core\{closure}() #9/mywebsitename.de/crm/vendor/slim/slim/Slim/Slim.php(1210): call_user_func_array(Object(Closure), Array) #10/mywebsitename.de/crm/vendor/slim/slim/Slim/Slim.php(1356): Slim\Slim->applyHook('slim.before.dis...') #11/mywebsitename.de/crm/vendor/slim/slim/Slim/Middleware/Flash.php(85): Slim\Slim->call() #12/mywebsitename.de/crm/vendor/slim/slim/Slim/Middleware/MethodOverride.php(92): Slim\Middleware\Flash->call() #13/mywebsitename.de/crm/application/Espo/Core/Utils/Api/Auth.php(138): Slim\Middleware\MethodOverride->call() #14/mywebsitename.de/crm/application/Espo/Core/Utils/Api/Slim.php(125): Espo\Core\Utils\Api\Auth->call() #15/mywebsitename.de/crm/application/Espo/Core/Application.php(93): Espo\Core\Utils\Api\Slim->run() #16/mywebsitename.de/crm/api/v1/index.php(33): Espo\Core\Application->run() #17 {main} Next Doctrine\DBAL\DBALException: An exception occurred while executing 'CREATE FULLTEXT INDEX IDX_SYSTEM_FULL_TEXT_SEARCH ON `account` (name, description, billing_address_city, billing_address_street, billing_address_country, billing_address_postal_code)': SQLSTATE[HY000]: General error: 1283 Column 'description' cannot be part of FULLTEXT index in/mywebsitename.de/crm/vendor/doctrine/dbal/lib/Doctrine/DBAL/DBALException.php:91 Stack trace: #0/mywebsitename.de/crm/vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(702): Doctrine\DBAL\DBALException::driverExceptionDuring Query(Object(PDOException), 'CREATE FULLTEXT...', Array) #1/mywebsitename.de/crm/application/Espo/Core/Utils/Database/Schema/Schema.php(196): Doctrine\DBAL\Connection->executeQuery('CREATE FULLTEXT...') #2/mywebsitename.de/crm/application/Espo/Core/DataManager.php(95): Espo\Core\Utils\Database\Schema\Schema->rebuild('Account') #3/mywebsitename.de/crm/application/Espo/Core/DataManager.php(62): Espo\Core\DataManager->rebuildDatabase('Account') #4/mywebsitename.de/crm/application/Espo/Controllers/FieldManager.php(71): Espo\Core\DataManager->rebuild('Account') #5/mywebsitename.de/crm/application/Espo/Core/ControllerManager.php(143): Espo\Controllers\FieldManager->postActionCreate(Array, Object(stdClass), Object(Slim\Http\Request), Object(Slim\Http\Response)) #6/mywebsitename.de/crm/application/Espo/Core/ControllerManager.php(159): Espo\Core\ControllerManager->processRequest(Object(Espo\Controllers\FieldManag er), 'create', Array, Object(stdClass), Object(Slim\Http\Request), Object(Slim\Http\Response)) #7/mywebsitename.de/crm/application/Espo/Core/Application.php(281): Espo\Core\ControllerManager->process('FieldManager', 'create', Array, '{"type":"varcha...', Object(Slim\Http\Request), Object(Slim\Http\Response)) #8 [internal function]: Espo\Core\Application->Espo\Core\{closur... [] []
    [2019-03-05 08:30:41] Espo.ERROR: API [POST]:/Admin/fieldManager/:scope, Params:Array ( [scope] => Account ) , InputData: {"type":"varchar","required":false,"trim":true,"dy namicLogicVisible":null,"dynamicLogicRequired":nul l,"dynamicLogicReadOnly":null,"name":"shopsystem", "label":"Shopsystem","tooltipText":null,"isPersona lData":false,"inlineEditDisabled":false,"default": null,"maxLength":null,"options":[],"audited":false,"readOnly":false,"tooltip":fal se} - Error while rebuilding database. See log file for details. [] []
    [2019-03-05 08:30:41] Espo.ERROR: Display Error: Error while rebuilding database. See log file for details., Code: 500 URL: /crm/api/v1/Admin/fieldManager/Account [] []
    What can I do to add a few more entities to company.

    Leave a comment:


  • tanya
    replied
    Yes, and you won't be able even add new entity or fields....
    What if you install new instance and check, if it will work?

    Leave a comment:


  • sarunijus
    replied
    thanks, I also installed fresh copy of espocrm 4.8.2, imported database tables from the main, but situation is the same. So it means I won't be able to upgrade to newer version, right?

    Leave a comment:


  • tanya
    replied
    Sorry, no any idea

    Leave a comment:


  • sarunijus
    replied
    No prefixes in database tables..I've already tried this : Possible it helps https://github.com/espocrm/espocrm/issues/217, not working.

    Leave a comment:


  • tanya
    replied
    Attempting to upgrade from 4.5.0 to 4.5.1 The error is: [2017-04-30 14:41:38] Espo.ERROR: Fault to rebuild database schema. Details: Unknown database type

    do you have any prefixes in database tables?

    Leave a comment:


  • sarunijus
    replied
    Any more ideas, how can I fix database, Tanya? many thanks.

    Leave a comment:


  • sarunijus
    replied
    Yes, I cleared cache few times before running rebuild. Also logged out and logged in again.Server type: MariaDB, Server version: 10.0.33-MariaDB, PHP version: 7.1.7
    Last edited by sarunijus; 11-15-2017, 02:38 PM.

    Leave a comment:

Working...