I had posted a similar thread in the Setup & Administration forum, but never received an answer. The issue was that I had upgraded to the Beta 3 Refresh from Beta 3 running on SQL Server 2005 Standard September CTP. I attempted the upgrade to SQL Server 2005 Standard RTM, but as anyone who tried this remembers it wipes out most of your databases. Of course I had backups, but this required me to deviate slightly from the upgrade guidelines as I could not simply attach the MDF files. At any rate, when I ran through the installation successfully (used SQL Server 2005 Enterprise RTM instead) and restored the appropriate databases everything worked in my team project except for Reports. I opened up the Reporting Services Configuration Manager and received a schema mismatch error for the ReportServer database.
I tried mirroring the installation on another machine (same computer name, etc) and created the exact same team project with identical group membership, then backup up that ReportServer database and restored it over the same database on the original server box, with no luck--reporting services simply stopped working. Can anyone explain to me how I can just recreate the ReportServer database so I can use the Reports feature of TFS I didn't build any custom reports or make any custom modifications whatsoever--the ReportServer database should contain just the default data that is present when the team project is initially created.
Thanks,
Larkin
Recreating ReportServer database
DougRotondo
You basically need to get Reporting Services back to a healthy state on your machine without worrying about any of the content in the Reporting Services DB. If you can do that without breaking anything else, then you will be close to a solution. I think you were probably very close to having a completely working system just after you restored your databases. Take a look at the Beta 3 Refresh upgrade guide:
http://msdn.microsoft.com/vstudio/teamsystem/b3rmigrate.aspx
Notice that it does not ask that the Report Server DB be attached. Instead, the process relies upon a content-free, but working SQL Server Reporting Services deployment and then walks through the steps for pushing reports to the server in the final step.
Since you have been through the backup/restore process, it may be easiest for you to just reinstall TFS on your production machine following the Beta 3 Refresh upgrade guide to identify the DBs and the process of restoring Reporting Services content.
A more surgical approach would be to uninstall/reinstall SQL Reporting Services to get it back to a healthy state. The one thing that comes from the installation process that you would be missing in that case are the Reporting Services Data Source definitions. The TFS installer uses a utility called createds.exe to create the Data Sources used by reports. Those Data Sources can be seen by browsing to http://<server>/reports on a healthy TFS server. You could create the Data Sources manually or could use the createds.exe utility from the TFS Tools subdirectory.
RogReis