You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great extension! It's so far has saved me a lot of time. However, I do have a problem with passing a secure variable with my u/p to update the model. I looks like it updates but when I go to process it, no luck. The process model task says
The JSON DDL request failed with the following error: Failed to execute XMLA. Error returned: 'The following system error occurred: The user name or password is incorrect.
A connection could not be made to the data source with the Name of 'SqlAzure somewhereyoudontknow.database.windows.net datatrax'.
'..
I have validated the u/p several times and looked at the connection string in SSAS and it looks ok. using the same u/p to manually update works fine.
The text was updated successfully, but these errors were encountered:
DrJohnT
changed the title
vsts - username and password not being passed to update tabular model
DeployCube: username and password not being passed to update tabular model on Azure AS
Jan 11, 2021
@realdevopsguy
I have updated the underlying PowerShell module (i.e. https://github.com/DrJohnT/DeployCube) to fully support deployment of tabular cubes to Azure Analysis Services. I just need to expose the relevant fields in my DeployTabularModel extension (i.e. u/p).
Great extension! It's so far has saved me a lot of time. However, I do have a problem with passing a secure variable with my u/p to update the model. I looks like it updates but when I go to process it, no luck. The process model task says
The JSON DDL request failed with the following error: Failed to execute XMLA. Error returned: 'The following system error occurred: The user name or password is incorrect.
A connection could not be made to the data source with the Name of 'SqlAzure somewhereyoudontknow.database.windows.net datatrax'.
'..
I have validated the u/p several times and looked at the connection string in SSAS and it looks ok. using the same u/p to manually update works fine.
The text was updated successfully, but these errors were encountered: