Yes, this is a timeout error. You can check the execution logs. And you could also set the Execution Tmeout Proerties of the report to a higher amount using the "Report Execution Timeout" option. But generally you want to find the root cause which maybe on the SQL side. See if running the report in Visual Studio preview mode does not give you a better error explanation. And check the query itself in SQL Server Management Studo.