CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • scheduled job failure following upgrade to 4.3.3
Pages: [1]

Author Topic: scheduled job failure following upgrade to 4.3.3  (Read 607 times)

ldgpangeo

  • I post occasionally
  • **
  • Posts: 38
  • Karma: 0
  • CiviCRM version: 4.2.6
  • CMS version: drupal-7.17
  • MySQL version: 5.5.23
  • PHP version: 5.3.13
scheduled job failure following upgrade to 4.3.3
May 26, 2013, 05:38:30 pm
I support two sites on the same cloud hosting service.   One upgrade went fine, the second is experiencing a bizarre error.

I can run the scheduled jobs from the web interface with no problems or error messages.   When cron runs the same jobs, it reports "Sorry but we are not able to provide this at the moment." and "DB Error: no such table".   The cron job logs into civicrm as a user with admin rights -- hence, it's unclear why it should be unable to access a db table.  Furthermore, the same installation on the other site on this same hosting service never encountered this error.

Suggestions, clues, fixes?

ldgpangeo

  • I post occasionally
  • **
  • Posts: 38
  • Karma: 0
  • CiviCRM version: 4.2.6
  • CMS version: drupal-7.17
  • MySQL version: 5.5.23
  • PHP version: 5.3.13
Re: scheduled job failure following upgrade to 4.3.3
May 27, 2013, 04:34:38 am
found the solution at

http://wiki.civicrm.org/confluence/display/CRMDOC42/Managing+Scheduled+Jobs?showChildren=false#ManagingScheduledJobs-DBError:nosuchtable

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • scheduled job failure following upgrade to 4.3.3

This forum was archived on 2017-11-26.