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

Error occured during deployment #389

Closed
Guavaq opened this issue Feb 5, 2020 · 7 comments
Closed

Error occured during deployment #389

Guavaq opened this issue Feb 5, 2020 · 7 comments

Comments

@Guavaq
Copy link

Guavaq commented Feb 5, 2020

Hi there

Great product as always.

When I am deploying to AAS I get the following error shown below. It does appear to still complete the deployment.

image

@TheDataViking
Copy link

TheDataViking commented Feb 5, 2020

@Guavaq I noticed the same error today as part of our release pipelines to Azure Analysis Services.

I tried solving this with the latest update of the AMO library and Tabular Editor. It seems that the AMO have been released a couple of times since the latest build of Tabulareditor.

@otykier can this be related to the latest AMO release (18.4.0.5) which was release a couple of weeks ago ?

https://www.nuget.org/packages/Microsoft.AnalysisServices.retail.amd64/

@Guavaq
Copy link
Author

Guavaq commented Feb 6, 2020

@TheDataViking thanks for the message

Apologies for the question but how would I go about updating the latest version of AMO

I did install this but I still get the same error: https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-data-providers

@otykier I cannot send the .bim file as it contains specific NDA details.

@otykier
Copy link
Collaborator

otykier commented Feb 6, 2020

Seems like Azure Analysis Services has been updated with a build not supported by the current AMO used by Tabular Editor (18.2.3).

I will provide an updated build that targets 18.4.0.5 shortly.

@Guavaq
Copy link
Author

Guavaq commented Feb 6, 2020

Thanks @otykier it still deploys the measures. Just gives the error

@TheDataViking
Copy link

Great @otykier

It seems to even deploy the model fully for a new database. It just keep throwing the error

@otykier
Copy link
Collaborator

otykier commented Feb 6, 2020

Fixed in 2.9.2.

@Guavaq
Copy link
Author

Guavaq commented Feb 6, 2020

Thanks @otykier I can confirm it is now working!

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

No branches or pull requests

3 participants