CadActiveSupport

troubleshoot

Troubleshooting PTC FlexNet License Server Issues

A checklist for diagnosing why Creo cannot obtain a floating license from the FlexNet license server.

If Creo cannot obtain a floating license, the issue can generally be narrowed down by checking the license server, network connection, license file, and Creo client configuration.

Use the checklist below to help identify where the problem is occurring before moving into more detailed troubleshooting.

1. Confirm the Problem

First, determine whether the issue affects:

  • One user — More likely to be a workstation, network, or Creo configuration issue.

  • Multiple users — More likely to be related to the FlexNet license server, license file, or network.

  • Remote users only — Check VPN and network access to the license server.

Also note the exact FlexNet error shown when Creo starts. Error numbers such as -15, -5, or -61 can help identify the cause when searching PTC Support. PTC documents these errors individually.

2. Verify the License Server Is Running

On the license server, confirm that the PTC FlexNet License Server service is running.

If your environment uses FlexNet Admin (lmadmin), you can also open the FlexNet Admin interface and verify that the PTC vendor daemon is running and licenses are being recognized. PTC's lmadmin interface can display license status, expiration information, and the status of license-server processes.

If the service is stopped, attempt to start it and check whether any errors are reported.

If the FlexNet service will not start: Common symptoms may include Windows Error 1053, an msvcp120.dll missing error, FlexNet appearing as Unreachable, or the installer remaining stuck on Starting. PTC provides specific troubleshooting for these conditions, including issues related to the Microsoft Visual C++ 2013 Redistributable:

PTC – lmadmin_ptc Service Fails to Start in FlexNet Publisher (CS317655)

Tip: If nobody in the organization can launch Creo, checking the license server is usually a good place to start.

3. Verify the Client Can Reach the License Server

Creo workstations typically reference the floating license server using a license source in the format:

port@servername

For example:

7788@PTCLicenseServer

Your organization's port and server name may be different.

From the affected workstation, verify that:

  • The server name is correct.

  • The workstation can communicate with the license server.

  • The required FlexNet ports are not being blocked by a firewall or VPN.

  • The problem is not limited to users connecting remotely.

If the Creo installer or Reconfigure utility shows the license server as Unreachable, PTC has troubleshooting specifically for that condition:

PTC – FlexNet License Server Shown as Unreachable (CS60089)

PTC lists an unreachable server during Creo installation as a common FlexNet connectivity symptom.

4. Check the License File and Host ID

If the FlexNet service is running but licenses are still unavailable, verify that the license file installed on the server is correct.

Check that:

  • The license has not expired.

  • The license was generated for the correct Host ID.

  • The correct and current license file is installed.

  • The expected Creo license features are present.

An incorrect Host ID can prevent the PTC vendor daemon from starting correctly, while an expired or incorrect license file can prevent clients from obtaining licenses.

If you recently received a new license file, see:

[Updating Your License File in FlexNet]

5. Check the Creo Workstation

If other users can obtain licenses but one workstation cannot, the license server itself is likely functioning.

On the affected computer, check:

  • The configured license server name and port.

  • Whether Creo was recently reconfigured or updated.

  • Whether the user is connected to the required company network or VPN.

  • Whether the Creo startup configuration is requesting a license feature that exists on the server.

If needed, run Creo Reconfigure and verify that the correct FlexNet license source is configured.

Tip: If the error states “No Such Feature Exists”, Creo may be requesting a license feature that the server is not currently providing. PTC documents this condition as FlexNet error -5.

6. Review the FlexNet Logs

If the cause is still unclear, review the logs on the license server.

FlexNet logs can help identify problems such as:

  • The PTC vendor daemon failing to start

  • Invalid Host ID information

  • License-file errors

  • Expired licenses

  • License requests being rejected

For FlexNet Admin installations, PTC identifies the license-server log as an important source of troubleshooting information.

The exact error in the log is often the best term to search in the PTC Knowledge Base.

Additional PTC Troubleshooting

If the checklist above does not identify the problem, PTC provides a guided troubleshooter that walks through common FlexNet licensing and installation issues:

PTC – Guided Licensing & Installation Troubleshooter

The troubleshooter covers common problems encountered while installing, starting, or connecting to FlexNet-based PTC applications.