Skip to main content
Jan 26, 2016 11:47 AM UTC
Acknowledged

Multiple session of Creo3 embedded with Windchill

Related products:Creo Parametric

With the deployment of Creo3 we lost the ability for our user base to run 2 session of Creo while connected to Windchill.  This has affected many users in our company.  On their behalf I am requesting that they regain the option to run 2 session of Creo when connected with Creo.

35 replies

Jan 26, 2016 1:50 PM UTC

PTC has always recommended that you do NOT run multiple sessions of Creo connected to Windchill. They have finally figured out how to enforce their recommendation.

If you do run multiple sessions, you MUST use different cache folders for each session.

If our designers want to see another drawing for reference while in Creo, they use the image that is stored in Windchill with CreoView.

Jan 26, 2016 2:03 PM UTC

We had users that insisted on doing multiple Creo 2.0 sessions and it caused trouble. We just did some testing on this and with Creo 3.0, and Pro/INTRALINK 10.2 you can connect with two sessions of Creo 3.0. However, you must use the same workspace. If you change workspaces in one Creo session, when you go to the other session the workspace (and displays etc) are changed there too.

Jan 28, 2016 1:59 PM UTC

So why do they insist you not run multipule sessions... I have done this for as long as i can remember and I have more than 15 years with PTC products.  I have not had any issues with corrupting workspaces or anything like that.  I think you are looking more at a licensing issue on PTC part not a problem on the users part. 

Jan 28, 2016 2:40 PM UTC

Not being able to run multiple sessions is a hit on my productivity. My workaround for this new limitation takes time and is extremely inconvenient.

Jan 28, 2016 2:40 PM UTC

The main reason I would like to have two sessions of Creo open at the same time is so I can have one online and offline. This will allow me to compare the features in the model tree at the same time.

Jan 28, 2016 3:34 PM UTC

You can run multiple sessions, but each session needs its own cache folder. By default the startup scripts use a single cache folder.

I am guessing that with no problems running multiple sessions, you have it set so that each sessions uses its own cache folder.

It has nothing to do with licensing, since one workstation SHOULD only be using one license no matter how many sessions are running because only one session is active at a time.

3-Newcomer
Jan 28, 2016 4:08 PM UTC

That's not true with floating licenses, each session uses it's own license.  That is how locked licenses work. I believe there's a product idea here somewhere to change that, but I can't find it.  I might be thinking of this discussion instead: Running multiple sessions of CREO without consuming multiple licenses

Jan 28, 2016 4:23 PM UTC

I have never run multiple cache and have never had a problem.  So I don't know where that idea comes from

Jan 29, 2016 4:07 AM UTC

There seems to be a lot of confusion going around.  Let me see if I can clarify some things.

First, running multiple sessions of Creo (Pro/e) while connected to Windchill and sharing the same cache is currently supported and has been supported since Windchill 9.1 (M010+) w/ Wildfire 4 (M070+) and Windchill 9.1 (M020+) w/ Wildfire 5 (F000+).  "Cache sharing between multiple Pro/ENGINEER sessions of the same datecode when logged into Windchill with the same account, working with the same cache and even the same Workspace is supported."  See CS131176 for more info.

Second, a change was made to how cache sharing works starting in Creo 3 that requires all Creo sessions connected to the same cache to also be connected to the same workspace.  If you change workspaces in one of the Creo sessions it will change workspaces in all the others.  This is documented here: CS202061

Third, node-locked licenses are considered "uncounted".  This means if you have a node-locked license on your computer, you can run as many simultaneous session of Creo you want (or your computer can handle).  On the other hand, floating licenses only allow one session of Creo at a time.  If you start a second session, a second floating license will also be retrieved.  (The only way around this restriction is to borrow a floating license.  Once borrowed, the floating license will act like a node-locked license for the duration of the borrowing period.)  This node-locked vs. floating license difference has been around for at least twelve years, so I highly doubt PTC will consider changing it now.  See CS33927 for more info on this topic.

Jan 29, 2016 11:31 AM UTC

Tom you are correct now why did PTC change it in Creo 3.  Why do I have to have all sessions of creo hooked to one workspace.  What is the motive behind changing it.