James,
what happended to me was that BPM for whatever reason point to a non-existent path when running mdrv.exe.
Check BPM_all.log for such an error
..
[GeneralScriptTaskExecutor] Could not create MDRV process. Failed to run script xyz
..
As per <script>\res\cmdline.txt BPM tries to run
C:\HP\LoadGenerator\bin\mdrv.exe -usr C:\ProgramD...
but
Directory of C:\HP\LoadGenerator\bin
05.07.2016 16:21 303.104 aes_crypt.dll
05.07.2016 16:21 9.216 aes_crypt_tool_cmd.exe
05.07.2016 16:21 31.744 aes_crypt_tool_gui.exe
05.07.2016 16:21 53.760 LrTcLogger.dll
4 File(s) 397.824 bytes
so no mdrv.exe here, and thus BPM fails to start the script, which is executed via mdrv.exe.
LGSA has been installed to
C:\Program Files (x86)\HP\Load Generator\bin
however BPM tries to start the script from
C:\HP\LoadGenerator\bin\
This most likely happens when the initial installation of LGSA fromout the BPM installer fails, it seems parts of it are installed, but not all.
Then LGSA is installed manually, which picks a different path for the product.
BPM however uses the old, bad path and thus cannot execute mdrv.exe as it doesn't exsit.
BPM then thinks it has to use the "wrong" folder.
Workaround / Fix
Modify
C:\ProgramData\HP\BPM\config\topaz_agent_ctrl.cfg
[General]
..
LoadGeneratorHome=C:\HP\LoadGenerator
..
to
[General]
..
LoadGeneratorHome= C:\Program Files (x86)\HP\Load Generator
..
Save the changes, start BPM, check.
Greetings
Siggi