Email send failed since upgrade to 5.4.4

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • khopper
    Senior Member
    • Sep 2017
    • 329
    #1

    Email send failed since upgrade to 5.4.4

    Getting errors in espo log (debug)
    [2018-10-30 19:47:11] Espo.ERROR: Workflow[59d27fa3dac63fbe9]: Action failed [sendEmail] with cid [0], details: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Pending-0' for key 'IDX_JOB_STATUS'. [] []
    [2018-10-30 19:47:11] Espo.DEBUG: Workflow\Actions: Start [sendEmail] with cid [1] for entity [Account, 5bd35b75e80c8b41d]. [] []
    [2018-10-30 19:47:11] Espo.ERROR: Workflow[59d27fa3dac63fbe9]: Action failed [sendEmail] with cid [1], details: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Pending-0' for key 'IDX_JOB_STATUS'. [] []
    Tags: None
    • yuri
      Member
      • Mar 2014
      • 8438
      #2
      Check whether `status` column of `job` table is a primary key. If yes -- make it not a primary key. `id` column should be a primary key.
      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

        Comment

        • khopper
          Senior Member
          • Sep 2017
          • 329
          #3
          no the status column is not primary. What is next?
          1 Photo

            Comment

            • yuri
              Member
              • Mar 2014
              • 8438
              #4
              Check whether IDX_JOB_STATUS index is unique. It should not be unique.
              If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

                Comment

                • khopper
                  Senior Member
                  • Sep 2017
                  • 329
                  #5
                  I can't send emails from aany workflow rules or via the stream when tagging anyone.
                  Should I just delete every record with this ID?
                  I also can't find anything in relation to this: key 'IDX_FBD8E0F8A71ECAB0'

                  [2018-10-31 13:19:19] Espo.DEBUG: WorkflowManager: End workflow [afterRecordSaved] for Entity [Account, 5bd74ed28a4324996]. [] []
                  [2018-10-31 13:20:01] Espo.ERROR: Uncaught Exception PDOException: "SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5a27077f955632a17' for key 'IDX_FBD8E0F8A71ECAB0'" at /var/www/espocrm/application/Espo/ORM/DB/Mapper.php line 739 {"exception":"[object] (PDOException(code: 23000): SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5a27077f955632a17' for key 'IDX_FBD8E0F8A71ECAB0' at /var/www/espocrm/application/Espo/ORM/DB/Mapper.php:739)"} []
                  [2018-10-31 13:21:01] Espo.ERROR: Uncaught Exception PDOException: "SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5a27077f955632a17' for key 'IDX_FBD8E0F8A71ECAB0'" at /var/www/espocrm/application/Espo/ORM/DB/Mapper.php line 739 {"exception":"[object] (PDOException(code: 23000): SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '5a27077f955632a17' for key 'IDX_FBD8E0F8A71ECAB0' at /var/www/espocrm/application/Espo/ORM/DB/Mapper.php:739)"} []
                  [2018-10-31 13:21:13] Espo.DEBUG: WorkflowManager: Start workflow [afterRecordSaved] for Entity [Account, 5bd8b9de09296b4a0]. [] []
                  1 Photo
                  Last edited by khopper; 10-31-2018, 01:52 PM.

                    Comment

                    • yuri
                      Member
                      • Mar 2014
                      • 8438
                      #6
                      It seems something happened with your environment. Did you upgrade anything apart from crm?

                      You can delete. But I think the problem will appear again.
                      If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

                        Comment

                        • khopper
                          #6.1
                          khopper commented
                          10-31-2018, 02:03 PM
                          Editing a comment
                          No, I did not upgrade anything else.
                        • khopper
                          Senior Member
                          • Sep 2017
                          • 329
                          #7
                          I managed to resolve this by setting and saving the `status` column as primary key and then undoing that change to the table `job`.

                            Comment

                            Previous template Next
                            Working...