In this article, we will discuss the error message “Msg 567: Unable to retrieve data for this section of the report. Following error occurred. File is not a recognizable trace file.“
Problem
I encountered this error while I was working with the Log files. I was trying to get various information about the stored procedures like date of creation, last modification, etc. You can visit my article “SQL Server stored procedure modified date” to know more.
- When I tried to access the Schema Changes History in the SQL Server Management Studio, I got this error.
Solution – Unable to retrieve data for this section of the report
- The first thing you would after facing this error is to verify if the path to the log file is correct.
- In my case, the path was correct but still I was not able to open the Schema Changes History.
- However, I noticed one thing, the size of this log file was 0 Bytes. Also, there were more log files with the similar names.
- I concluded that either the file is corrupt or the SQL Server is not able to connect to this log file.
- Therefore, I deleted the file with 0 Bytes of size i.e. log_23.trc.
- Then I opened the Schema Changes History again in the SQL Server Management Studio.
- I noticed that, this time SQL Server was pointing to the another log file. and I was able to access the logs. All the recent logs were available.
You may like the following SQL server tutorials:
- Stored procedure for search functionality in SQL Server
- Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements
- Try catch in SQL Server stored procedure with examples
- Msg 11555 NOT NULL parameters are only supported with natively compiled modules, except for inline table-valued functions
- SQL Server stored procedure parameters
- Error: 40 – could not open a connection to sql server
- The conversion of a date data type to a DateTime data type resulted in an out-of-range value SQL
- The configuration option ‘xp_cmdshell’ does not exist or it may be an advanced option
In this way, I was able to resolve this issue, Msg 567: Unable to retrieve data for this section of the report
I am Bijay having more than 15 years of experience in the Software Industry. During this time, I have worked on MariaDB and used it in a lot of projects. Most of our readers are from the United States, Canada, United Kingdom, Australia, New Zealand, etc.
Want to learn MariaDB? Check out all the articles and tutorials that I wrote on MariaDB. Also, I am a Microsoft MVP.