AS connector failing to work even though WHOAMI/UPN is returning correct information

[luisrh]

Am I testing this for our in house tabular models.  I am a member of the domain and we since we are offc 365 users we are in Azure Active Directory -   The error I receive is the standard  "Power BI user name xxxx.@mycompany.com cannot connect to  'serverName\tabularInstance' Analysis Services Server due to an effective user name mismatch" 

I went thru the normal troubleshooting that tells you to use WHOAMI\UPN and it should return you xxxx@my.company.com for your user.    I get the expected  xxxx@mycompany.com return.

When looking at the event viewer it seems that it's not connecting to the model.   Below are the entries on DMG event viewer log:

Creating new MSOLAP connection to AS server. Activity ID: 621f4a6c-75c7-4313-a7ee-5dde364716e1

Do impersonation for user domain\xxxx. Activity ID: 621f4a6c-75c7-4313-a7ee-5dde364716e1

The MSOLAP connection is opened. Activity ID: 621f4a6c-75c7-4313-a7ee-5dde364716e1

Creating new MSOLAP connection to AS server. Activity ID: 99605ae0-7081-4056-bfe1-e14bfadb28a4

Do impersonation for user domain\xxxx. Activity ID: d456ea25-ff2a-410c-bf16-fca424c24cbc

Open MSOLAP connection failed. The connection string is provider=MSOLAP.5;data source=servername\tabularInstance;protocol format=XML;transport compression=None;EffectiveUserName=xxxx@mycompany.com. Activity ID: d456ea25-ff2a-410c-bf16-fca424c24cbc

Above you can see that the connectionString is set up with correct UPN user.  I assume this may be related to yet another issue with AD on premise we need to change when synching with AAD.   Could you give me an idea of what I can tell our IT group about it?

I am trying to test the direct query capability of Power BI and something that we intend to do for all our hosted customers.  I'd like to get ours working first -

It seems that AAD and effectiveUserName approach is quite limiting.  Allowing for users to connect with using CustomData and not requiring AAD would be preferable.   Either way,  If you can guide me to get the existing approach working it woud be great.

thanks

[Seth_C_Bauer]

PowerBI sits on top of Azure and utilizes its infrastructure, thus the AAD requirement.

You mention office 365 and on premise... Have you synced your on prem AD to AAD, and this error is happening after the fact?

I'm guessing you've already seen this, but if not here are the support articles for the AS set up.

https://support.powerbi.com/knowledgebase/articles/471577-configure-a-power-bi-analysis-services-con...

https://support.powerbi.com/knowledgebase/articles/546004-power-bi-analysis-services-connector-in-de...

[luisrh]

Yes the synch has been done already -  I have gone thru the troubleshooting as well.   As I am saying, this seems to be a pretty large blocker to adoption as I am not the only person having these issues.    AAD requirement is something I hope goes away to make it simpler to use.  

thanks

[Nainesh]

Hi,

I faced the same problem as you. I was working with SQL Server 2012, and Installing SQL Server 2012 Service Pack 2 resolved the issue for me.