none
Unable to browse reporting service from Sharepoint Performance Designer

    Question

  • We have Sharepoint 2013 as web farm and SQL Server 2016 with reporting service (Native) installed on different machines. We are trying to edit an existing report from one of the dashboards but we are unable to browse the reporting service. After loading for quite some time, this message comes up:

    We tried creating a new report but this is happening as well. We recently upgraded our reporting service from SQL Server 2014. Not sure if this functionality has worked before the upgrade as the person who integrated Share point and Reporting server has already left the company.

    In addition, found the error below when adding new web parts in sharepoint:

    Report Viewer
    A Web Part or Web Form Control on this Page cannot be displayed or imported. The type Microsoft.ReportingServices.SharePoint.UI.WebParts.SPViewer, RSWebParts, Version=8.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 could not be found or it is not registered as safe.


    

    • Edited by Mayzing Monday, February 26, 2018 6:23 AM
    Saturday, February 24, 2018 8:34 AM

All replies

  • Hi,

    This error is a common error. It's hard to narrow down this issue based on this error.

    Do you get any error in ULS log?

    About how to troubleshoot Server and Database Connection Problems with Reporting Services, you can refer to the following article.

    https://docs.microsoft.com/en-us/sql/reporting-services/troubleshooting/troubleshoot-server-and-database-connection-problems-with-reporting-services

    Feel free to reply if there is any update.

    Best Regards,

    Carl Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.


    Monday, February 26, 2018 10:05 AM
  • Hi Carl,

    Thanks for your reply.

    ULS log is giving errors of multiple missing assemblies that is being referenced in the databases.

    [MissingFeature] Database [FMSTPrivate_Content_DB_02] has reference(s) to a missing feature: Id = [2e814f75-1d83-4fe1-ad19-1ee2c7ada8ad]. The feature with Id 2e814f75-1d83-4fe1-ad19-1ee2c7ada8ad is referenced in the database [FMSTPrivate_Content_DB_02], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.[MissingSetupFile] File [Features\LifeInSharePoint.Metro_SITE.LifeInSharePoint.Metro\MasterPages\LifeInSharePointSearch.master] is referenced [1] times in the database [FMSTPrivate_Content_DB_02], but is not installed on the current farm. Please install any feature/solution which contains this file. One or more setup files are referenced in the database [FMSTPrivate_Content_DB_02], but are not installed on the current farm. Please install any feature or solution which contains these files.[MissingWebPart] WebPart class [b0695eeb-b02f-24a0-f318-fda2cbc00763] (class [QuestechSystems.SharePoint.WebControls.WebParts.EventCalendarListWebPart] from assembly [QuestechSystems.SharePoint.EventCalendarList, Version=1.0.0.0, Culture=neutral, PublicKeyToken=95970ee7e3d484ea]) is referenced [1] times in the database [FMSTPrivate_Content_DB_02], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [FMSTPrivate_Content_DB_02], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

    Connection to Reporting service works fine. Existing web parts works fine in share point. Only when adding new web part or refreshing an existing reports to update to the latest version that it fails. 

    Regards,

    May

    Tuesday, February 27, 2018 10:41 PM
  • Hi,

    About your error message, it seems that it's caused by missing feature.

    You can use PowerShell code to remove the missing features.

    There is a similar blog, you can refer to it:

    http://get-spscripts.com/2011/06/removing-features-from-content-database.html

    And also you can use SharePoint Feature Admin clean up tool from CodePlex to remove the missing features:

    https://featureadmin.codeplex.com/

    About resolving missing setupfile, you can refer to:

    http://alstechtips.blogspot.sg/2015/06/sharepoint-2013-missingsetupfile-fileis.html

    http://www.dreamsharepoint.com/powershell-resolving-missingsetupfile-error/

    Best Regards,

    Carl Zhou




    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, March 02, 2018 2:52 AM
  • Hi,

     

    If the post helps you, you can mark it as answer to help other community members to find the information quickly.

    Have a nice day!

     

    Best Regards,

    Carl Zhou


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, March 08, 2018 9:03 AM
  • Hi Carl,

    Thanks for sharing all these information.

    I managed to connect to reporting from SharePoint Performance designer by giving access to account running the reporting service as SharePoint admin, granting browser role to the same account in reporting and running the designer as administrator. 

    However, the issue with the missing features and setups still need to be addressed. Will let you know if the answers you have given helped us resolved the issue.

    Regards,

    May

    Friday, March 09, 2018 3:30 AM