Refresh TMSL Not Working about vsts-release-aas HOT 6 CLOSED

Can you manual refresh the model via SSMS? Looks to me that the credentials to the datasource are somehow not correct.

from vsts-release-aas.

Thank you for the response. I've tried both a sql server admin account and the user/pw credentials our application uses in the connection string, but both result in the same error.

Both accounts are Azure Active Directory users however. Is there something in addition to the "Source User Login" other than USER@MY_DOMAIN.COM that must be specified if it is an AD account?

The AAS admin account I use to deploy the model is also an AD account and I have not had a problem with that task.

from vsts-release-aas.

Thanks for the help Jan. Looks like this is an issue with the datasource connection as I can't even execute that TMSL from SSMS after it has been deployed.

from vsts-release-aas.

I believe this is an issue with the model definition within the JSON. Would you have an example model that can be used with both deploy and TMSL tasks that I could possibly compare against? Still getting this issue.

from vsts-release-aas.

any solution to this issue? i have a similar problem. I do the deployment but I need to update the data to complete the task, I get a connection failure problem when updating. it only works if I run data tools. nor by ssms it works. can you help me?

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.