Has anyone come across the error “Action Parameter Decryption Failure” in client logs when running a fixlet that prompts for parameter values?
I’ve come across two fixlets in the past week that fail to run for the above reason: Configure REST API credentials for BES Server Plugin Service (fixlet:1190), and OSD Server setup. Both these fixlets prompt for username/password values before action can be taken. The action never runs through and returns “” as the result.
The client log file is the only point that indicates any information about the error:
At 23:37:28 +1000 - mailboxsite (http://iemserver:52311/cgi-bin/bfgather.exe/mailboxsite7680265)
Relevant - Configure REST API credentials for BES Server Plugin Service (fixlet:1190)
At 23:37:30 +1000 -
ActionLogMessage: (action:1190) Action Parameter Decryption Failure.
ActionLogMessage: (action:1190) ending action
Is this an issue with the environment, or is it common aross IEM in general? How can the problem be corrected?
I’ve been troubleshooting this issue for weeks now. No assistance from support via three different PMRs - all have been closed without resolution. Was running .585. Now running .777.
I recreated each action and found that some of the variables do not apply properly. This happens all throughout the Bare Metal Server Deployment sequence. I’m still working on my custom action groups to get this going.
Charles, after a fair bit of trial and error (and VM snapshots), I’ve a workaround to get the OSD group to install successfully. When I confirm the process, I’ll post it here. If you get any word on your PMR, I’d love to know what the solution is as there are some action that I can’t/don’t want to have to manually recreate.
Hi Everyone. This is a known issue in version 9.0.777.0. A patch is currently being tested and should be released very quickly. The use of secure parameters as used in a couple of products but especially in OSD do not work on this particular version. For ckj9779, not sure if you were having issues on the previous version 9.0.586.0 but you should not have been having this issue at that point.
The issue appears to have been present in 9.0.649.0 as well - I was not able to execute “
Configure REST API credentials for BES Server Plugin Service
” successfully with this release.
Is it likely to see a fix released within, say, four weeks?
Just got an email about version 9.0.785 for agents only being released. This appears to address this issue. I can test it out shortly and confirm it works.
Here is the email:
IBM is pleased to announce the availability of version 9.0.785.0 (Patch 3) of the IBM Endpoint Manager platform. This release is only for the Agents. The Root Server, Web Reports, and Relays will not be released within this patch and the 9.0.785.0 Agents will support the 9.0.777.0 (Patch 2) platform.
Note: This release fixes an issue on Agents with Secure Parameters that was introduced in 9.0.777.0. The Fixlets for this patch will allow upgrading of 9.0.777.0 Agents on Relays and Servers. The full change list is available
here
.
This upgrade is available to all IBM Endpoint Manager customers at no charge. IBM recommends upgrading whenever possible to take advantage of new features, optimizations, and bug fixes. As with all Endpoint Manager platform upgrades, you can upgrade any component manually or by using Fixlet messages available on the BES Support Fixlet site.
Published Site Versions:
BES Support v.1123
Additional Notes:
The full IBM Endpoint Manager Platform 9.0 technical change list is available at:
Confirmed that it is working now for the “Configure REST API credentials for BES Server Plugin Service” fixlet. I can try out the OSD part if it later and see. I was able to get around this in OSD by setting the “Options: Enable 9.0 Encryption” to “No Encryption”
Thanks Martin. This updated version of the client (9.0.785.0) resolves the issue for the for both the REST API credentials and the OSD Deployment group.
Charles, deploy the updated client when you have an opportunity. You’ll probably need to run the “
Bare Metal Server Clean Up Post Uninstall or Install Failure
” task before you can retry installing OSD again.