Answers.Body: <p>I'm not sure what causes this - but an upgrade on a site of mine (MySQL 5.5, Debian 8.9) caused my <code>civicrm_mailing_job</code> database table to not allow <code>NULL</code> values for <code>start_date</code> and <code>end_date</code>.  Since a <code>NULL</code> start date is a condition for sending emails, this causes CiviMail to fail.</p>
  
  <p>To fix this, you need to run the following SQL commands:</p>
  
  <pre><code>ALTER TABLE civicrm_mailing_job MODIFY start_date timestamp null;
  ALTER TABLE civicrm_mailing_job MODIFY end_date timestamp null;
  </code></pre>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-21T15:59:10.053Z
Answers.Text: This is caused by using an experimental version of the "doctorwhen" extension.  There's a patch to fix this in the works.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-10-21T02:43:53.997Z
Answers.LastActivityDate: 2017-10-21T02:43:53.997Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>CiviMail is no longer sending out mailings after a recent upgrade.  The start and completed dates, instead of being blank, are "0th, 0 12:00 AM".  How do I fix this?</p>
  
Tags: <civimail>
Title: CiviMail won't send mailings; start/completed date is "0th, 0 12:00 AM"
ThreadText: # CiviMail won't send mailings; start/completed date is "0th, 0 12:00 AM"
  
  (Asked by: username_0 on 2017-10-21)
  
  CiviMail is no longer sending out mailings after a recent upgrade. The start and completed dates, instead of being blank, are "0th, 0 12:00 AM". How do I fix this?
  
  **Tags:** civimail
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2017-10-21. Score: 1
  
  I'm not sure what causes this - but an upgrade on a site of mine (MySQL 5.5, Debian 8.9) caused my civicrm_mailing_job database table to not allow NULL values for start_date and end_date.  Since a NULL start date is a condition for sending emails, this causes CiviMail to fail.
  To fix this, you need to run the following SQL commands:
  ALTER TABLE civicrm_mailing_job MODIFY start_date timestamp null;
  ALTER TABLE civicrm_mailing_job MODIFY end_date timestamp null;
  
  > **Comments:**
  > **username_0**: This is caused by using an experimental version of the "doctorwhen" extension.  There's a patch to fix this in the works.  
  
  ---
  
  