Skip to main content
Solved

FME Server Automation error: javax.crypto.IllegalBlockSizeException: Data must not be longer than 245 bytes

  • December 16, 2019
  • 2 replies
  • 146 views
arekpierchala
Contributor
Forum|alt.badge.img+1

Hi

I've got an error:

javax.crypto.IllegalBlockSizeException: Data must not be longer than 245 bytes

when trying to change and save Automation (schedule trigger + 3x sequenced workspaces)

FME Server win64, b19643

Got an error when trying to set on trigger Start Date&Time - error after Save button click.

Any suggestion?

Best answer by rylanatsafe

Hi @arekpierchala, I'm sorry that you have encountered this error. A similar posting was made by another FME Community member – they were able to identify that this error was related to a 'Password' Published Parameter in one of the Workspace actions.

I was able to get the Automation to save/run by manually overriding that password parameter within the Automation dialog

Hope that helps! If you still have issues, please use the 'Report a Problem' form on our FME Technical Support page.

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.

2 replies

rylanatsafe
Safer
Forum|alt.badge.img+14
  • rylanatsafeSafer
  • Safer
  • 671 replies
  • Best Answer
  • December 23, 2019

Hi @arekpierchala, I'm sorry that you have encountered this error. A similar posting was made by another FME Community member – they were able to identify that this error was related to a 'Password' Published Parameter in one of the Workspace actions.

I was able to get the Automation to save/run by manually overriding that password parameter within the Automation dialog

Hope that helps! If you still have issues, please use the 'Report a Problem' form on our FME Technical Support page.

jovitaatsafe
Safer
Forum|alt.badge.img+11
  • jovitaatsafeSafer
  • Safer
  • 635 replies
  • May 1, 2020

Hi @arekpierchala,

just wanted to update you that a recent change in the latest release of FME 2020.0.1 should have fixed this error message if you'd like to give it a try. You can find it in the downloads page here.

Community Stats

32,102
Posts
121,897
Replies
39,750
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.