On-Premise Gateway not Connecting the SSAS Data Properly

[117325]

We recently created an on-premise gateway to connect to the analysis packs on the SQL server. Our system login credential does not match with SQL server  login, therefore we have followed the instruction on this article (https://docs.microsoft.com/en-us/power-bi/service-gateway-enterprise-manage-ssas) and performed AD lookup mapping. After that, we were able to connect the the SSAS data source and be able to see the tables. But when trying to create tan visual, we have received the following error: "Couldn't retrieve the data for this visual. Please try again later. Please try again later or contact support. If you contact support, please provide these details."

Activity ID407e2a7b-e1de-4cff-9ec3-e27808baa299

Request ID5bab7aff-c783-3a4c-6e53-1ea0dacd11ed

Correlation IDb464e0c0-9391-ed91-2da9-5c386608389c

TimeThu Apr 05 2018 10:13:01 GMT-0500 (Central Daylight Time)

Version13.0.4829.217

Cluster URIhttps://wabi-us-north-central-redirect.analysis.windows.net

After checking the gateway logs, the error code appear to be 1056899072. Can someone please help with this issue?

Below is the error message from the log:

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 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

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 ---

[v-jiascu-msft]

Hi @117325,

Error message from the logs:  The name provided is not a properly formed account name.

How did you format the user names used in the mapping? It should be an effective user name.

Best Regards,

Dale

[117325]

This is what we did:

How to configure your gateway to perform the AD Lookup:

1. Download and install the latest gateway
2. In the gateway, you need to change the On-premises data gateway service to run with a domain account (instead of a local service account – otherwise the AD lookup won’t work properly at runtime). You'll need to restart the gateway service for the change to take effect. Go to the gateway app on your machine (search for “On-premises data gateway”). To do this, go to Service settings > Change service account. Make sure you have the recovery key for this gateway, since you'll need to restore it on the same machine unless you want to create a new gateway instead.

3. Navigate to the gateway’s installation folder, C:\Program Files\On-premises data gateway as an administrator, to ensure that you have write-permissions, and edit the following file:

   Copy

   Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config 

4. Edit the following two configuration values according to your Active Directory attribute configurations of your AD users. The configuration values shown below are just examples – you need to specify them based on your Active Directory configuration.

   

5. Restart the On-premises data gateway service for the configuration change to take effect.