Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Microsoft.AnalysisServices.Deployment.exe Not Found During SSAS Deployment in Azure DevOps Pipeline #13

Open
Letsdoit1455 opened this issue Sep 4, 2024 · 1 comment · May be fixed by #14

Comments

@Letsdoit1455
Copy link

I’m currently having a problem with my release pipeline to the SSAS server, specifically during the deployment stage. When running the pipeline, I encounter an error during the deployment part of the cube with version 15. When I switch to the latest version, it says that it can’t find Microsoft.AnalysisServices.Deployment.exe.

The weird part is that I can confirm the mentioned executable is installed by running Find-AnalysisServicesDeploymentExeLocations on my C drive.

Here’s the errorr
Warning can't find Microsoft.AnalysisServices.Deployment.exe. (paraphrase since i can't access my pipeline atm to see the exact error) but it was similiar.

Cannot validate argument on parameter 'Version'. The argument "" does not belong to the set "15,14,13,12,11" specified by the ValidateSet attribute. Supply an argument that is in the set and then try the command again.

@LeVoid
Copy link

LeVoid commented Oct 30, 2024

I've had the same issue today.
The pipeline task tries to find a valid Deployment.exe Version that matches the PreferredVersion you specified (or "latest" by default).

The task doesn't know about SSMS 20 yet, so if that is the version you are using this may be the issue.

I fixed this by altering the powershell scripts

  • Select-AnalysisServicesDeploymentExeVersion
  • Get-AnalysisServicesDeploymentExePath

I added "20" to the ValidateSet for the "Version" and "PreferredVersion" parameter respectively.

The error you described originates from the first script delivering a null value for the second script because the correct version wasn't found.

Edit: Same goes for SSMS 19, which would correspond to PreferredVersion "16".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants