Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Help ! Can't login, SELECT permission denied .......


Help ! Can't login, SELECT permission denied .......

Author
Message
onlo
onlo
SSC Veteran
SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)

Group: General Forum Members
Points: 207 Visits: 612
Dear all,

"SELECT permission denied on object 'configurations', database 'mssqlsystemresource', schema 'sys'"

This morning, I suddenly got this error when I use a SQL Login account to login through SQL 2005 Management Studio, 9.0.2047.

The login name doesn't have db_owner right but worked properly before.

I tried to fix the problem by :

USE master
GRANT SELECT ON sys.mssqlsystemresource.configurations TO PUBLIC

but failed :
Msg 15151, Level 16, State 1, Line 1
Cannot find the object 'configurations', because it does not exist or you do not have permission.

Though the problem could be fixed by adding sysadmin right to the user, I don't think it is a proper way to fix the error.

Any ideals ?
Robert-378556
Robert-378556
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1568 Visits: 1007
Why not sys.configurations?
Proper qualifier would be database.schema.objectname.
Run dbcc checkdb. If ok, check the log file, if someone dropped permissions. "public" must have select permission on this system view.
onlo
onlo
SSC Veteran
SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)SSC Veteran (207 reputation)

Group: General Forum Members
Points: 207 Visits: 612
Thanks.
I fixed the problem by myself.
In fact, what I did was what you suggested.
Thanks a lot.
hagebozu
hagebozu
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 Visits: 23
Thanks for this post. I'm not a DBA - just owner of a few databases on our server. I just experienced this problem the other day - was working in SSMS in the morning, and then I get back from lunch, and kaboom - I couldn't connect through SSMS anymore! My DBA kept telling me "I can see that you're logged-in right now! - what do you mean you can't get in?", but none the less, SSMS kept telling me it couldn't connect... This is the only post I could find anywhere online, help, or my manuals (after 3 days of searching) that had an answer for this specific issue.

So now that I've just learned of the existence of SQL-Server's "5th" system database, I am curious - if nobody (generally) even knows about it, and it isn't a database that can be restored from backup, how does this kind of accident happen - dropping the public role's permission to stuff on this database? I mean, aside from somebody executing a drop statement on purpose... Have you seen this a lot?

Oh well - thanks again! I mean, work stoppage was nice while it lasted, but you know...BigGrin
- dave
George Yin
George Yin
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 75
thanks! It helps in my case on different system table
bbsr
bbsr
Valued Member
Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)

Group: General Forum Members
Points: 57 Visits: 172
hi,

i know it is an old thread but i am having the same issue. I tired giving select permission to public on sys.configuration but still getting the same error message

"The SELECT permission was denied on the object 'configurations', database 'mssqlsystemresource', schema 'sys'. (Microsoft SQL Server, Error: 229)"

can there be any other reason??

thanks
Perry Whittle
Perry Whittle
SSCrazy Eights
SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)SSCrazy Eights (8.8K reputation)

Group: General Forum Members
Points: 8780 Visits: 16554
Non admin users have permissions on sp_configure to view SQL server configs.

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
irina hossain
irina hossain
Forum Newbie
Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)Forum Newbie (6 reputation)

Group: General Forum Members
Points: 6 Visits: 151
I had the similar problem.

I granted SELECT permission to database objects to a group. The users could query the tables, however, they couldn't see the table lists when they tried to expand tables in a database. The error message they were getting:

"The SELECT permission was denied on the object 'tables', database 'mssqlsystemresource', schema 'sys'."

When I was searching in Google, I found this article and executed the following query.

USE master
GO
GRANT SELECT ON [mssqlsystemresource].[sys].[tables] TO PUBLIC
GO

I However, received the following error:

"Cannot find the object 'tables', because it does not exist or you do not have permission."

Then I turned the trace ON and found that when the user tries to expand the table list, it executes a T-SQL batch behind the scene which uses SELECT from the object sys.tables and that is where the error was coming from. Then I ran the following query:

USE user_DB
GO
GRANT SELECT ON [mssqlsystemresource].[sys].[tables] TO PUBLIC
GO

It failed again with the error:
"Cannot find the object 'tables', because it does not exist or you do not have permission."

Finally, the following query worked:
USE user_DB
GO
GRANT SELECT ON [sys].[tables] TO PUBLIC
GO

Glad that it worked finally :-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search