@psethu01
Hello, In any case, if you are using or setting the license in a multi-threaded application, please ensure that the license code is only executed once and is executed first in the entire application lifecycle. Please check whether the license-setting code is being executed repeatedly and concurrently. If so, you should fix this issue.
could you please provide a detailed introduction of your runtime environment, including hardware information, OS, and installed software? Is it possible to set up a similar environment locally in single-machine mode to simulate and reproduce your issue?
We further analyzed your error message and found that the error may stem from a Socket connection issue (/usr/lib/python3.11/socket.py) or a Py4j communication failure. Therefore, we recommend ensuring that network communication is functioning properly, and also check if everything works fine without using Aspose.
Thank you!
Hi,
We tried running a single node environment hitting the same issue. The application runs fine if we dont call the license file and just use the aspose lib without it.
It is quite unusual that the licensing issue persists even when setting the license in a single-node environment. Hopefully, you are not processing the licensing code repeatedly in your app. We will investigate this further and get back to you soon. But could you please also give us details about your runtime environment, including hardware information, OS, and installed software, etc.? Is it possible to set up a similar environment locally in single-machine mode on your end to simulate and reproduce your issue?
@psethu01
We have two ways to set the license: one is by using the file name, and the other is by using a stream. If you are currently using the first method, you can try the second method.
from aspose.cells import License
lic = License()
# Try to set license by lic file name
lic.set_license(yourPath + "Aspose.Cells.Pythonvia.NET.lic")
from aspose.cells import License
import io
# Try to set license from the stream.
lic = License()
lic_stream = io.FileIO("Aspose.Cells.Pythonvia.NET.lic")
lic.set_license(lic_stream)
lic_stream.close()
Hope helps a bit!
Could you please provide sample databricks Code
See the example code below for reference:
from aspose.cells import License
import io
# Create License object
lic = License()
# Read license file from DBFS path
license_path = "/dbfs/FileStore/licenses/Aspose.Cells.Pythonvia.NET.lic"
# Use a stream to load the license
with open(license_path, "rb") as f:
stream = io.BytesIO(f.read())
lic.set_license(stream)
when I am trying to run the above code I am getting the below error:
“Fatal error: The Python kernel is unresponsive.”
attaching the screenshot
macro error.jpg (99.2 KB)
@psethu01
It seems that Python does not work. Please remove all codes about Aspose.Cells and just simply call print(“Hello World”)
@psethu01
Hi!
First, please try using the Aspose library without loading the license file to verify whether the issue is truly related to the license.
from aspose.cells import CellsHelper
print(CellsHelper.get_version())
If the problem still occurs, it may indicate an issue with the Aspose library itself, rather than just a license-related problem.
If the above code runs without issues, please try the following methods:
- Copy the license file to a local temporary directory (e.g.,
/tmp) and load it from there:
from aspose.cells import License
lic = License()
lic.set_license("/dbfs/tmp/Aspose.Cells.Pythonvia.NET.lic")
- Alternatively, use the DBFS API to read the license content, which may help bypass potential compatibility issues with distributed environments:
from aspose.cells import License
import io
license_content = dbutils.fs.head("dbfs:/FileStore/licenses/Aspose.Cells.Pythonvia.NET.lic", 10000)
lic = License()
lic.set_license(io.BytesIO(license_content.encode("utf-8")))
Additionally, regarding the error message “Fatal error: The Python kernel is unresponsive,” our research suggests that this is often caused by resource exhaustion.
Please also check your system’s resource usage (e.g., memory and CPU) for further insights.
Thank you!
I tried to running the below code
“from aspose.cells import CellsHelper
print(CellsHelper.get_version())”
It’s having a issue loading the Aspose Library .
aspose library error.jpg (23.5 KB)
@psethu01
I registered a user on Databricks and installed the latest version of aspose-cells-python (25.7) in a Notebook.
When I ran the code above, the result was as follows:
databricks.png (5.3 KB)
Could you please share how you are running the code on Databricks?
Is it possible that your setup—such as file system, cluster, or other configurations—is different from mine?
(As mentioned above, I simply registered, installed the package, and ran the code without any other setup.)
@psethu01
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): CELLSPYTHONNET-295
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
@psethu01
Hello, after some time of investigation, we have basically identified the issue. After applying the fix, the error “The Python kernel is unresponsive” no longer appears when calling set_license("license.lic") .
We plan to release this version in early to mid-August. However, if it is urgent for you, we can also provide a hotfix. Thank you!
@psethu01
We are preparing a hotfix right now. I will notify you here as soon as it’s ready to install. Thank you!
@psethu01
Hi, We have published a hotfix on PyPI. Please install and test it. Our test results are as follows:
TestLic.png (15.5 KB)
Hope, it helps a bit!
@xinya.zhu
Hi, While running the code with the hotfix we are getting he below error
“RuntimeError: Proxy error(InvalidOperationException): The subscription included in this license allows free upgrades until 17 Jan 2024, but this version of the product was released on 25 Jul 2025. Please renew the subscription or use a previous version of the product.”
Would it be possible to add the fix to the version 24.1.0 .
@psethu01
Sorry! We can not provide the fix based on old version, so you have to renewal your order.
And you can test with temporary license first.