SharePoint And SSRS - URL Access And Setting Parameters
Jun 29, 2007
I want to create some links in Sharepoint that will take me directly to a report, display it within the SharePoint full page report viewer and set some parameter values along the way.
I would like to set up a subscription that has two date parameters, I would like the end_date to be today and the start_date to be (today - 1 Month). The interface does not seem to support expressions?
I saw some documentation that said to use defaults in the report but that does not help because I may want multiple subscriptions with different params like 1 person may want (today - 2 months) as the start date ...
Hoping someone may be able to help with a problem I'm having with SSRS parameters....
My report has 2 parameters - the User Id used to login to the application and the Department(s) within the organisation. Based upon the User's role, the user may have access to data for one or many Departments.
Thus, the first parameter needs to be set in code based upon the User's login, however, the range of the second parameter (i.e. the range of Departments that the user can access) is controlled by the value of the first parameter.
The second parameter is to appear as a drop-down of Departments to which the User has access.
The report is to be produced for the selected Department.
Are you able to advise how to restrict the range of values for the second parameter based upon the value of the first parameter?
We have SSRS reports (pointing to SQL 2012) containing cascading parameters that we have deployed on SharePoint 2013 and once a user makes a selection to the parent parameter, child parameters are getting refreshed based on the selection in the parent parameter and then we see this:
Once we hit Apply, the Loading image comes up and approximately10 seconds later, The whole webpage gets refreshed and the parameter selections get reset to default parameters.
This is getting frustrating because there are about 10 parameters in the report and once a user makes selections and hit apply if the page gets reset, the user has to make all the selections again.
We are working with Microsoft support on this who suggested us to increase the timeout setting of DistributedCache service on all our SharePoint servers which did seem to work initially but I do see this issue happening occasionally.
I have an SSRS report with parameters for Created On Start and Created On End. Users run this manually and choose the date range to display records for.
I would like to set up two different subscriptions
1) to send weekly on Monday morning for "last weeks" records and 2) to send monthly to send "last month's" records.
We have an Office SharePoint 2007 site, we developed a couple of web parts and added them to our site. We used SQL Server Reporting services 2005 as our reporting solution. The reports are hosted on the report center and when we need a report, we open it by sending a URL requesting the report, passing the report parameters in the URL query string. So the report is filtered based on the parameters passed from the web parts.
But since best practices say that you should host reports directly under SharePoint, by configuring the reporting services to run in the SharePoint integrated mode. We followed the steps and installed SharePointRS and we finally succeeded to publish the reports to a SharePoint folder, but we had a limitation: we are unable to pass the report parameters internally to the report hosted in SharePoint. If we passed them in the query string as the report center case, SharePoint neglects them totally. So the question is: how can I pass parameters internally between a SharePoint web part and a SQL server 2005 reporting services report hosted in SharePoint?
Since I wasn't getting any replies with answers or suggestions to my initial posting, I figured I would continue to list the problems and solutions I've encountered while trying to setup and utilize SharePoint integration mode, and read data from SharePoint with SSRS reports (developed in VS2005). Hopefully this is helpful to anyone that is also trying to learn all this stuff and figure it out.
(Single server - W2K3R2_SP2 as: DC / SQL2005 Standard / MOSS2007 Enterprise - see the bottom of this posting for the steps I took to set that up)
Note: After I get this to work, I intend to post my experiences for setting up SharePoint Integration with SQL and SP on separate boxes.
1. In the new reporting section under SharePoint application management in the Central Admin Console, the Grant database AND Set Server Defaults work when using the domain admin account, but not when using the SQLSPS service account I used to setup both SQL and SharePoint. Why can't I use the service account? Is the domain admin account now going to be used as a service account for accessing the sharepoint database?
This question remains unanswered as of yet.
2. Reporting Services configuration tool shows Sharepoint integration as red x when I create a new database in integration mode. (the service account SQLSPS and the Server object are members of the group WSS_WPG). If I switch back to native mode (the original reportserver database), the red x goes to a blue exclamation instead. Using Service Credentials or Windows credentials (as either the service account SQLSPS or as domain admin) doesn't change anything.
RESOLVED by using a domain user account for the ReportServer WebApp. Even though everything is installed on the same machine, it seems using the default of NETWORK SERVICE wasn't acceptable. Possibly because SharePoint is configured to allow additional machines in the farm?
3. http://servername:8080/reportserver will display Report Server information as it did before the integration on port 80, but http://servername/reportserver doesn't display anything through SharePoint.
Resolved. I needed to define a repository before I could view it (go figure). When I created a sharepoint site based on a report center template, created a data connection library and report library, and then referenced that by http://servername/sites/myReportCenterSite/myReportLibrary, I was able to see the equivalent of http://servername/reports (which is now disabled due to integration mode).
4. Unable to deploy to new report center sharepoint site I mention above using Visual Studio. I kept getting "A connection could not be made to the report server http://servername/sites/ReportCenter. Server was unable to process request. The request failed with HTTP status 503: Service unavailable (System.Web.Services). In Visual Studio, the project properties were: TargetDataSourceFolder = http://servername/sites/myReportCenterSite/myDataConnectionLibrary, TargetReportFolder = http://servername/sites/myReportCenterSite/myReportLibrary, TargetServerURL = http://servername/sites/myReportCenterSite/
Found these errors in the event logs on the server.
Event Type: Warning Event Source: W3SVC Event ID: 1021 Description: The identity of application pool, 'ReportServer' is invalid. If it remains invalid when the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.
Event Type: Warning Event Source: W3SVC Event ID: 1057 Description: The identity of application pool 'ReportServer' is invalid, so the World Wide Web Publishing Service can not create a worker process to serve the application pool. Therefore, the application pool has been disabled.
Event Type: Error Event Source: W3SVC Event ID: 1059 Description: A failure was encountered while launching the process serving application pool 'ReportServer'. The application pool has been disabled.
RESOLVED the issue by changing the Application Pool used by reporting services from ReportServer to DefaultAppPool and changing the account DefaultAppPool used from NETWORK SERVICE to my service account SQLSPS. I have no idea why ReportServer is invalid, it was set to use the service account SQLSPS the same as DefaultAppPool is. Perhaps the reporting services add-on makes a change to invalidate this?
5. Attempting to read a SharePoint list using a SSRS report. This should be fun.
First, created a new custom list in the ReportCenter SharePoint sites I've been using and called it myCustomList. I added one item with a title of myCustomListItem1. I don't know if I need to do more than that for a simple test of reporting or not yet.
Second, configured new shared data source. Name = myCustomList1DataSource, type=XML, Connection String = http://servername/_vti_bin/lists.asmx (this URL is viewable in IE), Using Windows authenticaion.
Third, in VS2005 on a workstation in the domain, create new report item (report1.rdl). New dataset for report; Name=Report1DataSet, Data Source=myCustomList1DataSource (Shared), Command type = text, Query String = [See Queries and associated errors below]:
Initial query obtained from: Connecting SQL Reporting Services to a SharePoint List (David Wise) http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx
Note: Queries when executing the dataset (which errors out) and when executing a query in CAML Viewer for the same information (which does work just fine) both initially return 401.1 and 401.2 errors (as viewed in Fiddler). Since the CAML query works, I have not tracked this down yet.
Parameter; Name => listName, Value => =myCustomList
Was NOT prompted to define the query parameters
- Gets this error: "An error occurred while setting the command text property of the data extension command. The XmlDP query is invalid. (Microsoft.ReportingServices.DataExtensions)."
- Advanced information from the error => 'http' is an unexpected token. The expected token is '"' or '''. Line 2, position 19. (System.Xml)
B. Changed: Placed the namespace URL in quotes (also tried with and without / in namespace after /soap)
Parameter; Name => listName, Value => =myCustomList (also tried Value => myCustomList) (no equal sign)
Clicked "!" to execute, and got prompted to define the query parameters Entered Name => listName, Value => myCustomList
- Gets this error: "failed to execute web request for the specified URL (Microsoft.ReportingServices.DataExtensions)."
- Advanced information: <faultstring>Server did not recognize the value of HTTP Header SOAPAction: http://schemas.microsoft.com/sharepoint/soap/GetListItems/.</faultstring>
C. Try the query string that seems to work for Stramit CAML Viewer to read myCustomList
Also tried <Query xmlns="http://schemas.microsoft.com/sharepoint/soap/"> </Query>
And tried entering no query...
Parameter; Name => listName, Value => =myCustomList (also tried Value => myCustomList) (no equal sign)
Clicked "!" to execute, and got prompted to define the query parameters Entered Name => listName, Value => myCustomList
- Gets this error: "failed to execute web request for the specified URL (Microsoft.ReportingServices.DataExtensions)."
- Advanced information: <soap:Fault><soap:Code><soap:Value>soap:Receiver</soap:Value></soap:Code><soap:Reason><soap:Text xml:lang="en">Server was unable to process request. ---> Data at the root level is invalid. Line 1, position 1.</soap:Text></soap:Reason><soap: Detail /></soap:Fault>
RESOLVED. Went back to the query used in B above, and mysteriously it works now. This could be the "funny things happen" symptom I've been reading about. We'll see if it continues to function.
Here's what I've learned so far on Issue #5:
1. XML is confusing. XmlDP is even more confusing...whatever that is. Apparently it's new to/with Reporting Services in SharePoint integration mode? 2. There is far too little documentation regarding XmlDP and querying SharePoint lists from SQL Reporting Services. 3. According to http://msdn2.microsoft.com/en-us/library/ms159741.aspx: You must use the generic query designer to create the query. The query is not analyzed to identify parameters; therefore you must create parameters through the Parameter tab on the Dataset dialog box.
Tried this query:
<Query> <SoapAction>http://schemas.microsoft.com/sharepoint/soap/GetListItems</SoapAction> <Method Namespace="http://schemas.microsoft.com/sharepoint/soap/" Name="GetListItems" /> <Parameters> <Parameter Name="listName"> <DefaultValue>myCustomReport2</DefaultValue> </Parameter> <OrderBy> <FieldRef name="ows_Date" /> </OrderBy> </Parameters> </Query> I was still prompted for the listName and the list returned with ows_Date still out of order. So maybe that proves this statement is true? <translation: why make it convenient when it's already [somewhat] functional?> 4. When building the dataset, anything I place in the "Query string" box has to be enclosed in <query></query> tags or it errors out. I am trying to understand how to translate the CAML viewer query (which does work but isn't wrapped in query tags) into something that fits between query tags, and it hasn't gone well so far. <translation: To be at one with your reports Grasshopper, you must understand xml> 5. According to http://srv1/sites/ReportCenter/_vti_bin/lists.asmx, "GetListItems" operation is supported <translation: you're getting warmer...> 6. According to the soap output of my site http://srv1/sites/ReportCenter/_vti_bin/lists.asmx?op=GetListItems, I am only allowed to specify the following parameters: listName, viewName, query, viewFields, rowLimit, queryOptions and webID. <translation: that and $3.00 will get you a cup of coffee> 7. According to http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx, only listName, viewName and rowLimit parameters are usable(?) (query and queryOptions may not be working properly with SSRS). <translation: that kind of sucks> 8. When this started mysteriously working again, I tested using the "/" at the end of the namespace (wouldn't work without) and the "=" sign in front of the parameter value as defined on the parameter tab of the dataset (turns out to be optional).
As long as I can query SharePoint and get my list information back, I'm going to consider this issue closed and move on to actually using this information in a report. I'm sure that won't work right either, but why stop now?!
6. Ok, now that I can read SharePoint list data with SSRS, I need to try and actually do something with it.
A. Begin by setting up new data to report on
1. Create a new custom list (myCustomList2) and add a test record. This list will simulate the data we intend to submit to SharePoint using InfoPath, so it has a number of custom/created columns in it
2. Modify the working information from #5 above; add a new shared data source (myCustomList2DataSource), tell the dataset to use the new shared data source, change the information set in the parameter tab (Name => listName, Value => =myCustomList2) and test the dataset. Lucky me, it actually returned the record I entered on the first try.
B. Begin to build the report with the dataset returned
1. So, as I'm feeling good that it's actually reading the list in Step A without me threatening to destroy the machine, I look to the left in the Dataset results navigation pane in VS2005 and realize there are NO fields for me to choose to report on. 2. At this point, I have no clue what to do about getting this XML data into a report. Not that I have a large clue about SSRS otherwise, but I have at least been able to build SSRS reports when using a SQL database as the datasource. Fyi, http://msdn2.microsoft.com/en-us/library/ms159741.aspx states: "Reports can use data from XML documents and Web services, or embed XML in the query. There is no built-in support for retrieving XML documents from a SQL Server database.", in case anyone is trying to do that....
RESOLVED. Since the fields were not appearing automatically, I had started to add new fields to the dataset manually (if it doesn't work, beat it with a hammer, right?). I entered half a dozen or so fields, each one with the exact name as displayed in the query results, and then decided it would be fun to hit the refresh fields icon. As soon as I did that, all the fields shown in the query immediately appeared in the dataset and I was able to add them to a report. I don't know if I hit the refresh fields when working in issue #5, so I can't say if they are there now because of that, or because of adding some fields manually first, a combination of the two, or if it's just one of those mystery items I'm reading about with sharepoint reporting.
7. Rows are being returned even though they have NULL values (so far anyway), and most data is returning nicely for the bulk of the columns I created in the list I'm reporting on. Here are the current issues:
A. I have one column in my SharePoint list that is multi-lined text. If the text type is either rich text or enhanced rich text, the value returned in the query is formatted like this: "<div class=ExternalClassyadayada<div>My notes display here". If I set the column to be plain text, this doesn't happen. I will need to figure out how to filter that for my report.
RESOLVED. David Wise had some code listed at http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx that addressed this issue somewhat. I modified it to match my circumstances. Disclaimer: I'm not a programmer, so use this at your own risk.
function ExtractMultiLineText(myField as string) as string dim strBegin as string dim strEnd as string dim myBegin as integer dim myEnd as integer dim myTextLength as integer strBegin = "<div>" strEnd = "</div>" if myField = nothing then return "" if myField = "" then return "" myBegin = Instr(myField, strBegin) + Len(strBegin) myEnd = Instr(myField, strEnd) myTextLength = myEnd - myBegin
if myBegin < 1 then return myField return mid(myField, myBegin, myTextLength) end function
B. I have two columns in the SharePoint list that are set as number values with 0 decimal places. When I query those however in SSRS, they return with the number plus like 12 zeroes behind the decimal. Not a major issue, but I'll put it on the list anyway.
RESOLVED. Used the Int() function; =Int(Fields!ows_myProblemNumber)
C. If I go to "/_vti_bin/lists.asmx?op=GetListItems", it appears from the sample soap output that I am allowed to ask GetListItems for is: listName, viewName, query, viewFields, rowLimit, queryOptions and webID. As I mentioned in issue #5, according to http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx, only listName, viewName and rowLimit parameters are usable(?) and query and queryOptions may not be working properly with SSRS.
So, if I can't put anything other than this in my query string;
<Query> <Method Namespace="http://schemas.microsoft.com/sharepoint/soap/" Name="GetListItems"/> <SoapAction>http://schemas.microsoft.com/sharepoint/soap/GetListItems</SoapAction> </Query> and I only have a couple parameters to pass on top of that, then it appears to me that my options for filtering the amount of data returned from the SharePoint list is to figure out a way to do it with expressions in the parameters or in the report itself. Am I missing something? Is this really all I get to work with out-of-the-box?
More to come...
================================== Installation steps taken to build the server VM: ==================================
(Using VirtualPC 2007) 1. Build OS (2003R2SP2) and promote to DC
1a. Create domain user service account SQLSPS 2. Prep for SQL
3a. Verify SSRS works 3b. RS config tool shows SP integration as blue exclamation 3c. Use service account SQLSPS for anything requiring Windows credentials 4. Install SQL2005 SP2
4a. Verify SSRS works 4b. RS config tool shows SP integration as blue exclamation 5. Prep for SharePoint
5a. Install .NET 3.0 6. Install MOSS2007 Enterprise and configure
6a. Webapps, SSP and anything else use svc acct SQLSPS 6b. Move Default website to port 8080 and re-activate (SharePoint stopped the site) 6c. Verify SSRS works on 8080 7. Install Reporting Services Add-in 8. Create new RS database in integration mode (with service credentials)
8a. RS config tool shows SP integration as red x 9. SP central admin /application management / manage integration settings
9a. reports server = http://srv1:8080/reportserver (since default port has been moved to 8080) 10. SP central admin /application management/grant database access
10a. using the FQDN, confirm servername and default instance - click OK 10b. Prompted for an account to use to retrieve information; svc acct SQLSPS did not work, domain admin did though 11. SP central admin / application management/set server defaults
11a. Accepted all defaults 12. Verify reportserver answers at http://srv1:8080/reportserver (via reportserver AppPool and DefaultAppPool) 13. Changed the application pool identity for the ReportServer AppPool from Network Service to the domain user service account I used for all SQL and SharePoint configurations (SQLSPS) and rebooted. The red x for sharepoint integration in the RS configuration tool is now a green checkmark.
I get the following error when I try to navigate to a report/model/data source, stored in a Sharepoint Document Library using a Sharepoint URL based on an Extranet or Intranet zone - but it works OK using the url for the Default zone:
System.Web.Services.Protocols.SoapException: The specified path refers to a SharePoint zone that is not supported. The default zone path must be used. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SecurityZoneNotSupportedException: The specified path refers to a SharePoint zone that is not supported. The default zone path must be used.
Is this a limitation of the SQLRS-WSS3 integration or is there a workaround?
I have a sharepoint on a windows internal database server (some version of sql express 2005). When I run the app, it says that I need SQL server reporting services 2005. I dont think that this component is bundled with "windows internal database server". Is there anyway I can download this component or otherwise make this work?
Seems a bit silly that they would make a tool requiring a component that doesnt need to be installed for sharepoint to run.
Does anyone know of a link or list that has all the parameters for the "rs:" section of the URL access parameter, except for the ones in the Microsoft books?
I'm running MOSS 2007 in Integrated Mode, and I have a number of reports that are deployed to the Reports Library, and are working just fine when you go there and run them interactively.
Now however, I need to address the report via a URL, and pass it a parameter. Just to add a bit more pain, the report is in mdx, and expects an mdx parameter.
Here is the parameter "prm_cost_centre":
[DIM LEARNER AIM].[COST CENTRE DESC].&[Business]
Here is the URL of the report:
http://vmmoss:88/ReportsLibrary/Report1.rdl
(If you hit that URL as is, it runs fine, using the default parameter)
Now, I know that we have to escape the ampersand, so I'm thinking that this URL should do it.
http://vmmoss:88/ReportsLibrary/Report1.rdl&rs:Command=Render&prm_cost_centre=[DIM LEARNER AIM].[COST CENTRE DESC].%26[Business]
But it doesn't - It throws a 400 Bad Request error.
I know I must be very close, but I just can't work out what URL I need to pass in order to get the damn thing to run.
I'm deploying a performance point site which includes several parameterized SSRS reports. Reporting services is configured to run in Sharepoint integrated mode.
I'd like to pass the parms to certain reports via URL posts when a user clicks on certain fields in a scorecard.
I can setup the basic URL to open a report, as follows:
When this URL is executed, the sharepoint site redirects with the following URL, which opens the report and prompts for a text date paramater (DatePrompt) in the format dd-mmm-yy (i.e. 01-Sep-07)
"...Sharepoint sees the Report Viewer Web Part as a single item and will continually rename it sequentially as Report Viewer [x].... This is a limitation of SharePoint..." http://books.google.com/books?id=b0dXlx5aww8C&pg=PA314&lpg=PA314&dq=report+viewer+web+part+title&source=web&ots=U0MVGHySWU&sig=pGBgHh2gXYWcpuZMqttY7S9B65c&hl=en
If this is true then it applies also to the ReportExplorer webpart. Is there a current fix for SharePoint? Or is there a current fix for the webParts?
I can see customers complaining that they would like to see on their SharePoint ReportExplorer WebParts pointing to separate environments (SSRS) and multiple ReportViewer webparts pointing to different reports. Which would result in ReportExplorer [1], ReportExplorer [2],....ReportExplorer [x] and ReportViewer [1], ReportViewer [2],....ReportViewer [x].
Instructing customer's to ignore webpart title's and look at report names is NOT going to be acceptable. Especially since other webparts within Sharepoint behave differently.
I have recently installed Reporting Services Integrated mode with minor issues and at the end I was able to execute reports as well as add the content types.
I am now working on doing the same exact thing except I do not see Report Server Content types. I am able to upload a report and execute it but cannot add the Content Types. When I login into Central Administrator I see the content type in there. Is there something I am missing to add it to "My Site"
We are using xml to pull data from a custom sharepoint list into sql 2005. We have set a parameter that allows the user to filter the data by surname, however when the user tries to filter the list the drop down box brings up a list of every record, so there are duplicate entries for each surname.
Is there a way of filtering this so that there is only one instance of the users surname instead of it showing all the records?
I have the integration set up between Sharepoint and SSRS, but I follow the Add-in readme below. I do not see the Reporting Services select content types section. I can manually create each content type(Report, Builder, Datasource, etc..) but the images for then when I click Add in the list there are no images associated to the different content types.
Set Permissions and Add Reporting Services Content Types You must assign user and group accounts to SharePoint groups or permission levels to grant site access to those users. Users who can access a site can also perform reporting tasks. For example, users with view permissions to access a site can also view reports on that site. To complete the integration steps, you must ensure that all users who access and manage report server content on a SharePoint Web application have the appropriate permissions. You might also want to add Reporting Services content types so that users who have permission to use Report Builder can start it from the New menu. To add content types:
Open the library for which you want to add Reporting Services content types.
On the Settings menu, click Document Library Settings.
Under Content Types, click Add from existing site content types. If Content Types is not available, locate the General Settings section and click Advanced settings to allow content type management.
In the Content Types section, select Yes to allow multiple content types.
In the Select Content Types section, in Select Site content types from list, click the arrow to select Reporting Services.
In the Available Site Content Types list, click Report Builder Report, and then click Add to move the selected content type to the Content types to add list.
To add Report Model and Report Data Source content types, repeat steps 5 and 6.
When you finish selecting all the content types that you want to add, click OK.
I am trying to query the SharePoint database to get a list of how many times a table name is being used in our SSRS reports.Here is my current query:
DECLARE @TEXTTOSEARCH AS VARCHAR(200) SET @TEXTTOSEARCH = 'tablenamehere' ;WITH XMLNAMESPACES (DEFAULT 'http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition', 'http://schemas.microsoft.com/SQLServer/reporting/reportdesigner' AS rd)
[code]...
This works for some tables since the names are unique and I can just do a search for that. However, some of the table names are simple and can also be used as aliases.if there was some way to get the list of table names easier.
I have installed SQL 2012 on my DB Server. The SSRS database version table(s) list the current version as 163. The Version number that's displayed in the Programs and Features for SSRS Add-in for SharePoint (yes, on the db server) is 11.2.5623.0.
On my two SharePoint servers the version number for SSRS Add-in for SharePoint shows 11.2.2058. I have installed SQL Server 2012 Service Pack 2 on all three machines. When the SharePoint box calls into SSRS to render a report I get this error:
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '163'. The expected version is '162'. --->
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is '163'. The expected version is '162'.
what else I need to install - and where - to correct this error. What is expecting version '162' and why?
I have integrated sharepoint list data to SQL Server reporting services. I am using the below to query sharepoint list data using sql reporting services.
By using this query, I am getting a dataset which includes all the columns of sharepoint list. Among these columns, I wanted to display only 2 columns (i.e Region and Sales type) using chart. I have created a Region parameter but when I click preview, the drop down box is giving me all the repeatative values of region like
RG1,RG1,RG1,RG2,RG2,RG2,RG2,RG3..........
I wanted to display only distinct values of Region parameter so that whenever end user select region from the parameter drop down, it will display the respective value of Sales type column.Also when I select only RG1 parameter, it is giving me a chart including the sales type of all the Regions. (it should display me only the sales type of RG1) How can I link these 2 columns so that they will display the values respectively.
I am looking for a good tutorial on how to set up Data Driven subscriptions through the SharePoint 2012 version of SSRS. I am needing to set up a Data Driven subscription that uses one report, but sends out the specific portion of the report to the appropriate recipients. I have used the information located at URL.... but it doesn't seem to provide all the steps needed to schedule the reports needed. It focuses around setting up the reports to go to shared folder locations. I need something around setting it up to go to email recipients.
I'm configuring now Reporting Services on SQL Server 2005 in Office Sharepoint Server 2007 integration mode. In the beginning of the process, I had already installed SQL Server 2005 with RS and Office SPS 2007. I used following guides to make further steps: How to Configure Reporting Services to Use a Non-Default Web Site (Reporting Services Configuration)
How to Configure Service Accounts (Reporting Services Configuration)
How to Configure SharePoint Integration on a Standalone Server How to Configure the Report Server Integration Feature in SharePoint Central Administration
Troubleshooting a Side-by-Side Installation of Reporting Services and Windows SharePoint Services
So I installed RS add-in for SPS, made RS configuration and almost all SPS configuration. I stopped with error
"An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> Server was unable to process request. ---> The request failed with HTTP status 404: Not Found. " in "Set server defaults" command.
My servers configuration is following: 1. Both RS and SPS are running on the same server. 2. I cannot change port of default web site, so I made different web site "Reporting services" under same web server with port 8086 (http://mtx-sps2007:8086/reportserver)
3. RS Windows service runs under domain system account that is a member of local Administrators group (account name sql2k5sps7) 4. RS Web service runs under NT AuthorityNetworkService account 5. Database connection configured using mentioned above account sql2k5sps7
6. Report Server Web Service URL in SPS is set to http://mtx-sps2007:8086/reportserver 7. Authentication Mode in SPS is set to "Trusted account" 8. My account, under which I make a connections through terminal services to SPS and RS servers and through http to reportingservices page is a member of local administrators group of both my PC and server. 9. I'm not familiar with SPS (honestly speaking, with RS too, but at least I learning this quickly, but SPS is out of my responsibilities scope) 10. ReportServer runs under separated app pool that runs under NT AuthorityNetworkService account
And now I'm fighting with this error on "Set server defaults" command. It's interesting that from my PC there is no credentials prompt when entering SPS administrations page and error is following: An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode But from terminal client, connected to SPS and RS server, there is a credentials prompt (I enter my credentials) and error is as mentioned abowe: An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> Server was unable to process request. ---> The request failed with HTTP status 404: Not Found. Also, the same error I got when I tried to add a report to report viewer web part on SPS test page.
Can anyone help me with this? I would be greately appreciated to any help on resolving this issue.
I'm running SSRS 2005 (9.00.3027.00) in Sharepoint integrated mode on a Win2003 SP1 box. This works fine for most reports, including matrix reports sourcing data from SSAS 2005.
However, I have a couple of large matrix reports (7 columns per group, 12 column groups, 150 rows, 1 row per group, data from SSAS) that run fine when I run them in VS2005, but as soon as I try and run them from within Sharepoint/Report Server I get "An unexpected error has occurred.". Sometimes this happens after 60 seconds, sometimes more (up to 3 minutes)
If I filter them down to 7 column groups they work perfectly (altbeit slowly,1-2 mins), 8 groups works sometimes, 9 never works. I've checked that the report execution timeout is set to 10 minutes.
The SSRS log shows the errors as WrapperReportRenderingException and JobCanceledException. I'm not sure whether the the rendering error causes the cancelled error or vice versa. does anyone know what I can do about this?
By the way, from looking at the CPU usage of the server, it seems as though SSRS does carry on rendering the report long after Sharepoint has given up and returned with the helpful error.
Many thanks in advance
Alex
Log extract as follows:
w3wp!library!7!01/25/2007-11:11:44:: Call to GetPermissionsAction(http://uk-ls-it-02/Reports/Triangles/Gross Triangle Treaty Property.rdl). w3wp!library!7!01/25/2007-11:11:44:: Call to ListParentsAction(http://uk-ls-it-02/Reports/Triangles/Gross Triangle Treaty Property.rdl). w3wp!library!7!01/25/2007-11:11:49:: Call to GetPermissionsAction(http://uk-ls-it-02/Reports/Triangles/Gross Triangle Treaty Property.rdl). w3wp!library!1!01/25/2007-11:11:50:: Call to GetPermissionsAction(http://uk-ls-it-02/Reports). w3wp!library!13!01/25/2007-11:11:50:: Call to GetSystemPropertiesAction(). w3wp!library!13!01/25/2007-11:11:51:: i INFO: Call to RenderFirst( 'http://uk-ls-it-02/Reports/Triangles/Gross Triangle Treaty Property.rdl' ) w3wp!runningjobs!7!1/25/2007-11:13:20:: i INFO: Adding: 1 running jobs to the database w3wp!runningjobs!7!1/25/2007-11:14:20:: i INFO: RunningJobContext.IsClientConnected; found orphaned request w3wp!reportrendering!13!01/25/2007-11:14:20:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException: An error occurred during rendering of the report., ; Info: Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.ReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.SharePoint.Library.SPRequest.OpenWebInternal(String bstrUrl, Guid& pguidID, String& pbstrRequestAccessEmail, UInt32& pwebVersion, String& pbstrServerRelativeUrl, UInt32& pnLanguage, UInt32& pnLocale, String& pbstrDefaultTheme, String& pbstrDefaultThemeCSSUrl, String& pbstrAlternateCSSUrl, String& pbstrCustomizedCssFileList, String& pbstrCustomJSUrl, String& pbstrAlternateHeaderUrl, String& pbstrMasterUrl, String& pbstrCustomMasterUrl, String& pbstrSiteLogoUrl, String& pbstrSiteLogoDescription, Object& pvarUser, Boolean& pvarIsAuditor, Int32& plSiteFlags) at Microsoft.SharePoint.SPWeb.InitWebPublic() at Microsoft.SharePoint.SPWeb.get_ServerRelativeUrl() at Microsoft.SharePoint.SPWeb.get_Url() at Microsoft.ReportingServices.SharePoint.Server.Utility.GetSPItemMetaDataAndContent(String path, UserContext userContext, Boolean returnContent, Guid& id, ISecurableObject& secObj, SharePointImpersonatedWeb& wrapper, Byte[]& content, String& mimeType) at Microsoft.ReportingServices.SharePoint.Server.Utility.GetSPItemType(String objectName, UserContext userContext, Guid& id, ISecurableObject& secObj, SharePointImpersonatedWeb& wrapper) at Microsoft.ReportingServices.SharePoint.Server.Utility.GetSPItemType(String objectName, UserContext userContext, Guid& id) at Microsoft.ReportingServices.SharePoint.Server.Utility.GetSPItemType(String objectName, UserContext userContext) at Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelper.Microsoft.ReportingServices.Diagnostics.IPathManager.IsSupportedUrl(String path, Boolean checkProtocol, Boolean& isInternal) at Microsoft.ReportingServices.Diagnostics.CatalogItemUrlBuilder.IsReportServerPathOrUrl(String pathOrUrl, Boolean checkProtocol, Boolean& isPath) at Microsoft.ReportingServices.ReportRendering.ReportUrl..ctor(RenderingContext reportContext, String initialUrl, Boolean checkProtocol, NameValueCollection unparsedParameters, Boolean useReplacementRoot) at Microsoft.ReportingServices.ReportRendering.Action.get_DrillthroughReport() at Microsoft.ReportingServices.ReportRendering.Action.get_DrillthroughID() at Microsoft.ReportingServices.Rendering.HtmlRenderer.BaseRenderer.GetActionUri(Action action) at Microsoft.ReportingServices.Rendering.HtmlRenderer.HTML4Renderer.HasMultipleActions(ActionCollection actions, Int32& actionIndex, RenderActionInfo& firstActionInfo) at Microsoft.ReportingServices.Rendering.HtmlRenderer.HTML4Renderer.RenderTextBoxPercent(TextBox textBox, Boolean renderId) at Microsoft.ReportingServices.Rendering.HtmlRenderer.HTML4Renderer.RenderReportItem(ReportItem reportItem, Int32 borderContext, Boolean renderId) at Microsoft.ReportingServices.Rendering.HtmlRenderer.HTML4Renderer.RenderRangeCellsContent(MatrixCell lastCell, Int32 cellBorderContext) at Microsoft.ReportingServices.Rendering.HtmlRenderer.BaseRenderer.RenderRangeCells(Matrix matrix, Int32 indexRow, Int32 startCell, Int32 endCell, IntList hiddenColumns, Int32 borderContext, Boolean dirLefRight) at Microsoft.ReportingServices.Rendering.HtmlRenderer.BaseRenderer.RenderNonSplitMatrixLevel(Matrix matrix, MatrixMember currMember, Boolean& newRow, Boolean partialItem, Int32 level, IntList hiddenColumns, SizeCollection cellHeights, Boolean changableRows, Int32 borderContext, Boolean dirLefRight, MatrixContext matrixContext) at Microsoft.ReportingServices.Rendering.HtmlRenderer.BaseRenderer.RenderNonSplitMatrix(Matrix matrix, MatrixMember member, Boolean& newRow, Boolean partialItem, Int32 level, IntList hiddenColumns, SizeCollection cellHeights, Boolean changableRows, Int32 borderContext, Boolean dirLefRight, MatrixContext matrixContext) at Microsoft.ReportingServices.Rendering.HtmlRenderer.BaseRenderer.RenderMatrixContent(Matrix matrix, Boolean partialItem, Int32 borderContext, Boolean dirLefRight, Boolean expandLayout, MatrixContext matrixContext) at Microsoft.ReportingServices.Rendering.HtmlRenderer.HTML4Renderer.RenderMatrix(Matrix matrix, Boolean partialItem, Int32& borderContext, Boolean renderId) at Microsoft.ReportingServices.Rendering.HtmlRenderer.HTML4Renderer.RenderReportItem(ReportItem reportItem, Int32 borderContext, Boolean renderId) at Microsoft.ReportingServices.Rendering.HtmlRenderer.BaseRenderer.RenderCellItems(ReportItemCollection repItemCol, Hashtable partialItems, Hashtable expandItems, PageTableCell currCell, Int32 borderContext, Int32 linkToChild, Boolean layoutExpand) at Microsoft.ReportingServices.Rendering.HtmlRenderer.HTML4Renderer.GenerateTableLayoutContent(PageTableLayout rgTableGrid, Hashtable partialItems, ReportItemCollection repItemCol, Boolean bfZeroRowReq, Boolean bfZeroColReq, String docMapId, Boolean inDocMap, Boolean renderHeight, Int32 borderContext, Int32 linkToChild, Boolean layoutExpand) at Microsoft.ReportingServices.Rendering.HtmlRenderer.HTML4Renderer.GenerateHTMLTable(ReportItemCollection repItemCol, Double dxParent, Double dyParent, PageData pageData, String docMapId, Boolean inDocMap, Int32 borderContext, Int32 linkToChild, Boolean expandLayout) at Microsoft.ReportingServices.Rendering.HtmlRenderer.HTML4Renderer.RenderRectangle(Rectangle rectangle, PageData pageData, Int32& borderContext, Boolean renderId) at Microsoft.ReportingServices.Rendering.HtmlRenderer.BaseRenderer.RenderPage(Int32 index) at Microsoft.ReportingServices.Rendering.HtmlRenderer.BaseRenderer.RenderPages() at Microsoft.ReportingServices.Rendering.HtmlRenderer.BaseRenderer.RenderBody(HtmlTextWriter htmlTextWriter) at Microsoft.ReportingServices.Rendering.HtmlRenderer.ViewerReportArea.Render(HtmlTextWriter outputWriter) at Microsoft.ReportingServices.Rendering.HtmlRenderer.Html40RenderingExtension.InternalRender(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions, CreateAndRegisterStream createAndRegisterStream) at Microsoft.ReportingServices.Rendering.HtmlRenderer.RenderingExtensionBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions, CreateAndRegisterStream createAndRegisterStream) --- End of inner exception stack trace --- at Microsoft.ReportingServices.Rendering.HtmlRenderer.RenderingExtensionBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo, NameValueCollection clientCapabilities, EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions, CreateAndRegisterStream createAndRegisterStream) at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension renderer, DateTime executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc, CreateReportChunk cacheDataCallback, Boolean& dataCached) --- End of inner exception stack trace --- w3wp!runningjobs!13!01/25/2007-11:14:20:: i INFO: CancelableJobExecution.Execute caught our thread abort exception w3wp!library!13!01/25/2007-11:14:20:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.JobCanceledException: An administrator has canceled the job., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.JobCanceledException: An administrator has canceled the job. ---> Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.ReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.Threading.ThreadAbortException: Thread was being aborted. --- End of inner exception stack trace --- w3wp!webserver!13!01/25/2007-11:14:20:: e ERROR: Reporting Services error Microsoft.ReportingServices.Diagnostics.Utilities.JobCanceledException: An administrator has canceled the job. ---> Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException: An error occurred during rendering of the report. ---> Microsoft.ReportingServices.ReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.Threading.ThreadAbortException: Thread was being aborted.
Works fine in Visual Studio. Once deployed to SharePoint though, the drill through returns an error that says report can't be found. So I added the .rdl to the conditional statement in the report Design.
We have been looking for a way to executing bursting of SSRS reports within SharePoint (integration mode) from a SSIS package after a successful load. We found this MSDN article which has a PowerShell script to "fire" a subscription.URL....One of the parameter needed is the SubscriptionID.
We have a Report Server integrated with SharePoint. A month ago we deployed a report (rdl file) in SharePoint, but the person who deployed it was no longer connected with us. So we decided to deactivate it in our Active Directory. Yesterday, our users returned issues regarding they are unable to access their report. I believe the issue was "object reference not set to an instance of an object".
So I tried to download the rdl file and redeployed it but i am getting error upon deploying to SharePoint. My workaround is to delete the rdl file in SharePoint, redeploy the shared datasource and shared datasets and the rdl file. It went and was now able to run the report in SharePoint.
Is there something relation/happened when deactivating the account in AD that users unable to access the report in SharePoint?
I am in the process of migrating 300+ reports and 200ish subreports to SharePoint 2013 hosted. I wanted to avoid the duplication of creating copies of all the subreports across 9 different folders.
I have a set of SSRS reports published on the server. It can be accessed through a web application or through SharePoint. Most of the reports work fine through both - web app and SharePoint. However, one of the report, which returns large amount of data has some problem:
1. It generates fine from web app 2. It generates fine from SharePoint; only if one or two values selected from Filter dropdown 3. However, if all items (about 20 items) selected from Filter dropdown... and click on View Report, it processes for a while and then shows nothing. The page remains blank.
Did some research and felt the problem is with Distributed Cache Service.
I am setting up sharepoint and sql server integration environment. I am considering the following topology: PowerPivot for SharePoint 2013 and Reporting Services in SharePoint mode Two Server Deployment
[URL]
I am looking to follow the topology example by the letter, which involves installing PowerPivot for SharePoint (aka SSAS in SharePoint mode) in the same server as my SQL, and installing SSRS in SharePoint (SP) integrated mode in the same server as SharePoint.
I understand, however, that if I wanted to install SSRS in SP mode in the same server as SQL, I could but only if the server contains the SP Object Model.
My first question is, what would involve having the SP Object Model in the SQL Server?
Would only installing SP binaries be enough; or Do I need to do a minimal install of SP in the SQL server enough for it to joing the SP farm? And most importantly, what would be the licensing implications for SP in case I want proceed down this route and have SSRS in SharePoint mode installed in the same server as the SQL?
I have created a ssrs report using ssrs-2012 that contains 2 tables 2 pie charts and 1 line chart. But I am unable to see 2 pie charts and and 1 line chart after deploying the rdl in sharepoint server.
Why I am not able to see those charts, or sharepoint server will not support charts at all.
I have published SSRS reports to sharepoint and used the Reporting Services Report viewer to present the reports on a Page. Everything works fine for the day, however in the morning, when I go to view the page, I get an error message
The report server cannot process the report. The data source connection information has been deleted. (rsInvalidDataSourceReference)