Skip to main content
Question

Issues with Emailer and FME2019.1

  • September 20, 2019
  • 1 reply
  • 22 views
A
Forum|alt.badge.img+1

Hi, I downloaded a workbench which was on FME Server to a FME 2019.1 desktop workspace but I can't get it to run due to an issue with Emailer and Python as per the message below. The workbench was previously a FME 2017.1 workbench when it was first uploaded to FME Server.

 

2019-09-20 12:04:19| 17.1| 0.0|ERROR |Python Exception <ImportError>: bad magic number in 'Emailer': b'\\x17\\r\\r\\n'

 

2019-09-20 12:04:19| 17.1| 0.0|FATAL |PythonFactory failed to load python symbol `Emailer.Emailer'

 

2019-09-20 12:04:19| 17.1| 0.0|FATAL |Emailer_2_CALLER (PythonFactory): PythonFactory failed to close properly

 

2019-09-20 12:04:19| 17.1| 0.0|ERROR |Emailer_2_CALLER (PythonFactory): A fatal error has occurred. Check the logfile above for details

 

I have tried upgrading the Emailer transformer to the most recent version but this didn't make a difference.

I have also tried changing the Python Compatibility from Python 3.5+ to Python 2.7 but then the workbench fails at the very start and won't read in my Oracle Spatial table.

Any ideas?

Thanks,

 

 

 

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

debbiatsafe
Safer
Forum|alt.badge.img+21
  • debbiatsafeSafer
  • Safer
  • September 24, 2019

Hi @aquamarine

I'm sorry you ran into this issue.

In general, "Python Exception <ImportError>: bad magic number in ..." errors occurs when an old incompatible .pyc file is loaded. The old .pyc file is likely from a previous install of FME and this situation can occur when your current FME build is installed over an older FME build in the same folder.

 

 

I would suggest performing a clean uninstall of FME following the instructions from this article: https://knowledge.safe.com/articles/962/re-installing-fme-if-there-is-a-problem-with-the-i.html and reinstall FME.

Community Stats

32,182
Posts
122,173
Replies
39,855
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.