Sorry I used the filename without the dot i.e. “Aspose.PDF.ReportingServices.lic” (the latest filename name appears with the dot because i have tried to match the DLL name but this is also not working).
Regarding your suggestion to try the other locations, are you referring to the following ? If yes, this is not possible, these folder don’t exist
The default instance directory for Microsoft SQL Server 2016 is MSRS13.MSSQLSERVER. For the Microsoft SQL Server 2017 and later the default instance path is C:\Program Files\Microsoft SQL Server\SSRS. For the Power BI Report Server the default instance path is C:\Program Files\Microsoft Power BI Report Server\PBIRS.
@hengert
I looked in the source files for the documentation (which have the most up-to-date information) - there the phrase about license file names looks like this. Lic.png (4.7 KB)
The development team gave the following explanation:
“The supported license file names are: ‘Aspose.Pdf.ReportingServices.lic’, ‘Aspose.Pdf.Reporting.Services.lic’, ‘Aspose.Pdf Product Family.lic’, ‘Aspose.Pdf.Product.Family.lic’, ‘Aspose.Total.ReportingServices.lic’, ‘Aspose.Total.Reporting.Services.lic’, ‘Aspose.Total Product Family.lic’, or ‘Aspose.Total.Product.Family.lic’. If the license file has any other name, please save it under one of the supported names.”
This is from the current documentation that comes with the extension. The case of the names, the periods - everything is important.
The product searches for a license file with a specific name, located in a specific folder relative to the library. If the license is in the right folder, but the name does not match, or if the file name is correct, but the path is wrong - the license will not be found.
Can you attach a screenshot showing the name of the license file and the paths to the library and the license file?
Like I said earlier, this is not the first Aspose tool we are buying for Reporting Services, and it is always a nightmare to make the licence work. And I have browse all the possible logs in ReportServer and can’t find any error with regards to Aspose.
@hengert
Try placing several license files under different names and restarting the service/server.
If this does not help, send the license (as described here ) so that we can study and try to reproduce the problem.
@hengert
Please tell me what version of the product you are using?
Do you know if they are using the most recent version of the product? The reason I ask is the license files only work with the newest version of the product. We can create a SHA1 license file that will work with older version if that is needed. Please let us know how you would like to proceed.
I have sent in a zipped file the 2 licences received.
The first I have received was the licence for Aspose PDF for reporting services that also never worked and then I tried with the product family which worked.
@hengert
The problem was reproduced with the license you attached.
The license file was provided exactly as it was issued by the sales department.
There is no point in trying the old version of the license - temporary licenses that worked are in the latest format.
I created a task for the development team with high priority and they will begin work on it, if not today, then definitely on Monday.
Unfortunately, I cannot predict how long the fix will take and provide you an ETA. I will try toinform you about the work on the task.
I wrote about the problem to the sales department, with a suggestion that maybe a temporary license should be issued. But I don’t know what their policies are.
@hengert
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): PDFRS-33606
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
I would rather prefer to get the final licence rather than a temporary license that would need to be replaced at some point and having the risk of ending in the same situation again.
Can you also please let me know if you have tried the 2 temporary licence i have provided (aspose pdf for reporting services and the aspose pdf product family) ?
If yes, did it work only for the product family licence like it was for me ?
If not, can you try it to see if this is related to the aspose pdf for reporting services ?
I agree that it is inconvenient, but I cannot be sure that the problem will be solved quickly. If you have the opportunity, you can wait for the fix, it may not take long. But in case you need the full result in the meantime, have a temporary license.
I just looked at the format of the licenses that worked in full mode. I attached both temporary licenses to the issue and indicated that it only worked with one of them. So the development team has this information and maybe they will do these checks. Lic_3.png (49.3 KB)
I got contacted by your sales department and they have delivered a temporary license for Aspose PDF for Reporting Services and like I thought this is not working.
I asked him to provide me with a temporary Product family license and as expected it worked.
I assume you guys have a problem with the “for Reporting Services” license.
Would that work for you to provide us with a Product Family license ?