This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BladeLogic Server Automation Suite
BMC BladeLogic Server Automation Suite
Windows patch analysis jobs (PAJs) in BladeLogic Server Automation (BSA) randomly fail against some targets on each run.
The same job can be run against the same group of Windows targets, but different targets would fail each time. The error in the job run results is the same:
Error while running pre-analysis on server: winsrv001, Error: Cannot copy shavlik hfcli.exe file from '/opt/bmc/bladelogic/NSH/share/patch/windows/shavlikSDK/hfcli.exe' to '//winsrv001/C/Program Files/BMC Software/BladeLogic/RSCD/sbin/hfcli.exe' (Caused By: Caught exception running command - /opt/bmc/bladelogic/NSH/bin/nsh --norc -c "cksum '//winsrv001/C/Program Files/BMC Software/BladeLogic/RSCD/sbin/hfcli.exe'" Error: java.rmi.NotBoundException: ProcessSpawner (Caused By: java.rmi.NotBoundException: ProcessSpawner (Caused By: ProcessSpawner)))
The application server running the PAJ expects the process spawner to copy certain executables to the targets. However the process spawner is not responding to the application server. BSA Process Spawner may be down
Review the spawner.log file on the app server that ran the job.
Look for unresolved startup errors, such as:
Error installing to Start: name=bladelogic.service.ManagementService state=Create
com.bladelogic.om.infra.app.service.ServiceInitializationException: Failed to start management service
Stop and start the process spawner (/etc/init.d/blprocserv stop; /etc/init.d/blprocserv start) then tail the spawner log to make sure it start correctly.
Then retest the job.