Search

The server principal "testuser" is not able to access the database "msdb" under the current security context. by Namburu

Closed
as Fixed Help for as Fixed

5
0
Sign in
 to vote
Type: Bug
ID: 424329
Opened: 3/17/2009 3:23:45 AM
Access Restriction: Public
2
Workaround(s)
7
User(s) can reproduce this bug
Recently we have migrated to SQL server 2008 and we see some connectivity issue for the users who are not part of the sysadmin group.

A read only user able to connect to SQL server using SQL Server 2008 Management Studio successfully, but when he tries to expand the databases node gets the error messge
The server principal "testuser" is not able to access the database "msdb" under the current security context.
Details (expand)
Product Language
English

Version

SQL Server 2008 - Enterprise Edition

Category

Tools (SSMS, Agent, Profiler, etc.)

Operating System

Win2003 Enterprise Server (RTM)
Operating System Language
English
Steps to Reproduce
take a user user with readonly permissions and log into the server through Management studio and try to expand databases node.
Actual Results
error message" The server principal "testuser" is not able to access the database "msdb" under the current security context. " is thrown
Expected Results
should be able to see all the databases.

Platform

32
File Attachments
0 attachments
Sign in to post a comment.
Posted by Ion Freeman on 3/23/2011 at 6:35 AM
Is there a hotfix for this? Is it coming in a service pack? I'm using SQL Server 2008. Our DBAs are not super interested in granting permissions just so we can use the object browser, so it would be nice if this were fixed. I see the bug is marked as fixed, and that you've decided to fix it before Denali, but I would like to know when and how I can get the fix.
Posted by Microsoft on 1/18/2011 at 12:33 AM
Dear customers,

We have decided to fix this issue before Denali release.

Regards,
Sumesh
Posted by pellet88 on 10/4/2010 at 11:46 AM
I don't feel the workarounds are good enough either. We have to disable guest when we install also and don't want to have to add users to the msdb database. It would be nice to fix this before SQL 11.
Posted by SQLRocker on 7/14/2010 at 2:03 PM
The workaround is NOT good enough. Its a security issue in our company. We have to disable the guest users everywhere & this WORKED in sql 2005. We cannot enable guest user or add hundreds of ID's to msdb. Fix it.
Posted by Aaron Christneson on 5/24/2010 at 6:58 AM
I found a solution

use msdb
grant connect to guest
Posted by SA-Sys-Admin on 4/13/2010 at 1:18 PM
Is there a fix for this issue? I'm having the same issue and even though the work around works, i'd like to get away from having to grant all users access to msdb.
Posted by hellomahesh on 9/22/2009 at 7:00 AM
Any solution or workaround for specific to fshaik problem mentioned above?

Posted by Harinarayan on 6/17/2009 at 4:36 PM
Workaround suggested worked for me.
Posted by Microsoft on 6/11/2009 at 2:06 PM
Hi Rama,

Thank you for the feedback. Our current plan is to address this issue in SQL 11. I will keep you updated as we move forward.

Cheers,
Hongfei
Posted by faiazps215 on 4/17/2009 at 7:01 PM
facing the same issue : ErrorMessage: ErrorMessage: Could not update the metadata that indicates table [DBO].[tblabcis enabled for Change Data Capture. The failure occurred when executing the command '[sys].[sp_cdc_add_job] @job_type = N'capture''. The error returned was 916: 'The server principal "S-1-9-3-644345232-1214516278-707265154-4152033466." is not able to access the database "msdb" under the current security context.'. Use the action and error to determine the cause of the failure and resubmit the request. ErrorProcedure: sp_cdc_enable_table_internal ErrorSeverity: 16 ErrorState: 1 ErrorLine: 607 ErrorNumber: 22832
Posted by Riley Schumacher on 4/8/2009 at 7:01 AM
We encounter a similar problem with non sys admin ids when they expanded the Database section in 2008 Management Studio. We determine the problem was that in the msdb the guest id had been disabled. We disable the guest ID in msdb when we install and configure the instance as a security task. If you grant msdb to the id with no rights the id can expand the databases part of Management Studio without the error. We did not have this problem in the 2005 Management Studio.
Sign in to post a workaround.
Posted by SQLRocker on 7/14/2010 at 2:44 PM
NOT GOOD ENOUGH. It worked in SQL 2005 , It should work in SQL 2008 also. We can't enable guest user or add 100's of users to MSDB to weaken our security!
Posted by Riley Schumacher on 4/8/2009 at 7:01 AM
We encounter a similar problem with non sys admin ids when they expanded the Database section in 2008 Management Studio. We determine the problem was that in the msdb the guest id had been disabled. We disable the guest ID in msdb when we install and configure the instance as a security task. If you grant msdb to the id with no rights the id can expand the databases part of Management Studio without the error. We did not have this problem in the 2005 Management Studio.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement