MixCR license shows as expired after activating

[DoryAbelman]

Hello,

I’m encountering an issue with activating a MiXCR license on a slurm cluster. I received a license from the MiXCR team, which the link with the license confirms is active. However, when I attempt to activate it, I run into a problem where the license appears to activate successfully, but subsequent checks indicate that it is expired.

Steps Taken:

1. I allocated resources on the build node:
   salloc --partition=build -c 1 -t 1:0:0 --mem 2G

2. Allocation was successful, and I loaded the MiXCR module:
   module load mixcr/4.1.2

3. I activated the license:
   mixcr activate-license

4. After entering the license key, I received a message stating:
   License activated successfully.

However, immediately after, checking the license status returned:
mixcr license-status

Output:
License error: AuthorizationError: License expired

Running MiXCR scripts on the cluster also produces the same error:

sh ALQ_S13.sh

Output:
License error: AuthorizationError: License expired

The license status link from the MiXCR licensing portal confirms the license is active.
I’m wondering if there’s an issue with how I’m activating the license on the cluster. Any insights or suggestions would be greatly appreciated.

Thank you very much for your time and help!

Best regards,
Dory

[mizraelson]

Is there an active internet connection on the cluster? MiXCR requires access to a licensing server to verify the license.

[DoryAbelman]

Dear @mizraelson,

I also wanted to follow up and share that the license activation and status check worked successfully with MiXCR version 4.6.0. However, our cohort is using version 4.1.2 for consistency, and we are hoping to activate and use the license with that version instead.

If there are any specific steps or recommendations for troubleshooting this issue with version 4.1.2, I would greatly appreciate your guidance.

Thank you again for your time and support.

Best regards,
Dory

[mizraelson]

There is no specific difference in license handling between 4.1.2 and 4.6.0. Does you script run successfully with 4.6?

[DoryAbelman]

Dear @mizraelson,

Thank you for your reply. Yes, the script runs successfully with MixCR 4.6.0. When I try to activate it, I get the following:

[dabelman]$ module load mixcr/4.6.0
By using this software, you agree the license at https://mixcr.readthedocs.io/en/develop/license.html
[dabelman]$ mixcr activate-license
Please enter the license:
<license>
Checking the license...
Ok
License activated successfully.
[dabelman]$ mixcr license-status
App version: 4.6.0; built=Sat Dec 09 14:48:42 EST 2023; rev=c9fafa41fe; lib=repseqio.v4.0
Unmatched argument at index 0: 'license-status'

However, I still get license expired when I try to run it with mixcr/4.1.2

[dabelman]$ module load mixcr/4.6.0
By using this software, you agree the license at https://mixcr.readthedocs.io/en/develop/license.html
[dabelman]$ mixcr activate-license
Please enter the license:
<license>
Checking the license...
Ok
License activated successfully.
[dabelman]$ mixcr license-status
License error: AuthorizationError: License expired

I wanted to please ask whether this issue arises because of a compatibility problem between the license and older versions of MixCR (e.g., 4.1.2). I'm wondering if there may be a different way to activate the license for MixCR 4.1.2 specifically, or if I need to exclusively use 4.6.0 with the updated license.

I was able to use 4.1.2 successfully on an older license prior to its expiration. I can move up the entire cohort to 4.6.0 though if preferred.

Thank you for your assistance!

Best regards,
Dory

[mizraelson]

I tested it on my end with both versions, and the same license works seamlessly. There are several ways to activate the software, and they should all work regardless of the version:

1. Creating a license file:
   You can create a mi.license file in one of the following directories:

• ~/ (home directory)
• The directory containing the mixcr.jar file
• The directory containing the MiXCR executable

If placing the file in the home directory, you can also use the name .mi.license.

2. Using environment variables:

   MI_LICENSE env var with the content of mi.license file
   MI_LICENSE_FILE env var with the path to mi.license file

That being said, I would highly recommend reanalyzing the entire cohort using the latest software version, which is currently 4.7.0.

[DoryAbelman]

Dear @mizraelson,

Thank you very much for your time and sharing these tips, I appreciate it and will attempt these solutions. I will also attempt to re-analyze the cohort using the latest MixCR version. I appreciate your time in resolving this.

Best wishes,

Dory