I have deployed Initiate software scan fixlet on servers which is getting completed on windows systems and getting stuck on HP-UX, Linux, SunOS, AIX systems.
below is the BODY Action Script Execution Detail
Failed if {exists file “bzip2” of folder (parameter “toolsfolder”)}
wait sh “{parameter “homefolder” as string}/checkBZIP2Status.sh” “{parameter “toolsfolder” as string}” “{parameter “homefolder” as string}”
else
wait sh “{parameter “homefolder” as string}/checkBZIP2Status.sh” “{parameter “homefolder” as string}” “{parameter “homefolder” as string}”
endif
continue if {exit code of action = 0}
delete “{parameter “homefolder” as string}/checkBZIP2Status.sh”
You are better off opening a support case in this situation. Chances are your machines are missing some pre-req tool/path/etc but they will narrow the scope for each OS type to see where it is failing and why, and then how to overcome it. For what it is worth, we are running scans on the same exact OS platforms and the scans are working ok.
i am facing this issue with new version of initiate software scan fixlet 9.2.41.0, earlier with version 9.2.40 it’s working fine.
Even more of a reason to go through Support. We haven’t upgraded to latest version of the scan but will most-likely hold off on it now.
Open a support case with IBM. There is a change to scanner installation folder in ILMT 9.2.41 as mentioned in the release notes (https://www.ibm.com/docs/en/license-metric-tool/9.2.0?topic=tool-whats-new). I think these changes require scanner upgrade to 9.2.41 for the scan task and corresponding Analysis to return correct information for non-Windows servers. This applies to only ILMT scanner tasks and not BFI ones.
3 Likes
i am hitting this right now – for AIX / COGNOS clients.
Review what scanner version is deployed and upgrade it if needed. Check the Software Scan Status Analysis results for any error status codes. You can also check client logs for error messages when the scan tasks are run.
Also open a support case with IBM for any further help.
1 Like
I’ve had the same problem and I think it’s specific to the latest release 9.2.41. There’s a new version of the Initiate Software Scan task, version 9.2.41.1. Stop the 9.2.41 action and restart the new 9.2.41.1 Initiate Software Scan and it should work OK.
