License Validation Fails
On this page
7.2 License Validation Fails
Product license, licensing account, application role, and database account are separate identities. Record the exact message and entry before changing anything.
7.2.1 Identify the Restriction
| Symptom | Check | Do not |
|---|---|---|
| Invalid/expired/validation required | About and official issuance/renewal | Edit files or copy another license. |
| Advanced function unavailable | Edition/features | Reinstall expecting extra rights. |
| Login works, maintenance/print denied | User/group/layout policy | Borrow admin identity permanently. |
| Wrong application password | Project account/access policy | Repeatedly try a website password. |
| Database login fails | Database identity/service | Replace the product license. |
Open About through Licence and inspect edition, expiry, and actual state. Features may need both license and role permission.
7.2.2 Load the Correct License Normally
Securely retain the existing CREVIALicense.Key. Confirm the new official file belongs to this product/machine, not an application request, image, HTML download, or renamed unrelated file. Use Load License File in About, follow prompts, and preserve failures instead of repeatedly overwriting. After success, verify edition/term and reenter/restart as instructed. Report time, exact error, version, and license business reference through official secure support if unresolved.
Do not text-edit contents, delete files to recreate trials, or expose full contents in screenshots. Retained old files are diagnostic evidence, not reusable licenses for other machines.
Figure 7.2-1. Show English About state/load entry and distinguish licensing from role permissions. Hide license contents, fingerprints, email, and credentials.
7.2.3 Connectivity, Time, and Renewal
Verify date/time zone/synchronization, proxy, firewall policy, and official service reachability. Ordinary web/database access does not prove license-service connectivity. Administrators should correct clocks normally and complete official verification, not roll back dates, cycle zones, or alter certificates. Retain time-anomaly messages even if the clock appears correct. Use supported offline renewal where available; disconnection does not promise automatic extensions. Expired/revoked/wrong-machine licenses are not cured by restarting.
7.2.4 Migration and Policy Changes
Hardware replacement can require migration/reissue. Copying a root/license or restoring an image is not authorization for another machine. If only one role/layout fails, the designer must check saved policies, group SQL, and COC login rights, then save/republish. Changed CDPS configuration does not update an old COC layout. Do not disable access control or delete groups as a troubleshooting shortcut; such policy changes need separate approval and backup.
7.2.5 Retest and Escalation
Check that required functions work and prohibited ones remain restricted. Website login/database connectivity alone does not prove license recovery. State application/version, startup-versus-function failure, recent hardware/time changes, last success, and renewal result. Send redacted facts first and license files only via the designated secure channel; omit passwords and device keys.