Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
Anonymous
Not applicable

Power BI Report Server and SSAS on different machines

Hi!

I just got this working after consulting this article:

https://docs.microsoft.com/en-us/power-bi/report-server/configure-kerberos-powerbi-reports?redirecte...

 

So I have a tabular cube on one machine and report server on a different machine. I have set up SPNs and granted Kerberos delegation as described in the article above.

When I tried a testreport it still couldnt connect (We couldnt connect...) to the cube but once I changed the settings for the data source on the report from "As the user viewing the report" to "Using the following credentials" and checking the "Log in using these credentials, but then try to impersonate the user viewing the report" it worked.

Why do I need to change this setting to make it work? Is it some permissions that is missing?

 

For mor context, my user has all privilages to the cube and the report server. Prior to changing the setting on the data source, when I view the report as my own user I dont get any error. But when I view the report as a user that only is assigned a role in the cube I get the error.

 

Can anybody share any light on this?

1 ACCEPTED SOLUTION

On the delegation settings on the service account running the PBI RS we have Use Kerberos only. I have asked the domain admin to change it to Use any authentication protocol. Hope that helps.

This might be your issue. In my experience any slight variation from the instructions and it just does not work and it gives no meaningful error.

 

I don't *think* having all 3 methods listed in the rsreportserver.config file will be an issue since NTLM is last and Negotiate should attempt Kerberos first and then fall back to NTLM if that fails.

View solution in original post

6 REPLIES 6
d_gosbell
Super User
Super User


@Anonymous wrote:

So I have a tabular cube on one machine and report server on a different machine. I have set up SPNs and granted Kerberos delegation as described in the article above.

When I tried a testreport it still couldnt connect (We couldnt connect...) to the cube but once I changed the settings for the data source on the report from "As the user viewing the report" to "Using the following credentials" and checking the "Log in using these credentials, but then try to impersonate the user viewing the report" it worked.

Why do I need to change this setting to make it work? Is it some permissions that is missing?

 


So configuring the connection in that way will effectively bypass Kerberos so this most likely means that something is not quite right in your Kerberos configuration.

 

One way to double check this is to run a profiler trace against SSAS listening for the Existing Session, Initialize Session, Error and Begin Query events at a minimum. If Kerberos is NOT configured correctly you will see sessions from Anonymous users trying to connect to your cube. Unfortunately Kerberos needs everything to be configured 100% correctly or it just fails so you need to triple check the SPNs an constrained delegation settings in the MSFT docs.

 

If you do see user names in the profiler trace it means that Kerberos is working but something is wrong with your roles in SSAS and you should double check that you have granted read permisions.

Anonymous
Not applicable

Thanks for your tips!

 

There are two settings that are different in my environment compared to the one that GuyinaCube has that I know of is:

* On the delegation settings on the service account running the PBI RS we have Use Kerberos only. I have asked the domain admin to change it to Use any authentication protocol. Hope that helps.

* In rsreportserver.config I have (by default) all three methods listen in this order:

<RSWindowsNegotiate />
<RSWindowsKerberos />
<RSWindowsNTLM />

 

I have run the profiler and just as you suspected my test user who gets the error shows up as anonymous in the SSAS trace when I set the report on Report Server as "As the user viewing the report". If I run Power BI Desktop as this user and connects to the cube it works fine though.

 

Did this give you any clues?

On the delegation settings on the service account running the PBI RS we have Use Kerberos only. I have asked the domain admin to change it to Use any authentication protocol. Hope that helps.

This might be your issue. In my experience any slight variation from the instructions and it just does not work and it gives no meaningful error.

 

I don't *think* having all 3 methods listed in the rsreportserver.config file will be an issue since NTLM is last and Negotiate should attempt Kerberos first and then fall back to NTLM if that fails.

Anonymous
Not applicable

After swithcing to "Use any authentication protocol" the test user can see the contents of the report without setting the "Using the following credentials" on the data source of the report.

Thanks!

xpherion9
New Member

Are you using different domain service account for PBI RS and SSAS? Your account works as you are admin to both server?

Anonymous
Not applicable

YEs, I have one service account for the SSAS och one for PBI RS. My account is admin on both servers.

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.