Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Help ! Can't login, SELECT permission denied ....... Expand / Collapse
Author
Message
Posted Sunday, June 15, 2008 11:16 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 2:12 AM
Points: 193, Visits: 552
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 ?

Post #517361
Posted Tuesday, June 17, 2008 6:33 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, November 20, 2014 4:37 AM
Points: 1,275, Visits: 932
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.
Post #518157
Posted Tuesday, June 17, 2008 7:56 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 2:12 AM
Points: 193, Visits: 552
Thanks.
I fixed the problem by myself.
In fact, what I did was what you suggested.
Thanks a lot.
Post #518694
Posted Thursday, July 3, 2008 10:07 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, March 3, 2011 5:28 PM
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...:D
- dave
Post #528208
Posted Thursday, November 6, 2008 3:37 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, November 5, 2012 6:56 AM
Points: 1, Visits: 75
thanks! It helps in my case on different system table
Post #598592
Posted Thursday, March 3, 2011 3:26 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, March 18, 2014 8:07 AM
Points: 56, Visits: 168
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

Post #1072977
Posted Saturday, March 5, 2011 3:04 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:33 PM
Points: 6,626, Visits: 14,197
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"
Post #1073681
Posted Friday, July 12, 2013 10:07 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 7, 2014 9:15 AM
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



Post #1473133
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse