Email Bug

[tanya]

Check apache log and espocrm logs, run rebuild.php file from espocrm directory in terminal

[deant]

From apache error log...
[Thu May 04 09:27:35.169322 2017] [:error] [pid 1740:tid 932] [client 192.168.1.179:1258] PHP Fatal error: Call to undefined method Espo\\Hooks\\Common\\NextNumber::afterSave() in C:\\Bitnami\\espocrm-4.2.7-0\\apps\\espocrm\\htdocs\\application\\Espo\\Core\ \HookManager.php on line 125, referer: http://sales.schoolpride.com/espocrm/
[Thu May 04 09:27:35.169322 2017] [:error] [pid 1740:tid 916] [client 192.168.1.179:1259] PHP Fatal error: Call to undefined method Espo\\Hooks\\Common\\NextNumber::afterSave() in C:\\Bitnami\\espocrm-4.2.7-0\\apps\\espocrm\\htdocs\\application\\Espo\\Core\ \HookManager.php on line 125, referer: http://sales.schoolpride.com/espocrm/

from espo log...
[2017-05-04 09:34:09] Espo.ERROR: Uncaught Exception PDOException: "SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Failed-2017-04-02 01:55:00' for key 'IDX_JOB_EXECUTE_TIME'" at C:\Bitnami\espocrm-4.2.7-0\apps\espocrm\htdocs\application\Espo\Core\Utils\ Cron\Job.php line 217 {"exception":"[object] (PDOException(code: 23000): SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Failed-2017-04-02 01:55:00' for key 'IDX_JOB_EXECUTE_TIME' at C:\\Bitnami\\espocrm-4.2.7-0\\apps\\espocrm\\htdocs\\application\\Espo\\Core\ \Utils\\Cron\\Job.php:217)"} []


Do you want me to run the rebuild.php from....
C:\Bitnami\espocrm-4.2.7-0\apps\espocrm\htdocs\data\.backup\upgrades\589a3b 4e6903c\files
or
C:\Bitnami\espocrm-4.2.7-0\apps\espocrm\htdocs
...I found a rebuild.php in both of these folders.

[tanya]

Hello
Check in database, if IDX_JOB_EXECUTE_TIME in job table is UNIQUE (has not be)
rebuild.php in espo dir (second one)

[deant]

Thank you for helping me with the rebuild.php. Successfully upgraded to 4.6.0
Our email issue still exists though.
Where would I find the value for IDX_JOB_EXECUTE_TIME?

[tanya]

It's a name one of indexes in `job` table in database. This index hasn't to be unique. Your error message says it's unique key and duplicates are there.

[murugappan]

Dear Dean,

The software design and structure is fantastic. Its much more simpler than Suitecrm which has deplorable documentation and lousy support. Too complicated too. It needs a real professional hacker to get Suitecrm to work. The support here for espocrm also sucks! Many of the questions are still left hanging, if not outdated. Seems like if they dont know the answer, they just keep quiet and hope for you to sign-up for pay-support. Sigh! How do i do that when the basics dont work??

Coming to your problem, we had the same. The email in the inbox say "body not fetched". After some struggling, we found out why. It was the cron job scheduler within espocrm. Its under admin function. You have to play around the "mail fetching" scheduler and get the right timing. What is happening is that, when the scheduler is to too quick, while one cron job is running and fetching, another one gets triggered by espocrm which goes for the same email from the external mailbox. Conflict happens and cron skips fetching the complete email.

This is what happen to us. So we retimed the scheduler and now runs well. You will hit the same snag with mass mailing as well. You would find partial mailing only. Suggestion break-up the target list into smaller packets.

Hope this helps.

[fancymedia]

Murugappan, can you share your cron settings? we tried several combinations but were unable to make it work. Thanks, Chris.