I was running into this (almost) exact same issue. I was trying to create a batch script to use via a Control-M job to upgrade Patrol Agents. The error message was exactly the same and I was using an install package created via BPPM CMA 9.6. Today I created a silent install the old-fashioned way (download the products you need, download the Installation utility, unzip them, create a silent install, distribute via tool of choice...), referenced that in my script, and it now works like a charm. Which is really a shame considering creating install packages became much easier using the CMA repository. I'd be interested to know the root cause of this.

I should note that I had no problem installing/upgrading agents using a CMA install package outside of our batch template script. I assume something is similar between blade logic deployment configuration and our batch template which causes the CMA install package to have issues finding the install.ctl file.

I opened a case on this and thought the answer might be useful. After extracting the CMA install package, in the "bmc_products\Install\instbin" folder you can find an "install.exe". In my case, we copied/pasted that executable two directories back in the "bmc_products" folder. In my script, we then executed the install as follows: install.exe -install install.ctl -userlog "C:\Program Files\BMC Software\log".I think the log location specified in the -userlog switch is arbitrary. When we specified the command as such instead of "RunSilentInstall.exe" in my script, the installation completed successfully with no "Unable to create new control file. Windows error: 123" error. I'm not familiar with BL, but I'd imagine if you did the same steps and specified the install command like I did, you might also have success and avoid having to manually create silent images the old way.