Hi guys I am getting some problem when i am connecting my report server can any one help me ?? i am getting this erro in report manager 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 '147'. The expected version is 'C.0.9.45'. (rsInvalidReportServerDatabase)

Have you tried connecting Report Server Configuration Manager? Try to connect to your Server Server first and then setup the database from there. Here you can create a new database or update the version of an existing one.

Hi Abhishek, Based on the error message, this issue is caused because reporting services databases can not be upgraded to suit the current reporting services. If the solution provided by RMehta does not work, try to add RSExecRole to the db_owner role in the reporting services databases. By design, the RSExecRole is a member of the db_owner role for the report server databases, allowing the report server to update its own schema in support of an auto-upgrade process. Below steps are to add RSExecRole to the db_owner role in the reporting services databases: 1. Open SQL Server Management Studio and connect to the database that hosts the ReportServer and ReportServerTempDB databases. 2. In Object Explorer, expand the following nodes: Databases, ReportServer, Security, Roles and Database Roles. 3. Right-click db_owner, and click Properties. 4. On the Database Role Properties page, click Add. 5. On the Select Database User or Role page, types RSExecRole, and then click Ok twice. 6. Repeat these steps for the ReportServerTempDB. 7. Restart the Report Server services. You might need to restart the service twice. Please try and let me know the result. thanks, Jerry

Hi Jerry, We came across this issue and tried this fix without any luck. Still getting "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 '147'. The expected version is 'C.0.9.45'. (rsInvalidReportServerDatabase)". We bounced the Report Server services multiple times. Do you have any other suggestions? Thank You, Stephenhttp://www.blogmynog.com

It turns out one of the SQL DBA decided to upgrade the ReportServer DB to R2 without knowing it's being used for SCOM.http://www.blogmynog.com

Thanks for posting this. When I moved reporting services to a new server I had to figure out the double hop issue. Then I was having to add users to the db_owner role to run reports. Thanks to this post, no more! CB