If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > Microsoft SQL Server > SELECT permission was denied Errors on MSSQL

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-27-09, 08:11
jrocheleau jrocheleau is offline
Registered User
 
Join Date: Apr 2009
Posts: 3
SELECT permission was denied Errors on MSSQL

I am trying to set up a DotNetNuke installation on Windows XP with IIS 5.1 and MSSQL Server Express 2008. I have checked the permissions on the account trying to access the database and everything is checked. However I keept getting the error, do I need to make ever user in the database an admin to edit and do everything to the database?

Code is Below:
Code:
Index #: 0
Source: .Net SqlClient Data Provider
Class: 14
Number: 229
Message: The SELECT permission was denied on the object 'sysobjects', database 'mssqlsystemresource', schema 'sys'.

Index #: 1
Source: .Net SqlClient Data Provider
Class: 14
Number: 229
Message: The SELECT permission was denied on the object 'sysobjects', database 'mssqlsystemresource', schema 'sys'.
Reply With Quote
  #2 (permalink)  
Old 04-27-09, 14:59
tosscrosby tosscrosby is offline
Registered User
 
Join Date: Apr 2008
Location: Along the shores of Lake Michigan
Posts: 242
The best thing to do is create appropriate roles and assign them to your users. Maybe one with dataread only, another for dataread/datawrite (if applicable), etc, all pointing to the appropriate database and/or tables within the database. A whole lot easier to maintain a few roles as opposed to many users.

--Edit: NEVER make all users an admin on the instance!
Reply With Quote
  #3 (permalink)  
Old 02-03-12, 03:53
psen78@yahoo.com psen78@yahoo.com is offline
Registered User
 
Join Date: Feb 2012
Posts: 1
It look like someone would have revoked the permissions on sys.configurations
for the public role. Or denied access to this view to this particular user. or user has been created after public role removed from the sys.configurations tables.

Provide SELECT permission to public user sys.configurations object.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On