Suggested Actions

Suggest an improvement

Submit a request for new functionality or enhancement to an existing feature that would make the product behave more efficiently or extend its capability.

For Example:

  • I would like to see products differently.

  • I would like to see the product do something new.

  • I have an idea for how the product could be improved.

Open a support case

Create a new support case to get help with a problem you may be experiencing. This if the product behaves in a way in contravention to the documentation or displays an error visibly or in any log files or debug.

For Example:

  • I cannot get the product to work the way i want.

  • I donot understand something about the product.

  • I believe I have discovered a problem with the product.

This website uses cookies. By clicking OK, you consent to the use of cookies. Click Here to learn more about how we use cookies.
OK
sonny_dewit
Flexera beginner
‎Feb 23, 2021 04:15 AM

No socket connection to license server manager when upgrading client dll to v11.17.1.0

When upgrading the client dll from:

  • v11.16.2.0 build 242433 (ipv6) i86_n3 (lmgr.lib)

to:

  • v11.17.1.0 build 268393 (ipv6) i86_n3 (lmgr.lib)

Some of our customers get the error "No socket connection to license server manager" when connecting to a working license server.

When switching the dll back to the old version, the license server can be connected to immediately (no restart, no port changes, etc.)

The license server is using lmadmin-x64_n6-11_17_1_0.exe, with our dhsdelft daemon version v11.17.0.0 build 264148 (ipv6) x64_n6 (lmgr.lib). This setup works when we use the old dll, but gets us the error from the subject when we also update the dll on the client computer.

The license file they use to connect to the server looks like this:

SERVER servername 0000000000 TCP:27010
USE_SERVER

We are unable to reproduce the issue on our side when using the same operating systems for client and server. When we test, the old and new dll work fine:

  • Client: Windows 10 20H2
  • Server: Windows Server 2016

We double checked the port status on the client despite the old version working without issue, and the ports are open for access by the client (lmadmin port and vendor daemon port).

The license server shows no entries in the vendor daemon log when the client receives this error.

What could cause this error?

0 Kudos
Reply