Known Issuesđź”—
Virtual Private Networksđź”—
If you wish to connect to a license server over a virtual private network, you will need to add the server to your My Connections list either manually by entering the IP address, or by using a configuration file. In most default network configurations, Bonjour discovery cannot be used across subnets, such as from a virtual private network to a LAN.
Firewallsđź”—
macOS and Windows firewalls on the license server may block incoming connections to the server from the client computer, even though the PACE License Daemon is digitally signed.
The simple solution to this issue is to disable the firewall. An alternate solution is to add the License Daemon to the exception list by finding it in its installed location.
- From the Firewall tab under System Preferences > Security & Privacy, press the “Firewall Options…” button.
- Press the “+” button to add an application.
- In the Find File dialog, press Cmd+Shift+G to allow you to enter a path.
- Paste the following path in the “Go to the folder:” text field: Â
/Library/PrivilegedHelperTools/ - Select “licenseDaemon” from the PrivilegedHelperTools folder.
At this point the License Daemon on the license server should be able to receive incoming connection requests from protected clients.
On the Windows platform, Windows Firewall needs to be configured to allow a sharable license server to communicate through the firewall with its clients.
For Windows 8/10/11:
- In Control Panel, select “System and Security”, then select “Windows Firewall”, then “Allow an app or feature through Windows Firewall”.
- Click on “Change Settings” to enable the “Allow another app…” button.
- Browse to find and select the
LDSvc.exeprogram and choose to add this app to both Public and Private Network Types.LDSvc.exeis found at the following path. Begin at the root directory on the Windows system disk to locate it:- For 64-bit Windows:
Program Files (x86)\Common Files\PACE\Services\LicenseServices - For 32-Bit Windows:
Program Files\Common Files\PACE\Services\LicenseServices
- For 64-bit Windows:
For Windows 7:
- In Control Panel, select “System and Security”, then select “Windows Firewall”, then “Allow a program or feature through Windows Firewall”.
- Click on “Change Settings” to enable the “Allow another program…” button.
- Browse to select the
LDSvc.exeprogram and choose to add this app to both Public and Private Network Types.LDSvc.exeis found at the following path. Begin at the root directory on the Windows system disk to locate it:- For 64-bit Windows:
Program Files (x86)\Common Files\PACE\Services\LicenseServices - For 32-Bit Windows:
Program Files\Common Files\PACE\Services\LicenseServices
- For 64-bit Windows:
Client/Server Connectionsđź”—
If client systems are intermittently or unable to connect to an iLok Server that was previously available, try the suggestions below.
- Verify iLok Server and Services
-
- Confirm the iLok Server and PACE License Services (Windows: LDSvc.exe) are running on the server system.
-
- Restart PACE License Services if needed. Ensure no dependent applications (such as iLok License Manager) are running before restarting.
-
- If the issue persists, uninstall and reinstall PACE License Services using the latest License Support installer from iLok.com.
- Check Affected Client Systems
-
- If only some clients are affected, the issue may be client- or network-related.
-
- On affected clients, uninstall and reinstall the latest License Support installer.
-
- Verify the iLok Server is visible and connected in iLok License Manager’s File > Preferences… > Network > My Connections.
- Confirm iLok Server License and the iLok USB
-
- An iLok USB with a valid, activated iLok Server license is required.
-
- Use iLok License Manager to confirm the license is valid and activated.
-
- Check the physical iLok USB: reseat it or try a different USB port.
-
- Optionally, activate/deactivate any license on the iLok USB to confirm it is functioning.
- Review Network Configuration
-
- Determine whether recent network changes may have affected connectivity.
-
- In managed environments, have a network administrator review logs and settings.
-
- Confirm My Connections and Server Admin settings in iLok License Manager > File > Preferences… > Network are correct.
-
- Ensure Apple Bonjour networking is not blocked or restricted.
- Verify Software Versions
-
- Confirm the latest verson of iLok License Manager is installed.
-
- Confirm the client software versions support network activation.
-
- The latest client software version may not always be network-activation aware.
-
- Contact the software publisher to verify the correct supported version.
- Avoid Cloning Client Databases
-
- Do not clone the local client database file (com.paceap.eden.clientdb.v1.01.sdb) across systems.
-
- Each client must maintain a unique database to avoid connection issues.
- Use an iLok USB Directly
-
- All PACE-protected software can alternatively be authorized by connecting an iLok USB with the appropriate license directly to the system.