Forum Discussion
"This report couldn't access the datasource" - SSAS Tabular Connection Issue
Hi!
I've created a SSAS Tabular model, of which I am Server Admin and have created a role which grants Read access and includes myself and some colleagues.
I've created a Power BI report which uses a Live Connection to the SSAS model.
I've published this and successfully set up a connection on the Gateway.
However, when myself or my colleagues access the report in the service, we get the above error and no visuals rendering.
Having read various other posts, I've recreated the Role and I've checked the UPN matches to our AD.
Any suggestions on what to try next would be great!
Cheers
Finally figured out a fix ourselves.
The SSAS Service needed to be ran as a domain account (DOMAIN\USER) ours was using a different service account (NT SERVICE\MSOLAP$...).
We also had to add the new SSAS Service domain account to the following AD group: Windows Authorization Access Group
We found that method by reading the following post:
After restarting the SSAS service, everything worked as expected.
6 Replies
Thanks Anonymous
Here's the bit of the log I think it could be. Not sure what I can make from it. Where it suggests to replace the effective username, the from and the to were identical.
6A7A1A51 [DM.GatewayCore] AdoNetDBFullConnectiongString: Service Msolap progid is different with on-prem. Service:MSOLAP.5. On-Prem:MSOLAP.8. 733C5FDB [DM.GatewayCore] Db pool opening raw database connection to [MSOLAP.8: <pi>MSOLAP.8:provider=MSOLAP.5;data source=<Server>;initial catalog=<Catalog>;cube=<cube>;sspropinitappname=PowerBI;effectiveusername=<username>;connect timeout=60:[Windows] Encrypted Credential information omitted</pi>] 24AC60C7 [DM.Pipeline.Common] Either LookupPropertyName <username> or TargetPropertyName is null or empty. Fall back to original value. DA9D25D4 [DataMovement.PipeLine.GatewayDataAccess] Replace effective user name in adomd connection string from <username> to <username>. Finally figured out a fix ourselves.
The SSAS Service needed to be ran as a domain account (DOMAIN\USER) ours was using a different service account (NT SERVICE\MSOLAP$...).
We also had to add the new SSAS Service domain account to the following AD group: Windows Authorization Access Group
We found that method by reading the following post:
After restarting the SSAS service, everything worked as expected.
Good evening friend, Jancarlos from Peru greets you, a query the domain account that runs the SSAS service, it is the one that you configured in the Gateway, that same account has to be in the AD group of authorizations, right?
Hi Jancarlos
It might be something different to that. This was something my IT team sorted I'm not 100% sure of the process.
I believe the following link covers the process they followed.
Hope this helps.
James
