Bug #35902

fatal error in scheduler / Swift mailer

Added by Stefan Franke almost 9 years ago. Updated over 2 years ago.

Should have
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


While trying to set up the cronjob for the scheduler, something apparently went wrong resulting in the non-accessibility of the scheduler. Now, when trying to access the scheduler, I always get the following error message:

Fatal error: Call to a member function clearAll() on a non-object in /PATH/TO/TYPO3-SRC/typo3/contrib/swiftmailer/classes/Swift/Mime/SimpleMimeEntity.php on line 800

At line 800 I found this code (TYPO3 Version 4.5.14):


It is trying to clear the cache at that point, but $this->_cacheKey is empty. As long as this line of code is commented out, it is working again.

There should be a check, whether $this->_cacheKey is empty or not.


Updated by Francois Suter almost 9 years ago

  • Target version deleted (4.5.15)

Updated by Steve over 8 years ago

I already had the same issue. I cleared the "lastexecution_failure" field in db tx_scheduler_task to get the scheduler back to work.


Updated by Lina Wolf over 8 years ago

UPDATE tx_scheduler_task SET lastexecution_failure = '' also temporarily solves the problem until problem arises again.


Updated by André Steiling over 8 years ago

Check your install tool configuration under $TYPO3_CONF_VARS['MAIL']: In my case missconfigured SMTP settings cause the PHP error. Set the mail transport to "mail" and test again. If it works, something with the further mail configuration theems do be wrong ...


Updated by Philipp Gampe over 8 years ago

This sounds more like a bug in swiftmail itself. Swiftmail is a third party product and TYPO3 will not mess in the code. Please check whether this code as been fixed upstream.


Updated by Christian Kuhn over 8 years ago

  • Status changed from New to Resolved

Not an issue with the scheduler itself: If a task send mails or something else, it should have proper error handling on its own (eg. by catching the mailer result and giving proper result values).


Updated by Michael Stucki about 7 years ago

  • Category set to scheduler

Updated by Michael Stucki about 7 years ago

  • Project changed from Scheduler to TYPO3 Core
  • Category changed from scheduler to scheduler

Updated by Gernot Ploiner almost 6 years ago

I had the same issue today.
My problem was a missing image in a RTE-Content (bodytext field). It was deleted from the uploads-folder.
After uploading the image again all works fine.


Updated by Benni Mack over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF