Error during deploying the model (Exception has been thrown by the target of an invocation.) about vsts-release-aas HOT 16 CLOSED

At this moment depoying a model via a SPN is not yet supported. I am in the process of rewriting all my VSTS extensions to NodeJS to be platform independent (and the are running faster) and it will include the deployment with SPNs, but it will take a little bit longer.

So at this moment you need an user and that user needs to be service admin to be able to deploy a model to AAS. And with the new version this user can be changed to an SPN, because you need access to both the Azure resource and the service itself.

(Duplicate of #5)

from vsts-release-aas.

Having the same problem

from vsts-release-aas.

We are not using a SPN to deploy a model through a VSTS release pipeline and we're experiencing the same error. I use my own credentials in the 'Analysis Services Admin' and 'Analysis Services Admin Password' , and I am one of the Analysis Services Admins. Could this have something to do with MFA?

from vsts-release-aas.

Probably it will as the MFA authentication will return a 'challenge'.
So if it is possible to use a fixed user/password without MFA or add an 'app password' to your user it should work.

from vsts-release-aas.

We are trying to use this extension in an enterprise environment where both solutions (fixed user/password and 'app passwords') are not allowed/disabled. Would be great if Service Principals would be supported in the (near) future.

from vsts-release-aas.

Having same issue. Is there a resolution to this.

from vsts-release-aas.

Also me.

from vsts-release-aas.

Getting this as well. We are using an App Registration. Shouldn't this be the same as username and password?

from vsts-release-aas.

Having same issue. Is there a resolution to this.

Works perfectly. Had problem with my password and Username.
It doesn't work with MFA..

from vsts-release-aas.

I just released a minor version (v1.2) with Service Principal support.

from vsts-release-aas.

Hi,

My release pipeline broke immediately. Do I need to recreate it? I'll give it a go.

from vsts-release-aas.

@reubster, can you share the error message? And can you make sure that the pipeline is using v1.2.2?

from vsts-release-aas.

The original error was

"##[error]Error during adding automatic firewall rule (Authentication failed: User ID and Password are required when user interface is not available.)
##[error]Authentication failed: User ID and Password are required when user interface is not available." 

However, I've made a few random tweaks in the settings, saved and run again and it's fine now.

Perhaps it just needed a re-validation to recognise some new defaults or something?

Thanks for making the update. Very helpful. Now I can throw away the regular user and stick to using my SPN.

from vsts-release-aas.

Yesterday I fix a bug that was related to deployments without a firewall, so it could be that you were hitting the same error.
But good to hear that it is now working for you again!

from vsts-release-aas.

Hi liprec,

Yeah, I'm not currently using a firewall. Now when I try it, it works as long as I disable the remove after deploy switch.

from vsts-release-aas.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from vsts-release-aas.