AnsweredAssumed Answered

Solidworks 2015 dropping connection to license manager on server

Question asked by Rodney Peterson on Feb 12, 2015
Latest reply on Aug 7, 2015 by Kees Hoftijzer

Like • Show 0 Likes0
Comment • 6

I recently upgraded our server OS from server 2008 sp2 to server 2012 datacenter r2 and also

upgraded Solidworks enterprise from 2012 to 2015 and also upgraded all our seats of solidworks

from 2012 to 2015.

After doing this, 2 users regularly loose their connection to the license manager and then are forced to

save their work and then solidworks closes. They can re-start solidworks right away with no issues

like nothing happened.

We never had this problem before. I have done the following to resolve this issue with no success:

On clients and the server, created firewall inbound and outbound rules to allow TCPIP/UDP
communications on port 25734, 25735
Toyed with the network card adapter settings for example power usage and time settings.
Repaired the installation of solidworks.
Did a continuous ping to the server and one time returned a timed out response but not again
when I checked a few more times.

Anyone else having this issue or have any ideas on how to resolve?

Here is a snapshot of the message I get:

Paul Wyndham May 6, 2015 4:03 PM

Correct Answer

What I have found is if the users have borrowed a license in the past, it might be stuck in the License borrow tab of the SolidNetwork License Manager. Then, when they are using SolidWorks it doesn't show up in the list on the left side, so it thinks it can't find it.

Just select the file from the borrowed list and return it.

If that does not work and the user does not show up on the server list of people pulling a license you can edit the registry key: HKEY_CURRENT_USER\Software\FLEXlm License Manager\Borrow and delete it from there. It should take affect right away, but you might have to restart the computer.

See the reply in context

1 person had this question

Outcomes

Jared Conway Feb 24, 2015 12:54 AM

as a quick workaround for the users, have them borrow the license

then run a constant ping on their system for a day and take a look at whether there are any network drops

at least that will help narrow down the problem

Actions

Steven Hanson May 5, 2015 6:21 PM

We are having the same issue started when we upgraded to 2015 SP2 a few weeks ago I could copy and paste your description and troubleshooting almost word for word and didn't find a solution. I have an open ticket with my VAR and will let know if find anything.

The only workaround we have found is the same as Jared mentioned of checking out license.

Actions

Rodney Peterson @ Steven Hanson on May 6, 2015 10:48 AM

The persistent ping doesn't always yield the same result, as in dropped communications or latency issues. I have also found that in the beginning

the problem was confined to me and 1 other person. Now I seldom have an issue and another user has the problem. It makes no sense and I do not have the debugging experience or tools to figure this out.

glad I'm not alone anymore...misery loves company I guess.

Actions

Paul Wyndham May 6, 2015 4:03 PM

Just select the file from the borrowed list and return it.

Actions

Rodney Peterson @ Paul Wyndham on May 7, 2015 11:23 AM

Ty Paul Wyndam, this was(I hope) the problem. The user that had this happening all the time had

licenses borrowed some time ago and once he returned them he has not yet experienced this issue.

tyvm.

Actions

Kees Hoftijzer @ Paul Wyndham on Aug 7, 2015 5:52 AM

We have the same issue. Since upgrading from Solidworks 2014 to 2015 SP3 some users get the message 'could not obtain licence for the following product(s): Solidworks Standard". We have more than enough free license at that time.

It seems to happen only to users who had previously borrowed a license but did not fully return it before installation of the new version. That is, the borrowed license was expired before the new installation, but it was still mentioned in the license borrowed tab (the user had not pushed the '<return' button).

However, the solution by Paul Wyndham seems to solve some of this issue. But not completely. It still comes up at some users. Maybe less frequent.

I don't know what to do about this, my VAR also doesn't know ...

Actions

6 Replies

Jared Conway Feb 24, 2015 12:54 AM
Mark Correct
Correct Answer
as a quick workaround for the users, have them borrow the license

then run a constant ping on their system for a day and take a look at whether there are any network drops

at least that will help narrow down the problem
Like • Show 0 Likes0
Actions
Steven Hanson May 5, 2015 6:21 PM
Mark Correct
Correct Answer
We are having the same issue started when we upgraded to 2015 SP2 a few weeks ago I could copy and paste your description and troubleshooting almost word for word and didn't find a solution. I have an open ticket with my VAR and will let know if find anything.

The only workaround we have found is the same as Jared mentioned of checking out license.
Like • Show 0 Likes0
Actions
- Rodney Peterson @ Steven Hanson on May 6, 2015 10:48 AM
  Mark Correct
  Correct Answer
  The persistent ping doesn't always yield the same result, as in dropped communications or latency issues. I have also found that in the beginning
  the problem was confined to me and 1 other person. Now I seldom have an issue and another user has the problem. It makes no sense and I do not have the debugging experience or tools to figure this out.
  
  glad I'm not alone anymore...misery loves company I guess.
  
  ty
  Like • Show 0 Likes0
  Actions
Paul Wyndham May 6, 2015 4:03 PM
Unmark Correct
Correct Answer
What I have found is if the users have borrowed a license in the past, it might be stuck in the License borrow tab of the SolidNetwork License Manager. Then, when they are using SolidWorks it doesn't show up in the list on the left side, so it thinks it can't find it.

Just select the file from the borrowed list and return it.
If that does not work and the user does not show up on the server list of people pulling a license you can edit the registry key: HKEY_CURRENT_USER\Software\FLEXlm License Manager\Borrow and delete it from there. It should take affect right away, but you might have to restart the computer.
Like • Show 0 Likes0
Actions
- Rodney Peterson @ Paul Wyndham on May 7, 2015 11:23 AM
  Mark Correct
  Correct Answer
  Ty Paul Wyndam, this was(I hope) the problem. The user that had this happening all the time had
  licenses borrowed some time ago and once he returned them he has not yet experienced this issue.
  
  tyvm.
  Like • Show 0 Likes0
  Actions
- Kees Hoftijzer @ Paul Wyndham on Aug 7, 2015 5:52 AM
  Mark Correct
  Correct Answer
  We have the same issue. Since upgrading from Solidworks 2014 to 2015 SP3 some users get the message 'could not obtain licence for the following product(s): Solidworks Standard". We have more than enough free license at that time.
  
  It seems to happen only to users who had previously borrowed a license but did not fully return it before installation of the new version. That is, the borrowed license was expired before the new installation, but it was still mentioned in the license borrowed tab (the user had not pushed the '<return' button).
  
  However, the solution by Paul Wyndham seems to solve some of this issue. But not completely. It still comes up at some users. Maybe less frequent.
  
  I don't know what to do about this, my VAR also doesn't know ...
  Like • Show 0 Likes0
  Actions

Solidworks 2015 dropping connection to license manager on server

Outcomes

Related Content

Recommended Content

Incoming Links