Forum Discussion
OnPrem Gateway issue
I have the On Prem data gateway set up.
I have 2 Analysis services Cubes on prem that I want powerBI reports to use.
Both Cubes are on the same SSAS server.
I have 2 data sources connections on the Gateway.
One data source works and we can "Get Data" and create the reports.
The other data source
when I try to "Get Data"
Get Data->Databases->Get->Sql Server Analysis Services->Connect->
I can see all the Data Source Names but once I click on the new one I get .....
Error text: A property in the XML for Analysis Services query is not valid. Substituted: AdomdDataAccessErrorResponseException:<pi>[0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.AdomdDataAccessErrorResponseException: AdomdException encountered while accessing the target data source. GatewayPipelineErrorCode=DM_GWPipeline_Gateway_DataSourceAccessError GatewayVersion= ErrorCode=-1056178141 ---> [1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException: Substituted: AdomdErrorResponseException:<pi>Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: XML for Analysis parser: The '[email protected]' value of the 'EffectiveUserName' XML for Analysis property is not valid
The same user can connect to both Cubes using Excel Pivot, SSMS, PowerBI Desktop, etc. So they have access to the Cubes and can browse them under SSMS.
What can be wrong and not setup?
- It would appear that the user is not part of the Admin role on the second SSAS Server.
4 Replies
- It would appear that the user is not part of the Admin role on the second SSAS Server.
ok I got to work...
Since I have 2 ssas db's (2 cubes)
and Have 2 data sources (one working and the other not working)
I thougth I was using the same user on both data sources but apparently I wasn't.
I could not determine what user name it was on the one that was working. But I changed it with the user and pwd from the one it wasn't working and that one started not to work so at the point I knew I had 2 different users for the data sources. So I added the one user to the Admin group of the server and it worked.
thanks