Forum Discussion
Unable to Connect to SQL Server
Hello,
I just wanted to add my experience to this. As the Network Manager, I was not comfortable allowing a user to run with admin credentials, so I wanted to find a way around this issue.
I also did have to use Run As Admin to get the connection to work. I discovered that I only needed to do that to establish the connection, though. Once I did, the program could then be run without the Run As Admin option and it would work.
Hope that helps someone.
As the error message mentioned, it seems a permission issue when loading the assembly, please try to run Power BI Desktop as administrator. If it still doesn't work, please repair your .NET Framework, restart your server and try again to see if it works.
Regards,
Dear v-sihou-msft ,
It worked for me running as administrator. But is there a way to make it work with a regular user?
I´m using the admin credentials for SQL connection, but wanted to run PowerBI Desktop with regular user.
Thank you,
Eduardo
Hello,
I just wanted to add my experience to this. As the Network Manager, I was not comfortable allowing a user to run with admin credentials, so I wanted to find a way around this issue.
I also did have to use Run As Admin to get the connection to work. I discovered that I only needed to do that to establish the connection, though. Once I did, the program could then be run without the Run As Admin option and it would work.
Hope that helps someone.
Helped me, thank you :)
This issue came up this morning for one of my employees. We do not allow Run as Admin for most employees. The solution we used was to go into Power BI Desktop and "clear credentials" for "all sources"; this is under the Transform Data menu.
Not sure if this helps.
I made some changes - not sure which worked!
domain admin: worked
Added domain user as local admin: didn't work (or was there some delay?)
Real SQL server name was vanguard2, so I used that at first for this SCCM power bi dashboard. Then, as we retained the original server name alias for older applications when we upgraded the server a couple of years ago, I decided to use that name 'VANGUARD' for the data connection. deleted the credentials, then it worked too.
could it be related to SPN's?
actually, when i say it worked, it stalled at a new error - my data coming from SCCM for malware has multiple records with the same data (appears to be a malware ID to name list)
Run as Admin worked for me.
Vladimir
Yes it worked for me too
