Skip to main content
D
davehaigh13-Aquamarine
13-Aquamarine
October 7, 2014
Question

Workspace recovery/rename tools

  • October 7, 2014
  • 13 replies
  • 13393 views
When you log in to the PTC User site, Go to Resources, Library, expand the public files area, (pick "View all Topics"), pick Scripts. The top three items are what you want.
See the attached email for how to use the file I posted. That file was written by Dan Wolf, one of the guys I work with recompiled it after making a minor change.

[cid:image001.png@01CFE207.F2D9C440]


David Haigh

    13 replies

    Show previous replies
    D
    DonSenchuk12-Amethyst
    12-Amethyst
    October 8, 2014
    That's very interesting. We've been experiencing a sharp increase in workspace problems lately.

    Just a quick question. Are you removing the .wf folder entirely? Or are you only deleting the .cache2008 folder (the cache) while leaving the .Settings folder?

    I assume you're removing the entire .wf if you have to reset the server registry every time. I wonder if only removing the cache and keeping the .Settings would accomplish the same thing but alleviate the need to re-register on every Creo launch.

    I ask because our .Settings folder contains more than just the server registry. Though, come to think of it, I could just copy out the user's specifics and copy in the default .fld file to re-register the server without needing to get them to use a mapkey.
    D
    davehaigh13-AquamarineAuthor
    13-Aquamarine
    October 8, 2014
    The settings folder also contains the favorites the user may have defined.

    David Haigh
    M
    MikeFoster10-Marble
    10-Marble
    October 8, 2014
    We set the following two folders in the Creo startup file:

    set PTC_WF_ROOT=%appdata%\PTC\ProENGINEER\Creo2\WF
    set CREO_AGENT_HOME=%appdata%\PTC\ProENGINEER\Creo2\CA

    When we clear cache as I described previously it's these two folders we're removing. I haven't gotten complaints about lost favorites so maybe our users don't use that functionality.

    Mike

    Terms & ConditionsCookie settingsAccessibility statement