Missing shared feature Reporting Services Sharepoint

We have all 64bit servers with Windows Server 2012 Standard Evaluation
In our SP Farm we decided to have 1 WFE Server, 1 App Server & 1 Sql Server
In Sql Server we installed "en_sql_server_2012_enterprise_edition_with_service_pack_2_x86_dvd"
With that we got the following version installed
Now when we are trying to install SSRS on our App Server we could not see the following Shared Features
- Reporting Services Sharepoint
- Reporting Services Add-in for Sharepoint products
Please suggest me what am i missing or where i was wrong?
Thanks,
Naveen.

Hi Naveen,
From the image in your post, it seems that there may be something wrong with your setup file of SQL server 2012.
Please make sure that you are installing SQL server with the intact setup file.
And the installation of SQL will also be affected by the viruses in your system.
So please make sure that there is no viruses in your App server.
As this issue is regarding to SQL server installation, I recommend you to post the question in SQL forum:
https://social.technet.microsoft.com/Forums/Lync/en-US/home?category=sqlserver.
More experts will assist you, then you will get more information relation to SQL Server.
Best regards.
Thanks
Victoria Xia
TechNet Community Support

Similar Messages

  • Missing shared feature Reporting Services Sharepoint and Reporting Services Add-in for Sharepoint products

    Hi, when I try to install SQL Server 2012 SP1 (ISO from Microsoft Download website) on a Windows Server 2012 and try to select the shared feature options: 
    - Reporting Services Sharepoint
    - Reporting Services Add-in for Sharepoint products
    They are both missing from the list.
    How do I solve this? Help!

    Hello,
    Did you download the SQL Server 2012 Express with Advanced Services edition from the Microsoft website? If so, this edition did not support SharePoint Integration mode.
    Just as Alberto post above, Business intelligence features are not all available in all editions of SQL Server 2012. You can refer to the following link about support features in Editions of SQL Server 2012:
    Reference:http://technet.microsoft.com/library/cc645993(SQL.110).aspx#Reporting
    Regards,
    Fanny Liu
    If you have any feedback on our support, please click here.
    Fanny Liu
    TechNet Community Support

  • Reporting Services – SharePoint missing

    Hello,
    I am trying to  add Reporting Services – SharePoint to my computer sql server installation.
    I am currently using Sql Server 2012 Enterprise:
    Microsoft SQL Server 2012 - 11.0.2100.60 (Intel X86)
        Feb 10 2012 19:13:17
        Copyright (c) Microsoft Corporation
        Enterprise Edition on Windows NT 6.1 <X86> (Build 7601: Service Pack 1)
    Unfortunately in Shared features I don't have the Reporting Services items mentioned in the microsoft article I am following.
    Could it be because I don't have Sharepoint installed on my computer?
    Or maybe, because my computer is 32 bit?
    Any suggestions?
    Thanks

    Hello,
    Based on your description, you install SQL Server 32 bit version. However, Reporting Services add-in for SharePoint  is 64-bit only. You should try to install SQL Server 64 bit version.
    Reference:Hardware and Software Requirements (PowerPivot for SharePoint and Reporting Services in SharePoint Mode)
    Regards,
    Fanny Liu
    Fanny Liu
    TechNet Community Support

  • SQL Server Reporting Services SharePoint Integrated mode - Power View is not supported

    Hi there,
    My environment is the following:
    SharePoint Server 2013
    SQL Server 2012 SP1 Enterprise edition
    I am getting the following message when trying to open BISM item with PowerView icon:
    "The feature: "Power View" is not supported in this edition of Reporting Services."
    My problem is that the first time I installed SQL Server Reporting Services SharePoint integrated, I used the SQL Server 2012 Standard edition ISO. But then I learned that Power View is only available with Enterprise and BI editions. So I uninstalled Reporting
    Services Add-in from Control Panel, Reporting Services from the installation media and deleted the three Reporting DBs in the SharePoint DB server.
    Then I used SQL Server 2012 SP1 Enterprise media to install again Reporting Services but not sure why I am still getting the message:
    "The feature: "Power View" is not supported in this edition of Reporting Services."
    Anyone can advice me what could be the problem? Maybe I have not complete deleted  the previous SQL Server Reporting Service Share Point integrated mode from the previous installation? What would be the proper way to uninstall Reporting Services?
    Any help will be welcome.
    Thanks and best regards,
    Joss

    Hi  Joss,
    I am in the same situation, 
    SQL Server was installed in the standard mode because of that the powerview option is not working. 
    I have changed teh edition using maintenance --> upgrade edition. the sql server components like DB engine, SSAS and integration services are now showing in enterprise edition. The reporting services are installed from the application end still showing
    as the reporting services are standard.
    we reinstalled the reporting services but still persists the issue.
    suggest me is there any work around to fix the issue other than reinstalled the whole SQL Server.
    Thanks
    Ramu

  • Difference between Reporting Services Sharepoint Mode and Reporting Services Add In for Sharepoint 2013

    Hi, We are building company site with Sharepoint 2013 Enterprise Edition and were wondering what is the difference between Reporting Services Sharepoint Mode and Reporting Services Add In for Sharepoint 2013? What are the roles/purposes of each one? What
    happens if only Reporting Services Sharepoint Mode  installed or vise versa.
    Thank you in advance

    Reporting Services in SharePoint mode is a service for displaying, managing, and creating SSRS reports within SharePoint. The addin is a pre-req for SharePoint that is used to display reports and is required for Reporting Services in Native or SharePoint
    mode, but does not by itself do anything.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • MDX Error in Reporting Services/Sharepoint

    Hi,
    I'm using SQL Server 2008 R2 SP1 CU5.
    I have a reporting that executes a DataSet with a MDX query. That report was executing very well before (in SQL Server 2008 R2 SP1), but after we updated SQL to SP1 Cumulative 5, the report returns an error. 
    The strange thing is, if we execute the MDX query in Analysis Service, and after that execute the report in sharepoint 2010, it works fine, but about 10 minutes after the reporting returns error again, until we execute again the query in AS.
    The error returned isn't clear, just say "Operation Cancelled", this same message is returned by the Analysis Services Log (Profiler).
    Some idea?
    PS.: Sorry my english.
    Se esta sugestão for útil, por favor, classifique-a como útil. Se ela lhe ajudar a resolver o problema, por favor, marque-a como Resposta.

    Hi Fdev,
    According to your description, you encounter the issue after apply SQL Server 2008 R2 SP1 CU5, right?
    Based on the limited information, we cannot give you the exact reason that cause this issue. In order to narrow down this issue, you can apply the latest Service Pack and Cumulative Update as GregGalloway said. Besides, you can troubleshoot this issue by
    using the Windows Event logs and msmdsrv.log.
    You can access Windows Event logs via "Administrative Tools" --> "Event Viewer".  SSAS error messages will appear in the application log.
    The msmdsrv.log file for the SSAS instance that can be found in \log folder of the instance. (C:\Program Files\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Log)
    Here is a blog about data collection for troubleshooting Analysis Services issues, please see:
    Data collection for troubleshooting Analysis Services issues
    Regards,
    Charlie Liao
    TechNet Community Support

  • What are Reporting Services SharePoint 2013 licensing requirements?

    Hi All
    I have a SharePoint Enterprise 2013 farm of 2 WFE, 2 APP servers.  And an 2012 SQL Enterprise server.
    I need Reporting services to be on the farm.
    I read all the SharePoint Farm servers running SSRS must have an SQL license, which seems excessive.  I assume it stands as "Additional Software" from the Product Use Document in SQL.  As long as the SQL server is licensed?
    What are the licensing options, keeping in mind that there is an SSRS Add-on (which I believe is freely available), and an SSRS instance?
    Cheers

    SSRS instances require a SQL Enterprise or BI license, depending on how you want to license it. This license is separate from the SQL Database Engine if not running on the same server.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Dropdown list is cut off in reporting service (SharePoint Integration Mode)

    We have a report running in SharePoint integration mode and we have a set of parameters. But the last parameter (near the bottom of the browser) with drop down list cannot be displayed completely.
    Kevin Li

    Hi KevinLi,
    According to your description, the last parameter in your parameter drop down list is not completed displayed. Right?
    In Reporting Services, when having too many available values which will exceed the report parameter drop down list area, it suppose to generate scrolling bar for selecting. In this scenario, it seems those available values just end at the bottom of
    the browser and exceed a little bit. But it can't trigger generating scrolling bar. However, it think you can select the last value successfully. So it doesn't effect your using too much. If you really need to display all values in parameter drop
    down list, you can try to change the resolution of your screen.
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou

  • Reporting Service SharePoint Integration Mode option is disabled in Reporting Service Configuration - SQL 2012

    Hi ,
     The option to select reporting service in sharepoint integration mode is disabled while trying to install SQL Server 2012. Any ideas?
    Raghavendra Shanbhag | Blog: http://moss-solutions.blogspot.com
    Please click "Propose As Answer " if a post solves your problem or "Vote As Helpful" if a post has been useful to you.
    Disclaimer: This posting is provided "AS IS" with no warranties.

    Hi Trevor,
    Need urgent help please.
    I have to install the SSRS in SP 2013.
    Database ( SQL Server 2012 SP1) and SP 2013 servers are separate.
    Installed SSRS in DB server (Integration mode).
    Installed ADD-IN for SSRS in SP2013 server.
    I have followed all the steps mentioned by microsoft.
    But , I stuckup as below, SSRS service in sharepoint does not get started.It is showing disabled.
    >Install-SPRSService
    >Install-SPRSServiceProxy
    >Get-SPServiceInstance -all |where {$_.TypeName -like "SQL Server Reporting*"} | Start-SPServiceInstance
    >get-spserviceinstance -all |where {$_.TypeName -like "SQL Server Reporting*"}
    TypeName                         Status   Id                                
    SQL Server Reporting Services... Disabled b2efbe68-114f-4459-b083-4d414528ab05
    And, while looking from Manage service application, the SSRS service shows 'Error Starting' while we go to start the service.
    Hitting the technical detail of the problem it takes us to 
    Following is the log entry through ULS viewer :
    Microsoft.ReportingServices.Diagnostics.SqlInstallation+ConfigurationErrorException: Installation Error: Could not find SharedCode on SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key.   
     at Microsoft.ReportingServices.Diagnostics.SqlInstallation.get_SqlSharedCodeDirectory()    
     at Microsoft.ReportingServices.Diagnostics.SqlInstallation.GetSkuFromSqlBoot(String instanceId, Int32& daysLeft)    
     at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision()    
     at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e)    
     at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument)    
     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    We have no clue whats going on.
    Please help.
    Thanks,
    Raghav

  • Reporting Services/Sharepoint 2013 dynamic Subscriptions.

    I am looking for a better solution to this problem.  What I have is about 200 reports and growing that are emailed on some schedule (most once a day as soon as possible). 
    This would mean about 200 sql jobs on the RS box, because each subscription create a sql job.  
    I am working on a data driven subscription that would create a schedule to run after the DW has finished processing. 
    I am noticing I am creating a lot of parameters.  I am also noticing that I will be creating some type of log table.  
    Reason is that I need to exec the jobs to run every say 5 min. 
    These jobs are looking at the DW log table to show its done and another log table to tell if they have ran or not for the day. 
    Thus the actual report will only email one time a day.  
    (not sure if someone has a better solution for this).    The solution at this point is create 1 new table to hold parameters that I will use for the subscriptions (for section to define a query to Retrieve Subscriber
    data).   The I will need a log table that I would populate once the report is actually sent.  
    Thus the real problem I have is that with 200 plus reports all trying to run at the same time. 
    In addition to AS trying to process and users all trying to run stuff. 
    To help balance this load I would rather have 1 or 2 jobs running on say the reporting services box or even the EDW box that just generates reports.  
    This way it runs the reports in a more serial manor.  
    I want to get this report from reporting services still.  
    What I am really looking for is how to dynamically exec all the pieces needed. 
    In other words build a table to hold all 200 reports and the metadata needed from them like format, to, cc, ect… 
    Then just create one job on RS that will exec code to loop through each report one at a time and create them. 
    I can have n number of job by just creating a grouping as well.
    Ken Craig

      The reports run 1x a day so taking the time to cashe them in SSAS or SQL (most come from sql) and then run them again in SSRS has just added load with no value.   Why hammer anything. 
    I have been digging more but still looking.  What I have found is that a job just loads a records into a table called AddEvent.  Something that picks up a record from that and runs it.  From what I can tell it uses the @eventdata to get the
    information out of the Subscriptions and Catalog table. 
    Not sure if I am on the right path but still thinking I need to take the 200 plus reports and load them into a table.  This would be all parameters and all subscription info.  Then have maybe just a couple jobs.  Example one job runs 175 reports
    and other runs 25.  I can group them how I like or add more jobs as I need to.  Including creating an order for them.  This way one job will run serial.  Thus allowing me to control the load on the SQL box and SSAS box.  Instead of
    having 200 queries all slamming sql server and/or SSAS at the same time.
    Ken Craig

  • SQL Server Reporting Services & SharePoint 2013

    Hi there,
    We are developing a web application in sharepoint 2013 in which we are using authentication mode="Windows”.  We have used a custom web part containing report viewer control for showing charts and reports, that we have
    developed using SSRS ( *.rdl files) and have all the .rdl files within Sharepoint Document Library.
    To start with, we were getting the error “Report Server has encountered a SharePoint error. (rsSharePointError) The user does not exist or is not unique.” To fix this, we changed <identity impersonate="false" /> from <identity
    impersonate="true" /> at web.config level which did the trick.
    However, we are now facing another issue wherein tabular reports are renedered ok in SharePoint through report viewer custom web part but chart based reports are not rendered. The chart image is not displayed. 
    Can somebody please help with a resolution?
    The code snippet for rendering the report is given below for reference purposes
    Thanks in advance
    Monica
    privatevoid
    BindReport()
                string reportFullPath
    = "http://c4968397007/ReportLibrary/Reports/"
    + ReportPath;
                litReportHeading.Text = ReportPath;
                reportViewerControl.ServerReport.ReportPath = reportFullPath;
                reportViewerControl.ServerReport.ReportServerUrl =newUri("http://c4968397007/_vti_bin/ReportServer");
                reportViewerControl.ProcessingMode = Microsoft.Reporting.WebForms.ProcessingMode.Remote;
                Microsoft.Reporting.WebForms.ServerReport
    serverreport = reportViewerControl.ServerReport;
    IReportServerCredentials irsc =newReportViewerCredentials("username","password","domainName");
                rvControl.ServerReport.ReportServerCredentials = irsc;
                rvControl.ServerReport.Refresh();

    Hi Monica,
    In your case, please check whether your report is render correctly on your report server. If so, I would suggest you to check the version of your Internet Explorer and try to use compatibility view as well.
    Another suggestion, please put the chart into a rectangle. Alternatively, can you please install the Microsoft Report Viewer 2010 try to resolve the issue? You can download the Report Viewer 2010 package from the following website:
    http://www.microsoft.com/download/en/details.aspx?id=23691
    Regards,
    Alisa Tang
    Alisa Tang
    TechNet Community Support

  • SSRS in SharePoint Mode: Reporting Services scale-out deployment is not supported in this edition of Reporting Services [not true]

    Hello,
    We are experiencing some issues with SharePoint 2013 which is driving me insane.
    We have a deployment with two SQL Servers (HA groups) and four SharePoint servers: 2 Application servers, and 2 Web FrontEnd servers.
    We installed SSRS for SharePoint in both application servers. The disc I have used is the MSDN image of SQL Enterprise 2012 w/ SP2.
    ISO name: en_sql_server_2012_enterprise_edition_with_service_pack_2_x64_dvd_4685849.iso
    MD5: 003e14c55fa648ad15f8be1e2439bd06
    The installation completes without any problems. We can start the SSRS SharePoint Service in the first application server without any issues. However when we try to start the second one, we get the following error:
    Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the sql reporting services service in the farm. The SQL Server Reporting Services cannot be started on
    this server unless it is stopped on all other servers in the farm.
    Now I am at a loss here. As I mentioned, we have used an image of SQL Server Enterprise. This is the same image we used on other environment, which worked as expected (we got no such error).
    I have included the text related to the correlation error from the SP logs below.
    Has anyone ever seen this issue before? Very, very strange!
    Regards,
    P.
    01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48) 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Authentication Authorization agb9s Medium Non-OAuth request. IsAuthenticated=True, UserIdentityName=, ClaimsCount=0 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Logging Correlation Data xmnv Medium Site=/ 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.22 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly High Leaving Monitored Scope (PostAuthenticateRequestHandler). Execution Time=9.742 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 6t8h High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.23, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.28 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Web Controls 88wu High [Forced due to logging gap, Original Level: Verbose] SPGridView.OnRowCreated() - Row.RowType={0}, .RowState={1}, .RowIndex={2}, .DataItemIndex={3} 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General af4yd High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.28, Original Level: Verbose] TenantAppEtag record requested but there is no sitesubscription or tenantId for site {0} so we will use the WebApp Id for the cache. 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.37 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Asp Runtime aj1kp High [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.43 OWSTIMER.EXE (0x1F10) 0x0B40 SharePoint Foundation Health abire Medium Failed to Sql Query data XEvent collector on sql-01. The error is Object reference not set to an instance of an object.
    01/29/2015 14:13:26.51 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 7034 Critical An attempt to start/stop instance of service Microsoft SQL Server Reporting Services Shared Service on server SPAP-01 did not succeed. Re-run the action via UI or command line on the specified server. Additional information is below. Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.40, Original Level: Verbose] SQL connection time: 0.0821 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88b9 High [Forced due to logging gap, Original Level: Verbose] Determining if the current user is a SharePoint Farm Administrator 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.53 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 8xqz Medium Updating SPPersistedObject ReportingWebServiceInstance. Version: 1118292 Ensure: False, HashCode: 52212853, Id: 5a4058b9-2ecd-421e-b9ae-818bbc57c8c6, Stack: at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error) at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb) at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags) 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database ahjqp High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.57, Original Level: Verbose] SQL connection time: 0.0965 for Data Source=sql-01;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15;Application Name=SharePoint[w3wp][2][SharePoint_Config] 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.79 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Database 8acb High [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Topology 88ch High [Forced due to logging gap, cached @ 01/29/2015 14:13:26.84, Original Level: Verbose] {0} 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.86 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General 8nca Medium Application error when access /_admin/Server.aspx, Error=Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.87 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Runtime tkau Unexpected System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.89 w3wp.exe (0x0B94) 0x294C SharePoint Foundation General ajlz0 High Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.InvalidOperationException: Reporting Services scale-out deployment is not supported in this edition of Reporting Services. This edition only supports one instance of the SQL Server Reporting Services Service in the farm. The SQL Server Reporting Services service cannot be started on this server unless it is stopped on all other servers in the farm. at Microsoft.ReportingServices.SharePoint.SharedService.Service.ReportingWebServiceInstance.Provision() at Microsoft.SharePoint.ApplicationPages.ServerPage.OnObjectModelAction(Object sender, ObjectModelActionEventArgs e) at Microsoft.SharePoint.WebControls.ActionLinkDataSourceControl.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Micro Trace uls4 Medium Micro Trace Tags: 0 nasq,2 agb9s,9 b4ly,309 8xqz,331 8nca,15 tkau,8 ajlz0 6f83e49c-cc03-d049-90f4-81439b542cf8
    01/29/2015 14:13:26.92 w3wp.exe (0x0B94) 0x294C SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://spap-01:5555/_admin/Server.aspx?ServerId=7f7d5eec-3791-44cf-a992-673eaea90f48)). Execution Time=712.2145 6f83e49c-cc03-d049-90f4-81439b542cf8

    Hi Wynn,
    I appreciate your attempt to address my concerns, but even your reply seems to ignore the fact that I have not only provided the name of the ISO, but the MD5 checksum of the ISO as well. Also this is the first time I am being asked to double-check the version
    of SSRS. The first reply I got to my query simply disregarded the version mismatch.
    As per your request, I have checked under the folder you have specified (C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\WebServices\LogFiles), but unfortunately there are no files under this folder in neither of my two application
    servers.
    We only have logfiles under C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS 
    Is there a way I can turn those logs on?
    In the meantime, we run the SQL Server Discovery tool and I have attached the summary for you to see that it finds the Enterprise Edition of SQL Server:
    Final result: Passed
    Exit code (Decimal): 0
    Start time: 2015-01-29 15:17:44
    End time: 2015-01-29 15:17:56
    Requested action: RunDiscovery
    Machine Properties:
    Machine name: SP-AP-02
    Machine processor count: 4
    OS version: Future Windows Version
    OS service pack:
    OS region: United States
    OS language: English (United States)
    OS architecture: x64
    Process architecture: 64 Bit
    OS clustered: No
    Product features discovered:
    Product Instance Instance ID Feature Language Edition Version Clustered Configured
    SQL Server 2012 Management Tools - Basic 1033 Enterprise Edition 11.2.5058.0 No Yes
    SQL Server 2012 Reporting Services - SharePoint 11.2.5058.0 No Yes
    Package properties:
    Description: Microsoft SQL Server 2012
    ProductName: SQL Server 2012
    Type: RTM
    Version: 11
    SPLevel: 0
    Installation edition:
    User Input Settings:
    ACTION: RunDiscovery
    CONFIGURATIONFILE:
    ENU: true
    HELP: false
    IACCEPTSQLSERVERLICENSETERMS: false
    INDICATEPROGRESS: false
    QUIET: false
    QUIETSIMPLE: false
    UIMODE: Normal
    X86: false
    Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20150129_151743\ConfigurationFile.ini
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file: The rule result report file is not available.
    The \Setup Bootstrap\Log folder also has several log files that indicates the version of SQL Server that has been installed. For instance here is an entry of the Detail.txt file:
    (01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : CreateSKUCookie succeeded, new checksum is 195 bytes.
    (01) 2015-01-28 19:10:27 Slp: -- SkuPublicConfigObject : Updated skuCheckSumInfo -> daysLeft=0 sqlEdition='ENTERPRISE' (0x6B9471A8) fileTimeInstalled=0 timeBombValue=0 editionType='Enterprise Edition' edition='Enterprise Edition' writeEditionStrings='True' checkSum=195bytes
    (01) 2015-01-28 19:10:27 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
    I hope this help while we don't have any logfiles in the folder you asked me to look into. Please advise me as in how to proceed if logfiles must be generated.
    Regards,
    P.

  • SharePoint 2013 - SQL Reporting Services Add-In

    Hi,
    In our old SharePoint 2010 environment the "SQL 2008 R2 Reporting Services ShrerPoint 2010 Add-in" has been installed which in turns provides the "SQL Server Reporting Services Report Viewer" web part.
    I have upgraded the Farm to SharePoint 2013 and SQL 2012. Where I can get the the add-in above that is compatible with
    SQL 2012 and SharePoint 2013?
    I have found an add-in here for SQL 2012 and SharePoint 2010, but not sure this is compatible with SharePoint 2013...
    Many Thanks,

    Hi
    I am also getting the below Error while testing the Content Db with SharePoint 2013 Web application.
    1.  Assembly
    [Microsoft.ReportingServices.SharePoint.UI.ServerPages,
    Version=10.50.0.0, Culture=neutral,
    PublicKeyToken=89845dcd8080cc91] is referenced in the
    database [WSS_Content_8080], but is not installed on the
    current farm. Please install any feature/solution which
    contains this assembly.
    One or more assemblies are referenced in the database
    [WSS_Content_8080], but are not installed on the current
    farm. Please install any feature or solution which contains
    these assemblies.
    2.  Database [WSS_Content_8080] has reference(s) to a missing
    feature: Id = [c769801e-2387-47ef-a810-2d292d4cb05d], Name =
    [Report Server File Sync], Description = [Synchronizes
    Report Server files (.rdl, .rsds, .smdl, .rsd, .rsc) from a
    SharePoint document library to the report server when files
    are added or updated in the document library.], Install
    Location = [ReportServerItemSync].
    The feature with Id c769801e-2387-47ef-a810-2d292d4cb05d is
    referenced in the database [WSS_Content_8080], 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.
    I have SQL 2008 reporting Services SharePoint 2010 Add-in.
    for SharePoint 2013 we are using the SQL server 2008 Sp1. I think  it is not possible to use SQL server 2012 SP1 for the report Services in SharePoint 2013.
    Please suggest me to use the report services in SharePoint 2013 with Sql server 2008 SP1.
    Thanks And Regards
    Dileep Kumar

  • Reporting Services Add-In for SharePoint Products

    Hi,
    Can I use the SSRS Web part installed by the add-in to see local mode reports just by instaling the add-in or do I also need to install the "Reporting Services - Sharepoint" on SS Shared Features setup wizard?
    Thanks,
    DD

    Hi,
    Per the MSDN article: To use the Web Part, you must have installed and configured the Reporting Services Add-in and configured the report server for SharePoint integration.
    You must also have reports to display in the viewer. You can only open reports that are in a library, a library folder, report history, or a link from a Library Web Part to a Report Viewer Web Part.
    You cannot open reports that are saved as an attachment to an item in a custom list.
    More reference:
    http://msdn.microsoft.com/en-IN/library/ms159772.aspx
    As this issue is related to reporting service, if you have more issues about reporting service, I recommend you post your issue to the forum for Reporting Service.
    http://social.technet.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlreportingservices
    More experts will assist you, then you will get more information relation to this topic.
    Thank you for your understanding and support.
    Thanks & Regards,
    Jason
    Jason Guo
    TechNet Community Support

  • SharePoint 2010 with SQL Reporting Services 2012 "Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"

    i have a small sharepoint farm "2 servers" (WFE) and SQL Server 2012 ,
    i installed rsSharePoint for reporting services , as a read the Reporting services is Application Service  with SQL 2012 not as SQL 2008 R2 with SharePoint integrated mode, so after installation when am trying to configure the  SQL Server
    Reporting Services Application services i got the below error :
    "Installation Error: Could not find SOFTWARE\Microsoft\Microsoft SQL Server\110 registry key"
    any kind of help would be much appreciated .

    I'm having the same issue, but to me it seems like the instructions I've seen are all over the place.  I already have SP 2013 and SQL 2012 SP 1 installed.  I already added the features for Reporting Services - Sharepoint and Reporting Services
    Add-in for SharePoint Products.  I didn't see the Reporting Service service in CA, so I ran the powershell scripts to add SPRSService and SPRSServiceProxy. 
    My initial quest, was to get the BI features enabled, which took me on the journey of adding the Report Services, then I got the error.
    Then when I read this about installing the BI features
    http://blogs.msdn.com/b/querysimon/archive/2012/11/26/installing-the-bi-features-of-sharepoint-2013.aspx, which I already had SQL and SP installed.  Do I have to rerun and selct the SQL Server PowerPoint for SharePoint option?  I have the PowerPoint
    Configuration Tool on my SQL server, I run it and I get PowerPivot for SP 2013 Configuranoi is missing prerequisits:  SP 2013 EE is required.  Which I have EE.
    Is Reporting Services different or in addition to the BI Feature (PowerPivot)? 
    Have I missed a step?
    Thanks for you help.
    Kim
    Kim.Williams

Maybe you are looking for