ProfileUnity License Server Errors at Logon — "Not Defined" and "Could Not Be Contacted"

Users receive a pop-up error at logon referencing the ProfileUnity License Server. Two distinct messages are possible, each with a different root cause. This article covers both.

Which Error Message Are You Seeing?

The two messages look similar but have different root causes. Identifying which one you have determines where to start.

Step 1 — Deploy ClientSettings.xml

ClientSettings.xml contains the connection string the client uses to locate and authenticate with the License Server. It must be present in the deployment share before client tools can make any license request.

1. Log in to the ProfileUnity Management Console and navigate to the Administration page.
2. In the Client Settings section, verify the following before deploying:
   • ProfileDisk and FlexDisk VMDK Mode — Set to Disable ProfileDisk and FlexDisk VMDK only if you are not currently using ProfileDisk. If ProfileDisk is in use, leave this at its current setting.
   • Deployment Path — Confirm this matches the share where your ProfileUnity client tools are stored (typically \\domain\NETLOGON\ProfileUnity or the path shown in your GPO).
3. Click Deploy Client Settings. This uploads ClientSettings.xml to your Deployment Path.

Step 2 — Update Client Tools to Read ClientSettings.xml

With ClientSettings.xml deployed, the client tools must be updated to read it. Use one of the following methods depending on how your environment is configured.

Option A — GPO Computer Startup Script (recommended)

If a GPO Computer Startup Script is configured, the action required depends on your VDI technology. LwL.ProfileUnity.Client.Startup.exe runs at machine startup and reads ClientSettings.xml from the deployment share — but only if the machine goes through a full OS boot. Technologies that fork from a running parent VM do not boot and therefore do not run the startup script on the clone.

Option B — Run the Startup Executable Manually

If no GPO Computer Startup Script is configured, run the following from an elevated Command Prompt on the affected machine and then recompose or reboot:

LwL.ProfileUnity.Client.Startup.exe

Step 3 — Test Network Connectivity to the License Server

If the error persists after Steps 1 and 2, the client can find the server address but cannot reach it over the network. Run the appropriate command below from an affected desktop session. Replace <ProU-Server> with the IP address or FQDN of the ProfileUnity Console server.

ProfileUnity 6.8.5 and later — Port 443

powershell Test-NetConnection -Port 443 -ComputerName <ProU-Server>

ProfileUnity 6.8.4 and earlier — Port 5672

powershell Test-NetConnection -Port 5672 -ComputerName <ProU-Server>

Step 4 — Verify Console Services Are Running

On the ProfileUnity Console server, open services.msc and confirm the following three services are running:

If the Liquidware Labs ProfileUnity License Service is stopped, start it and wait a few minutes to confirm it stays running. Then reboot an affected desktop to test. If the service stops again shortly after starting, it may be crashing — collect the logs in the next section and open a support case.

Port Reference

The following table lists all ports required for ProfileUnity communication. Port 8000 is the default Management Console port and can be changed in the Administration section of the Management Console.

Deep Troubleshooting — Logs, Connection Strings & Startup.exe

If the standard steps have not resolved the issue, this section explains how to trace the problem through the logs and configuration files — from the moment LwL.ProfileUnity.Client.Startup.exe reads ClientSettings.xml to the point the client tries to call the License Server at logon.

How LwL.ProfileUnity.Client.Startup.exe Populates Local Configuration

Understanding this flow is essential for diagnosing any licensing issue. Every time a machine reboots (or the startup script runs), the following happens:

Log Files to Check

All ProfileUnity client logs are written to C:\Windows\Temp\ProfileUnity\. Start with these three for license issues:

Verifying the Connection String Was Written Correctly

After Startup.exe runs, open the following file on the affected endpoint in a text editor (admin rights required):

C:\Program Files\ProfileUnity\Client.NET\LwL.ProfileUnity.Client.License.Service.exe.config

Search for LicenseServerConnectionString. The entry should look similar to this (value will be encrypted):

<setting name="LicenseServerConnectionString" serializeAs="String">
    <value>[encrypted string — should not be blank]</value>
</setting>

Quick Diagnostic Checklist

• ☐ClientSettings.xml exists in the deployment share and has been deployed from the current console
• ☐startup_*.log — Startup.exe ran after the last reboot (launchStartupUpdateExeResult is not False)
• ☐startup_update_*.log — exists and shows no errors writing connection strings
• ☐LwL.ProfileUnity.Client.License.Service.exe.config — LicenseServerConnectionString is populated (not blank)
• ☐clientlicensingservice_*.log — shows a connection attempt (not "no server defined")
• ☐Test-NetConnection -Port 443 — returns TcpTestSucceeded: True from an affected machine
• ☐ Console services — all three running (ProfileUnity Service, License Service, MongoDB)
• ☐ No proxy or firewall blocking outbound port 443 TCP from VDI clients to the console server

If the Issue Persists — Files to Send to Support

If the error continues after completing all steps above, open a support case and attach the following three files from an affected endpoint: