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 »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • After upgrade to 4.0.1 one of my cron jobs returns Invalid key value sent
Pages: [1]

Author Topic: After upgrade to 4.0.1 one of my cron jobs returns Invalid key value sent  (Read 454 times)

MulderDSM

  • I post occasionally
  • **
  • Posts: 100
  • Karma: 0
  • CiviCRM version: 4.6.0
  • CMS version: Joomla 3.4.1
After upgrade to 4.0.1 one of my cron jobs returns Invalid key value sent
May 26, 2011, 05:58:01 pm
I have two cron jobs, one that updates the membership database every night and one that sends mail every night.

Both these cron jobs have been in place for a while, after upgrading joomla to 1.6 and civicrm to 4.0.1, the updatemembership jobs runs fine, but the civimail.cronjob.php returns a Invalid key value sent error message.

I did not change the key I use.
I validated both of the civicrm.settings.php files contain the correct key.

Any other suggestions?

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • After upgrade to 4.0.1 one of my cron jobs returns Invalid key value sent

This forum was archived on 2017-11-26.