You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Experimenting with the --targetdacpac batch run commandline switch, I'm able to confirm that an .sbm file is getting properly generated on our client, and pushed to the batch nodes (alongside the platinum dacpac file and .cfg targets file) .
However, the batch job exits early with exit code -728 - A Target Dacpac file was specified but could not be located at 'C:\scrap2\npr\MyTargetDacPac.dacpac'
The "C:\scrap2..." path was the value supplied to the --targetdacpac file, so I wouldn't expect that exact path to be mirrored on the batch node. However, I'm wondering if this dacpac file is even needed on the batch nodes at all, since the .sbm file was already created from it?
I hacked in this line to BatchManager.CompileCommandLines(), which otherwise allowed it to process successfully (against the same database that the targetdacpac was extracted from, at least):
threadCmdLine.DacPacArgs.TargetDacpac = null;
A logging note -- though the batch job / task failed, the -728 error only appeared in the console log and stdout.txt files -- the Errors.log and stderr.txt were empty.
The text was updated successfully, but these errors were encountered:
…uthenticationType"
Fixes#387 "Batch runs called with --targetdacpac failing to find file on batch nodes"
Added ability to specify a settings file and identity args for `sbm utility override`
Updated connection string when using managed identity
Fixes#386 "Batch commands appear to not honor settingsfile-defined AuthenticationType"
Fixes#387 "Batch runs called with --targetdacpac failing to find file on batch nodes"
Added ability to specify a settings file and identity args for `sbm utility override`
Updated connection string when using managed identity
Resetting static ManagedIdentity and TenantId values. Only an issue when running unit tests
Experimenting with the
--targetdacpac
batch run commandline switch, I'm able to confirm that an .sbm file is getting properly generated on our client, and pushed to the batch nodes (alongside the platinum dacpac file and .cfg targets file) .However, the batch job exits early with exit code -728 -
A Target Dacpac file was specified but could not be located at 'C:\scrap2\npr\MyTargetDacPac.dacpac'
The "C:\scrap2..." path was the value supplied to the --targetdacpac file, so I wouldn't expect that exact path to be mirrored on the batch node. However, I'm wondering if this dacpac file is even needed on the batch nodes at all, since the .sbm file was already created from it?
I hacked in this line to BatchManager.CompileCommandLines(), which otherwise allowed it to process successfully (against the same database that the targetdacpac was extracted from, at least):
threadCmdLine.DacPacArgs.TargetDacpac = null;
A logging note -- though the batch job / task failed, the -728 error only appeared in the console log and stdout.txt files -- the Errors.log and stderr.txt were empty.
The text was updated successfully, but these errors were encountered: