Skip to main content
T
tcasola1-Visitor
1-Visitor
February 20, 2015
Solved

In Creo 2.0 (MOD 080) can users borrow more than 1 license?

  • February 20, 2015
  • 15 replies
  • 5480 views

As known, (unless FlexNet server is 11.10.1) users cannot return borrowed license until they expire.

We have those rare situations where the user may need to “extend” the amount of days they need to borrow a license.

According to PTC there is no way to extend the days, but PTC representative stated users can borrow another license (so they can have 2 borrowed licenses) before the current borrowed license expires.

We cannot get this multiple license borrowing to work. We’ve asked for guidance how to accomplish this, but haven’t been told.

We've gone into the xxx\PTC\Creo2.0\Parametric\bin folder and tried: parametric_borrow.bat & ptcborrow.bat with no luck.

Is there a special variable and/or setting needed to be added to Creo and/or the License server?

Any information would be greatly appreciated.

Best answer by MartinHanak

Tom,

1.]

You cannot borrow two identical licenses. For example two PROE_FoundationAdv.

2.]

You can borrow two different licenses. For example PROE_FoundationAdv and PROE_FAPAAX.

3.]

Return of borrowed license to the server before the expiration date has been implemented in Creo Elements/Pro 5.0 M150, Creo Parametric 1.0 M050 and Creo Parametric 2.0 M020.

4.]

To see borrow information on user workstation, user can use two commands:

  • ptcstatus
  • "<Creo 2.0>\Common Files\Mxxx\x86e_win64\obj\lmutil.exe" lmborrow -status

5.]

To return borrowed license early, user can use this command:

  • "<Creo 2.0>\Common Files\Mxxx\x86e_win64\obj\lmutil.exe" lmborrow -return -c 7788@SERVERNAME LICENSENAME

Also, the BORROW environment must be configured properly. In the past I created document containing all necessary information (unfortunatelly in Czech language).

Martin Hanak

15 replies

M
MartinHanak24-Ruby III
24-Ruby III
February 20, 2015

Tom,

the information concerning BORROW functionality provided by PTC is not very good. You have to compile information from several sources to get all you need.

I have never tried to borrow 2 licenses, but I can test it if you want ...

In the past I tested BORROW functionality in combination with FLEXnet 10.8 (lmgrd.exe+ptc_d.exe processes) and FLEXnet 11 (lmadmin.exe+ptc_d.exe). It worked as expected in both cases. I am accustomed to FLEXnet 10.8, therefore I will use this version as long as it is possible.

Martin Hanak

T
tcasola1-VisitorAuthor
1-Visitor
February 20, 2015

Martin,

I've tried numerous places to see if it was possible to borrow more than one license, and there is little information out there.

Today PTC finally came back and stated with our current license server configuration, there is NO WAY to return a license early; there is NO WAY to extend a license, and there is NO WAY to borrow more than 1 license.

If you want to test it trying to obtain more than once license, be my guest. However I wouldn’t go crazy.

Thanks for answering so quickly.

Be well, and have a great weekend!!

Tom

M
MartinHanak24-Ruby IIIAnswer
24-Ruby III
February 23, 2015

Tom,

1.]

You cannot borrow two identical licenses. For example two PROE_FoundationAdv.

2.]

You can borrow two different licenses. For example PROE_FoundationAdv and PROE_FAPAAX.

3.]

Return of borrowed license to the server before the expiration date has been implemented in Creo Elements/Pro 5.0 M150, Creo Parametric 1.0 M050 and Creo Parametric 2.0 M020.

4.]

To see borrow information on user workstation, user can use two commands:

  • ptcstatus
  • "<Creo 2.0>\Common Files\Mxxx\x86e_win64\obj\lmutil.exe" lmborrow -status

5.]

To return borrowed license early, user can use this command:

  • "<Creo 2.0>\Common Files\Mxxx\x86e_win64\obj\lmutil.exe" lmborrow -return -c 7788@SERVERNAME LICENSENAME

Also, the BORROW environment must be configured properly. In the past I created document containing all necessary information (unfortunatelly in Czech language).

Martin Hanak

Terms & ConditionsAccessibility statement