WinViewer - License cannot be confirmed. Error code: 01-002

WinViewer - License cannot be confirmed. Error code: 01-002

Posted by: license on 6 June 2019, 5:21 am EST

• 

  license

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 6 June 2019, 5:21 am EST

  Hi

  One of our buildservers has started failing builds with the error below within the last few days. The others still works fine.

  C:\bamboo_agent_home\xml-data\build-dir\SER-RDM-JOB1\ProjectFolder\Properties\licenses.licx(2): error LC0004: Exception occurred creating type 'GrapeCity.ActiveReports.Viewer.Win.Viewer, GrapeCity.ActiveReports.Viewer.Win.v11, Version=11.0.8705.0, Culture=neutral, PublicKeyToken=cc4967777c49a3ff' System.ComponentModel.LicenseException: License cannot be confirmed. Error code: 01-002
  

  The error only occurs when the buildserver builds unattended as a service.

  When logging into the server with same user as the build agent runs as, I am able to build our solution both from Commandline (using deven.com /rebuild) and by opening Visual Studio and rebuilding there.

  When opening the GrapeCity License Manager our license is shown correctly as “Professional License”.

  I have been looking around the forums, but cant seem to find a solution or suggestion on what to do to fix/debug the problem.

  Can you please help us out here, so we can get this working again.

  Best regards
  
  /Anders

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 6 June 2019, 12:36 pm EST

  Hello Anders,

  Could you please try with the following steps:
  
  1: Remove the licenses.licx from your project.
  
  2. Build your project on VSO
  
  3. Use the ApplicationLicenseGenerator on Licensed machine to generate a license.dll for your project executable from step 2. Please refer to the “To license ActiveReports when you cannot compile the calling application or the calling application is COM” topic in the following link
  
  https://help.grapecity.com/activereports/webhelp/AR13/webframe.html#arHOWLicensingActiveReports.html
  
  4. Add this .dll to the project references(CopyLocal=true)

  Thanks.

• 

  license

  • Post Options:
  • Link
    Copy

  Posted 11 June 2019, 2:58 am EST

  Hi Mohitg

  I’m afraid we are misunderstanding each other here.

  The solution I am building is a multi-project C# solution, which is built using Visual Studio on our buildservers, and using license.licx to setup which components needs licensing.

  This has worked like a charm for several years. And it works on all our developer machines, and on our 3 other buildservers.

  It is just this one particular buildserver that seems to fail on not being able to license Active Reports .

  We have tried reinstalling Active Reports on the failing buildserver - but with no result.

  My colleague think there might be some correlation between having an active User session on the buildserver while it is building and not. Can that be right?

  The failing buildserver is a Windows 2016 - the working ones are currently Windows 10 machines.

  We are fully able to build the solution manually on the buildserver, and when having an active user session the build agents (which run as a Windows service logged on as the same specific windows user) also manages to build the solution.

  But it seems that if we don’t have the active user session, the build agents fails to build.

  It seems like a larger operation if we need to re-configure our build chain to import a new assembly and change our CI-pipeline with builds, tests, obfuscation, etc in master and development branches.

  I would like you to reassure me that the only valid option to keep using Active Reports is that we change how we build and package our solution - as this will be a process that will take me multiple days to complete, test and verify that our end product still works as intended - and all build-pipelines are correct. We have multiple products depending on the same base assemblies that use Active Reports features.

  Can you point me to some knowledge base articles, release notes etc that confirms this breaking change - and that it’s not just a configuration problem with the one buildserver?

  Best regards
  
  /Anders

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 12 June 2019, 5:25 am EST

  Hello,

  I have created a case 384375 on SupportOne(https://supportone.componentone.com). You can login to SupportOne with Forum credential.

  Please reply on S1 thread for further conversation.

  Thanks.