Forum Discussion
DM_GWPipeline_Gateway_ImpersonationError
- 10 years ago
I just went back to try it again so that I could get a screenshot of the setup and it seems to be working now.
Hi adrianrog,
Could you please post a screenshot about your scenario? We need to know that which Authentication Method you choose when adding data source and the format of your account .
In addition, please make sure that the account being used matches the Authentication Method. Moreover, if you choose Windows Authentication Method, please install the gateway in a domain joined machine, which is in the same domain as the server running SQL Server instance.
Thanks,
Lydia Zhang
- adrianrog10 years agoNew Member
I just went back to try it again so that I could get a screenshot of the setup and it seems to be working now.
- Anonymous8 years agoNot applicable
We are getting the same error.
We have created a separate SSAS server and have not joined in our current domain.
The gateway gets connected successfully to the SSAS server in the domain.
So we decided to see what happens for a SSAS server not in the domain and we get this error.
Is there any workaround?