May 28, 2015 at 11:38 am
After installing SSMS on some computers - the only way we can get SSMS to run correctly is to run it as the administrator. Is there a way where you don't have to do that? These end users are logging as themselves and have accounts in SQL Server all set up - but SSMS will only launch for them if we right click and select "run as administrator".
After doing some digging - it seems that this is a common problem out there. Any one find a work around?
Thanks!
May 28, 2015 at 1:30 pm
What error do you get when you try and run SSMS as a normal user? Does the user(s) getting the error have permissions on the db instance(s) with their regular accounts?
Joie Andrew
"Since 1982"
May 28, 2015 at 1:49 pm
I get the following error when trying to run it:
The 'VsDebugPresentationPackage, Version=10.0.0.0, Culture=neutrail, PublicKeyToken=B03f5f7f11d50a3a' package did not load correctly.
However - if you run it as the administrator it runs just fine. The user has sysadmin right in SQL Server - so it appears it has to do with something on the OS. The only solution I can see is to always run it with admin rights - which I would love not to do.
June 1, 2015 at 6:53 am
This is a client based permissions issue and not a SQL Server permissions issue.
You will need to either add the user to local admin on their machine, or lower the restrictions on the access control under Admin tools.
update... disable the policy under your Local Security Policy:
http://superuser.com/questions/464758/how-do-i-disable-administrator-prompt-in-windows-8
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply