diff --git a/knowledge-base/images/TelerikLicenseFile.png b/knowledge-base/images/TelerikLicenseFile.png
new file mode 100644
index 000000000..fdc386e46
Binary files /dev/null and b/knowledge-base/images/TelerikLicenseFile.png differ
diff --git a/knowledge-base/resolving-invalid-license-watermark-telerik-reporting-pdfs.md b/knowledge-base/resolving-invalid-license-watermark-telerik-reporting-pdfs.md
new file mode 100644
index 000000000..b9979e011
--- /dev/null
+++ b/knowledge-base/resolving-invalid-license-watermark-telerik-reporting-pdfs.md
@@ -0,0 +1,59 @@
+---
+title: Resolving Invalid License Watermark When Using Telerik Reporting in Website Projects
+description: Learn how to resolve the invalid license watermark issue when using Telerik Reporting in Website projects, even after following licensing steps such as downloading the license key, using NuGet packages, and VB/CS script files.
+type: how-to
+page_title: Fixing Invalid License Watermark in Telerik Reporting Output
+meta_title: Fixing Invalid License Watermark in Telerik Reporting Output
+slug: resolving-invalid-license-watermark-telerik-reporting
+tags: licensing, reporting, license-key, watermark, telerik-reporting
+res_type: kb
+ticketid: 1704846
+---
+
+
+## Environment
+
+
+
+
+ | Product |
+
+ Licensing/Reporting
+ |
+
+
+ | Version |
+
+ 19.3.25.1111
+ |
+
+
+
+
+## Description
+
+I have an older ASP.NET Website project that uses Telerik Reporting to generate reports. Despite following all licensing documentation downloading the license key, using NuGet packages, and VB script files—the reports display an invalid license watermark. Other Telerik controls, such as grids, work without issues. Re-running the Reporting Upgrade Wizard completes without errors, and all files in the bin directory are updated to the latest versions.
+
+## Solution
+
+To resolve the invalid license watermark issue:
+
+1. Ensure the Telerik Reporting license is correctly embedded in the backend/server project during build time. Refer to the [Adding a License Key to Projects without NuGet References]({%slug license-key%}) section.
+
+1. Add a `TelerikLicense.vb`/`TelerikLicense.cs` file to your project. For Website projects, place the `TelerikLicense.vb`/`TelerikLicense.cs` file in the `App_Code` folder.
+
+ 
+
+ > The image shows where the TelerikLicense file (TelerikLicense.vb or TelerikLicense.cs) is located in the Website project
+
+1. Use the `EvidenceAttribute` for each Telerik product requiring licensing. Add the Reporting script key downloaded from your [Telerik account's License Keys page](https://www.telerik.com/account/your-licenses/license-keys).
+
+1. Verify that the script key includes all purchased Telerik licenses. This solution relies on using the script key instead of the license key. Use the Telerik.Licensing NuGet package and provide the script key either through an environmental variable or the `telerik-license.txt` file.
+
+1. Rebuild the project and test generating a report to confirm the license watermark is removed.
+
+## See Also
+
+* [Fixing License Errors in Telerik Reporting Runtime]({%slug resolving-invalid-license-telerik-reporting%})
+* [Adding a License Key to Projects without NuGet References]({%slug license-key%})
+* [Telerik Reporting Overview]({%slug telerikreporting/welcome-to-telerik-reporting!%})