SSRS Sharepoint Mode.excel question

Hello all,
I have a question regarding following:
"I want to create an environment where I want to be able to use SSRS 2008 to return a report directly in Excel, if possible. I know
of the facility to export a report to excel... but, what I really need is that if someone clicks on a particular report, instead of rendering in Report viewer, it should prompt the user to download the report in excel format."
This can be found here http://www.sqlservercentral.com/Forums/Topic1095310-150-1.aspx
And ofouse the solution is given there as well; here: http://weblogs.asp.net/srkirkland/archive/2007/10/29/exporting-a-sql-server-reporting-services-2005-report-directly-to-pdf-or-excel.aspx
My question is... how do I create this into "a button" on sharepoint lets say "export to excel" without end using on sharepoint having to set the parameters and then
hitting view report.
Please ask any more questions or screen shots if required be to make this a little bit more confusing. I do have visual studios 2012 for development work.
Regards, A.Singh

Hi A.Singh,
In SQL Server Reporting Services, we can export a report directly to a file format without viewing it in the browser via URL access method. Here is an example for your reference, please see:
http://<SharePoint_site>/_layouts/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl=/<SharePoint_Document_Library>/<Report_Name>.rdl&rp:Year=2001&rs:Format=EXCEL
For how to create a expected button that directly export a report without view it in SharePoint, I would suggest you discuss this topic in SharePoint forum for better support:
SharePoint General discussion forum:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/home?forum=sharepointgeneralprevious
Regards,
Elvis Long
TechNet Community Support

Similar Messages

SQL Reporting services installing sharepoint mode - Error while installing

Hi I have SharePoint 2013 environment and now i am trying to install SSRS sharepoint mode.
I use SQL server enterprise version 2012 SP1.
While installing this i got and error at the end.
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
The following error has occurred:
Could not load file or assembly 'System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
1- Now i am not able to uninstall this
2- I also don't see the service application in Central admin under New.
Please help me to resolve this issue.
My name is yogendra

Hi,
According to your post, my understanding is that you failed to install SSRS sharepoint mode.
Please make sure you install Reporting Services SharePoint Mode for SharePoint 2013
correctly.
You can refer to:
Install Reporting Services SharePoint Mode for SharePoint 2013
Installing and configuring SQL Reporting services on SharePoint 2013
In addition, please install Windows Management Framework 3.0 on the
build server.
More information:
Exception
Message: Could not load file or assembly 'System.Management.Automation, PublicKeyToken=31bf3856ad364e35'
How to use SQL Server in Windows and Windows Server environments
Best Regards,
Linda Li
Linda Li
TechNet Community Support

SSRS 2012 Sharepoint Mode ItemNotFoundException

Hello,
I have a big problem with the new SSRS 2012 (Sharepoint Mode) at one of my customers Sharepoint 2010 farm and I hope somebody can help. I get always the following error message if i try to open a report over the Report Viewer Webpart or try to save a report
over Report Builder 3.0 in a document library. SSRS 2010 is configured on a Single Server Farm (Sharepoint Mode) and published as a Sharepoint Application Service. Kerberos is also configured in the whole farm.
Message Report Builder:
Message Report Viewer in Sharepoint 2010:
ULS Log:
06/13/2012 14:09:19.10    w3wp.exe (0x08F4)                          0x08C4   SharePoint Foundation
    Topology                         e5mb   Medium     WcfReceiveRequest: LocalAddress:
'http://<spfarmssrs>:32843/8e68c61c48d3486b8f5780736e9de269/ReportingWebService.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sqlserver/reporting/2011/06/01/ReportServer/Management/get_IsWebServiceEnabled'
MessageId: 'urn:uuid:77ac2a30-b595-4faa-83f6-e2ce1e41e283'   665ee657-7c17-474e-b050-d115a932180f
06/13/2012 14:09:19.10    w3wp.exe (0x08F4)                          0x08C4   SharePoint Foundation
    Monitoring                       nasq   Medium     Entering monitored scope (ExecuteWcfServerOperation)
665ee657-7c17-474e-b050-d115a932180f
06/13/2012 14:09:19.13    w3wp.exe (0x08F4)                          0x08C4   SharePoint Foundation
    Monitoring                       b4ly   Medium     Leaving Monitored Scope (ExecuteWcfServerOperation).
Execution Time=36.9361189760151   665ee657-7c17-474e-b050-d115a932180f
06/13/2012 14:09:19.29    w3wp.exe (0x08F4)                          0x08C4   SharePoint Foundation
    Topology                         e5mb   Medium     WcfReceiveRequest: LocalAddress:
'http://<spfarmssrs>:32843/8e68c61c48d3486b8f5780736e9de269/ReportExecution.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sqlserver/reporting/2011/06/01/ReportServer/Execution/LoadReport' MessageId:
'urn:uuid:b07b919a-fc06-4cf8-add1-617f40a1d42f'   665ee657-7c17-474e-b050-d115a932180f
06/13/2012 14:09:19.29    w3wp.exe (0x08F4)                          0x08C4   SharePoint Foundation
    Monitoring                       nasq   Medium     Entering monitored scope (ExecuteWcfServerOperation)
665ee657-7c17-474e-b050-d115a932180f
06/13/2012 14:09:20.55    w3wp.exe (0x08F4)                          0x08C4   SQL Server Reporting
Services    Report Server Catalog            0000   Unexpected   Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ItemNotFoundException:
The item 'http://<spfarm1>/Reports/Unbenannt.rdl' cannot be found.;   665ee657-7c17-474e-b050-d115a932180f
The Sharepoint Environment looks like:
- Sharepoint Farm 1:
Server 1: WFE -> is connected to the published Reporting Servers on Server 3.
Server 2: Sharepoint Application
- Sharepoint Farm 2:
Server 3: SSRS 2010 Sharepoint Mode
Reporting Services Service Application published
- Database Server is a SQL Server 2008 R2 Cluster
- SP1 and the CU Februar Patch is installed on all servers.
- Kerberos is configured for all service users.
Hope someone can help to resolve the problem.
Regards
Chris

Hello Chris,
Thanks for your response.
I did some research on my side, and found some similar issue on the Internet. Please try the following solutions.
http://go4answers.webhost4life.com/Example/rdl-upload-issue-sharepoint-2010-60988.aspx
http://social.msdn.microsoft.com/Forums/is/sqlreportingservices/thread/da1f9f8a-d641-4493-bcc0-aeb5d3caf216
If you have further question, please tell us freely.
Regards,
Edward
Edward Zhu
TechNet Community Support

Integrate SSRS Native Mode with Sharepoint 2013

Hi, I have read numerous posts that go back and forth on the question "is SSRS Native Mode supported to work with SharePoint 2013?" and it seems like the answer is no, it is not. Even with SP1 like some people suggested it seems like it is impossible
to integrate the two.
In this case is the next step simply to somehow (IIS?) route the Report Server Web Service URL to a SharePoint page?
What should I do with the fact that everyone in my domain can access the above mentioned URL?
Thank you for any and all answers, I appreciate it!

Hi Nestalna,
As per my understanding, you want to allow everyone in your domain to access Report Server Web Service URL, but you don’t know how to grant permissions, then you think we can control permission using sharepoint, right?
In native mode, we can grant permissions to access Report Server Web Service URL by following steps:
From the Start menu, point to Programs, point to Administrative Tools, and then click Computer Management.
Click to expand the Local Users and Groups node.
Right-click Groups, then click New Group, type the name and description, then add domain users to the group.
Start Report Manager.
Click Site Settings.
Click Security.
Click New Role Assignment.
In Group or user name, enter the group you created above.
Select a system role, and then click OK.
In this way, domain users can access report manager. If they want to view, add, and manage report server content, subscriptions, report processing, and report history, we need to assign Item-level role on specific folders or items to them. Besides, in earlier
version of SQL Server 2012, we can configure Reporting Services to native or sharepoint integrated mode, from SQL Server 2012, we can configure Reporting Services to native and sharepoint integrated mode.
For more information about Grant User Access to a Report Server, please refer to the following document:
http://technet.microsoft.com/en-us/library/ms156034(v=SQL.105).aspx
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu

SQL 2012 SP1 Enterprise (SSRS in SharePoint mode): Reporting Services scale-out deployment is not supported in this edition of Reporting Services

Hello,
SSRS in SharePoint mode is driving me insane.
We are recreating a SharePoint 2013 (SP1) farm in a test environment with the following set-up:
2 SP Web FrontEnds
2 SP Application Servers
1 SQL Server
At both SP APP Servers, we installed SSRS (SQL 2012 Enterprise w/ SP1) in SP integrated mode.
We managed to start the SSRS SP service at the first SP APP Server. However when we try to start it on the second APP Server, 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 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. "
Now I can't stress this enough: This is a SQL Server 2012 SP1 Enterprise. This is the image we got from our MSDN subscription. There is no mistake here.
Could someone please advise why SP might think this version of SSRS is not the correct one?
Thanks in advance for your help.
Regards,
P.

Hello,
I'm afraid that is not it.
After a long, frustrating and strenuous investigation and troubleshooting, we found the problem.
The problem is the current ISO for SQL Server 2012 Enterprise SP1 (x64) found at MSDN. Bear in mind that we downloaded this ISO from MSDN about a month ago.
As soon as we recreated the environment using the ISO for SQL Server 2012 Enterprise SP2 (x64) found at MSDN, everything worked as expected -- and that includes running more than one SSRS in SharePoint mode.
Also bear in mind that we tried updating the SQL SP1 install with SP2 and subsequent cumulative updates but that never fixed the problem.
There is something fundamentally wrong with that ISO with SP1 slipstreamed in it that no matter the subsequent updates installed, SSRS in SharePoint mode fails to work properly on a multi-server environment. We went as far as SP2 with CU3 and nothing seemed
to fix the problem. And yes, we also performed manual updates to the SSRS and PowerPivot SharePoint MSI add-ins.
I am shocked and distraught to find out that I lost hours of work due to a dodgy ISO image.
Regards,
P.

Using Sharepoint 2013 with SSRS native mode !

Hi there !
We have 2 servers A & B. A is Sharepoint server and on B we have installed SSRS in native mode. Server C is database. We are not looking to use SharePoint Integration mode but We are planning to use native mode only !
We are looking for a way to make A & B talk as how a report hosted on B will show up on A since its not in integrated mode?
Can you please let us know of the proper steps to deploy this?
Thanks in Advance !

the "integration" between SP and SSRS native mode is basically an IFrame.
you should be able to find the RS native mode integration solution file (which is just two webparts, the report manager web part, and report viewer web part) somewhere on the SQL server / media... should still work with SP2013.
Keep in mind that SharePoint's authentication will be COMPLETELY INDEPENDENT AND UNUSED when accessing the reports... an iFrame is just another web request made by the browser.
Scott Brickey
MCTS, MCPD, MCITP
www.sbrickey.com
Strategic Data Systems - for all your SharePoint needs

SSRS 2012 SharePoint Mode Impersonate

SP 2013 / SSRS 2012 in SharePoint Mode. Everything worked fine until we started configuring for Kerberos for using Pass-Through Authentication to data sources. We have this working in our current SP 2010 / SSRS 2008 Integrated Mode and so have experience
both with creating SPNs for delegation and editing SSRS config-files.
Any documentation we have found from Microsoft on editing the report server web.config are in best case incomplete and many are just wrong. For example adding what Microsoft recommends - '<authentication mode="Windows"/>' -
causes the RS service application to crash. This does seem to be covered by other options in the config-file, but we are not able to find any documentation for that.
Is anybody aware of a place where this is actually documented?
Thanks.
Regards, Stig

Hi Heidi,
many thanks for the reply. We have already been through this post and believe that we have configured Kerberos with constrained delegation exactly as described. We have quite some experience with that already as we do have a functioning SharePoint 2012 with
SSRS Integrated mode that have also been configured for Kerberos.
Our doubts/issues here lies purely with what we need to do with the SSRS web.config file. We have been through not only the referenced post, but a multitude of others as well. Our understanding from all these is that we need to have <identity impersonate="true"
/> in the SSRS web.config file for it to be able to pass-through the identify of the client user.
This however produces an error for accessing SSRS in any way: "
The report server cannot decrypt the symmetric key that is
used to access sensitive or encrypted data in a report server database.".
We have researched this error and tried all manners of backup/restore the key and deleting the encrypted data as it is being referred to, but none of this helps.
If we set this back to <identity impersonate="false" /> the SSRS functionality then works again, but we are then not getting the Kerberos identity passed through to the remote database server (which the data source points to).
This is why we asked for documentation on how exactly SSRS is using the web.config file.
Regards, Stig
Regards, Stig

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.

SSRS integrated mode in SharePoint 2013

SSRS integrated mode was working now when i click on SSRS service application it gives internal server error 503. In ULS log i see
System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
How to fix it? I recreted Service application and started and stopped service too but nothing seems to be working. How to re-install it completely by removing all the services from the Server?
Also how to switch mode from integrated to native since our end users might decide to go to native if integrated does not meet their business need. I do not see any article to switch from integrated to native mode.
It is really frustrating to keep fighting with this issue.
Any help will be appreciated.
Thanks.
Adit

Make sure the Application Pool driving the SSRS SA is online. Check the System Event Log and Application Event Log on the SSRS server.
You cannot move between Native and Integrated any longer. You need to just re-deploy SSRS in the native config with a new SSRS database.
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.

SSRS in SharePoint mode 14 hive

Hello
I have an environment with 2 servers :
- Sharepoint Server (APP + Front),
- SQL Server (Database engine, Analysis Service (tabular+ PowerPivot, MDM).
Now i am trying to install SQL Server 2012 BI features and especially Powerview for SharePoint.
In the SharePoint Server i installed "Reporting Service In SharePoint Mode" and "Reporting Service Add-in for SharePoint"
The installation is completed successfully but apparently all files are installed into 14 folder ?
So i can't see "Reporting" folder in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\WebServices
I have created the service application for reporting service.
Now when i try to select system settings I receive this error
"the remote server returned an error (500) internal server error"
Have you any idea ?
Should i install SharePoint 2013 and "Reporting Service SharePoint Mode" in SQL Server box ?
What thing I am missing or what should I do ?
Thanks in advance
sharepoint 2010

Hello
I have an environment with 2 servers :
- Sharepoint Server (APP + Front),
- SQL Server (Database engine, Analysis Service (tabular+ PowerPivot, MDM).
Now i am trying to install SQL Server 2012 BI features and especially Powerview for SharePoint.
In the SharePoint Server i installed "Reporting Service In SharePoint Mode" and "Reporting Service Add-in for SharePoint"
The installation is completed successfully but apparently all files are installed into 14 folder ?
So i can't see "Reporting" folder in C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\WebServices
I have created the service application for reporting service.
Now when i try to select system settings I receive this error
"the remote server returned an error (500) internal server error"
Have you any idea ?
Should i install SharePoint 2013 and "Reporting Service SharePoint Mode" in SQL Server box ?
What thing I am missing or what should I do ?
Thanks in advance
sharepoint 2010

SSRS Integrated mode failes (timeout) when executing lengthy reports.

Hi All,
I have SSRS 2008 R2 running in integrated mode with SharePoint 2010 foundation. The SharePoint farm and SSRS are both configured for Kerberos authentication. Both SSRS and SharePoint are working well. The vast majority of reports
compile in less than 30 seconds, users are generally happy.
Except, I have a couple of reports which take a long time to execute on the SQL side, I cant change this, that's just how it has to be. The simplest of the reports to explain is a report, with 1 parameter with four values, which performs
up to four actions on the SQL Server and then returns around two dozen rows of the result, typically the entire process completes in around 10 minutes. If I run this report via the ssrs /reportserver WFE the report always completes, results are presented
on screen, no issues whatsoever. When I run the same report from within SharePoint, its a different story, the report will complete only if I select just one of the four parameter actions, resulting in the total report execution time of
around 4 minutes, However when running the report with all four parameters selected, the loading spinner appears, then after 6 minutes, disappears entirely. The page returns to the parameter selection, no results are presented.
Having checked all the SSRS log files and ExecutionLogStorage table, they suggest that the report carries on building in the background, and then completed roughly 10 minutes after starting.
So my conclusion is that something in SharePoint does not like the extended duration of the report execution. But what is it, What triggers the 6 minute timeout?
Any help much appreciated.
Regards
Dan

Hi danbridgland,
According to your description, there are a couple of reports in SSRS Sharepoint integrated mode. The query takes a long time to execute in SQL Server. When you run the report via Sharepoint WFE, the report works fine. When you run the report in Sharepoint
Application, the report will be displayed if you select one parameter value, if four values of the parameters are selected, the report disappears after 6 minutes’ loading.
In Native mode, SSRS uses a default timeout of 9000 seconds. In SharePoint integrated mode the timeout is reduced to 120 seconds. The timeout in SharePoint is actually related to the fact that reports are rendered using the http runtime. Any operation that
is launched from within SharePoint using the httpRuntime object has to complete within the timeout parameters. In this case, we can directly editing timeout in web.config by following steps:
Locate web.config for the SharePoint site you have configured for SSRS integration (default location: C:\inetpub\wwwroot\wss\VirtualDirectories\80).
Open the file in an XML or text editor.
Navigate to httpRuntime element, inside the tag, add executionTimeout="9000".
In addition, in SharePoint integrated mode, reports typically run slower than when the same reports run in native mode. One main cause of this latency can be attributed to SharePoint object model calls that are made. For detail information, please refer
to the following document:
http://support.microsoft.com/kb/2216504
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu

SSRS/SharePoint Migration 2010 to 2013 connection issues

We are currently attempting to move our SharePoint 2010 to 2013 and SSRS Information. The first attempt at this we were unable to get SSRS to show up in Central Admin. We decided to rebuild all servers and re-installed everything.
This time we have SSRS showing up in Central admin and we are able to run some reports from our sites now. In our 2010 environment we are using "Windows authentication (integrated) or Sharepoint user" option with SharePoint Lists. I am unable to
get this to work in our 2013 Environment, the stored credentials with windows authentication will work however.
I have read t through many different books, MS Guides, Blogs, Forums, etc but unable to solve this issue.
I have tried editing the rsreportserver.config to match our Production, did not help. (also tried different authentications)
I found an article saying to change the "Forms" Auth in some config files to "Windows" did not help
When I try to go to our \\localserver\reportserver (appserver) I get a blank page with this info:
HTTP/1.1 200 OK
Server: Microsoft-IIS/8.5
Date: Fri, 21 Nov 2014 22:30:03 GMT
Connection: close
I have tried going into Central Admin -> General Application Settings -> Report Server Integration. and fill out this information also but receive this error:
Failed to establish connection with report server. Verify the server URL is correct or review ULS logs for more information. Product area: SQL Server Reporting Services, Category: Configuration
Pages
I am not sure if I have missed some step along the way of migrating and setting up this information. Any help or other things to try would be very helpful.
Thanks!

Hi young99,
According to your description, you get connection issue after migration from SharePoint 2010 to SharePoint 2013. Right?
In this scenario, we are not clear how you did the migration. Please follow these steps and check if you miss anything:
Restore Reporting Services encryption keys
Backup the SharePoint content databases and detach it.
Backup Reporting Services catalog database.
Copy Reporting Services configuration files.
Restore SharePoint Content databases to the new farm.
Restore the Reporting Servicesencryption keys.
Restore the SQL database that is the Reporting Services catalog database (ReportServer).
Restore Reporting Services configuration files.
Create a new Reporting Services service application.
For more information, please see:
Migrate a Reporting Services Installation (SharePoint Mode)
If you have any question, please feel free to ask.
Best Regards,
Simon Hou

Ssrs sharepoint 2013 error: "A delivery error has occurred ...not a sharepoint document library..."

Greetings SSRS/SharePoint experts,
SharePoint 2013 with SSRS - Creating a subscription to a report that is in SharePoint
I'm trying to create a subscription to publish a report to a sharepoint document library.
I've configured all the settings and on clicking OK get the following error:
"A delivery error has occurred. ---> Microsoft.ReportingSerives.Diagnostics.Utilities.DeliveryErrorException: A delivery error has occurred. ---> Microsoft.ReportingServices.Diagnostics.Utilities.InvalidExtensionParameter: One of the extension
parameters is not valid for the following reason: The delivery path is either not a SharePoint Document Library Folder or does not exist in the Share Point farm."
SQL Server Developer Edition 2012 SP1
SharePoint 2013 Standard
Just wondering if anyone has a solution.
I've tried changing the proxy settings as per this post
http://social.technet.microsoft.com/Forums/en-US/19817dc7-6725-40d8-befa-1b94099a71bd/sql-server-2012-reporting-services-in-sharepoint-2013-integrated-mode-dilivery-extension
Workaround is to not use a sharepoint document library but write the report to a windows file share (this works but is not optimal).
Hoping someone at Microsoft or an expert will come back with something.
Kind regards
Gio

Hi,
Can you check the SharePoint ULS log located at : C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS, and look at the log there when the error occurs?
You can also check the Application Event Log on the SQL Server to see if there are any additional errors.
Tracy Cai
TechNet Community Support

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.

SharePoint 2010 Excel Services with SQLserver 2012 cubes

I have two tier sharepoint 2010 enterprise setup
1)wfe and app server
2) sqlserver
I also have a sqlserver 2012 which hosts all our BI cubes .
is it possible to connect excel (office 2010) to sql 2012 BI and save that in my sharepoint 2010 server under shared documents and expect it to refresh when aall authenticated users hit " refresh all connections"
It is not able to hit refresh . I get a " unable to refresh data for a data connection in this notebook" the following connections fail to refresh.
Interesting when I do the same this using sql server 2008 r2 BI , everything works fine

Hi,
According to your description, my understanding is that the SharePoint 2010 Excel Service cannot work with SQL Server 2012.
Did you install Service Pack 1 for SharePoint 2010?
SharePoint 2010 Service Pack 1 is required for SQL Server 2012 PowerPivot for SharePoint features.
Please check if the Service Pack 1 is installed for SharePoint 2010. If not, please download it from the link below and install it:
http://www.microsoft.com/en-hk/download/details.aspx?id=26623
More references:
http://msdn.microsoft.com/en-us/library/ee210708(v=sql.110).aspx
http://msdn.microsoft.com/en-us/library/6d61be91-0396-443c-a7f4-02dcf973775e(v=sql.110)
Best regards.
Thanks
Victoria Xia
TechNet Community Support

SSRS Sharepoint Mode.excel question

Similar Messages

Maybe you are looking for