# License Server Troubleshooting

Start with System & Advanced > System Health. Correct its warnings before changing application code or issuing replacement license files.

# Setup code is rejected

  • Use the one-time code shown by IntelliLock for this generated website.
  • Copy it without leading or trailing spaces.
  • Confirm that the generated setup-token file still exists in App_Data.
  • Generate a new website package if the token was deleted before setup.
  • A successful setup consumes the token; it cannot be reused.

# Login shows an unencrypted-connection warning

This warning means the current request uses HTTP. It is intentionally non-blocking for local setup, but credentials are not protected in transit. Add an HTTPS binding and certificate before production use. Then set Security.RequireHttpsForManagement=true.

# A Project file is missing

ProjectFilePath is relative to the website's App_Data directory and must point to a .ilproj or .nrproj located safely inside it. Do not enter an absolute path or .. traversal. Restore/upload the project file and run System Health again.

Only .ilproj projects can be used for Web Management setup and IntelliLock Validation/Floating services. .nrproj is supported for .NET Reactor license generation records.

# License status is ServerValidationFailed

Check, in this order:

  1. The application can reach the configured Validation URL.
  2. The URL is the intended root or virtual endpoint and uses HTTPS in production.
  3. The endpoint's Project exists and has the same master-key identity as the project that protected the application.
  4. A license with a LicenseID matches that exact central License record.
  5. The Customer exists and is enabled; the License is not blocked or expired.
  6. Product and Project relationships match the information in the file.
  7. For a legacy file without LicenseID, its company/name/product information identifies a permitted legacy match.
  8. System Health reports no missing Project or relationship.

Do not solve this by deleting identity fields from a current license. Exact IDs remove ambiguity and ensure that blocking the intended record takes effect.

# Initial Floating registration is denied

  • Confirm that the Floating License selects a central License.
  • Check the central License, Customer, expiration and blocked state.
  • Confirm that the license file contains the expected FloatingLicenseID and LicenseID when it was created by the current system.
  • Verify that the selected endpoint uses the correct .ilproj.
  • Inspect the Floating License Monitor for occupied or stale sessions.
  • Compare the configured maximum users, refresh interval and timeout.

Older files without FloatingLicenseID use the compatibility search and can be ambiguous when multiple pools share the same customer/product identity.

# HTTP 429 from a public service

The request exceeded a rate-limit bucket. Current defaults allow 6,000 Validation requests per minute per effective client IP, 6,000 initial Floating registrations per minute per effective client IP, and 60,000 Floating ping/disconnect requests per minute with pool separation.

If many independent clients appear under one reverse-proxy IP, configure trusted proxy handling correctly before raising limits. Never trust arbitrary forwarded IP headers from the public internet.

# Email test fails

  • Verify host, port, TLS mode, user name and sender restrictions with the email provider.
  • Re-enter the SMTP password; stored passwords are never displayed again.
  • Confirm that the web host permits outbound connections to that SMTP port.
  • If the host requires its own relay/proxy, use the host-supplied relay settings.
  • Retry queued messages only after the test email succeeds.

# Database import is rejected

Confirm that the uploaded password belongs to the uploaded database, not the current database. A version newer than the installed Web Management version is rejected. A current database created with a different password pepper cannot safely replace account data unless its matching installation files are also restored.

Missing project files, empty/unsafe project paths and other relationships that System Health can report and an administrator can repair no longer abort an otherwise valid import. The import completes, reports the Health totals and reminds you to copy the required project files separately into App_Data.

Use Import for classic unversioned databases. Merge is intended for business and custom-table data and deliberately excludes security/configuration tables. For a complete server move, restore the matching database, pepper, settings and project files together instead of mixing files from separate installations.

# The website reports a server move

Restore the complete App_Data folder, enter the existing database password and choose a new server-bound or portable binding. An incorrect password is rejected. If the database, project files, pepper or portable key were omitted from the backup, restore them from the same backup set rather than mixing installations.

# Text displays à or â characters

Verify that every deployable ASP.NET text/source file is UTF-8 with BOM, recycle the IIS application pool and clear only compiled ASP.NET/cache output. Do not convert files to an ANSI code page. Decorative symbols in custom markup should prefer HTML entities.

© Copyright Eziriz. All rights reserved.