Post reply

Unable to connect: Msg 229, level 14, State 5 SELECT permission denied on object ''spt_values'' database ''master'', owner ''dbo''

  • January 18, 2005 at 9:15 am

    #66390

    We're getting a strange error msg with one login using

    query analyzer:

    "Unable to connect: Msg 229, Level 14, State 5

    [Microsoft][ODBC Sql Server Driver][Sql Server]

    SELECT permission denied on object 'spt_values',

    database 'master', owner 'dbo' "

    Here's the strange thing: One developer telling me that he can't connect to SQL thru Query Analyzer which returns above permission deny error. Rest all developers in the team can connect to the same with out any problem. they were trying to conn using there Windows authentications... all there windows a/c where added to NTgroup. and given READ/WRITE to all.

    This is a system table in master. I've checked for blocking, open transactions and the knowledge base and

    come up with nothing.  

    Only one user unable to connect Why??? All other logins seem fine.  Any ideas would be much appreciated.

    Thanks, - venkat

     

  • January 18, 2005 at 10:19 am

    #537890

    I would check that PUBLIC has select access on spt_values in the master database.


    Shamless self promotion - read my blog http://sirsql.net

  • January 19, 2005 at 4:48 am

    #538019

    Yeah I did that. All users in PUBLIC DB role had SELECT permission on above table.

     Here we had problem with only one user... rest all users with same permission set able to connect. Thats bit confusing me...

    Any help???

    Thanks - Venkat

     

  • January 19, 2005 at 4:50 am

    #538020

    That user has not been removed from the PUBLIC role?


    Shamless self promotion - read my blog http://sirsql.net

  • January 19, 2005 at 6:40 am

    #538042

    Nope. I don't think we can remove an user from PUBLIC DB role...

    Thanks - Venkat

  • January 19, 2005 at 8:06 am

    #538080

    Sometimes, I come across this issue as well.  Ask the developer if he/she has modified his/her ODBC connection.  If they modified the ODBC and are trying to connect differently, then you may get this error.   

    What happens if you grant select on <>tablename> to <username>, using the NT Account the developer is in?

    Hope this helps.

    Scott

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply