Renewal reminders not sending in 4.3.3?

[megaw]

Decided I wanted to try the renewal reminders out so I set up a test contact and gave him a 12 month membership and set the renew reminders to send out daily from 12 months before end date.

Waited a day and nothing so I checked the job was running and that I hadn't misspelled mr test users email address. Even manually executing the job results in no mail being sent.

I'm not sure what else to look for as other emails get sent from civimail and the membership confirmation email gets sent ok.

Also is there any way to have the emails go to an admin email only instead of the contacts email? So I can notify staff of when a membership is pending and they can add it to their todo list?

Edit: forgot to mention that I can see the Membership signup in the activity report but there is no Membership Renewal Reminder activity showing. So it's like the membership is never seen as needing a reminder even though it falls in the range specified.

[megaw]

Now I'm actually getting a db error: syntax error from the job after removing the membership off the test user and adding a new one. Kind of a super unhelpful error message in that it says nothing. Off to hunt down the log that has the real error.


Edit: error disappears as soon as a relative date is set instead of an absolute date. Set a relative date and the job executes successfully according to the job log but no email gets sent.

[megaw]

Well even though people are reading this but have no ideas of what is up I'll just update on what little I've found.

I decided to see if reminders in general were an issue or just membership renewals. It appears to be the later as I have an even happening wednesday and set up an event reminder to go out today. It sent out just as you would expect it to. Membership renewals continue to not send. 

[Yashodha Chaku]

megaw :

Now I'm actually getting a db error: syntax error from the job after removing the membership off the test user and adding a new one. Kind of a super unhelpful error message in that it says nothing. Off to hunt down the log that has the real error.

Can you try to replicate the error scenario on our demo (http://drupal.demo.civicrm.org/)

-Yashodha

[megaw]

I set up 2 reminders one absolute date and one relative date. Will have to wait till tomorrow for the absolute date to trigger before I can tell you if there is an error.

Is the demo site set up to mail out? I didn't get the membership confirmation email for the one I just created on there for John Doe.

[Donald Lobo]

the demo site does not send out email. there is no regular cron job either

you can execute the scheduled job manually from the scheduled jobs page

lobo

[megaw]

Yep manually executed but as it doesn't send mail (which is the issue) i can't tell if the relative date reminders worked as no activity was listed in the activity report either.

The absolute date will have to wait for tomorrow as I can't set a absolute date reminder for the same day as todays date.

[megaw]

Heh well it seems I can't test it or reproduce it on the demo site since it got wiped.

As I cant set an absolute date reminder to trigger on the same day as you create the reminder if the site resets every day I can't reproduce the DB error conditions.

Since it doesn't email I can't tell if membership reminders work or not using demo either.

[sstern]

Megaw: Did you every get closure on this? I'm also having a problem with renewal reminders.

[megaw]

No I just disabled em and moved on to other parts of the project. I haven't yet tested em again on 4.3.4 though that seemed to fix a lot of issues with scheduled cron jobs running with wget.

[Jens-Erik]

Did you remove the explanation in the parameters section that are there by default on new installations? They cause a syntax error, which can be confusing, especially because on an upgraded old installation they didn’t show up.

[sstern]

Did you remove the explanation in the parameters section that are there by default on new installations? They cause a syntax error, which can be confusing, especially because on an upgraded old installation they didn’t show up.

There are no parameters....

According to the log:

0
Summary
Starting execution of Send Scheduled Reminders
Details

Parameters parsed (and passed to API method):
a:1:{s:7:"version";i:3;}

Full message:
Starting execution of Send Scheduled Reminders

[Eileen]

Hi,

I've just done a bit of digging on civicrm mailings & it seems that if when you run the update log it schedules the reminders and then processes them. The reminders has to be run every day without fail as it will only schedule for that day. If you have technical problems for a day and miss a day you have to .... do something

[DamonKirkpatrick]

I am seeing a similar problem.  Renewals were working fine until February when I upgraded to 4.2.9.  All the processes are running correctly.  Renewals are set to send at "15 Days before Expiration Date".

The membership status update process executes with the following result: Finished execution of Membership status processor with result: Success (Processed 20409 membership records. Updated 19 records. Sent 0 renewal reminders.)

[osarusan]

I am having the same problem.
I have membership renewal reminders set up, the cron job is set to run daily, it runs and says success, but no emails are ever sent.
I've tried manually running it, automatically running it; it doesn't seem to have any effect at all. The cron job runs and does't report any errors, but no emails are ever sent!
Has anyone figured out what is wrong yet?