Home Dashboard Directory Help
Search

Failed to retrieve data for this request. - Microsoft.SqlServer.Management.Sdk.Sfc by CH121


Status: 

Closed
 as Fixed Help for as Fixed


7
0
Sign in
to vote
Type: Bug
ID: 376819
Opened: 10/21/2008 9:53:19 AM
Access Restriction: Public
1
Workaround(s)
view
1
User(s) can reproduce this bug

Description

UPDATE - Found workaround http://support.microsoft.com/default.aspx?scid=kb;EN-US;956179



Using Sql Server Management Studio 10.0.1600.22 and connecting to a sql server 2005 I receive the following error:
TITLE: Microsoft SQL Server Management Studio
------------------------------

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

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

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

------------------------------

The server principal "USERNAME" is not able to access the database "SybariEnterpriseManager" under the current security context. (Microsoft SQL Server, Error: 916)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3152&EvtSrc=MSSQLServer&EvtID=916&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------


Further Details:
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
Program Location:

at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DatabaseNavigableItemBuilder.<ReadData>d__0.MoveNext()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DatabaseNavigableItemBuilder.BuildDynamicItemWithQuery(IList`1 nodes, INodeInformation source, INavigableItem sourceItem, String urnQuery, Boolean registerBuilder, Boolean registerBuiltItems)
Details
Sign in to post a comment.
Posted by Rakesh Kesavan on 3/9/2012 at 9:08 AM
the issue got fixed after upgrading to SQL 2008 R2.

thanks,
Rakesh
Posted by Microsoft on 4/16/2010 at 8:32 AM
I'd like to inform you that the work that we did in the SQL Server 2008 R2 release as solved this problem.
Thank you,
Bill Ramos
Posted by Microsoft on 2/3/2009 at 10:32 AM
Another very helpful thing to do:

Just before you click to expand "Databases", start a Profiler trace (although you will have to start it with a more priviledged login than the "public" role one used in the bug, but I assume you have one).

Capture the activity to the server from the point of expanding "Databases" until you get the error you are reporting, then stop the trace and save it as a .trc file to attach to the bug.

Then optionally, you can distill the trace batches down to the offending script commands by pasting the trace batches one after another into a editor window in SSMS and executing them until you see the familiar error in the results pane. Then whittle the T-SQL down until it still repros the error.

For example, we already know that merely "use [xyz]" will fail with that error if you try it on a non-accessible database, but the assumption is you are seeing the error at a more unusual level than on the actual non-accessible database nodes.

Thanks,

Ed Dudenhoefer

Posted by Microsoft on 2/3/2009 at 9:37 AM
Thanks for your feedback! However, we have trouble repro the bug. Can you clarify in more detail the user repro, such as exactly where the unexpected error is occuring (expanding "Databases" perhaps, which would be unusual).

Thanks!

Mingwu Zhang
Sign in to post a workaround.
Posted by Danny Hummel on 2/26/2010 at 9:52 AM
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. Select the 'Databases' node, then 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 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.


Credit goes to: http://www.orcsweb.com/blog/desiree/the-server-principal-a-is-not-able-to-access-the-database-b-under-the-current-security-context-microsoft-sql-server-error-916/