Search results matching tags 'excel' and 'sql server'http://sqlblog.com/search/SearchResults.aspx?o=DateDescending&tag=excel,sql+server&orTags=0Search results matching tags 'excel' and 'sql server'en-USCommunityServer 2.1 SP2 (Build: 61129.1)“Excel found unreadable content” when exporting a Reporting Services reporthttp://sqlblog.com/blogs/jamie_thomson/archive/2010/01/22/excel-found-unreadable-content-when-exporting-a-reporting-services-report.aspxFri, 22 Jan 2010 20:16:26 GMT21093a07-8b3d-42db-8cbf-3350fcbf5496:21358jamiet<p><em>[This is just a quickie, I’m putting it up here for anyone that received the messages above and searches for it online!]</em></p> <p>Earlier today my team experienced some issues with a Reporting Services report that when attempting to export to Excel would cause Excel to throw the error “Excel found unreadable content” (I really should have got a screenshot but I didn’t think to do that. Sorry.)</p> <p>Of course we went down the usual routes. Searching online threw up a Microsoft KB article <a href="http://support.microsoft.com/kb/929766" target="_blank">Error message when you try to open a workbook in Excel 2007: &quot;Excel found unreadable content in Book_Name&quot;</a> which describes a situation related to Analysis Services.</p> <p>Turns out it was nothing at all to do with Analysis Services. The solution was actually a lot simpler – our Reporting Services server had run out of disk space and clearing down some space on that disk immediately solved the problem.</p> <p>&#160;</p> <p>So, if you encounter the above error – check your disk usage!</p> <p>Hope that helps!</p> <p>&#160;</p> <p><a href="http://twitter.com/jamiet" target="_blank">@Jamiet</a></p>