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
I am experiencing an issue when attempting to use a wildcard in the 'Path to .asdatabse file' option of the 'Deploy SSAS tabular model' step in the pipeline.
If I specify the full path to the .asdatabse file it works without an issue and successfully deploys. However, as soon as I take the name of the file out and replace this with a wildcard the deployment fails and the only error I receive in the build log is as follows:
I would like to use the wildcard option as its likely that future Tabular model projects will have multiple tabular models and for Continuous Integration it would be ideal to have these deploy, without the need to customise each build script/pipeline
Any help you can provide would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
DrJohnT
changed the title
Issues using wildcards with asdatabse path in SSAS Tabular Cube Deployment Tools Extension in AzureDevOps
DeployCube: Issues using wildcards with asdatabse path in SSAS Tabular Cube Deployment Tools Extension in AzureDevOps
Jan 11, 2021
I am experiencing an issue when attempting to use a wildcard in the 'Path to .asdatabse file' option of the 'Deploy SSAS tabular model' step in the pipeline.
If I specify the full path to the .asdatabse file it works without an issue and successfully deploys. However, as soon as I take the name of the file out and replace this with a wildcard the deployment fails and the only error I receive in the build log is as follows:
2020-03-30T01:53:57.3366041Z ##[error]Error: Error executing C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Microsoft.AnalysisServices.Deployment.exe
I would like to use the wildcard option as its likely that future Tabular model projects will have multiple tabular models and for Continuous Integration it would be ideal to have these deploy, without the need to customise each build script/pipeline
Any help you can provide would be greatly appreciated.
The text was updated successfully, but these errors were encountered: