Watermark when exporting a pdf via a report subscription to Windows File Share

I run reports created in SSRS out of Microsoft Reporting Services. When I run the reports in IE and export them to pdf via aspose pdf they export correctly and formatted as I would expect. When I set up a report subscription and select the Windows file share option, which would generate a copy of the report and place it in a folder on the server, they do not format correctly and I receive the watermark as if this was an invalid or expired license. “Evaluation Only. Created with Aspose.Pdf for Reporting Services. Copyright 2002-2015 Aspose Pty Ltd.”


I’ve done my best to follow the installation instructions and have added the .dll file to almost every folder on the server as instructed here

License|Aspose.PDF for Reporting Services

and here

Install to Visual Studio Report Designer|Aspose.PDF for Reporting Services

as well as other folders indicated in other aspose sites. what am I doing wrong?

Hi Pia,


Thanks for your inquriy. We are looking into you query and will update you soon.

Best Regards,

ParagonOutcomes:
I run reports created in SSRS out of Microsoft Reporting Services. When I run the reports in IE and export them to pdf via aspose pdf they export correctly and formatted as I would expect.
Hi Pia,

From above stated description, it appears that when using SSRS to generate PDF from .RDL, the output is properly generated without any watermark.

ParagonOutcomes:
When I set up a report subscription and select the Windows file share option, which would generate a copy of the report and place it in a folder on the server, they do not format correctly and I receive the watermark as if this was an invalid or expired license. "Evaluation Only. Created with Aspose.Pdf for Reporting Services. Copyright 2002-2015 Aspose Pty Ltd."
From above description, can you please share some details on how you are creating copy of .RDL file and then exporting it to PDF format using Windows File Share. Are you using some solution to call a service for this purpose or some other approach. Please share the details and if possible, some sample solution (if you are using any) along with input .RDL file, so that we can test the scenario in our environment. We are sorry for this inconvenience.

I am creating the report (rdl) in Visual Studio 2010. We then deploy the report to Microsoft SQL Server Reporting Services. Once the reports are deployed they are accessible through our application, which is a web app. When run in our application SSRS allows a user to export the file to xls, doc, pdf and now with Aspose they can be exported to Pdf via Aspose Pdf. This all works fine. In SSRS there are also report subscriptions…

https://msdn.microsoft.com/en-us/library/ms156307(v=sql.110).aspx

…when a subscription is created the user has the option to email the file to an email address or to forward the file to a shared folder on the server, this is called Windows File Share. While creating a subscription either via email or via file share the user has the same options of delivering those files as xls, doc, pdf, html, and Aspose Pdf.

It is the file share option that no longer works since we purchased a new license. The files when exported are not justifying the text and the watermark as indicated in my original message is appearing on the exported Pdf via Aspose Pdf option.

I cannot send you the rdl file due to confidentiality agreements with our client. However, I would be more than happy to hop on a call with someone and/or have a web meeting to avoid the back and forth related to these kinds of chats.

Thank you, Brian (not Pia).

Please be advised that we think we are all set with this issue now. Today the reports exported to file share no longer have the watermark and they are formatting correctly. Not sure what fixed it but last week I did add the license file and the dll file to just about every folder suggested in your various instructions. At the time when I added those files nothing changed but maybe it just took some time to update on the server. ?? thank you, Brian

Hi Brian,


Thanks for sharing the details.

We are glad to hear that your problem is resolved. As per your above description, it appears that service was not able to load license file in earlier attempts and therefore evaluation watermark was being displayed in resultant files. But now it appears to load the license file properly. Please continue using our API and in the event of any further query, please feel free to contact.