Fix: Device Limit Reached Error after IP Change in ZappySys ODBC
Source: Dev.to
Problem
After changing the IP address of a virtual machine, you may start seeing a “License Error – Device Limit reached” message when using ZappySys ODBC. This usually happens after VM redeployment, network changes, or infrastructure updates.
Why This Happens
ZappySys ODBC uses Device-based Client Access Licenses (CALs), where each IP address is treated as a separate device.
- One Device CAL is included by default
- Each unique IP address counts as one device
- When a VM IP changes, it is detected as a new device
- The previous IP may still be registered against the license
If no additional Device CALs are available, the connection is rejected.
Solution (Quick Fix)
In most cases, you can resolve this issue by refreshing the license state:
- Deactivate the existing ZappySys license
- Activate the license again
- Restart the ZappySys Application Gateway service
Restarting the gateway forces the license to reload and updates the active IP address.
When Additional CALs Are Needed
If your environment frequently changes IP addresses or uses multiple machines, you may need additional Device CALs to avoid this issue in the future.
Conclusion
This error is not caused by a misconfiguration, but by IP‑based licensing behavior. Re‑activating the license and restarting the Application Gateway resolves the issue in most single‑VM scenarios.