May 28, 2014 at 2:18 pm
Is it possible to set up a subscription in SSRS to write to a sharepoint directory via the URL?
For example, I have a sharepoint site and I want to write to the directory via : http://myserver/reports/myuser/pdfs/SOME_REPORT_YYYYMMDD.pdf
A consultant here told me that it was totally ok to write directly to the HTTP directory as above but I received an invalid path ("must be UNC convention" error).
I'm using SSRS 2012 (new test machine) and wanted to see if it was possible to write out files to the URL string of a SharePoint install.
May 29, 2014 at 6:27 am
You need to the the unc path for that directory... In Sharepoint switch to Windows Explorer view.
May 29, 2014 at 7:08 am
Thanks for tips. Cannot publish the reports to sharepoint quite yet as we are not ready for security on the report front. There are report templates that are run per user and each user cannot see the other's report. Once we build the security in place, we will be directly publishing reports to SharePoint but for the first phase (next few months) it will be PDF per user.
May 29, 2014 at 8:03 am
jbarry 87949 (5/29/2014)
Thanks for tips. Cannot publish the reports to sharepoint quite yet as we are not ready for security on the report front. There are report templates that are run per user and each user cannot see the other's report. Once we build the security in place, we will be directly publishing reports to SharePoint but for the first phase (next few months) it will be PDF per user.
Kerberos.....
May 29, 2014 at 11:15 am
Yep, I'm aware Kerberos for those permissions.
I'm looking to see if we can write PDF to a SharePoint via SSRS subscription (as in using a windows file share).
I cannot see the UNC structure from the SSRS server when I enter it as \\sharepoint\reports\ at all. I can on my local though.
Probably some windows server level setting vs client windows setting.
May 29, 2014 at 12:39 pm
The account SSRS uses might need to have the share mapped.
Setting up Kerberos would be preferred, then you do not have to deal with running and saving the report.
Leveraging user level security directly on the report - running under their context - is what you need.
So you only have to publish the report more or less as a template.
Less to maintain.
Kerberos also overcomes the double hop - very common using these tools across multiple servers.
Your scenario is likely tip of the iceberg.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply