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

Jul 19, 2016 4:52 PM UTC

Hi Ben,

I read CS202061 but unfortunately it went right over my head. I know Pro E/Creo well but I have never dived into the admin/behind the scene side. Where do I even start to try to set these options listed below. I have done some reading on the site. Are these win environment varaiables or are these changed in a startup script?

  • Set a unique PTC_WF_ROOT, PTC_WF_CACHE and CREO_AGENT_HOME environment (directory paths) for each session of Creo where a different state in the Server Registry are desired (eg. if wanting to change the active Workspace in session 1 but not session 2 )
Jul 19, 2016 7:19 PM UTC

I have not done this, but you need to set them in a batch file that would then launch Creo.

Also having a different start-in folder for each session of Creo, defined in the shortcut, may be enough that you would have different settings for those values inside of Creo. I tried to look in Creo to see what they are set at, but could not find them, I thought back in WF, they were listed in some menu display.

Jul 20, 2016 9:07 PM UTC

I figured it out. You have to save a copy of your current .psf file and then edit the new .psf file. Saving a copy of your .psf file allows you to pick a different startup configuration immediately after launching Creo.

MY .psf file was located here: C:\CREO_3\Creo 3.0\M090\Parametric\bin

After saving a copy of your .psf file you need to edit the file.

A) Give a new name in the row Desc= (I called it "Creo Alt Workspace")

B) at the bottom add:

    Env=PTC_WF_ROOT= Put any folder loaction that makes sense to you. For example: C:\PTC\ALT-ROOT\BHILL

I had to register the server location for the new session so it can see Windchill. I also had to load my config and customization.ui files for the new session. I placed my config and customization.ui files in the .settings folder that is created automatically after you type a folder location for the Env=PTC_WF_ROOT=. Not sure if placing the config and .ui files in the .settings folder is necessary but I did. I only had to register the server the very first time I launched the new session.

Aug 2, 2016 2:25 PM UTC

Hello PTC,

is there a chance to get an answer directly from PTC to this idea?

Any plans to bring it back?

All our users are complaining about this missing functionality.

Jochen

Aug 2, 2016 2:46 PM UTC

PTC has answered it in CS202061 which tells how to set up multiple cache locations for multiple sessions of Creo.

Aug 5, 2016 1:02 PM UTC

what are the CON's of having two cache's?  (what happens with items that don't get "synced")


This keeps me from working on multiple projects at once. I now have to dedicate days to specific projects instead of pulling up separate session on separate workspace and responding to small issues or requests.

Sep 22, 2016 5:40 AM UTC

Hello PTC,

once again. Is there a plan at PTC to bring this functionality back to Creo3.0?

CS202061 is only a workaround and not a final solution. There are disadvantages for administrator and for users working with different caches and different start environments.

Sep 22, 2016 12:30 PM UTC

Can I get a list of those Pros/Cons?  I would like to weight those before I take this plan to the Admins?

Sep 22, 2016 3:09 PM UTC

So far I have not had any issues. But I am accessing different workspaces or working offline with at least one of the sessions. You might run into problems with corrupting data if for some reason you are working out of one workspace with two different sessions.

Mar 14, 2017 2:28 PM UTC

Good day everyone,

The article Tom Uminn‌ shared, CS202061 is the best practice.

I am still working internally to see if there are other solutions and if/when this change can be implemented.

Please use the same variables into the proe startup batch file as follows .
PTC_WF_CACHE
C:\users\%username% \working_folder\cache
PTC_WF_ROOT
C:\users\%username%\working_folder

Another document is CS18736

Best,

Toby