Log-File: "checkSynchronization' does not exist"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • lucakuehne
    Senior Member
    • Feb 2016
    • 195

    Log-File: "checkSynchronization' does not exist"

    Hi

    Since I updated EspoCRM to the newest version, a message reugarly pops up saying "Error 404: Not found"
    Also in the logs there are many of these entries:
    Code:
    [2019-07-22 12:46:03] Espo.ERROR: (404) Action GET 'checkSynchronization' does not exist in controller 'MailChimp'.; GET /api/v1/MailChimp/action/checkSynchronization; line: 129, file: C:\xampp\htdocs\application\Espo\Core\ControllerManager.php [] []
    [2019-07-22 12:46:18] Espo.ERROR: (404) Action GET 'checkSynchronization' does not exist in controller 'MailChimp'.; GET /api/v1/MailChimp/action/checkSynchronization; line: 129, file: C:\xampp\htdocs\application\Espo\Core\ControllerManager.php [] []
    [2019-07-22 12:46:33] Espo.ERROR: (404) Action GET 'checkSynchronization' does not exist in controller 'MailChimp'.; GET /api/v1/MailChimp/action/checkSynchronization; line: 129, file: C:\xampp\htdocs\application\Espo\Core\ControllerManager.php [] []
    [2019-07-22 12:46:48] Espo.ERROR: (404) Action GET 'checkSynchronization' does not exist in controller 'MailChimp'.; GET /api/v1/MailChimp/action/checkSynchronization; line: 129, file: C:\xampp\htdocs\application\Espo\Core\ControllerManager.php [] []
    [2019-07-22 12:47:04] Espo.ERROR: (404) Action GET 'checkSynchronization' does not exist in controller 'MailChimp'.; GET /api/v1/MailChimp/action/checkSynchronization; line: 129, file: C:\xampp\htdocs\application\Espo\Core\ControllerManager.php [] []
    [2019-07-22 12:47:19] Espo.ERROR: (404) Action GET 'checkSynchronization' does not exist in controller 'MailChimp'.; GET /api/v1/MailChimp/action/checkSynchronization; line: 129, file: C:\xampp\htdocs\application\Espo\Core\ControllerManager.php [] []
    I guess those are deprecated functions from an old version of EspoCRM. But why are they still there and how can I fix this?

    Kind regards
    Luca Kühne
  • Maximus
    Senior Member
    • Nov 2018
    • 2731

    #2
    Hello.
    From what version you have upgraded? What version of MailChimp pack do you have?

    Comment

    • lucakuehne
      Senior Member
      • Feb 2016
      • 195

      #3
      Originally posted by Maximus
      From what version you have upgraded?
      I'm not quite sure anymore.
      But I think I upraded form 5.5.3 to 5.6.4 for EspoCRM itself.
      And I also upgraded from the old Advanced Pack (which included Mailchimp) To the newest Advanced-Pack and newest Mailchimp-Pack

      Originally posted by Maximus
      What version of MailChimp pack do you have?
      Version 1.0.1
      Last edited by lucakuehne; 07-22-2019, 02:07 PM.

      Comment

      • yuri
        Member
        • Mar 2014
        • 8440

        #4
        Please try the following:

        1. Uninstall Advanced Pack.
        2. Remove directory application/Espo/Modules/Advanced/
        3. Install Advanced Pack 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

        • lucakuehne
          Senior Member
          • Feb 2016
          • 195

          #5
          Hi yuri

          Thanks for your response.. Sadly I got stuck on the last step, because I can't download the latest version. It seems like your portal is broken. When I want to download the Advanced pack or Mailchimp Integration I get the following screen:
          Click image for larger version  Name:	image_3444.png Views:	1 Size:	22.5 KB ID:	50324

          I also get the following error in the console:
          Click image for larger version  Name:	EspoCRM Portal Error.PNG Views:	1 Size:	63.9 KB ID:	50325
          Last edited by lucakuehne; 07-23-2019, 06:18 AM.

          Comment

          • Maximus
            Senior Member
            • Nov 2018
            • 2731

            #6
            Hello.
            We have fixed it. Please try again. If it will not work please clear a cache of your web browser and try again. Ctrl + F5 combination may not clear cache deeply, so we suggest you to clear it with your browser advanced settings.

            Comment

            • lucakuehne
              Senior Member
              • Feb 2016
              • 195

              #7
              Hi Maximus

              I was able to successfully install the advanced pack as well as the mailchimp integration.
              But I still get these errors in the logs...

              Comment

              • yuri
                Member
                • Mar 2014
                • 8440

                #8
                Hi Luca,

                Could you please check whether you have the file "application/Espo/Modules/MailChimp/Resources/metadata/app/popupNotifications.json" existing. If you have this file, then:

                1. Uninstall Mail Chimp extension.
                2. Remove directory application/Espo/Modules/MailChimp/
                3. Install Mail Chimp extension again.

                Note, that the error you have is not critical.
                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

                • lucakuehne
                  Senior Member
                  • Feb 2016
                  • 195

                  #9
                  Originally posted by yurikuzn
                  Could you please check whether you have the file "application/Espo/Modules/MailChimp/Resources/metadata/app/popupNotifications.json" existing.
                  No, not even the folder "application/Espo/Modules/MailChimp/Resources/metadata/app/" is existing...

                  Originally posted by yurikuzn
                  Note, that the error you have is not critical.
                  I hope so.
                  But nonetheless it makes my users insecure and is annoying. Also it floods the whole logs.....
                  Last edited by lucakuehne; 07-23-2019, 11:25 AM.

                  Comment

                  • yuri
                    Member
                    • Mar 2014
                    • 8440

                    #10
                    Weird. Could you try to search in files contents

                    Code:
                    grep -R 'checkSynchronization' /path/to/espocrm/
                    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

                    • lucakuehne
                      Senior Member
                      • Feb 2016
                      • 195

                      #11
                      yuri

                      Your code was for Linux, but I did the same with
                      Code:
                      Get-ChildItem -Path <pathToEspocrm>\* -Recurse -Exclude *.log | Select-String -Pattern 'checkSynchronization'
                      But there was no result...

                      Comment

                      • yuri
                        Member
                        • Mar 2014
                        • 8440

                        #12
                        Do you have new errors "(404) Action GET 'checkSynchronization' does not exist in controller 'MailChimp'" logged ?

                        Maybe old file or metadata cached somehow.
                        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

                        • lucakuehne
                          Senior Member
                          • Feb 2016
                          • 195

                          #13
                          Hi Yuri

                          You are right.
                          After the changes there where still some entries, but after a while the error was not logged again.

                          Thank you! :-)

                          Comment

                          Working...