search

liprec / vsts-release-aas

Repository for my Analysis Service Azure pipelines tasks related to Azure Analysis Service or Power BI Premium
Other
27 stars 28 forks source link

Unable to obtain authentication token using the credentials provided #76

Closed NickelBronze closed 2 years ago

NickelBronze commented 2 years ago

My steps to execute XMLA no longer work, it's getting the following error.

Error connecting to tabular service. (Exception calling "Connect" with "1" argument(s): "Unable to obtain authentication token using the credentials provided. If your Active Directory tenant administrator has configured Multi-Factor Authentication or if your account is a Microsoft Account, please remove the user name and password from the connection string, and then retry. You should then be prompted to enter your credentials.")

I tried deleting the step and re-creating it. Quadruple checked the credentials.

Any advice?

NickelBronze commented 2 years ago

I'm able to deploy the model using the same credentials, no issues.

liprec commented 2 years ago

Can you share the debug log (variable: System.Debug set to true) to provide me some more details?

NickelBronze commented 2 years ago

image I noticed the following after the update.

The Service Connection Type selected is 'connectedServiceNameARM'. But when I click the drop down list, the only options are 'Azure Resource Manager' and 'Power BI'.

When looking at the log, I see that 'connectedServiceNameARM' is still chosen, even though I've selected 'Azure Resource Manager' (screen shot is of another release pipeline I didn't try fixing yet) log.txt .

liprec commented 2 years ago

The connection type has an new option (Power BI) and therefor I renamed the existing option. But it is only the 'friendly name' and not the option value itself: that is still connectedServiceNameARM

But indeed this is a (simple) bug: I forgot to update the task version, so it is still using a cached (old) version in your pipeline 🤦. Will update the version and release a new version.

liprec commented 2 years ago

The extension is updated to version 1.5.4 and will be available anytime soon.