Microsoft Sql Server 2005 Error 916
Contents |
Home > Tech Hub > The server principal ‘A' is not able to access the database ‘B' under the current security context (Microsoft SQL Server, Error:916) SQL Server The server principal ‘A' is not able to access the database ‘B' under the current the server principal is not able to access the database under the current security context. sql 2012 security context (Microsoft SQL Server, Error:916) by Desiree Harris on July 1, 2008 Hi
User Mapping In Login Properties Of Microsoft Sql Server Management Studio
All! I ran into an issue that I could not resolve for two days and, with the help of MS, it is finally
Sql Server Message 916 Dynamics Sl
resolved. It was enough of a thorn in my side that I thought I should post it online in hopes that it will help some resolve it a lot faster. The error: The server principal 'A' is
Error 916 In Sql Server 2008 R2
not able to access the database 'B' under the current security context (Microsoft SQL Server, Error:916) The issue: This issue occurs with SQL Server 2008 RC0 tools. Using SQL authentication, I could connect to database engine but I could not expand the ‘Databases’ node. It would result in the error above. The issue is with SQL Server Management Studio itself, not the database engine or any other aspect of SQL Server. I could connect to the the server principal is not able to access the database master SQL installation from another server running SQL Server 2008 RC0, using SQL authentication, and expand the ‘Databases’ node without any errors. But I couldn’t connect locally using SQL authentication. In a nutshell: Server A – While logged in locally on Server A, I could not connect and expand the ‘Databases’ node successfully using SQL authentication. Server B – I could connect to the SQL instance on Server A and expand the ‘Databases’ node using SQL authentication successfully. Based on my current understanding of the issue at hand, there are several work-a-rounds to correct this issue. Hopefully, one of them will work for you. Work around #1: 1.Within SQL Server Management Studio, view Object Explorer Details window by selecting View, Object Explorer Details in menu (or hitting F7) 2.Right-click on the column header and unselect 'Collation.'3.Refresh the server in Object Explorer and enumerate the databases Work around #2: 1.Within SQL Server Management Studio, view Object Explorer Details window by selecting View, Object Explorer Details in menu (or hitting F7) 2.In Object Explorer window click at Databases folder 3.In Object Explorer Details window right-click at the column header and select ‘Reset view’. 4.Refresh Databases folder Work around #3: 1.Check the database options for the “Auto Close” setting. If it is set to “True,” change it to “False” and test again. Further explanation: Collation for an offline database
2, 20107 Share 0 0 Note: If you’re reading this more than a few months away from July of 2010, do more research. Never trust an old blog as gospel on anything, including my entries. Always refer to Books Online for the authoritative answer, sqlstate 08004 (error 916) and if it’s wrong, file a bug against it using the “Feedback” Button. It kinds database is not accessible object explorer of goes without saying (so of course I’m saying it) that unless you have a *really* compelling reason to change anything in the how to map user to database in sql server system databases you shouldn’t. And by “system databases” what I mean are the big four: 1. master 2. model 3. msdb 4. tempdb In some cases however - specifically in the security area - we (Microsoft) http://www.sherweb.com/blog/the-server-principal-a-is-not-able-to-access-the-database-b-under-the-current-security-context-microsoft-sql-server-error-916/ have been less than clear on the system databases. I want to address one particular issue that’s been going around in discussions on the web, so I want to make sure I clear this up carefully. Statement: Don’t remove the “guest” account from the msdb system database. Hopefully that’s clear. Just don’t remove it. It’s not a bug that it's in there.You need to keep the guest account in msdb for LOTS of stuff https://blogs.msdn.microsoft.com/buckwoody/2010/08/02/dont-mess-with-the-system-databases-in-sql-server-or-error-916/ to work, from Policy Based Management (PBM) all the way to SQL Server Management Studio. If you do remove it, you’re apt to get this message(but only if you’re not in the sysadmin group): Failed to retrieve data for this request. (Microsoft.SqlServer.Manager.Sdk.Sfc) Additional Information: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) The server principal “Buck” is not able to access the database “msdb” under the current security context. (Microsoft SQL Server, Error: 916) I know, this is a very rare thing, and if you change something and then things quit working, you’ll probably put 2 + 2 together to know what happened. But just in case an admin removes it and you can’t access your databases through SSMS any more, well, there you go. We DO have documentation on this: http://msdn.microsoft.com/en-us/library/ee342155.aspx and we’ll be updating the security best practices whitepapers we have to make this very clear. But since some guidleines tend to sound like you should remove guest from EVERY database, I wanted to make sure you know what to do in the meantime. My friend Cliff Dibble, a Principal Program Manager on the same team at SQL Server I worked at has provided us a script you can use to see if you have the issue: /* Find the issue of 916 if result set is e
916) - by dbh Status : Closed as Fixed Fixed This item has been fixed in the current or upcoming version of this product. A more https://connect.microsoft.com/SQLServer/feedback/details/354291/the-server-principal-is-not-able-to-access-the-database-under-the-current-security-context-microsoft-sql-server-error-916 detailed explanation for the resolution of this particular item may have been provided in the comments section. 14 0 Sign into vote ID 354291 Comments 14 Status Closed Workarounds 2 Type Bug Repros https://www.youtube.com/watch?v=wWTGvszQ9nM 3 Opened 6/30/2008 7:22:23 AM Access Restriction Public Description I am running into an issue that I really need resolved today. Simply put, I am getting the error: The server principal "dhtest" is not sql server able to access the database "dhtest2" under the current security context. (Microsoft SQL Server, Error: 916) But, the details are a little fuzzy I have two installations of SQL Server 2008 RC0. Microsoft SQL Server 2008 (CTP) Enterprise Edition (64-bit) CTP is installed on one server running Windows Server 2008 x64. And, Microsoft SQL Server 2008 (CTP) Enterprise Edition CTP is installed on the other server running Windows Server microsoft sql server 2003. Both were installed with the same installation options (the SQL services are all running using a local admin account). I created two databases on the x64 server: db: dhtest user: dhtest with dbo permission dhtest db: dhtest2 user: dhtest2 with dbo permissions to dhtest2 I then try connecting via sql server management studio using SQL authentication and get this error: The server principal "dhtest" is not able to access the database "dhtest2" under the current security context. (Microsoft SQL Server, Error: 916) But . . . I can connect to the x64 server from the server running Windows Server 2003 with SQL server management studio just fine. No errors at all and I have access to the assigned database as expected. I also tested connecting from the x64 server to the Windows server 2003 with sql management studio and got the same error. So... it appears to be a security setting ont the x64 box. In event viewer I see the errors below but it doesn't make sense because the Windows Firewall is turned off. The Windows Filtering Platform has blocked a bind to a local port. Application Name: \device\harddiskvolume1\windows\system32\svchost.exe Network Information: Source Address: 0.0.0.0 Source Port: 59535 Protocol: 17 Process ID: 240 Application Name: \device\harddiskvolume2\program files (x86)\microsoft sql ser
Επιλέξτε τη γλώσσα σας. Κλείσιμο Μάθετε περισσότερα View this message in English Το YouTube εμφανίζεται στα Ελληνικά. Μπορείτε να αλλάξετε αυτή την προτίμηση παρακάτω. Learn more You're viewing YouTube in Greek. You can change this preference below. Κλείσιμο Ναι, θέλω να τη κρατήσω Αναίρεση Κλείσιμο Αυτό το βίντεο δεν είναι διαθέσιμο. Ουρά παρακολούθησηςΟυράΟυρά παρακολούθησηςΟυρά Κατάργηση όλωνΑποσύνδεση Φόρτωση... Ουρά παρακολούθησης Ουρά __count__/__total__ Microsoft SQL Server, Error: 916,(Fixed in 1 minute) Sot Kanna ΕγγραφήΕγγραφήκατεΚατάργηση εγγραφής Φόρτωση... Φόρτωση... Σε λειτουργία... Προσθήκη σε... Θέλετε να το δείτε ξανά αργότερα; Συνδεθείτε για να προσθέσετε το βίντεο σε playlist. Σύνδεση Κοινή χρήση Περισσότερα Αναφορά Θέλετε να αναφέρετε το βίντεο; Συνδεθείτε για να αναφέρετε ακατάλληλο περιεχόμενο. Σύνδεση Στατιστικά στοιχεία 517 προβολές 0 Σας αρέσει αυτό το βίντεο; Συνδεθείτε για να μετρήσει η άποψή σας. Σύνδεση 1 4 Δεν σας αρέσει αυτό το βίντεο; Συνδεθείτε για να μετρήσει η άποψή σας. Σύνδεση 5 Φόρτωση... Φόρτωση... Φόρτωση... Η δυνατότητα αξιολόγησης είναι διαθέσιμη όταν το βίντεο είναι ενοικιασμένο. Αυτή η λειτουργία δεν είναι διαθέσιμη αυτήν τη στιγμή. Δοκιμάστε ξανά αργότερα. Δημοσιεύτηκε στις 28 Μαρ 2016Microsoft SQL Server, Error: 916,(Fixed in 1 minute) Κατηγορία Πρόσωπα και ιστολόγια Άδεια Τυπική άδεια YouTube Εμφάνιση περισσότερων Εμφάνιση λιγ