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.
To be fair, the CS that links to PTC User's cache recovery tool does have alternate methods of recovery. The other one is "send us your .wf folder and we'll fix you right up". Maybe useful for some, but problematic for others (like myself).
Well our models are fairly massive. Some full rigs are upwards of 8-10 GB just to open in Creo. I wonder why there is an ability to see your available memory for cache but it means nothing because once a users local cache approaches ~3000KB (3GB) weird things start happening....then I delete the .wf folder and all it back to normal again until that their cache builds up again the next time.....
Bryant H. Hudson IV CAD/PDM Administrator Atlas Copco Drilling Solutions, LLC
A common symptom is an unretrievable model, even though it is listed in the Workspace and File Open dialog. The reason is that the cached file is wrongly removed by a clear cache or Event Manager cleanup operation.
Maybe that's where the issues are - We have never used the Cache tool in Pro/E to clear cache.
After verifying that all wanted files in all workspaces are uploaded, our users clear cache by removing the cache folder using a batch file (doesn't delete it - just moves it to a date stamped archive location). Next time Pro/E is launched a mapkey registers the server to generate a new cache.
I don't even know what an Event Manager cleanup operation is so it's unlikely we do that either.
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.