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