Forum Discussion

Frequent Visitor

8 years ago

On-Premise Gateway not Connecting the SSAS Data Properly

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

Icon for Microsoft Employee rank

Microsoft Employee

8 years ago

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
Frequent Visitor
8 years ago
This is what we did:
How to configure your gateway to perform the AD Lookup:
Download and install the latest gateway
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.
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
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.
Restart the On-premises data gateway service for the configuration change to take effect.