Troubleshooting Device Limit reached after IP change in ZappySys ODBC

Problem

If you changed the IP address of your virtual machine and started receiving a “License Error – Device Limit reached” message when using ZappySys ODBC, the Application Gateway may be rejecting the connection due to an IP-based licensing limitation.

This issue commonly appears after VM reconfiguration, redeployment, or network changes that result in a new IP address.

Why does this problem occur?

ZappySys ODBC licensing uses Device-based Client Access Licenses (CALs), treating each IP address as a separate device.

By default:

  1. One Device CAL is included, allowing connections from one IP address.
  2. When the IP address of a virtual machine changes, the Application Gateway treats it as a new device.
  3. The previously registered IP may still be associated with the license.
  4. If no additional Device CALs are available, the new connection is rejected.

In this situation, the following error may be displayed:

License Error - Device Limit reached.
Connection(s) from other IP address(es) already used available CALs (Client Access License) so your connection got rejected.

IP(s) => XX.XX.XX.XX.X; XX.XX.XX.XX.X

Because licensing is IP-based, changes to the network configuration can trigger this condition even when only one machine is in use.

Solution

In many cases, this issue can be resolved by refreshing the license state:

  1. Deactivate the existing license.
  2. Activate the license again.
  3. Restart the ZappySys Application Gateway service.

Restarting the gateway forces it to reload the license information and update the active IP address, allowing the connection to succeed.

Conclusion

This issue occurs when the ZappySys ODBC Device CAL limit is reached, typically after an IP address change on a virtual machine. Since licensing is IP-based, a new IP can be interpreted as a new device.

Reactivating the license and restarting the Application Gateway refreshes the license state, resolving the issue in most environments. For scenarios involving multiple or frequently changing IPs, additional Device CALs may be required.

Contact Us

If you encounter any further issues or need additional help, please reach out to our support team via live chat or submit a support ticket at support@zappysys.com.