TA_E_ENABLE_NETWORK_ADAPTERS on LinuxSolved

I have a customer trying to activate my software on a Linux machine and getting the TA_E_ENABLE_NETWORK_ADAPTERS error.

The machine is running Ubuntu Mate 22.04 on x86_64 architecture

TurboActivate is at 4.4.4.0

Al of the information that you give on your support pages is about fixing this issue on Windows machines. Please can you provide details of how to fix this on a Linux machine.

Thanks.

It's very likely they don't have any network adapters connected. Have them run:

lshw -class network

Give us the full result from running that from a terminal.

  *-network                 
       description: Wireless interface
       product: Wi-Fi 6 AX201 160MHz
       vendor: Intel Corporation
       physical id: 14.3
       bus info: pci@0000:00:14.3
       logical name: wlp0s20f3
       version: 01
       serial: 14:18:c3:e9:99:9a
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=6.5.0-28-generic firmware=77.2df8986f.0 QuZ-a0-hr-b0-77.u ip=192.168.1.71 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: iomemory:600-5ff irq:16 memory:6001114000-6001117fff

Much more information is needed. Because that's a valid device, and TurboActivate would detect that no problem.

Use the latest version of TurboActivate (and only the dynamic version, not the static version).

Provide more information if you're having problems: https://wyday.com/limelm/help/faq/#useful-reports

I am using version 4.4.4.0. 

Is that not the latest version on Linux?

I am using the dynamic version: libTurboActivate.so

What further information do you need and how do I get it?

Do you have the equivalent of the TurboActivate wizard for Linux that I can give to the customer for trouble shooting?

Can you have them run  cat /proc/net/dev from terminal and give you (us) the full results. What they've given us so far TurboActivate should happily accept it.

:~$ sudo cat /proc/net/dev
[sudo] password for XXXXX:
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:   21167     195    0    0    0     0          0         0    21167     195    0    0    0     0       0          0
wlp0s20f3: 2184865    2162    0    0    0     0          0         0   156237    1212    0    0    0     0       0          0
, edited

What do they get when they don’t run that with sudo?

Just run the command in a user-level terminal:

cat /proc/net/dev
:~$ cat /proc/net/dev
Inter-|   Receive |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:   63041     551    0    0    0     0          0 0    63041     551    0    0    0     0       0          0
wlp0s20f3: 1095910030  752658    0    1    0     0 0         0 31575707  355177    0    0    0     0       0 0
, edited

Please can you help me fix this activation issue.

We're working to try to reproduce this.

Any news on this issue? Do you need more information in order to reproduce this?

Please can you help me resolve this issue for my customer. They have been waiting patiently for a response but they still cannot activate. 

What more information do you need to reproduce the issue?

Can you create a tool similar to the TurboActivate wizard that I can give to the customer so that it can run some debugging commands and create the information that you need?

I pay a large fee to your company every month in order to use TurboActivate and I would like to know that you will be helping me with this issue

We haven't been able to reproduce this, but we're still digging into it.

It has now been 4 months since the customer has reported this issue and they are still not able to activate on their machine. 

What more information do you need? 

Answer

The output they provided is correctly parsed by TurboActivate's algorithms. We're digging into other causes, but this is the only person that's reported this problem on Linux, so it's very likely a *them* problem.

We haven't been able to reproduce this on any of our test machines or test VMs.

I'd recommend them updating their OS, rebooting and trying again. If that doesn't work, apply all BIOS updates from the manufacturer and upgrade to the latest Ubuntu (24.04) because Linux doesn't have separate "drivers" (everything is built into the Kernel, and updating the kernel is a bit like brain surgery if you don't know what you're doing). So, updating the whole OS is the easiest way to do it.

What model of computer are they on?

Did it come pre-installed with Linux or did they do that?

After upgrading the BIOS and base OS, if they’re still having problems we’ll give you a program that they can run on the machine to give us more information.

, edited
Answer

They updated their OS, rebooted and this time it worked. Thank you