Licensing issue with SectionRport

Posted by: hariharan.ramachandran on 29 December 2019, 9:24 pm EST

  • Posted 29 December 2019, 9:24 pm EST

    I recently upgraded to Active Reports 14 and I am getting the following error message when I try to run a section report.

    This application will be terminated because it was built without a license for SectionReport.

    First we are creating an object of GrapeCity.ActiveReports.Document.SectionDocument and adding GrapeCity.ActiveReports.SectionReport. Finally we are calling the Run method to Run the report.

    Run method throws the the exception "This application will be terminated because it was built without a license for SectionReport."

    I have applied the license using GrapeCity License Manager tool. I ran this utility as an Administrator. I also verified license.licx file and it has the proper version details.
  • Replied 29 December 2019, 9:37 pm EST

    Hello,

    Have you applied the license to following exe:
    C:\ProgramData\GrapeCity\gclm\gclm.exe

    Also, please add the following entry in your license.licx file
    GrapeCity.ActiveReports.SectionReport, GrapeCity.ActiveReports
    GrapeCity.ActiveReports.Viewer.Win.Viewer, GrapeCity.ActiveReports.Viewer.Win

    If the issue still exists, please share the stripped down sample with us so that we can replicate the issue at our end and helps you accordingly.

    Hope it helps.

    Thanks,
    Mohit


  • Replied 2 January 2020, 3:17 am EST

    I verified the license status using GLCM.exe and our product license is activated. I also verified license.licx file and it has SectionReport and Viewer entries.

    ActiveReports 14 is looking for license.licx in all the projects. In our case we have class library and it is consumed by another winform application. We cannot add any license file to the main winform application.

    Attached zip file has the sample project to recreate this scenario. This scenario is working fine in all the previous versions of active reports and stopped working in version 14.ActiveReports.zip
  • Replied 2 January 2020, 11:38 pm EST

    Hello,

    Thanks for the information. I am able to replicate the issue at my end. Hence, I have escalated the issue to our development team (278015)and will inform you once I get any information from them.

    Thanks,
    Mohit
  • Replied 7 June 2020, 6:44 pm EST

    Hello,

    I have created a new case on S1 for the same and replied there.
    https://supportone.componentone.com/casedetail/418345
    You can log in to the above link with the same forum credential.

    Thanks,
    Mohit
  • Replied 5 June 2020, 1:19 am EST

    Is there a status on this issue? I cannot view the support link above, and I am experiencing the exact same issue. We recently upgraded to AR 14.1, and I am still receiving this error.

    Thanks,
    David
  • Replied 7 June 2020, 6:47 pm EST

    Hello David,

    I have created a new case on S1 for the same and replied there.
    https://supportone.componentone.com/home/casedetail/439929
    You can log in to the above link with the same forum credential.

    Thanks,
    Mohit
  • Replied 10 June 2020, 10:14 am EST

    Ok - just upgrading and doing the same exact thing as David - any feedback on when this will be fixed?
  • Replied 10 June 2020, 3:18 pm EST

    Hello,

    I have replied the query on the following SupportOne case:
    http://supportone.componentone.com/casedetail/440306

    Thanks,
    Mohit
  • Replied 10 June 2020, 5:02 pm EST

    I don't have access to Case 439929 and 440306
  • Replied 10 June 2020, 6:06 pm EST

    Hello,

    You can access the following case with Forum credential:
    https://supportone.componentone.com/casedetail/418345

    If you have any questions related to this, please reply to the S1 case.

    Thanks,
    Mohit
  • Replied 15 June 2020, 12:37 am EST

    I am having the same issue and still see no cogent information here. I have a valid forum account (obviously) and cannot access ANY of the above links where there may be more information.

    Is this going to be fixed or not? If so, exactly when? We have upgraded many of our projects and are now stuck due to lack of support for Section reports.
  • Replied 15 June 2020, 7:55 pm EST

    Hi, we are having the same issue with the error "This application will be terminated because it was built without a license for SectionReport". In previous versions we used to generate a web project license with your "WebKeyGenerator.exe" but it seems this is not required in version 14?
    Our situation is that an MVC application calling a reporting web service is fine but a legacy ASP.Net application calling exactly the same web service fails with the above error. All report project references, web.config settings and licx contents are the same for the MVC and legacy ASP.Net applications.
    It would be difficult to post an example because the projects and dependencies are very large. We are hoping you can offer some more suggestions on top of your standard licensing suggestions. Or show the fixes related to this thread.
  • Replied 15 June 2020, 9:23 pm EST

    Hello Tab,

    You can access the following case with Forum credential(Only you can access this link):
    https://supportone.componentone.com/casedetail/441264

    If you have any questions related to this, please reply to the S1 case.

    Thanks,
    Mohit
  • Replied 16 June 2020, 6:19 pm EST

    Hello Hugh,

    Could you please check that FW of your legacy ASP.Net applications is equal or greater than 4.6.2 as AR14 supports only 4.6.2 or higher FW.

    Also, please open a separate case for your query. It will create confusion for us to track down the queries.

    Thanks,
    Mohit
  • Replied 16 June 2020, 7:12 pm EST

    Yes, the projects are all FW 4.6.2. After a build cleanup the MVC application is failing as well with the same error.
    I have logged a new topic here : https://www.grapecity.com/forums/activereports/licensing-issue-with-secti
  • Replied 18 June 2020, 3:46 am EST

    Is there any status on this issue? I cannot view any of the links you stated above (no permission), and I am experiencing the exact same issue.
    This application will be terminated because it was built without a license for SectionReport.
    We just upgraded to AR 14.1.
    Our project is very large and we cannot make a stripped down version.
    WE ARE DEAD IN THE WATER UNTIL THIS IS RESOLVED.
    PLEASE HELP.
  • Replied 18 June 2020, 6:44 pm EST

    Hello Rod,

    You can access the following case with Forum credential(Only you can access this link):
    https://supportone.componentone.com/home/casedetail/441798

    If you have any questions related to this, please reply to the S1 case.

    Thanks,
    Mohit
  • Replied 24 June 2020, 11:11 am EST

    Mohit, can you please generate a link for me to see the resolution on this issue. i have verified my build is at .net 4.6.2.
  • Replied 24 June 2020, 4:26 pm EST

    Hello Andrew,

    You can access the following case with Forum credential(Only you can access this link):
    https://supportone.componentone.com/home/casedetail/442478

    If you have any questions related to this, please reply to the S1 case.

    Thanks,
    Mohit
  • Replied 24 June 2020, 11:13 pm EST

    We are new to AR and evaluating ActiveReports 14, using the trial version, and receive a similar error when attempting to run .NET Core unit tests against an assembly using AR14.

    The error is: System.ComponentModel.LicenseException : This application will be terminated because it was built without a license for PageReport.

    I see a .gclicx file generated in the obj\Debug\netcoreapp3.1 folder, but there is no apparent file copied to the bin\debug\netcoreapp3.1 folder. I attempted to copy the gclicx file to bin\debug\netcoreapp3.1 and still received the same error.

    We are completely new to AR; If you could elaborate on a solution, we'd appreciate it.
  • Replied 25 June 2020, 3:05 am EST

    I really wish the results of this thread were made public, so others of us with the same issue could benefit from the potential solution(s). Everything here gets squirreled away into a support ticket that we can't globally access.
  • Replied 25 June 2020, 7:49 pm EST

    Hello,

    I know that a lot of customers are facing the same issue but we can't make it public as this step is for our customers only. I request you all, please open a new case on the following site( our private forum for the customer): if you are facing the same issue.
    https://supportone.componentone.com/

    Note: You can login to above site with the Forum Credential

    Thanks,
    Mohit
  • Replied 2 July 2020, 4:17 pm EST

    I am facing the same issue with new Active Report 14 license

    "Run method throws the the exception "This application will be terminated because it was built without a license for SectionReport.""

    For me Active reports 9 is running without any issue.

    How can I solve it?
  • Replied 2 July 2020, 9:06 pm EST

    Hello,

    I have replied to the following case:
    https://supportone.componentone.com/casedetail/444077

    Please reply to Supportone case only to avoid the confusion.

    Thanks,
    Mohit
  • Replied 2 July 2020, 9:32 pm EST

    We have the same issue with new Active Report 14 license:
    This application will be terminated because it was built without a license for SectionReport.


    Can you also help us?
  • Replied 5 July 2020, 4:40 pm EST

    Hello,

    You can access the following case with Forum credential(Only you can access this link):
    https://supportone.componentone.com/home/casedetail/444243

    If you have any questions related to this, please reply to the S1 case.

    Thanks,
    Mohit
  • Replied 19 July 2020, 11:11 pm EST

    Hello,
    We're experiencing the same issue:
    This application will be terminated because it was built without a license for SectionReport
    Could you please provide solution?
  • Replied 20 July 2020, 3:27 am EST

    Hello,

    Please to the "Why am I getting a licensing error?" topic in the following link:
    https://www.grapecity.com/blogs/new-installation-of-activereports14

    If the problem still occurs, please open a case using the following link:
    https://supportone.componentone.com/newcase

    Thanks,
    Mohit
  • Replied 20 July 2020, 4:20 am EST

    I wanted to add our experience so far.

    First, Section Reports in .Net Core are not ready for prime time. They are still apparently working on porting these to run properly in a .Net Core environment; you will have to use .Net Framework 4.8 to support them.

    We tried in vain (with support's help) to get the .gclicx thing working; never did.

    We finally found that we simply had to include a license.licx file in any project that dealt with or consumed a report. But what is included in the file is a matter of trial and error.

    We had multiple issues upgrading existing reports, with broken NuGet packages and the like, until the team handed us release 14.1.20250. That seemed to fix a lot of headaches.

    We had multiple issues upgrading NuGet packages from their stock installed versions... until we found that the release we were attempting to upgrade to had broken dependencies. They since seemed to have fixed that and we can now upgrade packages to the newer releases.

    We have repeatedly asked for release notes for the NuGet packages so we know what was fixed, etc.; to my knowledge and in communication with support, AR has no intention of releasing this information. I was advised that the flurry of NuGet package updates are for "customer specific" issues. I find this very much a shame - most if not all our other third party vendors provide release notes for each version of packages. How are we to know if we could benefit from someone else's fix?

    We found that AR adds a ton of NuGet packages to support things - as a result we have on my team gone the route of doing the following. Keep in mind that ALL of our reports are Section Reports, and therefore we're a bit of a special case here, but this has worked and we have things in production.

    For our .Net Framework projects:

    - Ensure they are at .Net 4.8
    - Create a separate class library project for reporting, .Net 4.8.
    - Place all of our reports in that project, and create functions which can be called and return memory streams.
    - Reference the class library in our primary project and simply call the functions when needed.

    For our .Net Core projects:

    - Create an entirely separate .Net 4.8 Web API project.
    - Put all our reports in the project and call using combinations of JWT (access) and passsing data using shared DTO/model classes. It returns a byte array.
    - No references required - because we can't (section reports). Also, keeps the incredible number of NuGet references from clobbering our web references.

    Was this a lot of work? Yes. A ton, and I feel like (afterwards) it was a mistake to jump on the 14.x bandwagon from 13, but I figured by 14.1 surely things must be stable. We were too far down the road to go back. That, and this is the very first release I can remember where we couldn't have AR versions live side by side.

    Good luck to all,

    --J
  • Replied 20 July 2020, 8:12 pm EST

    Hello,

    We are very sorry for all inconvenience caused to you. In AR14, we had to done lots of changes to include the .Net Core support like the following:
    1:Move AR assemblies from GAC to NuGet repository
    2:New Licensing Scheme
    3:Code refactoring

    That's why our AR customers are facing issue while upgrading from AR13 to AR14. However, all our customer reported issues related to these changes has been fixed in the latest hotfix which you can download from the following link:
    http://cdn.grapecity.com/ActiveReports/AR14/Hotfixes/ActiveReports-v14.1.20320.msi

    If you still are facing some issues with latest version, please let us know.

    Regarding the release notes of the hotfixes, we can provide it to the customer on demand for the hotfix release . You can contact us to get releases notes of any specific hotfix build.

    The support of SectionReport in .Net Core environment is in our ToDo list. This feature will be added in AR14.2 or AR15. After that, you can use the SectionReport directly in the .Net Core application without any trouble.

    >>We tried in vain (with support's help) to get the .gclicx thing working; never did.
    You can run the project by placing the "Licenses.licx" file in project where AR assemblies or library using the AR assemblies are consumed. However, this should work with the ".gclicx" as per the steps provided in the supportone case. If you can provide more details, we are willing to help you further with this issue so that we can make this work for you.

    We understand how difficult is it but we keep trying our best so that our customers can use AR with the latest technologies. And we appreciate such an honest product feedbacks which help us to enhance our product experiences.

    Thanks,
    Mohit
  • Replied 21 July 2020, 4:26 am EST

    Hello,

    Can we get the release notes for the hotfixes between what we originally installed, v14.1.19970, and v14.1.20320 please?
  • Replied 21 July 2020, 3:54 pm EST

    Hello,

    Please refer to the attached excel which includes a list of all issues which had been fixed between v14.1.19970, and v14.1.20320.

    Thanks,
    Mohit

    ReleaseNotes.zip
  • Replied 22 July 2020, 3:07 am EST

    Thank you, @Mohit - the release notes are very helpful.

    Apparently I need to write another sentence in the forum or it thinks I'm spamming.
    Ok, what if I wrote a third sentence?
  • Replied 22 July 2020, 3:33 am EST

    Hello John,

    You can write any number of sentences here. Also, I suggest to open a different ticket if you have a different issue to avoid confusion.

    Sorry if I do not understand your question.

    Thanks,
    Mohit
  • Replied 19 August 2020, 4:07 am EST

    We are having the same issue, but I cannot access any of the links above.

    We are moving up from AR 11 to AR 14. In the past, we've ran WebKeyGenerator.exe to get a string that we put in our website's web.config file similar to this...

    <add key="ActiveReports 9 License" value="bSYNGtwo...

    And while your docs for AR 14 says it I should have a WebKeyGenerator.exe, I do not have one after I install. You say I should here...

    https://www.grapecity.com/activereports/docs/v14/online/ar-installed-files.html
    https://www.grapecity.com/activereports/docs/v14/online/install-activereports.html

    How can I get my website to work? We are dead in the water as we already upgraded everything else and did not expect to have an issue when integrating Section Reports with our website.
  • Replied 19 August 2020, 8:40 pm EST

    Hi,

    Actually WebKeyGenerator.exe is intentionally removed from the AR14 installer.
    You can follow the below steps as replacement:
    1. Build the project using the licensed components on a developer machine which is licensed for development with all the components referenced in the project (this creates the .licenses resource).
    2. Find the licenses.licx in the Solution Explorer window. You can use the Show All Files toolbar button to see it or expand the Properties folder.
    3. Right-click the licenses.licx in the Solution Explorer window, and then select Exclude From Project.
    4. Use Windows Explorer (outside Visual Studio) to find the .licenses file in the obj\{configuration} folder (obj\Debug or obj\Release). The file should have the name {target}.dll.licenses (for example: project1.dll.licenses).
    5. Copy that file to the project folder and rename it to remove the target name (rename it from {target}.dll.licenses to dll.licenses). For example: project1.exe.licenses to exe.licenses.
    6. In the Visual Studio Solution Explorer window, find the dll.licenses (you might need to refresh the window), then right-click the file and select Include In Project.
    7. Change the Build Action for the dll.licenses from Content to Embedded Resource.
    8. The project can now be built without requiring a developer license on the machine, since the license has already been built and linked into the project.

    Thanks,
    Pragati
  • Replied 15 September 2020, 11:47 pm EST

    Hello Pragati,

    I followed all the mentioned steps, but after that when I run the application and try to generate the reports I get the License not found exception. Please see attached images. It worked before, with the .licx files.
  • Replied 16 September 2020, 6:56 pm EST

    Hello,

    Could you please share the application structure and how are you running your application on your machine.

    It will be helpful for us to narrow down the issue.

    Thanks,
    Mohit
  • Replied 22 September 2020, 9:27 pm EST

    Hello All,

    Please follow the steps as given in the below link to generate the license for the compiled code.
    https://www.grapecity.com/activereports/docs/v14/online/licensing-compiled-code.html
    If issue is still not resolve, please contact us on link as given in the following link:
    https://www.grapecity.com/activereports/docs/v14/online/licensing-support.html

    Thanks,
    Mohit
  • Replied 9 November 2020, 5:50 am EST

    Mohit,

    We are running into this same issue. We have a web service converted from AR7 to AR14. We have successfully converted other projects to AR14 (WinForms project and Windows Class Library), but are getting the "This application will be terminated because it was build without a license for Section Report" error when one of our web applications tries to run an Active Report in the web service. Everything is compiling fine. We have a license file with the following entries:

    GrapeCity.ActiveReports.SectionReport, GrapeCity.ActiveReports, Version=14.1.20320.0, Culture=neutral, PublicKeyToken=cc4967777c49a3ff

    GrapeCity.ActiveReports.Viewer.Win.Viewer, GrapeCity.ActiveReports.Viewer.Win, Version=14.1.20320.0, Culture=neutral, PublicKeyToken=cc4967777c49a3ff

    GrapeCity.ActiveReports.Export.Pdf.Section.PdfExport, GrapeCity.ActiveReports.Export.Pdf, Version=14.1.20320.0, Culture=neutral, PublicKeyToken=cc4967777c49a3ff

    GrapeCity.ActiveReports.PageReport, GrapeCity.ActiveReports, Version=14.1.20320.0, Culture=neutral, PublicKeyToken=cc4967777c49a3ff

    I have read through this entire thread and most of the time you have created a case with SupportOne. I have an "activated" license on my development machine so I don't understand why it's not recognizing the license.licx file. Lastly, one of your replies had talked about installing AR14 20320 which was supposed to fix the issue. I have done that, but still no resolution.

    If there are any other details that you need from me, please let me know. Thanks!

    Mark
    PDS, Inc.
  • Replied 9 November 2020, 5:57 am EST

    mroberts - we found that in our WinForms app we had to add a license file as well... our lines are


    GrapeCity.ActiveReports.SectionReport, GrapeCity.ActiveReports
    GrapeCity.ActiveReports.PageReport, GrapeCity.ActiveReports


    Never got it to work without that license file.
  • Replied 9 November 2020, 1:59 pm EST

    Hello Moberts, John,

    Actaully license scheme is changed between AR14 and AR7. Have you tried to follow the steps in the given in the following link:
    https://www.grapecity.com/activereports/docs/v14/online/licensing-compiled-code.html

    If you still facing some issue, please let me know.

    Thanks,
    Mohit


  • Replied 9 November 2020, 2:58 pm EST

    Mohit,

    This is a web service so it could be called by many other possible web applications. I went ahead and tried to create a .gclicx file using the following command according to the directions in the URL you supplied:

    gclm.exe "de456e2c-d2e3-4246-94e8-9648bbd6fbf0" -lc ./.gclicx "UX.PDSeRatingWS.dll"

    UX is the name of this particular web application that is calling the web service called PDSeRatingWS. The web service is what uses AR14 to generate a PDF report and return it to the web application. I took the .gclicx file and put it in the main directory of the web service project. When I look at the Properties, there doesn't seem to be a way to add a Build Action (which is Step 4 in the URL you sent) so I don't know how to proceed. I have attached some screen shots to for you to look at.

    Mark

  • Replied 9 November 2020, 3:03 pm EST

    Here are the screen shots in a .zip file.Screenshots.zip
  • Replied 9 November 2020, 3:12 pm EST

    Hello,

    >>When I look at the Properties, there doesn't seem to be a way to add a Build Action (which is Step 4 in the URL you sent)
    Can you please refer to the attached image and change the build action to Embedded Resource.

    >>This is a web service so it could be called by many other possible web applications
    Could you please confirm are you able to generates the .gclicx file for every web application that uses the WebService.

    Please feel to revert if you face any issue.

    Thanks,
    Mohit
  • Replied 9 November 2020, 3:25 pm EST

    Mohit,

    Do I put the .gclicx file into the web service solution or into the web application solution? Reminder: the web service is using AR14 and the web app is calling the web service. Currently, I have put the .gclicx file in the web service solution. When I put it in the web service solution, there are NO properties called Build Action so it's impossible to change as the instructions say to do. (That is why I included the 2nd screen shot in my attachment.)

    Mark
  • Replied 9 November 2020, 5:05 pm EST

    Hello Mark,

    Sorry, I missed the screenshot. I am trying to find the solution in case of WebSite. Could you please tell the can you add the licenses.licx in both WebSite and WebApplication to make it work?

    Thanks,
    Mohit
  • Replied 10 November 2020, 10:16 am EST

    Mohit,

    The web site has NO knowledge of Active Reports - it is only expecting a PDF file to be returned from the web service - so the web site project should NOT have a license file at all. And it is the web service project that is generating the error when it tries to Run() the report.

    This seems like a fairly straight forward example. Perhaps GrapeCity has some example code/project with a web service and how it is set up that I could look at.

    Is there a higher level of support? Maybe over the phone or where I could do a Zoom call with a support person. We are under a time crunch to get this figured out. I am on New York time zone and would be willing to stay up late to connect with you or another support person through phone or Zoom.

    Thanks for your help so far!!

    Mark
  • Replied 10 November 2020, 8:24 pm EST

    Hello,

    I am observing the license error at my end. I have escalated the issue to the development team (AR-25522) and will inform you once I get any information from them.

    Thanks,
    Mohit
  • Replied 11 November 2020, 1:14 am EST

    Hello,

    Can you please do the following steps:
    1) Open WebService in VS
    2) Move licenses.licx to the root with valid license entries
    3) Open the context menu of licx file in the solution explorer
    4) Click "Build Runtime Licenses"
    Observe: App_licenses.dll appears in Bin folder

    Hope it helps.

    Thanks,
    Mohit
  • Replied 12 November 2020, 3:40 pm EST

    Mohit,

    Sorry, I have had other issues come up with another project and I'm just getting back to this issue.

    I was able to create the App_Licenses.dll file. I got another error about another AR14 DLL that I needed to include. I included that, but I'm now getting an error about an AR version 3 DLL that is no longer present. AR version 3 is what we upgraded from. The error message is below. I have also included the contents of our current licenses.licx file below that. I don't know why it would be referencing the old version 3 DLL. I think we are past my original error about the SectionReport so that's good!!

    Let me know where to go from here. Thanks!

    Mark

    ===================

    Could not load file or assembly 'GrapeCity.Documents.Pdf, Version=3.1.0.519, Culture=neutral, PublicKeyToken=d55d733d2bfd5065' or one of its dependencies. The system cannot find the file specified.

    GrapeCity.ActiveReports.SectionReport, GrapeCity.ActiveReports, Version=14.1.19970.0, Culture=neutral, PublicKeyToken=cc4967777c49a3ff
    GrapeCity.ActiveReports.Viewer.Win.Viewer, GrapeCity.ActiveReports.Viewer.Win, Version=14.1.19970.0, Culture=neutral, PublicKeyToken=cc4967777c49a3ff
    GrapeCity.ActiveReports.Export.Pdf.Section.PdfExport, GrapeCity.ActiveReports.Export.Pdf, Version=14.1.19970.0, Culture=neutral, PublicKeyToken=cc4967777c49a3ff
    GrapeCity.ActiveReports.PageReport, GrapeCity.ActiveReports, Version=14.1.19970.0, Culture=neutral, PublicKeyToken=cc4967777c49a3ff
  • Replied 13 November 2020, 10:56 am EST

    Mohit,

    I added the AR14 version of the GrapeCity.Documents.Pdf.dll to my project. I also had to add GrapeCity.Documents.Common.dll. Once I did that my code is able to complete the SectionReport.Run() method that was failing before. However, it gets a few lines further and fails on the GrapeCity.ActiveReports.Export.Pdf.Section.PdfExport.Export() method. The error that is returned is "Add meta data failed". When I google for that error message, I find 1 article on your forums, but I'm not sure if it's really applicable. Can you help me with this error? Thanks.

    https://www.grapecity.com/forums/ar-dev/export-to-pdf-fails-for-so

    Mark
  • Replied 16 November 2020, 4:31 am EST

    It's been 3 business days and I haven't gotten a response from Mohit. Is anyone at Grape City able to help with my issue as stated in my last request? Please follow up with me soon if possible.

    Mark
  • Replied 16 November 2020, 5:22 pm EST

    Hello,

    We are very sorry for the delay!

    Similar issue has been observed with the old installer. However, it is fixed in the latest installer. Could you please check with the latest installer of AR. Please install the latest installer from the following link:
    http://cdn.grapecity.com/ActiveReports/AR14/Hotfixes/ActiveReports-v14.2.20665.msi


    Thanks,
    Mohit
  • Replied 17 November 2020, 6:17 am EST

    Mohit,

    I installed v14.2.20665 with the link you provided above. I copied the new .dll files to my project bin directory. I continue to get the same error - "Add meta data failed".

    Here are the lines of code - not sure if it will help. The Run() was getting the license error before. The "meta data" error is happening on the Export() line.

    rptARInvoice.Run()
    docAllInvoices.Pages.AddRange(rptARInvoice.Document.Pages)
    pdfExport.Export(docAllInvoices, memStream)


    Please let me know how to proceed. Thanks!

    Mark
  • Replied 18 November 2020, 2:28 am EST

    Hello Mark,

    I have try at my end and no issue is observed at my end. It is related to specific report. Could you please share the stripped down sample with me so that I can able to replicate the issue at my end.

    Thanks,
    Mohit
  • Replied 20 November 2020, 9:23 am EST

    Mohit,

    I think it would be too time consuming to try and create a stripped down version of our web service and then also a web application that called the webservice. I would also have to provide some data in a database that would be applicable.

    I will attach a .zip file of the 6 reports that we have in the web service. The one in particular that is causing the problem is ARInvoice.vb. Remember, these are old AR3 reports that were upgraded to AR14 using the Visual Studio 2019 menu item "Tools | Convert to ActiveReports14". My assumption is that Grape City installation adds that item to the Visual Studio 2019 menu.

    The error message "Add meta data failed" seems like a fairly straightforward error. I would think that your developers could tell us how that error gets generated. Maybe they can see something in our report files that will tell them what is causing the error. Again, we are running the 3 lines of code below - it fails on the 3rd line

    rptARInvoice.Run()
    docAllInvoices.Pages.AddRange(rptARInvoice.Document.Pages)
    pdfExport.Export(docAllInvoices, memStream)


    Remit.zip

    Thanks!

    Mark
  • Replied 23 November 2020, 6:53 pm EST

    Hello Mark,

    As I seen the report, it call the every subreport in this. And I found no issue in the report by going through code. Could you please confirm if we run the every subreport individually, then it will export correctly or not?
    Also, It is very helpful for us if you share the full stack trace and full export code(If you set any property of the PdfExport)

    This will help us to narrow down the issue at our end.

    Thanks,
    Mohit
  • Replied 24 November 2020, 6:41 am EST

    Mohit,

    I think I have figured it out. The previous exceptions/errors were saying specifically that there was a missing GrapeCity DLL. This error was "Add meta data failed", but I didn't check deeper into the exception object. When I looked at the exception object, it said it was missing GrapeCity.Documents.Imaging.dll. I have added that to our solution and am now able run the reports and export them to PDF. I need to do some more thorough testing, but it seems like all of the functions in the web service are now working correctly with AR14. If I run into anything further, I will follow up on this thread.

    Thanks for all your help getting us through converting this project to AR14.

    Mark
  • Replied 24 November 2020, 2:06 pm EST

    Hello,

    I am glad that your issue is now resolved. Please feel free to revert if you found any issue.

    Thanks,
    Mohit
  • Replied 29 September 2021, 1:52 am EST

    Hi Mohitg,

    Can you post a link for me as well, we are having this same issue? Also, can you get me a link to buying another developer license for Active Reports 14, Everything I click on takes me to a new version. I just need a license for AR 14.
Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels