from AI. The batch runs very nicely when called from the command line, it tests for connection to a SQLServer named instance and if not successful, runs command line call to sql server install.
When running batch from custom action launch file, the test for connection does not find instance, then attempts sqlserver install. The sqlserver install extracts sqlserver install folder structure, then fails in various different ways: at times it will simply hang, other times it will exit silently without finishing.
I seem to recall that installers may call setup.exe type installers, but not .msi type installers. This sort of feels like that's what's happening here.