October 2, 2017 at 1:46 pm
I am running SQL Server 2014 CU5 on Server 2012 and have an issue with opening the SQL Server Error Logs. When I naviage to Management and click on the plus sign next to SQL Server Logs I get the error message. Below is the text from the message.
Failed to retrieve data for this request.(Microsoft.SqlServer.Management.Sdk.Sfc)
An exception occurred while executing a Transact-SQLstatement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
A severe error occurred on the current command. Theresults, if any, should be discarded. (Microsoft SQL Server, Error: 0)
What is interesting is that it has been happening since we installed SQL Server - we have been going to the log file to check our error.
I would like to finally get this fix, so any help is appreciated.
Jeff
October 2, 2017 at 2:30 pm
jayoub - Monday, October 2, 2017 1:46 PMI am running SQL Server 2014 CU5 on Server 2012 and have an issue with opening the SQL Server Error Logs. When I naviage to Management and click on the plus sign next to SQL Server Logs I get the error message. Below is the text from the message.Failed to retrieve data for this request.(Microsoft.SqlServer.Management.Sdk.Sfc)
An exception occurred while executing a Transact-SQLstatement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
A severe error occurred on the current command. Theresults, if any, should be discarded. (Microsoft SQL Server, Error: 0)
What is interesting is that it has been happening since we installed SQL Server - we have been going to the log file to check our error.
Since you've had problems since installing, did you check the Summary.txt log in the setup bookstrap\Log directory after the installation?
Did you run a repair on the instance from the installation center or through setup.exe?
Sue
October 2, 2017 at 2:52 pm
Also, Since you are getting this error when you are trying to access SQL error logs from your SSMS. Just wanted to make sure, did you try to open SQL error log using notepad or some text editor by navigating to your LOGS folder. You should be seeing archived and current error log in that folder.
October 2, 2017 at 6:02 pm
Thank you very much for the reply
I actually did not look at the set up log, but maybe I should
I also can access the logs Current and Archived logs using notepad just fine.
I will see if running a repair will help and keep you posted. If anybody has seen this issue before please let me know.
Jeff
October 4, 2017 at 8:45 am
I'd upgrade SSMS, at least to 17.1 here and try again. There can be some flakiness at times with SSMS.
October 5, 2017 at 12:26 pm
Still trying to figure this one out I have done the following.
I used profile to figure out what script is running when trying to open the SQL Error logs and i captured the script and found out it is using the following stored procedure.
exec master.dbo.sp_enumerrorlogs
So when I try to execute this "exec master.dbo.sp_enumerrorlogs" in a new query window I get the following error
Msg 22004, Level 16, State 1, Line 5
Failed to open loopback connection. Please see event log for more information.
Msg 22004, Level 16, State 1, Line 5
Error log location not found.
I opened the SP and found that it calls
I checked the registry and the path to the error logs wasfine. I also checked the start upperameters of the service and it was also fine.
How does this Stored Procedure determine the path to theerror logs?
Also I was told running the Repair on SQL server is notan option because it’s a production database server.
Please let me know if you can. Any help is appreciated.
Jeff
October 5, 2017 at 12:58 pm
jayoub - Thursday, October 5, 2017 12:26 PMStill trying to figure this one out I have done the following.
I used profile to figure out what script is running when trying to open the SQL Error logs and i captured the script and found out it is using the following stored procedure.
exec master.dbo.sp_enumerrorlogsSo when I try to execute this "exec master.dbo.sp_enumerrorlogs" in a new query window I get the following error
Msg 22004, Level 16, State 1, Line 5
Failed to open loopback connection. Please see event log for more information.
Msg 22004, Level 16, State 1, Line 5
Error log location not found.
I opened the SP and found that it callsI checked the registry and the path to the error logs wasfine. I also checked the start upperameters of the service and it was also fine.
How does this Stored Procedure determine the path to theerror logs?
Also I was told running the Repair on SQL server is notan option because it’s a production database server.
Please let me know if you can. Any help is appreciated.
sp_readerrorlog calls xp_readerrorlog so there is no direct way to see where it is getting the location from. Most likely the registry as it is stored there.
You may want to check the MS ODBC version as 13.0 can have this issue. It is fixed in 13.1
The issue is reported in this link, applies to more than just SQL Server 2016. I think it's more dependent on the version of SSMS. Please read symptom #2 in the article:
SQL Server 2016 Agent fails to start or “Failed to retrieve data†error when you try to read error log from SSMS 2016
Sue
October 5, 2017 at 5:22 pm
Thank you very much.
i will update the drive in our dev environment and see what happens.
I will post the results.
Jeff
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply