We are using Aspose Cells and Aspose Words in our product. In particular version of our product, For Aspose Cells, We are getting below error even if We have valid Aspose cells license.
“You are using an evaluation copy and have opened files exceeding limitation.”
We are not seeing this issue in other version of our products. Code is also same for license set. And Same license is being used in all the versions
The error message you are encountering, “You are using an evaluation copy and have opened files exceeding limitation,” typically indicates that the license is not being recognized properly in the specific version of your product. This can happen for several reasons, even if the same license works in other versions.
Solution
Check License Initialization: Ensure that the license is being initialized correctly in the version where the error occurs. The license should be set before any Aspose.Cells functionality is called.
License File Path: Verify that the path to the license file is correct and accessible in the version of your product that is experiencing the issue.
Version Compatibility: Confirm that the version of Aspose.Cells you are using is compatible with the license. Sometimes, newer versions may require an updated license.
Reapply License: If possible, try reapplying the license in the problematic version to see if that resolves the issue.
Check for Multiple Instances: Ensure that there are no multiple instances of Aspose.Cells being initialized in your application, which could lead to conflicts.
Code
Here’s a sample code snippet for initializing the license:
// Create an instance of the license class
Aspose.Cells.License license = new Aspose.Cells.License();
try
{
// Load the license file
license.SetLicense("Aspose.Cells.lic");
}
catch (Exception ex)
{
Console.WriteLine("License initialization failed: " + ex.Message);
}
Next Steps
Review the license initialization code in the affected version.
Check the license file path and permissions.
Test with a different version of Aspose.Cells if possible.
If the issue persists, consider reaching out to Aspose support with detailed information about the versions and any relevant logs.
Please implement these steps and let me know if you need further assistance!
I suspect the licensing code (in your app) is not processed at all, so you should debug on the module of licensing code in your project (e.g., place break points on the lines of code) if the lines are processing or not. For your information, the licensing code should be processed first and evaluated at least one time in the whole application life cycle. Furthermore, if your license was not valid or already expired but your licensing code was processed, then you will get a warning message/exception to denote that your license was invalid or expired to use the Aspose.Cells version.
As I said earlier, Licensing code / code base is same in our all version of application. I don’t think this can be issue of any code.
There is one thing which is different in our version is aspose version is being used. License is recently renewed and Currently license working fine for 24.5 whereas 21.2 version where currently issue is there.
So, you are using new license with older Aspose libraries versions (e.g., 21.2). You should use newer version of the API with newer license and use your older license to work with older APIs versions. Alternatively, you may request SHA1 encoded license (copy) from Aspose.Purchase section or sales category for free. Then your scenario/case will work, i.e., use new license with older versions of the APIs. Please note, newer licenses are signed with SHA256 but older ones were signed with SHA1. You cannot use a SHA256 license with older versions of the APIs (which is older than 2/3 years or so). You may use your older license to work with older Aspose versions and use new license to work with newer Aspose versions. This scenario will always work.
No, you just need to post a query/request in Aspose.Purchase forum and ask them to provide SHA1 encoded license. They may provide you new (copy) license file which can be used with both new and older versions.