The server principal 'xxx' is not able to access the database 'yyy' under the current security context (Microsoft SQL Server, Error:916)

The issue:

This issue occurs with SQL Server 2008 Management Studio.  Can connect to database engine but cannot 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.

There are several work-a-rounds to correct this issue.

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 'Collation.', and deselect it.
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.

Reason for error:

Collation for an offline database is returned as NULL by the engine, and SSMS currently interprets NULL values as a permissions issue.  The error will occur even if Object Explorer Details view is not open.  The same issue will occur if you try to enable a setting that you don't have permission to access on all databases, for example data space used.

Add to Favourites

Print this Article