CiviCRM Community Forums (archive)

I am running CiviCRM 4.2.8 and my scheduled event reminders do not send. The log shows the following error:

Summary
Finished execution of Scheduled reminders sender with result: Failure, Error message: DB Error: syntax error
Details
Parameters parsed (and passed to API method):
a:1:{s:7:"version";i:3;}
Full message:
Finished execution of Scheduled reminders sender with result: Failure, Error message: DB Error: syntax error

This issue (I think) is already referenced in these two posts:
http://forum.civicrm.org/index.php?topic=24918.0
http://forum.civicrm.org/index.php?topic=24918.0

I'm hoping it's been resolved by now, but even with some expert help from Hershel have been unable to diagnose.

Any suggestions would be greatly appreciated!

Dates are relative, which I see has caused problems for others in the past. I will enable debugging and see what the log shows. Thanks Hershel!

the bad query and backtrace should be under:

files/civicrm/ConfigAndLog/CiviCRM.LONG MD5 HASH HERE.log

lobo

Can you upgrade to CiviCRM 4.2.9 (or 4.3.1 latest) and check if it still replicates for you?

-Yashodha

ZenLax :

Can you do try to replicate the same on demo (http://drupal.demo.civicrm.org/)

The scheduled reminder condition that triggers the DB error

PS : We've released 4.3.3 earlier today.

-Yashodha

I made a fresh D7 site and installed this CiviCRM 4.3.3 DB onto it and ran the Scheduled reminders sender job manually and I see this in the log:

May 13 16:25:22  [info] $backTrace = #0 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/Error.php(751): CRM_Core_Error::backtrace("backTrace", TRUE)
#1 [internal function](): CRM_Core_Error::exceptionHandler(Object(DB_Error))
#2 /home/mrbohlax/www/dev/sites/all/modules/civicrm/packages/PEAR.php(931): call_user_func((Array:2), Object(DB_Error))
#3 /home/mrbohlax/www/dev/sites/all/modules/civicrm/packages/DB.php(969): PEAR_Error->PEAR_Error("DB Error: syntax error", -2, 16, (Array:2), "SELECT e.contact_id as contact_id, e.id as entity_id, 'civicrm_participant' a...")
#4 /home/mrbohlax/www/dev/sites/all/modules/civicrm/packages/PEAR.php(564): DB_Error->DB_Error(-2, 16, (Array:2), "SELECT e.contact_id as contact_id, e.id as entity_id, 'civicrm_participant' a...")
#5 /home/mrbohlax/www/dev/sites/all/modules/civicrm/packages/DB/common.php(1905): PEAR->raiseError(NULL, -2, NULL, NULL, "SELECT e.contact_id as contact_id, e.id as entity_id, 'civicrm_participant' a...", "DB_Error", TRUE)
#6 /home/mrbohlax/www/dev/sites/all/modules/civicrm/packages/DB/mysql.php(898): DB_common->raiseError(-2, NULL, NULL, NULL, "1064 ** You have an error in your SQL syntax; check the manual that correspon...")
#7 /home/mrbohlax/www/dev/sites/all/modules/civicrm/packages/DB/mysql.php(327): DB_mysql->mysqlRaiseError()
#8 /home/mrbohlax/www/dev/sites/all/modules/civicrm/packages/DB/common.php(1216): DB_mysql->simpleQuery("SELECT e.contact_id as contact_id, e.id as entity_id, 'civicrm_participant' a...")
#9 /home/mrbohlax/www/dev/sites/all/modules/civicrm/packages/DB/DataObject.php(2421): DB_common->query("SELECT e.contact_id as contact_id, e.id as entity_id, 'civicrm_participant' a...")
#10 /home/mrbohlax/www/dev/sites/all/modules/civicrm/packages/DB/DataObject.php(1613): DB_DataObject->_query("SELECT e.contact_id as contact_id, e.id as entity_id, 'civicrm_participant' a...")
#11 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/DAO.php(155): DB_DataObject->query("SELECT e.contact_id as contact_id, e.id as entity_id, 'civicrm_participant' a...")
#12 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/DAO.php(917): CRM_Core_DAO->query("SELECT e.contact_id as contact_id, e.id as entity_id, 'civicrm_participant' a...", TRUE)
#13 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/BAO/ActionSchedule.php(940): CRM_Core_DAO::executeQuery("SELECT e.contact_id as contact_id, e.id as entity_id, 'civicrm_participant' a...", (Array:1))
#14 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/BAO/ActionSchedule.php(993): CRM_Core_BAO_ActionSchedule::buildRecipientContacts(3, "20130513162522")
#15 /home/mrbohlax/www/dev/sites/all/modules/civicrm/api/v3/Job.php(209): CRM_Core_BAO_ActionSchedule::processQueue(NULL)
#16 /home/mrbohlax/www/dev/sites/all/modules/civicrm/api/api.php(75): civicrm_api3_job_send_reminder((Array:1))
#17 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/JobManager.php(132): civicrm_api("Job", "send_reminder", (Array:1))
#18 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/JobManager.php(111): CRM_Core_JobManager->executeJob(Object(CRM_Core_ScheduledJob))
#19 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Admin/Page/Job.php(156): CRM_Core_JobManager->executeJobById("9")
#20 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/Page/Basic.php(182): CRM_Admin_Page_Job->browse(NULL, NULL)
#21 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Admin/Page/Job.php(141): CRM_Core_Page_Basic->run()
#22 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/Invoke.php(292): CRM_Admin_Page_Job->run((Array:3), NULL)
#23 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/Invoke.php(70): CRM_Core_Invoke::runItem((Array:13))
#24 /home/mrbohlax/www/dev/sites/all/modules/civicrm/CRM/Core/Invoke.php(52): CRM_Core_Invoke::_invoke((Array:3))
#25 /home/mrbohlax/www/dev/sites/all/modules/civicrm/drupal/civicrm.module(436): CRM_Core_Invoke::invoke((Array:3))
#26 [internal function](): civicrm_invoke("admin", "job")
#27 /home/mrbohlax/www/dev/includes/menu.inc(517): call_user_func_array("civicrm_invoke", (Array:2))
#28 /home/mrbohlax/www/dev/index.php(21): menu_execute_active_handler()
#29 {main}




Above is the full contents of that file. Not sure why it's cut off, but that's how it is in the file

Yashoda, Hershel, Lobo:

I was finally able to fix this issue and duplicate the source of the error. The error is caused by using a custom profile which does not display all possible participant status options. When creating a Scheduled Reminder from the Event page, only the custom profile options were showing.

However, when creating the reminder directly from Administer > Communications > Schedule Reminders, I am able to see ALL the Participant Status options (including the custom ones created for the Profile). The Scheduled Reminders created from this page work without the mysterious DB syntax error I receive when running directly from the Event configuration page.

So there is either a documentation update required or a code fix. But either way, I thank everyone here for their assistance in debugging the problem, and post this so others with custom participant status options will have a workaround that works.