We are holding the Aspose total license and we are using cells to do excel operations.
We are getting a below exception while we run unit tests on our code.
I’m not able to reproduce the issue in the sample but I’m attaching a sample that has and shows license is valid and sample able to open 500 workbooks and do a save on top of it without any issue.
Now, the below exception happens for us only on the server when we try to run the unit tests for the same workbook.
Need support on below points
If you run the sample app, you will get to know that we do hold a valid license for aspose total and able to perform 500+ excel operation smoothly, but that was not the case with the server. Is there a license issue here?
How come it fails only on the server? Does Aspose have/hold any sort of restrictions based on the machine name? - Would like to know how the licensing works in aspose if there is a restriction at the machine level.
What are your opinions on this issue?
Is there is any trace level debug which we can enable on Aspose and find out more information where exactly the issue is happening?
com.aspose.cells.CellsException: You are using an evaluation copy and have opened files exceeding limitation. 12:36:15 at com.aspose.cells.zuy.a(Unknown Source) ~[aspose-cells-18.9.jar:18.9.0] 12:36:15 at com.aspose.cells.zann.p(Unknown Source) ~[aspose-cells-18.9.jar:18.9.0] 12:36:15 at com.aspose.cells.zann.a(Unknown Source) ~[aspose-cells-18.9.jar:18.9.0] 12:36:15 at com.aspose.cells.zcly.d(Unknown Source) ~[aspose-cells-18.9.jar:18.9.0] 12:36:15 at com.aspose.cells.zd.a(Unknown Source) ~[aspose-cells-18.9.jar:18.9.0] 12:36:15 at com.aspose.cells.zanm.a(Unknown Source) ~[aspose-cells-18.9.jar:18.9.0] 12:36:15 at com.aspose.cells.Workbook.a(Unknown Source) ~[aspose-cells-18.9.jar:18.9.0] 12:36:15 at com.aspose.cells.Workbook.a(Unknown Source) ~[aspose-cells-18.9.jar:18.9.0] 12:36:15 at com.aspose.cells.Workbook.(Unknown Source) ~[aspose-cells-18.9.jar:18.9.0]
@lkak,
I have checked your sample project and it works fine as expected by detecting the valid license and performing the tasks without any evaluation warning.
Obviously there is some mismatch such that either product version is greater than the allowed version for the deployed license or simply license is not accessible somehow on the server.
There is no restriction by Aspose based in machine architecture.
Well, you may test some other product for the testing purpose to see if it works with the license or not? Similarly, display the product version to verify that the appropriate jar file is used in the project. If possible try to load the license from a file on the server and then test the scenario. Apparently License is not loaded properly on the server or different product version is used on the server. You may perform tests with some other products and share the feedback.
@ahsaniqbalsidiqui: Yep you’re right. It is license issue. We deploy in windows machine, but we build/run unit tests in linux machine and the issue was in the file path created a invalid license in linux machine.
And now, which is working fine in both windows & Linux machine. String ASPOSE_LICENSE_FILE_PATH = "aspose/license/Aspose.Total.Java.lic";
Thanks @ahsaniqbalsidiquib for your suggestion. And need clarity on a license, the mail id in license is no more with our organisation. If I change the email in license, it is changing to evaluation copy.
Where can I check how long the license is valid? like expiry date? communication mail in license is not with us. Any help here?
Yes, you should not change anything (including mail id) in the license. If you change/edit your license, it won’t work. Regarding changing your mail id in the license, please post your requirements/query in Aspose.Purchase section and one of our sales staff member will help you soon there.
please open your license file check the date inside <SubscriptionExpiry>....</SubscriptionExpiry> tag which denotes your license expiry date. Please note your license will never expire if you continue to use any version of Aspose.Cells which is released before your subscription expiry date. However, if you need to use any version of the product which is released after your subscription expiry date, then you need to upgrade your subscription.