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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Kobe24
Frequent Visitor

Enterprise Gateway unable to logon to SSAS server

I set up the Enterprise Gateway to connect to an SSAS server (SQL Server 2012 SP2). The connection tested fine in the Gateway management page, and when I tested the connection, the enterprise gateway successfully logged on to SSAS server. Here is the what the windows security logs captured:

 

An account was successfully logged on.

Subject:
Security ID: NT SERVICE\MSSQLServerOLAPService
Account Name: MSSQLServerOLAPService
Account Domain: NT SERVICE
Logon ID: 0x86082b0

Logon Type: 3

New Logon:
Security ID: MYDOMAIN\myUserName
Account Name: myUserName
Account Domain: MYDOMAIN
Logon ID: 0x861799c
Logon GUID: {30e418ff-065b-e9ca-ad0f-a3fe31cd1430}

 

After uploading a PowerBI report using the data source in this gateway (the report uses live connection to SSAS server), the report is unable to refresh and reported data source access error. The SSAS trace captured an error: The following system error occurred: Logon failure: unknown user name or bad password. 

 

Windows security log captured:

An account failed to log on.

Subject:
Security ID: NT SERVICE\MSSQLServerOLAPService
Account Name: MSSQLServerOLAPService
Account Domain: NT SERVICE
Logon ID: 0x7b290ce

Logon Type: 3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name:
Account Domain:

 

It seems like when the report try to access data through the Enterprise Gateway, it is unable to pass stored credentials when trying to log in. But it obviously passed the stored credentials when I tested the data source in the enterprise gateway management page

 

Any idea why this is happening? Thanks.

1 ACCEPTED SOLUTION
GuyInACube
Employee
Employee

I just tried this with a SQL 2014 SP1 AS MD instance and it worked without problems for multiple users. Seems like it may be environmental. The test connection for the data source will use the credentials you supplied in the data source. Usually this is formated as DOMAIN\user.

 

When you run the report, we will pass whatever the email address is, that you signed into Power BI with, in the EffectiveUserName property. This could lead to issues if that email address doesn't map to a UPN on your local AD account.

 

That could potentially explain the difference in behavior.  Can you verify that the email address the user logged in with matches the UPN for the Active Directory account on-premises?

Adam W. Saxton | Microsoft Employee | Business Intelligence
@GuyInACube | youtube.com/guyinacube

View solution in original post

16 REPLIES 16

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

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

Top Solution Authors
Top Kudoed Authors