Forum Discussion
Unaable to connect to SQL Server On-premise
- 1 year ago
Run Power BI Desktop as Administrator
The issue occurs because Power BI Desktop may require elevated permissions when connecting to SQL Server with certain user accounts or impersonation scenarios.
Steps:
- Close Power BI Desktop if it's currently open.
- Right-click on the Power BI Desktop shortcut and select "Run as Administrator".
- Open a new blank report and try connecting to your SQL Server again.
Why this works:
When running as Administrator, Power BI Desktop gains elevated permissions, allowing it to properly load necessary assemblies (like System.EnterpriseServices) and bypass potential restrictions related to impersonation or limited user rights.
If this solution works for you, the problem is likely related to permission constraints when connecting with a separate user or service account. Using elevated permissions resolves this mismatch.
Marking this as solved will help others encountering the same issue!
Run Power BI Desktop as Administrator
The issue occurs because Power BI Desktop may require elevated permissions when connecting to SQL Server with certain user accounts or impersonation scenarios.
Steps:
- Close Power BI Desktop if it's currently open.
- Right-click on the Power BI Desktop shortcut and select "Run as Administrator".
- Open a new blank report and try connecting to your SQL Server again.
Why this works:
When running as Administrator, Power BI Desktop gains elevated permissions, allowing it to properly load necessary assemblies (like System.EnterpriseServices) and bypass potential restrictions related to impersonation or limited user rights.
If this solution works for you, the problem is likely related to permission constraints when connecting with a separate user or service account. Using elevated permissions resolves this mismatch.
Marking this as solved will help others encountering the same issue!
Thanks. I didn't realize although login as "Administrator", but turned out I am open Power BI Desktop which is not as Admin.
Changed the shortcut to "Run as administator" and now working fine.
Thanks for all the help.