Am encountering an odd "javax.crypto.IllegalBlockSizeException" error when I try to save an Automation. There seems to be some issue with the associated workflow, however the workflow runs fine by itself, or via a schedule.
Has anyone else encountered something similar?
Hi @pmcpherson
Does the automation save/start if you remove the / from the name?
Jennifer,
Am still not sure what the error means exactly, but I was able to relate it to a password published parameter that was not importing correctly from the associated workspace. I was able to get the Automation to save/run by manually overriding that password parameter within the Automation dialog, although it was touchy in that it kept resetting.
Phil
This appears to be a bit of an issue with Automations. From my observations, it would appear that all password entries need to be re-entered any time a change is made to any of the published parameter values for the Automation. So, for example, if I just want to update a non-password parameter, I also need to update all password params. I don't think this should be the default behaviour.
This appears to be a bit of an issue with Automations. From my observations, it would appear that all password entries need to be re-entered any time a change is made to any of the published parameter values for the Automation. So, for example, if I just want to update a non-password parameter, I also need to update all password params. I don't think this should be the default behaviour.
Yes, the problem persists. Hopefully the Safe folks will add it to the bug-fix list for the next release. Thanks for commenting.
Hi @nic_ran and @pmcpherson,
It looks like this error message, tracked in an internal issue as (FMESERVER-14633), has been resolved for FME 2020.0.1 in the latest release, which can be downloaded here: safe.com/downloads
Please give that a try and let us know how it goes for you!
Hi @nic_ran and @pmcpherson,
It looks like this error message, tracked in an internal issue as (FMESERVER-14633), has been resolved for FME 2020.0.1 in the latest release, which can be downloaded here: safe.com/downloads
Please give that a try and let us know how it goes for you!
Jovita,
I've upgraded to FME Server 2020.0.1 and so far the error has not reappeared. Will advise if it shows up again. Thanks.
Phil
Hi @nic_ran and @pmcpherson,
It looks like this error message, tracked in an internal issue as (FMESERVER-14633), has been resolved for FME 2020.0.1 in the latest release, which can be downloaded here: safe.com/downloads
Please give that a try and let us know how it goes for you!
That's great news. Unfortunately, I don't have simple access to install a newer version of FME Server but will try to test it soon...