Skip to main content
T
23-Emerald IV
TomU23-Emerald IV
23-Emerald IV
August 18, 2016
Question

Multiple Sessions of Creo with One Floating License

  • August 18, 2016
  • 6 replies
  • 7685 views

Just saw this come through from PTC today.  This is pretty huge.  Multiple sessions of Creo running on the same computer will now pull only one floating license.

 

https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS234779

  • The requested change has been implemented into the license cutting tool
  • All newly retrieved or generated license files will have this function included
  • Launching multiple sessions using floating license will consume only one license for a single host

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

6 replies

J
James621-Visitor
1-Visitor
August 18, 2016

Thanks for the good news.

D
Domen_13083315-Moonstone
15-Moonstone
August 18, 2016

Do you understand what is meant with:

  • The requested change has been implemented into the license cutting tool
T
23-Emerald IV
TomU23-Emerald IVAuthor
23-Emerald IV
August 18, 2016

It means the change was made to the internal PTC tool that actually generates the licenses.  Based on the article it doesn't seem like anything needs to be done on our end except requesting a new license file.

D
Domen_13083315-Moonstone
15-Moonstone
August 19, 2016

Has anybody tested this? And is it working on your comuputer?

I got a new license from PTC, but it doesn`t work.

It still takes 1 license for 1 session.

M
MartinHanak24-Ruby III
24-Ruby III
August 19, 2016

Hi,

I tested it, too ... and opened Case at PTC Support to report that new functionality is not available​, yet.

MH

M
MartinHanak24-Ruby III
24-Ruby III
August 30, 2016

Hi,

yesterday PTC Support closed the Case. New functionality is available for all users using floating licenses.

MH

S
21-Topaz I
STEVEG21-Topaz I
21-Topaz I
August 25, 2016

We can't see this document anymore.  Listed as an internal PTC document.

T
23-Emerald IV
TomU23-Emerald IVAuthor
23-Emerald IV
August 25, 2016

It's not working.  R&D is trying to figure out why.  Martin has a case open and so do I.  Frustrating. 

S
21-Topaz I
STEVEG21-Topaz I
21-Topaz I
August 25, 2016

Ah.  Thank you for the update.

L
llie17-Peridot
17-Peridot
August 25, 2016

I know it is not work yet, but where was this publicized? Can you please provide the link?

S
23-Emerald III
StephenW23-Emerald III
23-Emerald III
August 25, 2016

It originally was viewable on the original post from Tom (above). It has since been removed.

T
23-Emerald IV
TomU23-Emerald IVAuthor
23-Emerald IV
August 25, 2016

It looks like PTC has fixed the issue.  I have three sessions of Creo running right now and I'm only pulling one floating license.

The key seems to be the addition of the option "DUP_GROUP=UHD" in each of the license sections.

Everyone should request a new license file and try it again.

P.S.  For those who manually parse the ptc_d.log file this may cause some confusion since each session shows up as a unique license request but the actual license usage is less.

L
llie17-Peridot
17-Peridot
August 25, 2016

Are you using Windchill? What does it do for data collision having same data (assembly) in multiple session? Our not so novice users might have multiple sessions opened to the same workspace.

B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
August 25, 2016

You can still only have the part checked out in one workspace.

If your engineers work without doing a checkout, make their changes, then checkout and check-in, he who does the final check-in wins for that around and the other check-ins from other workspaces get lost in the iterations, unless they are good are resyncing the workspace data. Even then I can see changes being lost or overwritten.

I am not a fan of using multiple Creo sessions connected to the same workspace nor am I a fan of multiple workspaces having the same parts for modification.

One workspace for one project, multiple projects working is ok. If one project modifies part A and part B, which use part A is in another workspace, lock part A in the Part B workspace to be read-only to prevent accidental double changes.

Using Windchill requires some discipline to get it working so you don't trash other parts.

Terms & ConditionsAccessibility statement