Weird issue with response file when activating LexFloatServer

General
#1

Hi again,

I am experiencing a really weird issue when trying to activate the LexFloatServer via the command line on Windows (both 11 and Server 2022). If the file name of the activation response is 48 characters long, I get error 40. I know how weird this sounds, so I triple-checked this across three different machines.

C:\LexFloatServer>LexFloatServer -a --license-key XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX --offline-response LexFloatServer_activation_response_product1.dat --config config.yml --product-file product.dat
[2025-03-11 18:51:27+01:00] INF Offline activating license key...
[2025-03-11 18:51:27+01:00] INF License activated successfully!

C:\LexFloatServer>LexFloatServer -a --license-key XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX --offline-response LexFloatServer_activation_response_product12.dat --config config.yml --product-file product.dat
[2025-03-11 18:51:53+01:00] INF Offline activating license key...
[2025-03-11 18:51:53+01:00] ERR License activation failed: 40

C:\LexFloatServer>LexFloatServer -a --license-key XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX --offline-response LexFloatServer_activation_response_product123.dat --config config.yml --product-file product.dat
[2025-03-11 18:52:23+01:00] INF Offline activating license key...
[2025-03-11 18:52:23+01:00] INF License activated successfully!

Background:

This issue first occurred during an installation on a customer’s server. The installation is automated via a script because we usually have to install multiple products (each with its own LexFloatServer). Our script renames the activation response files to include the corresponding product name, so the file name lengths vary.

During the process, I ended up with three successful activations and one failure (error 40). There are no differences in the license settings—it all comes down to the file name length. At first, I suspected the installation script, but after isolating the issue, I found that the problem persists, as shown in the console output above.

I can work around this, but this behavior is extremely weird and (to me) suggests some underlying issue.

Using LexFloatServer 4.13.3 (the unboxed version that fixed LexFloatServer Crash – possibly related to Windows Update)

Thanks!

#2

Hi @hoelku8imu,

Error 40 (LA_E_FILE_PATH) occurs when the specified offline response file path is invalid or the file is not found at the given location. Although the correlation with filename length is unusual, I recommend verifying that the correct file path is provided and that the offline response file exists in the specified location before proceeding with license activation.

#3

Hi @AneesKhan,

I totally get that checking the file path is the first thing to do, and I’d ask the same question :slightly_smiling_face:. I’ve verified this multiple times—the file is definitely there, and the path is correct. I also tested what happens when the file is missing, and as expected, that also results in error 40.

Thanks :slight_smile:

#4

Hi @hoelku8imu,

There is no such issue that would cause error 40 to be returned if the file exists and a valid file path for the offline response file is provided. However, please ensure that the correct “Filename” is being specified in the filepath.

#5

Hi @AneesKhan,

the file is there, the name is correct. If the filename is not 48 characters long, it works.

Interestingly, it seems to work in PowerShell but not in CMD.

Still, this is a real thing, not just a naming mishap. Maybe it’s a CMD quirk, maybe it’s LexFloatServer/LexActivator. It doesn’t happen when the product or config file name has 48 characters.

I recognize that this is a really unlikely edge case, and as I said, I can work around it. If you decide to look into it at some point:

C:\LexFloatServer>dir
 Volume in drive C is OS
 Volume Serial Number is XXXXXXXX

 Directory of C:\LexFloatServer

13.03.2025  12:13    <DIR>          .
14.11.2024  11:53             2.010 config.yml
14.11.2024  11:59         1.536.920 LexActivator.dll
14.11.2024  11:59         9.680.280 LexFloatServer.exe
12.03.2025  11:32             3.033 LexFloatServer_activation_response_product12.dat
13.03.2025  11:03    <DIR>          logs
30.08.2023  14:59               857 product.dat
               5 File(s)     11.223.100 bytes
               2 Dir(s) XXX.XXX.XXX.XXX bytes free

C:\LexFloatServer>LexFloatServer -a --license-key XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX --offline-response LexFloatServer_activation_response_product12.dat --config config.yml --product-file product.dat
[2025-03-13 12:13:45+01:00] INF Offline activating license key...
[2025-03-13 12:13:45+01:00] ERR License activation failed: 40

C:\LexFloatServer>ren LexFloatServer_activation_response_product12.dat LexFloatServer_activation_response_product123.dat

C:\LexFloatServer>dir
 Volume in drive C is OS
 Volume Serial Number is XXXXXXXX

 Directory of C:\LexFloatServer

13.03.2025  12:13    <DIR>          .
14.11.2024  11:53             2.010 config.yml
14.11.2024  11:59         1.536.920 LexActivator.dll
14.11.2024  11:59         9.680.280 LexFloatServer.exe
12.03.2025  11:32             3.033 LexFloatServer_activation_response_product123.dat
13.03.2025  11:03    <DIR>          logs
30.08.2023  14:59               857 product.dat
               5 File(s)     11.223.100 bytes
               2 Dir(s) XXX.XXX.XXX.XXX bytes free

C:\LexFloatServer>LexFloatServer -a --license-key XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX --offline-response LexFloatServer_activation_response_product123.dat --config config.yml --product-file product.dat
[2025-03-13 12:14:11+01:00] INF Offline activating license key...
[2025-03-13 12:14:11+01:00] INF License activated successfully!

Cheers

#6

Hi @hoelku8imu,

There seems to be no such issue as we are not able to replicate it. However, we will investigate it further and keep you posted here.

Thank you!