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

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 376819 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 10/21/2008 9:53:19 AM
Access Restriction Public


UPDATE - Found workaround;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:


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:



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)
Sign in to post a comment.
Posted by mukesh115 on 9/1/2014 at 4:45 AM
simple solution for that ...

disconnect server from sql server authentication and re-connect server by windows authentication
Posted by Rakesh Kesavan on 3/9/2012 at 9:08 AM
the issue got fixed after upgrading to SQL 2008 R2.

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.


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).


Mingwu Zhang