ASPOSE Connectivity issue

Aspose.Total Product Family
,
1

Hi Team,

We are using APOSE Valid Metered license key(ASPOSE TOTAL for .NET), we have notice that when we have made the call to ASPOSE server from our API we have go the below message and looks like this is due to connectivity issues with APOSE license servers.

Error Message on documents
“Created with an evaluation copy of Aspose.Words. To remove all limitations, you can use Free Temporary License”

and we have not got the popper` document response from ASPOSE

We have restarted our API service, and this has resolved this issue but again after some time (1 hour) the same issue has recurred .

Please provide us the Root cause and permeant solution for such issues .

2

@swapnil.chiddarwar

Summary
Your API loads a metered Aspose.Total for .NET license at runtime. The metered license requires periodic validation against the Aspose licensing service. When the validation request cannot be completed, the SDK switches to evaluation mode and the generated documents show the “Created with an evaluation copy …” watermark. Restarting the API reloads the license, so the watermark disappears until the next failed validation attempt.

Why it happens

  1. Metered‑license validation – A metered key is not a static file; the SDK contacts the Aspose licensing endpoint (e.g., `) roughly every 30–60 minutes to confirm that the key is still valid.
  2. Outbound connectivity problem – The validation request fails because the process cannot reach the Aspose server. Common causes are:
  • Firewall or network‑security‑group rules that block outbound HTTPS (port 443).
  • A corporate proxy that is not used by the .NET process or whose credentials expire.
  • A transient outage of the Aspose licensing service (rare).
  1. When validation fails, the SDK automatically falls back to evaluation mode, which adds the watermark to all subsequently generated files.

What to do next

  1. Confirm outbound connectivity
  • From the host that runs the API, run a simple request, e.g.:
curl -I
  • If the request times out or is blocked, adjust firewall/NSG rules to allow outbound TCP 443 to *.aspose.com.
  1. Configure proxy settings (if a proxy is required)
  • The Aspose SDK does not automatically pick up system proxy credentials. Set the default proxy before loading the license:
.NET Core / .NET 5+
var proxy = new WebProxy(")
{
Credentials = new NetworkCredential("proxyUser", "proxyPwd")
};
WebRequest.DefaultWebProxy = proxy;

Load the metered license
var license = new Aspose.Words.License();
license.SetLicense("Aspose.Words.metered.xml");
  1. Enable Aspose diagnostic logging (optional)
  • If the library version you use provides a logging API, enable debug logging to capture the exact exception that occurs during validation. For example:
Aspose.Words.Logging.LoggerFactory.SetLoggerFactory(
new Aspose.Words.Logging.ConsoleLoggerFactory(Aspose.Words.Logging.LogLevel.Debug));
  • Review the console output when the watermark appears; look for network‑related errors such as WebExceptionStatus.Timeout or NameResolutionFailure.
  1. Test with a permanent (non‑metered) license
  • Obtain a regular (non‑metered) license file from your Aspose account.
  • Replace the metered‑license call with:
var license = new Aspose.Words.License();
license.SetLicense("Aspose.Words.lic"); permanent license file
  • If the watermark no longer appears, the issue is confirmed to be the periodic validation of the metered key.
  1. Add simple retry logic around license loading (optional)
  • Network glitches can be mitigated by retrying the SetLicense call a few times:
const int maxAttempts = 3;
for (int i = 0; i < maxAttempts; i++)
{
try
{
var lic = new Aspose.Words.License();
lic.SetLicense("Aspose.Words.metered.xml");
break; success
}
catch (Exception) when (i < maxAttempts - 1)
{
Thread.Sleep(TimeSpan.FromSeconds(5));
}
}
  1. Escalate internally if the problem persists
  • Gather the following information for the team that manages licensing/network configuration:
  • Full stack trace or Aspose debug log captured at the moment the watermark appears.
  • Exact Aspose component versions (e.g., Aspose.Words 24.x, Aspose.PDF 24.x).
  • Details of the network environment (firewall rules, proxy configuration, outbound IP ranges).
  • Provide this data to the responsible internal group so they can investigate connectivity or licensing‑service issues.

By ensuring reliable outbound HTTPS access to the Aspose licensing endpoint (or by switching to a permanent license), the SDK will remain in licensed mode and the evaluation watermark should no longer be added to your documents.

3

@swapnil.chiddarwar,

Do you encounter the issue when using your Aspose.Total metered license with the Aspose.Words for .NET API, or does this issue occur with other APIs as well (if so, which ones)? If needed, we may request your metered license keys, but this should be done via a private message.