Highlighted
Super Contributor.. Charles L. Super Contributor..
Super Contributor..
159 views

Tasks Failure in Network Automation 10.11 - BadPaddingException Crypto key exception

Currently, our Network Automation's tasks (e.g. taking snapshot) failed for almost all network devices, with the following error message:

This task did not complete. BadPaddingException: Crypto key exception. Given final block not properly padded
Contact Technical Support.  (Reference stack trace ID 1027)

This happened after we had a disaster recovery test. When NA was failed over, to secondary server everything were fine. Issue started occurring when NA was failed back to primary server.

Currently, the issue is only occurring on primary application server.  The secondary application server can work fine with the primary database server.

My logic is that, if it works with the secondary server, it should also work with primary server. But, despite not making any change with the server during failover and failback, aside from moving the database's role and setup connection using tc_tools.sh

I have already raised a ticket to Microfocus, but the whole day, we have not received any meaningful answer, aside from being told that similar issue is found and fixed in version 10.30 and 10.40.

We will not be having such major upgrade while having an issue ongoing.

Hence, if there is anyone know regarding this issue and how to resolve it, please kindly advise.

Thanks in advance!

0 Likes
4 Replies
Super Contributor.. Charles L. Super Contributor..
Super Contributor..

Re: Tasks Failure in Network Automation 10.11 - BadPaddingException Crypto key exception

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Tasks Failure in Network Automation 10.11 - BadPaddingException Crypto key exception

Hi @Charles L. ,

if i recall correctly, that was caused because of the settings on the site_options.rcx.

the passwords in that file were encrypted with FIPS on the core that they work, so that is the reason the other one can run the task.

Pedro A. Batista
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the THUMB at the bottom left of the post and show your appreciation.
Super Contributor.. Charles L. Super Contributor..
Super Contributor..

Re: Tasks Failure in Network Automation 10.11 - BadPaddingException Crypto key exception

Thanks @Pedro_B_NA. I believe you helped us resolve the issue by providing the site_options.rcx. Which part of the rcx file that helped solve the issue?

Currently we are trying to understand the root cause, to help us avoiding the issue to reoccur in the future.

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Tasks Failure in Network Automation 10.11 - BadPaddingException Crypto key exception

Hi @Charles L. ,

the issue was because at some point you had FIPS enabled, when you disable it and restarted services, NA was unable to decrypt the passwords listed on the site_options.rcx, so that caused the issue, I just cleaned the passwords that were listed there (only one). 

in the future if you present the same issue just search for the string "encrypted"

Pedro A. Batista
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the THUMB at the bottom left of the post and show your appreciation.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.