KeyShot Support Portal
No socket connection to license server manager. (-7,10015) Print
Modified on: Wed, 16 Dec, 2020 at 4:14 AM
This error message means the connection was broken due to disconnection from the network, however the system has initiated roaming to another access point.
This is most commonly caused by the default ports are being used or a VPN/Firewall setting stopping the connection.
Please confirm that ports 27000-27010 are available in your network firewall.
If you have a Firewall or have other License servers running on the same machine you may need to change the Server Ports, this can be done by clicking the Server Ports button.
- FlexLM Port: Change this to avoid port conflicts If you have other License servers — the default is 27000
- Deamon Port: This is only used for network setups with a Firewall. If a Firewall is used, both ports need to be set and opened in the Firewall.
Please discuss this in detail with your IT department before assigning ports.
Once the ports have been assigned, start the Luxion License server to see if that solves the issue.
If this fails, on a PC:
Stop and close the Luxion License server, then hit the ‘windows’ key and enter ‘LMTools’.
Open LMTools and select the ‘Start/Stop/Reread’ tab.
If this tab shows that the server is started, click stop.
Start the service to see if it launches. You will see a small message at the bottom of the LMTools windows stating if it started or not.
If it does not start, select the ‘Config Services’ tab and select ‘View Log’.
Make a copy of this log and send it to support@luxion.com.
On a MacOS:
- Stop the Luxion License server and select the License Folder button
- Find the file LUXION.log
- Make a copy of this file and send it to support@luxion.com.
Did you find it helpful? Yes No
Checkout failed with error: -7, 10015, No socket connection to license server manager
Why am I getting a checkout failed with error: -7, 10015, No socket connection to license server manager?
Answer
It’s possible that the version of license server and client application is not compatible. For example, in the combination of v11.11.1 client application + v11.11 license server, -7 error occurs. The issue can be resolved by upgrading license server to v11.11.1.
Another possibility is that another application could be using the same port; for example, if MS Exchange is running on the same server, and the machine has been rebooted the service mad.exe) could be listening on port 27000. In this case changing the license server to a different port will resolve the issue.
Flexnet licensing error 7 10015
When upgrading the client dll from:
- v11.16.2.0 build 242433 (ipv6) i86_n3 (lmgr.lib)
- 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?
- All forum topics
- Previous Topic
- Next Topic
Flexera Alumni
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 17, 2021 01:44 AM
«No socket connection to license server manager» error generally occurs when the version of license server and client application is not compatible. For example, in the combination of v11.11.1 client application + v11.11 license server, «-7, 10015, No socket connection to license server manager» error occurs. The issue can be resolved by upgrading license server to v11.11.1. However, in your description of the case I noticed the license server you’re using (v11.17.1.0) is greater than the vendor daemon (dhsdelft v11.17.0.0) so this will work fine. You did also mention that the client dll was built with v11.17.1.0 which is higher than your vendor daemon.
Now, according to our version compatibility about the licensing components the following must be true.
The rules about FlexNet Licensing component version compatibility are summarized as:
1. Version of lmutil/lmtools must be >=
2. Version of lmadmin(or lmgrd), which must be >=
3. Version of vendor daemon, which must be >=
4. Version of the client library linked to the FlexEnabled application, which must be >=
5. Activation utility, which must be >=
6. Version of license file format
The issue could be that your vendor daemon may need to be upgraded to v11.17.1.0 to be equal to the license server and the client.
2464661 — SySAM 2.4 — Flex licensing error — Failed to return borrowed license — SAP PD
Flex licensing Error -7,10015 Failed to return borrowed license for feature PD_SHELL.
No socket connection to license server manager. License feature name:
PD_SHELL License search path: C:\ProgramData\PowerDesigner 16\powerdesigner.server.lic;
FlexNet Licensing error:-7,10015
For further information, refer to the Sybase Software Asset Management website at http://www.sybase.com/sysam
Environment
- SAP PowerDesigner
- SAP IQ
- SySAM 2.3
- SySAM 2.4
Product
SAP PowerDesigner all versions
Keywords
upgrade, license, SySAM , KBA , BC-SYB-PD , Bug Filed
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).