: Some users resolve the issue by uninstalling the CSI native image. This can sometimes be triggered by pressing F4 during the installation process (you may need to use Fn + F4 on laptops).
| Cause | Description | |-------|-------------| | | Typo or copy-paste error (e.g., missing characters, extra spaces). | | License file corruption | The .lic or .key file is damaged due to improper installation or disk errors. | | Network or firewall blocking | The software cannot reach the vendor’s license server for online validation (port blocked, proxy issues). | | System date/time mismatch | If your computer’s clock is off, the license may appear expired or not yet valid. | | License already in use | The license is tied to another machine or session (e.g., concurrent license limit reached). | | Outdated software version | The license format changed in a newer version, or your license is for an older release. | | Hardware ID change | Some licenses bind to hardware (MAC address, motherboard serial). Changing components can break recognition. | | Antivirus interference | Security software may quarantine or block the license validation module. | license not recognized error #120
: If using a network license, ensure the Sentinel RMS License Manager service is running on the server. : Some users resolve the issue by uninstalling