We are installing SQL 2008 R2 Reporting Services and have successfully completed the configuration wizard (we think). Now when we connect to the http://localhost/ReportServer we get the following error message: The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'C.0.9.45'. The expected version is '147'. (rsInvalidReportServerDatabase) Any ideas?

Hi NullReferenceExc, The SQL Server Reporting Services(SSRS) maintains a version for the its catalog databases. This version value is stored in the Report Server catalog databases. The version for each version of SQL Server Reporting Services(SSRS) is different. 'C.0.9.45' is used for SSRS 2008. In SSRS 2008 R2, the version should be '147'. So, the cause for the issue may be that you are using a SSRS 2008 catalog database. To fix the issue, please use the Reporting Services Configuration Manager to recreate to the Report Server catalog database(via "Database" tab). Additionally, the issue may occurs when the RSExecRole is not assigned to the Report Server catalog databses. If this is the issue, to fix this issue, we must add RSExecRole to the db_owner role in the Reporting Services catalog databases. To add RSExecRole to the db_owner role in the Reporting Services databases Open SQL Server Management Studio and connect to the database that hosts the ReportServer and ReportServerTempDB databases. In Object Explorer, expand the following nodes: Databases, ReportServer, Security, Roles, and Database Roles. Right-click db_owner, and click Properties. On the Database Role Properties page, click Add. On the Select Database User or Role page, type RSExecRole, and then click OK twice. Repeat these steps for the ReportServerTempDB. Restart the Report Server service. You might need to restart the service twice. If you have any more questions, please feel free to ask. Thanks, Jin ChenJin Chen - MSFT

Hi NullReferenceExc, The SQL Server Reporting Services(SSRS) maintains a version for the its catalog databases. This version value is stored in the Report Server catalog databases. The version for each version of SQL Server Reporting Services(SSRS) is different. 'C.0.9.45' is used for SSRS 2008. In SSRS 2008 R2, the version should be '147'. So, the cause for the issue may be that you are using a SSRS 2008 catalog database. To fix the issue, please use the Reporting Services Configuration Manager to recreate to the Report Server catalog database(via "Database" tab). Additionally, the issue may occurs when the RSExecRole is not assigned to the Report Server catalog databses. If this is the issue, to fix this issue, we must add RSExecRole to the db_owner role in the Reporting Services catalog databases. To add RSExecRole to the db_owner role in the Reporting Services databases Open SQL Server Management Studio and connect to the database that hosts the ReportServer and ReportServerTempDB databases. In Object Explorer, expand the following nodes: Databases, ReportServer, Security, Roles, and Database Roles. Right-click db_owner, and click Properties. On the Database Role Properties page, click Add. On the Select Database User or Role page, type RSExecRole, and then click OK twice. Repeat these steps for the ReportServerTempDB. Restart the Report Server service. You might need to restart the service twice. If you have any more questions, please feel free to ask. Thanks, Jin ChenJin Chen - MSFT

We used the 2008 R2 Reporting Services configuration manager to create the database, so why is it the wrong version? We are going to drop it and recreate it again to see if that resolves the issue. We also checked the role assignment and that was all correct.

Any news about this? We have another server and installed SQL Server 2008 R2 and trying to move our reports (SQL 2008) into the R2. but the same issue as abobe happen when configuring reporting services.

I am getting the same issue, but the version found is 'C.0.8.40' where '147' is expected. I have done the first step, and RSExecRole was already an owner of both databases. Any other help you could offer me? Thanks, Jesse

I ended up just deleting and recreating and everything worked fine after that.