Licensing: Unstable/changing Machine-ID
Changes in the network environment may affect the interface that is used to compute your machine ID (used to identify your license) and result in machine ID instability. You can use the PARASOFT_SUPPORT_NET_INTERFACES environment variable to specify a stable interface and prevent the machine ID from floating.
- Set up the PARASOFT_SUPPORT_NET_INTERFACES environment variable.
- Set the variable value to a stable Ethernet network interface. Do not use virtual, temporary or loopback interfaces.
- On Windows: Set the value to the MAC address of your network card. You can use the ipconfig -all command to obtain the address. Example:
- On Linux: Set the value to one of the network interfaces from the "inet" or "inet6" family. For Example: You can use the ifconfig command to obtain the list of available interfaces. Example:
If the problem persists, you can obtain diagnostic information by setting up the environment variable PARASOFT_DEBUG_NET_INTERFACES and setting its value to true. This will print to the standard output the checking procedure that can be shared with technical support , as well as the interface that is used to compute your machine ID. The interface will be marked with the [SELECTED] prefix.
brian_nuckles Posts: 32 admin
Manual Reset of MachineID-0 on Ubuntu 16.04
Navigate to /etc/default and edit the file named 'grub'
Replace the line GRUB_CMDLINE_LINUX=""
with the line GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"
Rebuild the grub configuration file:
sudo grub-mkconfig -o /boot/grub/grub.cfg
Update grub with: sudo update-grub
Add these lines to the bottom of /etc/network/interfaces
iface eth0 inet dhcp
Reboot your machine and check your Machine ID from the License Page.
Find more information here: https://askubuntu.com/
and here: http://www.itzgeek.com/how-tos/mini-howtos/change-default-network-name-ens33-to-old-eth0-on-ubuntu-16-04.html
There is another cause of this sort of problem: A disconnect between the host name as reported by hostname(1) and uname(1).
Correcting this will resolve this problem completely, no matter what network interfaces are available, (provided that there is at least one network interface which is IPv4 enabled.)
This is easily resolved by adding an entry, (or an alias), to the /etc/hosts file. No reboot is required.2
Or, it may be as simple as making sure that /etc/hostname contains the same name as uname -n
$ uname -n
$ cat /etc/hostname
Still facing this problem on Windows. From time to time it happens and machine id is another from one that belongs to key.
I have set PARASOFT_SUPPORT_NET_INTERFACES from real one value in my environment variables, but it didn't solve the problem.0
Well, I fixed this problem with support.
I had to set ethernet mac address as value of PARASOFT_SUPPORT_NET_INTERFACES instead of setting the wireless mac.0