Active Reports 11 with GitHub Actions

Active Reports 11 with GitHub Actions

Posted by: mohamed.elsayed on 3 February 2025, 12:15 pm EST

• 

  mohamed.elsayed

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 3 February 2025, 12:15 pm EST

  Hi There,

  I’m using Active Reports 11 with .NET Framework and I started a pipeline process on GitHub Actions with the following commands to activate, show status, and deactivate the Active Reports:

        # Step 5: Activate GrapeCity License
        - name: Activate GrapeCity License
          run: |
            C:\ProgramData\GrapeCity\gclm\gclm.exe "GrapeCity.ActiveReports.Viewer.Win.v11" -a "MY_PRODUCT_KEY"
  
        # Step 6: Check GrapeCity License Status
        - name: Check GrapeCity License Status
          run: |
            C:\ProgramData\GrapeCity\gclm\gclm.exe "GrapeCity.ActiveReports.Viewer.Win.v11" -s
        
        # Step 7: Build the solution
        - name: Build the solution
          run: |
            msbuild "$env:Solution_Name" /t:Build /p:Configuration=Release /p:Platform=x64 /clp:ErrorsOnly
          continue-on-error: false  # This ensures the build stops if it fails
  
        # Step 8: Deactivate GrapeCity License (in case of success or failure)
        - name: Deactivate GrapeCity License
          if: always()  # This ensures the license is deactivated even if the build fails or succeeds
          run: |
            C:\ProgramData\GrapeCity\gclm\gclm.exe "GrapeCity.ActiveReports.Viewer.Win.v11" -d

  However, I’m encountering the following errors:

  Step 5: error: The [index] is invalid or out of range.
  Step 6: error: The [index] is invalid or out of range.
  Step 7: System.ComponentModel.LicenseException: License cannot be confirmed. Error code: 01-001
  

  I checked the documentation and found that Active Reports 11 doesn’t support the commands used in modern Active Reports versions.

  My Questions:
  
  Did I make any mistakes in my commands?
  
  If not, is there a way to perform this process with Active Reports 11 using GitHub Actions?
  
  If not, what are the alternatives to achieve this operation?

  Thanks in advance

• 

  katyayny.raghuvanshi

  

  • Post Options:
  • Link
    Copy

  Posted 4 February 2025, 4:46 am EST

  Hi,

  You seem to be using the latest way of licensing ActiveReports on pipeline, but this method was introduced in ActiveReports 14 onwards, and it won’t work with ActiveReports 11.

  We would suggest that you refer to the attached thread for reference: https://developer.mescius.com/forums/ar-dev/how-to-build-ar-v9-on-a-azure-dev-ops

  You may also refer to the attached documentation link regarding licensing ActiveReports 11: https://help.grapecity.com/activereports/webhelp/AR11/webframe.html#arHOWLicensingActiveReports.html

  We hope this helps!

• 

  mohamed.elsayed

  • Post Options:
  • Link
    Copy

  Posted 26 February 2025, 10:51 am EST

  Hi,

  I followed the steps outlined in “To license ActiveReports when you cannot compile the calling application or the calling application is COM” from the URLs you provided. I generated the DLLs and EXE files in the format .GrapeCity.Licenses.dll, then copied and pasted them into the projects during the build process. I also excluded all the LICX files, and the build was successful. The reports work on my machine.

  However, when we run our project on clients’ machines, we encounter an error stating, “Your Trial period has expired.” I realized that it works on my machine because I have the License Manager with a valid license key activated. Once I deactivate it, the reports no longer work, which is the same issue our clients face since they don’t need to have the License Manager and activate the reports.

  Can you please guide me on how to solve this problem? Alternatively, if there is any other way to make ActiveReports work after a successful build without any issues, I would greatly appreciate it.

  Thanks

• 

  katyayny.raghuvanshi

  

  • Post Options:
  • Link
    Copy

  Posted 26 February 2025, 11:11 pm EST

  Hi,

  We would request that you create a case on the support portal here: https://developer.mescius.com/my-account/my-support

  You may add the detailed steps to replicate the issue over there and maybe provide us with a sample application replicating the issue so that we can investigate further.