From b6ae79da77419798f51e4dd4d49ddd4ac1e1a87c Mon Sep 17 00:00:00 2001 From: KB Bot Date: Wed, 2 Jul 2025 14:37:05 +0000 Subject: [PATCH 1/3] Added new kb article license-not-recognized-telerik-document-processing-libraries --- ...d-telerik-document-processing-libraries.md | 66 +++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 knowledge-base/license-not-recognized-telerik-document-processing-libraries.md diff --git a/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md b/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md new file mode 100644 index 00000000..c1d4feff --- /dev/null +++ b/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md @@ -0,0 +1,66 @@ +--- +title: Resolving License Validation Issues in Telerik Document Processing Libraries +description: Troubleshooting the issue where the license is not recognized during runtime in Telerik Document Processing Libraries. +type: troubleshooting +page_title: License Not Recognized in Telerik Document Processing Libraries +meta_title: License Not Recognized in Telerik Document Processing Libraries +slug: license-not-recognized-telerik-document-processing-libraries +tags: telerik, document, processing, license, validation, runtime, issues, licensing diagnostics +res_type: kb +ticketid: 1690929 +--- + +## Environment + +| Version | Product | Author | +| ---- | ---- | ---- | +| 2025.2.520| RadPdfProcessing |[Desislava Yordanova](https://www.telerik.com/blogs/author/desislava-yordanova)| + +## Description + +This article aims to address potential licensing issues while generating Excel files with Telerik Document Processing Libraries during runtime testing. The generated file contains a "License" tab with a trial message, despite the Build Output window indicating a valid license. The issue arises in a multi-project (e.g. Blazor WASM) application setup, where dependencies are shared across projects. + +## Cause + +This issue generally occurs due to incomplete license validation during runtime in complex setups, particularly when using shared libraries or plugin architectures. Even if the license is validated during build, runtime environments may fail to recognize it due to transitive dependency limitations. + +## Solution + +To ensure proper license validation and eliminate trial messages, follow the steps below: + +1. **License Key Placement**: Ensure the `telerik-license.txt` file is present in the root directory of all projects referencing Telerik Document Processing Libraries, including shared libraries or class libraries. + +2. **Explicit License Registration**: Add a call to `TelerikLicensing.Register()` early in your application lifecycle. For Blazor WASM applications, include this call in the `Program.cs` file. This approach validates the license explicitly. + + Example: + ```csharp + using Telerik.Licensing; + + var builder = WebAssemblyHostBuilder.CreateDefault(args); + TelerikLicensing.Register(); + builder.RootComponents.Add("#app"); + builder.Build().RunAsync(); + ``` + +3. **Verify Assemblies**: Ensure no trial versions of Telerik assemblies are referenced in any project. Replace trial assemblies with licensed versions, if necessary. + +4. **Enable Diagnostics**: Add the following property to your `.csproj` file to enable detailed licensing diagnostics during build and runtime: + ```xml + + diagnostic + + ``` + Review the diagnostic output for clues about license validation issues. + +5. **Direct Package References**: Add references to Telerik Document Processing Libraries and Telerik UI for Blazor NuGet packages directly in the Blazor WASM project. This resolves transitive dependency limitations. + +6. **Avoid Environment Variables**: Use only the `telerik-license.txt` file for license delivery instead of environment variables, which can cause issues due to length limitations. + +By following these steps, runtime validation issues should resolve, and the trial message will no longer appear in generated documents. + +## See Also + +- [Telerik Document Processing Licensing Overview](https://docs.telerik.com/devtools/document-processing/distribution-and-licensing/license-key) +- [Using TelerikLicensing.Register Method](https://docs.telerik.com/devtools/document-processing/distribution-and-licensing/license-key/adding-license-key-ci-cd-services#using-teleriklicensingregister-method-on-aws-lambdas) +- [Diagnostic Options for Telerik Licensing](https://docs.telerik.com/devtools/document-processing/knowledge-base/telerik-trial-version-message) +- [Troubleshooting Telerik Document Processing Licensing Issues](https://docs.telerik.com/devtools/document-processing/distribution-and-licensing/license-key/setting-up-license-key) From 02f3c8dde4461552981b83f6e7ef3d1b51c14b9a Mon Sep 17 00:00:00 2001 From: Desislava Yordanova Date: Wed, 2 Jul 2025 18:02:05 +0300 Subject: [PATCH 2/3] new KB for licensing - multi project application --- .../license-key/setting-up-license-key.md | 1 + ...d-telerik-document-processing-libraries.md | 26 ++++++------------- 2 files changed, 9 insertions(+), 18 deletions(-) diff --git a/distribution-and-licensing/license-key/setting-up-license-key.md b/distribution-and-licensing/license-key/setting-up-license-key.md index f38f948e..b8692af4 100644 --- a/distribution-and-licensing/license-key/setting-up-license-key.md +++ b/distribution-and-licensing/license-key/setting-up-license-key.md @@ -70,4 +70,5 @@ Whenever you purchase a new license or renew an existing one, always [download a * [Handling License Key File Name and Environment Variable Name Changes in the 2025 Q1 Release]({%slug handling-license-file-name-changes%}) * [Telerik.Licensing NuGet package is not available on the Telerik NuGet feed]({%slug dpl-telerik-licensing-nuget-feed%}) * [Diagnostic Options for Telerik Licensing]({%slug telerik-trial-version-message-diagnostic-options%}) +* [Resolving License Validation Issues in Telerik Document Processing Libraries]({%slug license-not-recognized-telerik-document-processing-libraries%}) diff --git a/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md b/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md index c1d4feff..fc36789d 100644 --- a/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md +++ b/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md @@ -18,11 +18,11 @@ ticketid: 1690929 ## Description -This article aims to address potential licensing issues while generating Excel files with Telerik Document Processing Libraries during runtime testing. The generated file contains a "License" tab with a trial message, despite the Build Output window indicating a valid license. The issue arises in a multi-project (e.g. Blazor WASM) application setup, where dependencies are shared across projects. +This article aims to address potential licensing issues while generating Excel (or PDF, DOCX, etc.) files with Telerik Document Processing Libraries during **runtime** testing. The generated file contains a "License" sheet (or a watermark) with a trial message, despite the **Build Output** window indicating a valid license. The issue arises in a multi-project (e.g. Blazor WASM) application setup, where dependencies are shared across projects. ## Cause -This issue generally occurs due to incomplete license validation during runtime in complex setups, particularly when using shared libraries or plugin architectures. Even if the license is validated during build, runtime environments may fail to recognize it due to transitive dependency limitations. +This issue generally occurs due to incomplete license validation during runtime in complex setups, particularly when using shared libraries or plugin architectures. *Even if the license is validated during build time, runtime environments may fail to recognize it due to transitive dependency limitations.* ## Solution @@ -32,17 +32,7 @@ To ensure proper license validation and eliminate trial messages, follow the ste 2. **Explicit License Registration**: Add a call to `TelerikLicensing.Register()` early in your application lifecycle. For Blazor WASM applications, include this call in the `Program.cs` file. This approach validates the license explicitly. - Example: - ```csharp - using Telerik.Licensing; - - var builder = WebAssemblyHostBuilder.CreateDefault(args); - TelerikLicensing.Register(); - builder.RootComponents.Add("#app"); - builder.Build().RunAsync(); - ``` - -3. **Verify Assemblies**: Ensure no trial versions of Telerik assemblies are referenced in any project. Replace trial assemblies with licensed versions, if necessary. +3. **Verify Assemblies**: Ensure **no trial** versions of Telerik assemblies are referenced in any project. Replace [trial assemblies]({%slug upgrade-trial-to-licensed-version%}) with licensed ones, if such even exist. 4. **Enable Diagnostics**: Add the following property to your `.csproj` file to enable detailed licensing diagnostics during build and runtime: ```xml @@ -52,7 +42,7 @@ To ensure proper license validation and eliminate trial messages, follow the ste ``` Review the diagnostic output for clues about license validation issues. -5. **Direct Package References**: Add references to Telerik Document Processing Libraries and Telerik UI for Blazor NuGet packages directly in the Blazor WASM project. This resolves transitive dependency limitations. +5. **Direct Package References**: Add references to the Telerik Document Processing Libraries NuGet packages directly in the Blazor WASM project. This resolves transitive dependency limitations. 6. **Avoid Environment Variables**: Use only the `telerik-license.txt` file for license delivery instead of environment variables, which can cause issues due to length limitations. @@ -60,7 +50,7 @@ By following these steps, runtime validation issues should resolve, and the tria ## See Also -- [Telerik Document Processing Licensing Overview](https://docs.telerik.com/devtools/document-processing/distribution-and-licensing/license-key) -- [Using TelerikLicensing.Register Method](https://docs.telerik.com/devtools/document-processing/distribution-and-licensing/license-key/adding-license-key-ci-cd-services#using-teleriklicensingregister-method-on-aws-lambdas) -- [Diagnostic Options for Telerik Licensing](https://docs.telerik.com/devtools/document-processing/knowledge-base/telerik-trial-version-message) -- [Troubleshooting Telerik Document Processing Licensing Issues](https://docs.telerik.com/devtools/document-processing/distribution-and-licensing/license-key/setting-up-license-key) +- [Telerik Document Processing Licensing Overview]({%slug introduction%}) +- [Setting Up Your Telerik Document Processing Libraries License Key]({%slug setting-up-license-key%}) +- [Using TelerikLicensing.Register Method]({%slug adding-license-key-ci-cd-services%}#using-teleriklicensingregister-method-on-aws-lambdas) +- [Diagnostic Options for Telerik Licensing]({%slug telerik-trial-version-message-diagnostic-options%}) From f7534da569745f959cefaac1e34d851ef58ae262 Mon Sep 17 00:00:00 2001 From: Desislava Yordanova Date: Mon, 7 Jul 2025 16:56:38 +0300 Subject: [PATCH 3/3] addressed Yoan's review --- .../license-key/setting-up-license-key.md | 3 +++ ...ized-telerik-document-processing-libraries.md | 16 ++++++++-------- 2 files changed, 11 insertions(+), 8 deletions(-) diff --git a/distribution-and-licensing/license-key/setting-up-license-key.md b/distribution-and-licensing/license-key/setting-up-license-key.md index b8692af4..dd8ae788 100644 --- a/distribution-and-licensing/license-key/setting-up-license-key.md +++ b/distribution-and-licensing/license-key/setting-up-license-key.md @@ -38,6 +38,9 @@ To activating the Document Processing Libraries: ```xml ``` + +>important The **Telerik.Licensing** verifies the DevSeat association at the time your classlib is built, and also provisions at runtime licenses in the Root app. When you have a setup such as **"Root app -> classlib -> Telerik UI"**, the Telerik UI will execute and verify the licensing for the classlib, but will not be applied transitively in the Root app. That's why you **need to add the Telerik.Licensing NuGet package reference to Root app manually**. + When you build the project, the _Telerik.Licensing_ NuGet package automatically locates the license file and uses it to activate the product. >important If your project doesn’t use NuGet packages, see [Adding a License Key to Projects without NuGet References](#adding-a-license-key-to-projects-without-nuget-references). diff --git a/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md b/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md index fc36789d..b1e15e3e 100644 --- a/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md +++ b/knowledge-base/license-not-recognized-telerik-document-processing-libraries.md @@ -5,7 +5,7 @@ type: troubleshooting page_title: License Not Recognized in Telerik Document Processing Libraries meta_title: License Not Recognized in Telerik Document Processing Libraries slug: license-not-recognized-telerik-document-processing-libraries -tags: telerik, document, processing, license, validation, runtime, issues, licensing diagnostics +tags: telerik, document, processing, license, validation, runtime, issues, licensing, diagnostics res_type: kb ticketid: 1690929 --- @@ -26,15 +26,17 @@ This issue generally occurs due to incomplete license validation during runtime ## Solution +The **Telerik.Licensing** verifies the DevSeat association at the time your classlib is built, and also provisions at runtime licenses in the Root app. When you have a setup such as **"Root app -> classlib -> Telerik UI"**, the Telerik UI will execute and verify the licensing for the classlib, but will not be applied transitively in the Root app. That's why you **need to add the Telerik.Licensing NuGet package reference to Root app manually**. + To ensure proper license validation and eliminate trial messages, follow the steps below: -1. **License Key Placement**: Ensure the `telerik-license.txt` file is present in the root directory of all projects referencing Telerik Document Processing Libraries, including shared libraries or class libraries. +* **Direct Package References**: Add references to the **Telerik.Licensing** package directly in the Root project. This resolves transitive dependency limitations. -2. **Explicit License Registration**: Add a call to `TelerikLicensing.Register()` early in your application lifecycle. For Blazor WASM applications, include this call in the `Program.cs` file. This approach validates the license explicitly. +* **Explicit License Registration**: Add a call to `TelerikLicensing.Register()` early in your application lifecycle. For Blazor WASM applications, include this call in the `Program.cs` file. This approach validates the license explicitly. -3. **Verify Assemblies**: Ensure **no trial** versions of Telerik assemblies are referenced in any project. Replace [trial assemblies]({%slug upgrade-trial-to-licensed-version%}) with licensed ones, if such even exist. +* **Verify Assemblies**: Ensure **no trial** versions of Telerik assemblies are referenced in any project. Replace [trial assemblies]({%slug upgrade-trial-to-licensed-version%}) with licensed ones, if such even exist. -4. **Enable Diagnostics**: Add the following property to your `.csproj` file to enable detailed licensing diagnostics during build and runtime: +* **Enable Diagnostics**: Add the following property to your `.csproj` file to enable detailed licensing diagnostics during build and runtime: ```xml diagnostic @@ -42,9 +44,7 @@ To ensure proper license validation and eliminate trial messages, follow the ste ``` Review the diagnostic output for clues about license validation issues. -5. **Direct Package References**: Add references to the Telerik Document Processing Libraries NuGet packages directly in the Blazor WASM project. This resolves transitive dependency limitations. - -6. **Avoid Environment Variables**: Use only the `telerik-license.txt` file for license delivery instead of environment variables, which can cause issues due to length limitations. +* **Avoid Environment Variables**: Use only the `telerik-license.txt` file for license delivery instead of environment variables, which can cause issues due to length limitations. By following these steps, runtime validation issues should resolve, and the trial message will no longer appear in generated documents.