cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
bu3699
Frequent Visitor

Gateway Connection error SSAS/SQL only , Excelworking PowerBI Desktop/pro

Hi, Everyone, could someone help me in viewing reports in online Powebi app.

I'll give you as much info as possible.

 

In our organisation we use 365, with that we noticed we can use power bi for free(Desktop) created some reports on my PC to deploy online (From CUBE).

 

Installed on premises gateway configured with my mail ID, and I am the cube server admin as well.

 

 

I couldn’t able to view report in power bi app, I can see datasource connected fine and added me as user automatically.

 

p1.png 

 

When I tried to import connection from workspace (DateSets) it throwing below error username or password is incorrect? And why above connection is sucesfull?

 

 p2.png

 

Thanks

12 REPLIES 12
Microsoft
Microsoft

Re: Gateway Connection error SSAS/SQL only , Excelworking PowerBI Desktop/pro

@bu3699,

When you interact with a report that uses SSAS live connection, the effective username is passed to the gateway and then onto your on-premises Analysis Services server.  The email address that you used to sign in Power BI Service is passed to Analysis Services as the effective user, if the email address doesn’t match a defined UPN within your local Active Directory, the above error could occur.

Please check your UPN following the guide in this article, if a match can’t be found, you can use “Map user names” feature to solve this issue.

Regards,
Lydia

Community Support Team _ Lydia Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
bu3699
Frequent Visitor

Re: Gateway Connection error SSAS/SQL only , Excelworking PowerBI Desktop/pro

@Lydia,

 

Thank you for your reply,

 

My Email Address and UPN are Identical and matches, still same issue?

When I deploy reports on to powerbi.com it says "This report couldn't access the data sources. Contact Author" . but connections in Datasource Setting are sucessfull.

 

ERROR LOG

 

DM.EnterpriseGateway Information: 0 : 2018-02-06T16:06:01.3023539Z DM.EnterpriseGateway	d09f83d1-5147-4fbe-bb2b-137566c5b85a	dfcde524-4348-46b7-8d05-f7ff93ea354b	MGPP	00000000-0000-0000-0000-000000000000	E8162E5D [DM.Pipeline.Common] Pool cleaner connections removed: 0, count: 0, buckets: 0
DM.EnterpriseGateway Information: 0 : 2018-02-06T16:06:01.3023539Z DM.EnterpriseGateway	d09f83d1-5147-4fbe-bb2b-137566c5b85a	dfcde524-4348-46b7-8d05-f7ff93ea354b	MGPP	00000000-0000-0000-0000-000000000000	E8162E5D [DM.Pipeline.Common] Pool cleaner connections removed: 0, count: 0, buckets: 0
DM.EnterpriseGateway Information: 0 : 2018-02-06T16:06:10.5365068Z DM.EnterpriseGateway	29c4216f-de1b-471a-9867-201785a45512	f575be36-f5bc-1e84-c666-1d9a499c9ad2	MGPP	c15219e9-e45b-4673-a3c7-2dae8f19dc80	7683252B [DM.GatewayCore] Deserialized EncryptCredentialsWithTestConnectionRequest, executing
DM.EnterpriseGateway Information: 0 : 2018-02-06T16:06:10.5677563Z DM.EnterpriseGateway	de02fa2d-a9c9-4e37-ad62-9598de72ab4e	f575be36-f5bc-1e84-c666-1d9a499c9ad2	MGTD	c15219e9-e45b-4673-a3c7-2dae8f19dc80	2C2CDAB4 [DataMovement.PipeLine.GatewayDataAccess] Replace effective user name in adomd connection string from 718E9B80-F20C-42EA-AA38-E45CBEEB6718 to 718E9B80-F20C-42EA-AA38-E45CBEEB6718.
DM.EnterpriseGateway Information: 0 : 2018-02-06T16:06:10.5677563Z DM.EnterpriseGateway	de02fa2d-a9c9-4e37-ad62-9598de72ab4e	f575be36-f5bc-1e84-c666-1d9a499c9ad2	MGTD	c15219e9-e45b-4673-a3c7-2dae8f19dc80	92A951F2 [DataMovement.PipeLine.GatewayDataAccess] updated credential username = <pi>mycompany\user1</pi> if need
DM.EnterpriseGateway Information: 0 : 2018-02-06T16:06:31.3057335Z DM.EnterpriseGateway	d09f83d1-5147-4fbe-bb2b-137566c5b85a	dfcde524-4348-46b7-8d05-f7ff93ea354b	MGPP	00000000-0000-0000-0000-000000000000	E8162E5D [DM.Pipeline.Common] Pool cleaner connections removed: 0, count: 0, buckets: 0
DM.EnterpriseGateway Information: 0 : 2018-02-06T16:06:31.3057335Z DM.EnterpriseGateway	d09f83d1-5147-4fbe-bb2b-137566c5b85a	dfcde524-4348-46b7-8d05-f7ff93ea354b	MGPP	00000000-0000-0000-0000-000000000000	E8162E5D [DM.Pipeline.Common] Pool cleaner connections removed: 0, count: 0, buckets: 0
DM.EnterpriseGateway Information: 0 : 2018-02-06T16:06:34.2276082Z DM.EnterpriseGateway	70c5fbc2-4b47-403b-a5cc-e956f5c7d72f	5a5eaffd-e7a6-f8d9-85e9-329ba1aabe51	MGPP	c15219e9-e45b-4673-a3c7-2dae8f19dc80	E5E3865A [DM.GatewayCore] Deserialized OpenConnectionRequest, executing
DM.EnterpriseGateway Information: 0 : 2018-02-06T16:06:34.2276082Z DM.EnterpriseGateway	fa33ae4d-9540-4a62-be36-b8a3e0cbf9d9	5a5eaffd-e7a6-f8d9-85e9-329ba1aabe51	MGCC	c15219e9-e45b-4673-a3c7-2dae8f19dc80	FDAA70D2 [DM.GatewayCore] Db pool opening raw database connection to [MSOLAP.5: <pi>MSOLAP.5:provider=MSOLAP.5;data source=EQMSQL04DEV;initial catalog=Ignite;timeout=180;effectiveusername=user2@mycompany.co.uk;sspropinitappname=PowerBI:[Windows] Encrypted Credential information omitted</pi>]
DM.EnterpriseGateway Information: 0 : 2018-02-06T16:06:34.2432333Z DM.EnterpriseGateway	fa33ae4d-9540-4a62-be36-b8a3e0cbf9d9	5a5eaffd-e7a6-f8d9-85e9-329ba1aabe51	MGCC	c15219e9-e45b-4673-a3c7-2dae8f19dc80	38921C54 [DataMovement.PipeLine.GatewayDataAccess] Replace effective user name in adomd connection string from user2@mycompany.co.uk to user2@mycompany.co.uk.
DM.EnterpriseGateway Error: 0 : 2018-02-06T16:06:34.2432333Z DM.EnterpriseGateway	fa33ae4d-9540-4a62-be36-b8a3e0cbf9d9	5a5eaffd-e7a6-f8d9-85e9-329ba1aabe51	MGCC	c15219e9-e45b-4673-a3c7-2dae8f19dc80	BAA79098 [DM.Pipeline.Diagnostics] Exception object created [IsBenign=True]: Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.AdomdDataAccessErrorResponseException: AdomdException encountered while accessing the target data source.; ErrorShortName: AdomdDataAccessErrorResponseException[ErrorCode=-1056899072,HResult=-2146233088]/Wrapped(AdomdErrorResponseException)[ErrorCode=-1056899072,HResult=-2146233088]
DM.EnterpriseGateway Error: 0 : 2018-02-06T16:06:34.2432333Z DM.EnterpriseGateway	fa33ae4d-9540-4a62-be36-b8a3e0cbf9d9	5a5eaffd-e7a6-f8d9-85e9-329ba1aabe51	MGCC	c15219e9-e45b-4673-a3c7-2dae8f19dc80	9DFB644E [DM.Pipeline.Common.TracingTelemetryService] Event: FireActivityCompletedWithFailureEvent (duration=26, err=AdomdDataAccessErrorResponseException, rootcauseErrorEventId=0)
DM.EnterpriseGateway Error: 0 : 2018-02-06T16:06:34.2432333Z DM.EnterpriseGateway	dd399a52-db7f-4d94-a6d1-b5b4e2295f03	5a5eaffd-e7a6-f8d9-85e9-329ba1aabe51	MGGC	c15219e9-e45b-4673-a3c7-2dae8f19dc80	6C969DB3 [DM.Pipeline.Common.TracingTelemetryService] Event: FireActivityCompletedWithFailureEvent (duration=27, err=AdomdDataAccessErrorResponseException, rootcauseErrorEventId=0)
DM.EnterpriseGateway Error: 0 : 2018-02-06T16:06:34.2432333Z DM.EnterpriseGateway	f0a4aa10-f92f-4ce1-82e8-59babb2a4b3c	5a5eaffd-e7a6-f8d9-85e9-329ba1aabe51	MGOC	c15219e9-e45b-4673-a3c7-2dae8f19dc80	6C969DB3 [DM.Pipeline.Common.TracingTelemetryService] Event: FireActivityCompletedWithFailureEvent (duration=27, err=AdomdDataAccessErrorResponseException, rootcauseErrorEventId=0)
DM.EnterpriseGateway Error: 0 : 2018-02-06T16:06:34.2432333Z DM.EnterpriseGateway	70c5fbc2-4b47-403b-a5cc-e956f5c7d72f	5a5eaffd-e7a6-f8d9-85e9-329ba1aabe51	MGPP	c15219e9-e45b-4673-a3c7-2dae8f19dc80	6C969DB3 [DM.Pipeline.Common.TracingTelemetryService] Event: FireActivityCompletedWithFailureEvent (duration=27, err=AdomdDataAccessErrorResponseException, rootcauseErrorEventId=0)
DM.EnterpriseGateway Error: 0 : 2018-02-06T16:06:34.2432333Z DM.EnterpriseGateway	80b1e786-6282-4b82-8047-38dff165cf98	5a5eaffd-e7a6-f8d9-85e9-329ba1aabe51	MDSR	c15219e9-e45b-4673-a3c7-2dae8f19dc80	4144A9EE [DM.GatewayCore] Error processing request: [0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.AdomdDataAccessErrorResponseException: AdomdException encountered while accessing the target data source.

GatewayPipelineErrorCode=DM_GWPipeline_Gateway_DataSourceAccessError
ErrorCode=-1056899072 --->
[1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException: Substituted: AdomdErrorResponseException:<pi>Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: The following system error occurred:  The user name or password is incorrect. 
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.AdomdConnectionProvider.OpenConnectionAsync()</pi>

GatewayPipelineErrorCode=DM_GWPipeline_UnknownError
InnerType=AdomdErrorResponseException
InnerMessage=<pi>The following system error occurred:  The user name or password is incorrect. </pi>
InnerToString=<pi>Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: The following system error occurred:  The user name or password is incorrect. 
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.AdomdConnectionProvider.OpenConnectionAsync()</pi>
InnerCallStack=   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.AdomdConnectionProvider.OpenConnectionAsync()
  ([1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException.StackTrace:)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.AdomdConnectionProvider.OpenConnectionAsync()
   --- End of inner exception stack trace ---
  ([0]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.AdomdDataAccessErrorResponseException.StackTrace:)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.AdomdConnectionProvider.OpenConnectionAsync()
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.ConnectionStrings.AdoNetDbFullConnectionString.<OpenConnectionAsync>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdoNetDbConnectionPool.<>c__DisplayClass1_0.<<CreateObjectInstance>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.AdoNetDbConnectionPool.<CreateObjectInstance>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.Common.Pool.BasePool`3.<CreatePoolObject>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.Common.Pool.StatelessPool`2.<Get>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<>c__DisplayClass10_0.<<GetDatabaseConnection>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<GetDatabaseConnection>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<>c__DisplayClass1_0.<<EnsureConnection>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<EnsureConnection>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.<DispatchImpl>d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorDispatcher.<Dispatch>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<DeserializeImpl>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<>c__DisplayClass8_0.<<Deserialize>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.Common.Diagnostics.PipelineTelemetryService.<ExecuteInActivity>d__7`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.Serialization.GatewayDeserializer.<Deserialize>d__8.MoveNext()

 

 

Thanks

pdao19
Frequent Visitor

Re: Gateway Connection error SSAS/SQL only , Excelworking PowerBI Desktop/pro

Hello,

We seem to have the same problem:

We have SSAS 2016, an on premise enterprise gateway and Power Bi Desktop Pro.

We’ve created a datasource connection to the cube successfully on the enterprise gateway.

We’ve created a report that connects to the same cube and published it to an Workspace successfully.

But when running the report  on the Workspace it gives us the error user name or password in the SSAS log and in the enterprise gateway log.

We made sure that the service account running SSAS service has read access to the AD and that the enterprise gateway and SSAS are in the same domain.

As anyone encounter the same problem?

Thanks

Super User III
Super User III

Re: Gateway Connection error SSAS/SQL only , Excelworking PowerBI Desktop/pro

Hey,

 

I'm wondering if you added yourself to the users pane.

Users who want to publish reports to a workspace have to be added as a user

image.png

 

Can you confirm that you also configured the users tab.

 

Regards,

Tom

Hamburg - Germany
If I answer your question, please mark my post as solution, this will also help others.
I accept Kudos :-), If you find my post helpful.

Proud to be a Datanaut!
pdao19
Frequent Visitor

Re: Gateway Connection error SSAS/SQL only , Excelworking PowerBI Desktop/pro

Thanks for your response, yes I've add myself in the user tab of the connection manager and I am admin of the workspace where I've published the report.

 

In the sql server profiler we have:
The user name or password is incorrect.

 

In the log of the gateway we have:

GatewayPipelineErrorCode=DM_GWPipeline_Gateway_DataSourceAccessError
ErrorCode=-1056899072 --->
[1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException: Substituted: AdomdErrorResponseException:<pi>Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: The following system error occurred:  The user name or password is incorrect.
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Connect(Boolean toIXMLA)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
   at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
   at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.AdomdConnectionProvider.OpenConnectionAsync()</pi>

Super User III
Super User III

Re: Gateway Connection error SSAS/SQL only , Excelworking PowerBI Desktop/pro

Hey,

 

can you also please check what values are returne by these both commands - issued at the command prompt of your machine:

  • whomai
  • whoami /upn

Basically the latter has to the same as the "email" you are using as login to the Power BI Service

 

Regards,

Tom

Hamburg - Germany
If I answer your question, please mark my post as solution, this will also help others.
I accept Kudos :-), If you find my post helpful.

Proud to be a Datanaut!
pdao19
Frequent Visitor

Re: Gateway Connection error SSAS/SQL only , Excelworking PowerBI Desktop/pro

Yes,

whoami gives my windows login name

ca\xxxx

and whoami /upn gives my email which is the same email I am using to connect to powerbi

xxxx.xxx@xxxx.ca

Super User III
Super User III

Re: Gateway Connection error SSAS/SQL only , Excelworking PowerBI Desktop/pro

Hey,

 

maybe my final questions 🙂

 

  • Are you using a domain account as service account for the gateway
  • The user that are using to configure the gateway "the connection" is instance admin of the SSAS Server and not just database admin

Regards,

Tom

Hamburg - Germany
If I answer your question, please mark my post as solution, this will also help others.
I accept Kudos :-), If you find my post helpful.

Proud to be a Datanaut!
pdao19
Frequent Visitor

Re: Gateway Connection error SSAS/SQL only , Excelworking PowerBI Desktop/pro

Hello,

I'm confirming that the account running the gateway is a domain service account as well as the account running ssas which is a domain service account as well.

We've also tried creating a connection in the connection manager using the ssas service domain account.

Thanks

Helpful resources

Announcements
‘Better Together’ T-Shirt Contest – Winner Announced!

‘Better Together’ T-Shirt Contest – Winner Announced!

And the winner is...

Announcing the New Spanish Forum

Announcing the New Spanish Forum

Do you need help in Spanish? Check out our new Spanish community section.

April 2020 Community Highlights

April 2020 Community Highlights

Info on our Super Users, MBAS content and badges, and updates to our support articles. - Read the full Community Highlights.

MBAS Gallery 2020

MBAS Gallery 2020

Watch Microsoft Business Applications Summit sessions on-demand.

Top Solution Authors
Top Kudoed Authors