Here is the procedure to reproduce the issue and the possible reason. We might need to work with Microsoft to identify a solution.
- Create a site collection named http://spsbx15/sites/Harry/
- Enable Powerview site feature and add an “PowerPivot Gallery” app
- Upload one Powerview file named “HelloWorldPicnicPowerViewRTM-2010.xslx” from Microsoft site
- Create a power report and same as “Report1” as in the following screenshot
- Backup the content DB as WSS_Content_Harry.bak
- Restore the content DB to different farm and change the permission for the system account
- Restore the site collection on destination farm using command “Mount-SPContentdatabase -name WSS_Content_Harry -Webapplication http://spsbx08”
- The site will be restored to http://spsbx08/sites/Harry/
- Grant the access permission to the new content DB to the system account
- $w = Get-SPWebApplication –Identity http://spsbx08
Here is the site from original SharePoint farm.
We are able to view the Report1 from original site.
Since Powerview report will generate database entries in SSRS database as in the following screenshot,we believe the Powerview reports need to connect to SSRS database tables to display the report. As site backed up and restored to new SharePoint farm, there is no process provided by Microsoft to backup and restore the Powerview related SSRS tables along with site collection content. As a result, the restored Powerview reports will not work! I've a workaround to fix this and will publish in future blog. We are working with Microsoft to verify whether we could have a automate way to fix all Powerview reports for the whole farm.
The good news for the restored site is you can create new Powerview reports without issues.