August 5, 2015 at 7:31 am
I get the following error when I try to expand the sql server log in the management studio. My login is in the securityadmin server role.
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
A severe error occurred on the current command. The results, if any, should be discarded. (Microsoft SQL Server, Error: 0)
August 5, 2015 at 7:43 am
I would try running the command
exec sp_readerrorlog
In case that the bug is because of the GUI, it should work. If there is another problem, then you'll see the real error.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 5, 2015 at 8:40 am
Adi Cohn-120898 (8/5/2015)
I would try running the command
exec sp_readerrorlog
In case that the bug is because of the GUI, it should work. If there is another problem, then you'll see the real error.
Adi
I get the following error
Failed to open loopback connection.
August 5, 2015 at 8:55 am
A short search on Google on the error that you got pointed me to this old thread - http://qa.sqlservercentral.com/Forums/Topic767980-146-1.aspx which shows 2 possible solutions. Hope that it will help you.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 5, 2015 at 9:46 am
I noticed that SQL SERVER was running under NTSERVICE\MSSQLserver account. I changed that to run under domain service account and this resolved the issue Thank you!
August 5, 2015 at 10:03 pm
This was removed by the editor as SPAM
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply