Announcement

Collapse
No announcement yet.

Error 500 after Upgrade

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error 500 after Upgrade

    I have Upgrade EspoCRm to 7.5.5 and the Extensions Advanced Pack V3.05 + Sales Pack V1.2.2.
    If I add an offer now. The error message Error 500 is displayed.

    Before adding I deleted the log file.
    After adding the log file has the content:​

    [2023-08-08 05:43:37] ERROR: (42000) SQLSTATE[42000]: Syntax error or access violation: 1066 Not unique table/alias: 'quoteItem'; POST /Quote; line: 76, file: /var/www/html/application/Espo/ORM/Executor/DefaultSqlExecutor.php
    [2023-08-08 05:44:05] ERROR: JobManager: Failed job running, job '64d1d5e8b164c3e35'. Job CheckEmailAccounts 5fa14dcba4f024d50: [0] cannot login, user or password wrong /var/www/html/vendor/laminas/laminas-mail/src/Storage/Imap.php:243; at /var/www/html/application/Espo/Classes/Jobs/CheckEmailAccounts.php:61.
    [2023-08-08 05:44:06] ERROR: JobManager: Failed job running, job '64d1d5e8b304faea6'. Job CheckEmailAccounts 5fa14f4985eebf18e: [0] cannot login, user or password wrong /var/www/html/vendor/laminas/laminas-mail/src/Storage/Imap.php:243; at /var/www/html/application/Espo/Classes/Jobs/CheckEmailAccounts.php:61.
    [2023-08-08 05:44:15] ERROR: JobManager: Failed job running, job '64d1d5e8b164c3e35'. Job CheckEmailAccounts 5fa14dcba4f024d50: [0] cannot login, user or password wrong /var/www/html/vendor/laminas/laminas-mail/src/Storage/Imap.php:243; at /var/www/html/application/Espo/Classes/Jobs/CheckEmailAccounts.php:61.
    [2023-08-08 05:44:15] ERROR: JobManager: Failed job running, job '64d1d5e8b304faea6'. Job CheckEmailAccounts 5fa14f4985eebf18e: [0] cannot login, user or password wrong /var/www/html/vendor/laminas/laminas-mail/src/Storage/Imap.php:243; at /var/www/html/application/Espo/Classes/Jobs/CheckEmailAccounts.php:61.


  • #2
    Hi GLMSK2023,

    A similar issue was discussed in the following thread: https://forum.espocrm.com/forum/gene...t-unique-table.

    In this case, the error may be related to the relationships. As Yuri wrote in the thread I gave an example earlier, to prevent this issue from happening, the relation name (link name) should be different from the entity name.​

    Comment


    • #3
      Thanks this solve the Problem.

      Comment

      Working...
      X