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
BAlexandrov
New Member

On-premise gateway to OLAP w/o Active Directory

Hi all,

We're evaluating PowerBI for reporting tool in a small organization. We use Office365 and bundled free PowerBI and SQL Server Standard on a VPC in a cloud. On the same machine is installed On-premise gateway. The machine is not part of a domain. There are also installed SQL Server Analysis services tabular model.

Connection to OLAP works using local user account(on the machine) with Excel easily and with PBI Desktop if is started with that account with runas user /netonly and there are no problems with this.

 

The problem is connecting app.powerbi.com to on-premise Analysis services.

 

Connection from app.powerbi.com works for SQL Server, using basic authentication, but does not work for Analysis services. Connection is made with that same local user account, who have permissions on OLAP and works with Excel/PBI Desktop. Test connections works but uploaded report cannot refresh and gives error refreshing. 

 

The error at the gateway logs is "The name provided is not a properly formed account name. ". Full text at the end.

 

Runing the gateway with administrative account does not help.

Specifying the user name as machinename\user does not help - Test connection works if the password is right so there is connection!

Experimenting with ADUserNameLookupProperty, ADUserNameReplacementProperty gives error that there is no domain available.

 

Full error:

GatewayPipelineErrorCode=DM_GWPipeline_Gateway_DataSourceAccessError
GatewayVersion=
ErrorCode=-1056899072 --->
[1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException: Substituted: AdomdErrorResponseException:<pi>Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: The following system error occurred:  The name provided is not a properly formed account name. 
   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
GatewayVersion=
InnerType=AdomdErrorResponseException
InnerMessage=<pi>The following system error occurred:  The name provided is not a properly formed account name. </pi>
InnerToString=<pi>Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: The following system error occurred:  The name provided is not a properly formed account name. 
   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 ---
2 REPLIES 2
Nutty81
New Member

Did you ever get this working?

v-juanli-msft
Community Support
Community Support

Hi @BAlexandrov 


@BAlexandrov wrote:

On the same machine is installed On-premise gateway. The machine is not part of a domain. There are also installed SQL Server Analysis services tabular model.


There may be some configuration missing, please learn how to refresh SSAS data in power bi from this video.

From this official document, when using Windows account for refresh, it must have Server Administrator permissions for the instance you are connecting to.

 

Best Regards
Maggie

 

Community Support Team _ Maggie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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.

Top Solution Authors
Top Kudoed Authors