Hot answers tagged

8

One of the great things about SharePoint is the ease with which you can create a list, and immediately have an online form people can use to enter data. Of course, once you have data in your SharePoint list, you’re inevitably going to want to implement some type of reporting against it. What’s the point of collecting all of this data if we can’t gain insight ...


5

Cross-Page connections are only supported by a few old webparts as it became obsolete after SharePoint 2003. In order to support Cross-Page connection the web part need to: derive from the Microsoft.SharePoint.WebPartPages.WebPart instead of System.Web.UI.WebControls.WebParts.WebPart (the recommended approach since WSS2.0/MOSS2007) declare the interface ...


4

Going stand alone will only (negatively) impact the security accounts used and the use of SQL Server Express 2008 R2 instead of your own SQL Server 2012 (and of course will prevent any growth later on) Both installations will run the Farm Configuration wizard which will configure most of the service (and you should do it manually to have better control once ...


4

In the Expressions dialog box of your report builder you can use the global variable UserId. Alternative, create a custom webpart which renders an Iframe (URL = reportviewerpage). Pass the current user data as a querystring. Use the querystring value (report parameter) in your report query.


4

SSRS, to be used in SharePoint Integrated Mode, must be installed on a server that has SharePoint installed and joined to the farm. Obviously this would not be a good idea to install SharePoint on a Database Engine server if you can avoid it. Install SSRS on your SharePoint server in Integrated mode. Yes, you must license SQL Server (SSRS) on your ...


3

Open the report folder in Windows Explorer view....:-)


3

I believe I figured this out. I had to go to the list of Data Connections that are being used by the reports, clicking on each data connection, clicking Test Connection (which rewires the connection and clears any cache related to that report) then clicking Okay. This solved my problem.


3

You can define the parameters normally in report builder but when you pass the parameters from query string you need to append it with rp: http://sitename.com/_layouts/ReportServer/RSViewerPage.aspx?rv:RelativeReportUrl=/Reports/MyReport.rdl&rv:ParamMode=Hidden&rp:city=Perth where Relative report url is the url to your .rdl file (Report file) ...


3

You need to install Reporting Services Shared Addin in the SERVER 2 [your second WFE]. Kindly refer to the scale out architecture mentioned in technet. http://technet.microsoft.com/en-us/library/hh479775.aspx The presentation layer of SSRS reports on SharePoint Integrated mode depends on this component which adds specific capabilities on Web Servers to ...


3

Ended up solving this myself using Powershell instead of C# (using mock-variables in this snippet). The Powershell script must be executed from the SharePoint server and under administrator privileges (both windows & SharePoint I believe). Edit: Also note that my SiteCollection is the root web for the web application #Powershell Clear-Host # Add ...


3

The RSViewerPage.aspx is a Out the boxed application page in the _Layouts folder. Application pages, which are also known as "_layouts" pages, are stored in a site's Microsoft Internet Information Services (IIS) virtual directory and support application implementations. Application pages are shared across all sites on the server, whereas a site ...


3

Use the Globals!ReportServerUrl variable from within Report Builder: If you just want the base URL of the site, then remove the _vti_bin bit by using an expression: =Replace(Globals!ReportServerUrl,"/_vti_bin/ReportServer","")


3

You're correct in that it needs access to the object model when running in Integrated Mode. In Native Mode the reports run in SSRS/SQL and not SharePoint directly. The report viewer for a native mode report is just an iframe, essentially. In integrated mode the reports are stored within SharePoint, so SSRS needs to be able to communicate with SharePoint to ...


3

Formula will be something like this: =IF(OR([Column3]="5", [Column3]="6"), [director approval date]-[finance approval date], "-") Here is the reference Example of common formulas


2

You should always make sure that your source and destination farms have the same configuration. To resolve your issue you'll need to reconfigure your reportserver wsp. To do that you can use the existing wsp and deploy it in 14,15 compatibility mode. Install-SPSolution -Identity contoso_solution.wsp -GACDeployment -CompatibilityLevel {14,15}


2

Unfortunately, there's not a way to do this OOTB in SharePoint. However, Adnan Amin created a PowerShell script that will list all users with their permissions for all sites, lists, items and export it as a CSV so you can view it with Excel, etc. Download the script at: https://gallery.technet.microsoft.com/SharePoint-Access-Report-ac5e8235


2

When using SharePoint integration, you can host Reports and other SSRS files in SharePoint document library, including but not limited to defining permissions for individual reports using SharePoint permission model (users, groups, permission levels). When using Report Viewer web part, you can configure lots of details regarding the displayed report using ...


2

Please create a Shared Datasource instead of "Datasource". I'll suggest you to read this step by step article, it helped me with my first report. J


2

This was a result of the Report Server Addin somehow being removed from the server. A re-install of this add-in resolved the issues.


2

PirateEric's comment is correct. Though, it's not that SSRS respects item level permissions, as SSRS is just making calls like any other app. So it's entirely the responsibility of SharePoint to implement permissions. If SSRS makes the call as a user with access to everything, then the report will have everything. If SSRS makes the call as the current user, ...


2

I would assume that the session management service is actually disabled/not provisioned as the message suggest. If that is the case, you can enable/reate it by using the PowerShell command Enable-SPSessionStateService -Defaultprovision This will provision a new service with the default configuration. If you need to change some of the parameter, please ...


2

Go to SharePoint Central Administration >> System Settings >> Manage Services on server, and check if SQL reporting services is there or not


2

I'm pretty sure this wont work. While reporting services is claims aware, you still need Claims to Windows Token Service (C2TWS) to access the data source - even if it's all local. You can't use local accounts with C2TWS because it will do a query to resolve the UPN to match to a claim.


2

Use Report View webpart, Add the Report Viewer Web Part to a Web Page (Reporting Services in SharePoint Integrated Mode) You can set webpart's property Show refresh button to true, so when a user clicks on refresh button it will update report.


2

We were able to get the RS component to successfully install by extracting the RSSharePoint.msi package from the SQL 2012 SP1 redistributable and using msiexec manually to install the package on each of the servers. The SSRS instance was unchanged, and once we had the SP1 SSRS SharePoint component installed on each of the WFEs, it worked fine - I'm assuming ...


2

It doesnt matter. However you must install the reporting services addon for SharePoint on the WFE (Front-End Server) if you want to use the "SharePoint integrated mode". You can find more infos here


2

See the post history for my previous version of this answer, it's actually wrong. SSRS 2012 as a service application is the equivalent of the Add-In in 2010. You can probably install and license in exactly the same way as before, but you install the SErvice Application where you previously installed the Add-In.


2

SSRS works fine in SharePoint Integrated Mode on WSS3, but you'll need to remember to install the Reporting Services Add In for the appropriate version of SQL Server you have installed.


2

The 504 Gateway Timeout error is usually a network error between servers on the network or an issue with an actual server. This may also mean that the report server is down or not working properly. If you have manually configured the proxy , verify that Bypass proxy servers for local addresses is set to true. <system.net> <defaultProxy> ...


2

Finally found the actual cause after I closely followed this link: http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/daa59eec-b651-42dd-9f6c-42aaa3fa4523 Looks like the original account that was used to create the *.rdl files and the data connection library was removed from SharePoint. The resolution is download the rdl files and ...



Only top voted, non community-wiki answers of a minimum length are eligible