Microsoft sql server ошибка 916

Wondering how to fix SQL Server Error 916. We can help you.

Often while connecting to SQL Server database using SQL Server Management Studio with limited permissions, we may face Microsoft SQL Server error 916.

Here at Bobcares, we often get requests from our customers to fix similar Microsoft SQL server issues as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix this error for our customers.

What causes SQL Server Error 916

A typical error message is given below:

Following are some of the causes for this error:

1. When a user with limited permissions tries to view the column data in a selected header.

2. At times, the database may be in offline mode.

3. Several databases with different collations are on the same instance, that is why SQL Server Management Studio is unable to retrieve the collation.

4. The database is configured to an auto-closed state.

5. Sometimes the database may get corrupt due to some malware, improper shutdown, or when the database goes in suspect mode.

How to fix SQL Server Error 916

Following are the two methods to fix this error.

1. Via SQL Server Management Studio (SSMS)
2. With the help of T-SQL

Steps for Fixing the error 916 via SSMS

1.  Firstly, connect the SQL Server instance having valid credentials using SSMS.

2. And go to the Object Explorer Details followed by the View Menu or press F7 for the same.

3. After that, open the Databases folder.

4. Then go to the object explorer and right-click to open the column header.

5. After that, right-click on the column header and uncheck all of the optional columns.

6. Finally, click the refresh button.

Now we will be able to see the database.

Often unchecking the COLLATION option automatically fixes the issue.

Steps for Fixing error code 916 via TSQL Query

We can connect to the database via Transact-SQL. Grant the specific login access to the named database TEST_DB, for instance.

We can use the following syntax:

USE msdb;
GO
GRANT CONNECT TO [TEST_DB/BOB];

Now we can try either of the following to fix this error.

1. Disabling Collation

1. First, we need to select the Object Explorer Details under the View section within the SSMS.

2. Then right-click on Column Header and deselect Collation.

3. Finally, refresh the server and operate a database.

2. Disabling the Auto Close setting of the database

Here we need to check the Auto Close setting of the database, set it to False, and proceed further.

[Need assistance? We can help you]

Conclusion

In short, we saw how our Support Engineers fix SQL Server Error 916 for our customers.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Know About SQL Server Error 916 and How to Fix It!

SQL Server is a relational database management system developed by Microsoft while focusing on large enterprise environment work over a network. The First version of SQL Server is 1.0 and released in the year 1989, the latest version is MS SQL Server 2016 Community Technology Preview 2.4 (CTP 2.1) released on September 30, 2015. This article is going to talk about SQL server error 916 in depth for users.

Table of Content

• Problem Identifying
• SQL Server Error 916
• Most Common Symptoms
• Resolving All of the Issues
• How to Resolve the Problem
• Bringing It All Together

Problem

Accessing the SQL server database by using SQL Server Management Studio having a limited number of permissions (database read or write) may produce the SQL Server Error 916 and the message displayed on the screen is – “The server principal username is unable to access the database databasename under the current security context.”

The main problem is due to bugs present in SQL Server Management Studio that prevents the user to connect to the database and refuses to display the database list. There may be several other reasons behind the getting SQL Server Error 916.

• The user is not permitted to view the data of selected column within the database.
• The database is currently not available.
• There are multiple columns such as Size, Space available, Data Space Used, Default file group, Index Space Used, Mail host, Primary file path and user has added at least one of them to the list of Object Explorer Details.
• If the Auto Close option for the database is enabled, then Collation column cannot be retrieved by SQL Server Management Studio (SSMS).
• For a database, Collation column contains NULL.

Due to the above causes, the error message will be displayed to the user.

SQL Error 916 – Symptoms

The symptoms of the SQL Server error 916 may vary depending upon the different scenarios explained further:

Symptom 1:

In SQL Server 2008, if a user tries to expand the database folders under a node even if he is not a member of a Sysadmin fixed server role or does not have the authority to access the database. If the guest user wants to expand the database nodes, connection permission is required otherwise; the following error message will be displayed:

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)

Symptom 2:

In SQL Server 2005, if a guest user who is neither a member of a Sysadmin fixed server role, nor having the permissions is able to expand the database node but cannot view the database properties. In this case, the user will receive the following error message:

Cannot show requested dialog.(SqlMgmt)

Additional Information:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Note: SQL Server error 916 is displayed even though the user is a database owner of that database.

Symptom 3:

A product of the Microsoft family, Microsoft Office Communications Server 2007 (OCS 2007) is affected by this issue and the services will not start even after the server is started. The following error message will be invisible in the Event Viewer:

Event Type: Error
Event Source: OCS User Services
Event Category: (1006)
Event ID: 30962
Date:
Time:
User: N/A
Computer: ‘computer name’

Description: Connection to back-end database succeeded, but failed to execute registration-stored procedure on back-end. This error should not occur under normal operating conditions. Contact product support.

Back-end Server: ‘server name’ Database: ‘database name’ Sql Native error: 916 Connection string of: driver={SQL Native Client}; Trusted Connection=yes; Auto Translate=No; Server=’server name’; Database=’database name’

Cause: Possible issues with back-end database.

Solution: Ensure the back-end is functioning correctly.

The above-mentioned symptoms are most common and lead to SQL Server Error 916 for SQL Server Management Studio. If the user finds any of them, he may try the best possible solutions described below to remove the error.

Also Read: How to View MDF File Without SQL Server

Resolving the Symptoms of SQL Error Code 916

In order to view the granted permissions for the guest-user, the following command is helpful if run by a member of a Sysadmin fixed server. Therefore, follow the below query to tackle SQL server management studio error 916 :

USE msdb;
 SELECT prins.name AS grantee_name, perms.*
 FROM sys.database_permissions AS perms
 JOIN sys.database_principals AS prins
 ON perms.grantee_principal_id = prins.principal_id
 WHERE prins.name = ‘guest’ AND perms.permission_name = ‘CONNECT’;
 GO

On running the above command, the users get to see a table containing all the attributes of guest user.

However, an empty result shows that guest user is in disable mode in the database and again the SQL Server error 916 will be occur. To overcome the error you may perform the following available solutions.

How to Remove the SQL Server Error 916:

To remove the error for accessing the database, the user can perform the following solutions. Evidently, any one of them will help you.

Solution No-1.

Let’s checkout the first way to fix the issue.

1. Select the Object Explorer Details under View section within the SSMS.
2. Right click on Column Header and deselect Collation.
3. Refresh the server and operate a database.

Solution No-2.

Here comes the second solution.

1. Click on View > Object Explorer details from the menu option of SSMS.
2. Within Object Explorer window, click on Database folder.
3. Right – click on the column header and select Reset View.
4. In order to perform the final step, refresh the Database folder.

Solution No-3.

Finally, we’re going to checkout the final solution.

1. Check the Auto Close setting of the database, set it to False and proceed further.

The above-described solutions may resolve the Microsoft SQL server management studio error 916 and the user can proceed with the workflow.

Conclusion

With the help of this page, an individual can be aware about the SQL Server error 916, the problems occur due to it, & what the causes are. Thus, a user can get in-depth knowledge about the SQL server and the possible error message displayed if the guest user wants to expand the database node in order to view its data.

title	description	author	ms.author	ms.date	ms.service	ms.subservice	ms.topic	helpviewer_keywords
MSSQLSERVER_916	The login does not have sufficient permissions to connect to the named SQL Server database. See an explanation of the error and possible resolutions.	MashaMSFT	mathoma	04/04/2017	sql	supportability	reference	916 (Database Engine error)

MSSQLSERVER_916

[!INCLUDE SQL Server]

Details

Attribute	Value
Product Name	SQL Server
Event ID	916
Event Source	MSSQLSERVER
Component	SQLEngine
Symbolic Name	NOTUSER
Message Text	The server principal «%.*ls» is not able to access the database «%.*ls» under the current security context.

Explanation

The login does not have sufficient permissions to connect to the named database. Logins that can connect to this instance of [!INCLUDEssNoVersion] but that do not have specific permissions in a database receive the permissions of the guest user. This is a security measure to prevent users in one database from connecting to other databases where they do not have privileges. This error message can occur when the guest user does not have CONNECT permission to the named database and the trustworthy property is not set. This error message can occur when the guest user does not have CONNECT permission to the named database.

When CONNECT permission to the msdb database is denied or revoked, [!INCLUDEssManStudioFull] can receive this error when Object Explorer tries to show the Policy Based Management status of each database. Object Explorer uses the permissions of the current login to query the msdb database for this information, which causes the error. The following error message also occurs:

Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

User Action

[!WARNING]
Before circumventing this security measure be sure to have a clear understanding of users are authenticated in various databases. The following methods may allow users that have permissions in one database to connect to other databases which could expose data to a malicious user. When contained databases are enabled, the following steps can allow database owners in one database to grant access to other database on the instance of [!INCLUDEssNoVersion].

You can connect to the database in one of the following ways:

• Grant the specific login access to the named database. The following example grants the login Adventure-WorksLarry access to the msdb database.

  USE msdb ;
  
  GO
  
  GRANT CONNECT TO [Adventure-WorksLarry] ;

• Grant the CONNECT permission to the database named in the error message for the guest user. The following example grants the CONNECT permission to the msdb database for the user guest.

  USE msdb ;
  
  GO
  
  GRANT CONNECT TO guest ;

• Enable the TRUSTWORTHY property on the database that has authenticated the user.

  ALTER DATABASE AdventureWorks SET TRUSTWORTHY ON;