topic Re: Creo Parametric workspace cache copied to new computer results in crash during launch in System Administration

Creo Parametric workspace cache copied to new computer results in crash during launch

MikePhillips — Wed, 08 Jan 2025 20:41:38 GMT

During the deployment of a new computer we frequently see the user's Creo Parametric workspace cache copied from the old computer to the new computer. This typically causes the user's new installation on the new computer to crash during launch. The solution to the crash issue is to remove or rename the old cache folder. Not a huge problem. Just a nuisance that results in lost productivity.

Do other companies see this issue?

If so, what do you do to avoid this situation?

Does anyone know why the cache can't be copied over to a new system?

Re: Creo Parametric workspace cache copied to new computer results in crash during launch

BenLoosli — Wed, 08 Jan 2025 21:45:50 GMT

We don't copy the cache over as we have dm_upload_objects set to automatic which always puts the latest files saved up on the server side cache. When the user logs into a new workstation, they set the server name and then the cache files get downloaded when they open their workspaces. This is also beneficial as a 'backup' in case the local drive fails, which we have had happen a few times.

My guess is there is computer information embedded in the cache files that are causing a mismatch between the old computer name and the new computer name.

Re: Creo Parametric workspace cache copied to new computer results in crash during launch

MikePhillips — Wed, 08 Jan 2025 22:10:59 GMT

We also set dm_upload_objects (but have only been doing that for a short while now). The computer deployment side of IT here wants to copy literally everything in an effort to prevent data loss. I would like to understand what that "mismatch" is so that our launch tool can be modified to detect it.

Thank for the reply Ben.

Re: Creo Parametric workspace cache copied to new computer results in crash during launch

Catalina — Fri, 14 Feb 2025 16:16:16 GMT

Hi @MikePhillips,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution or please feel free to detail in a reply what has helped you and mark it as the Accepted Solution. It will help other members who may have the same question.

Of course, if you have more to share on your issue, please pursue the conversation.

Thanks,

Re: Creo Parametric workspace cache copied to new computer results in crash during launch

MikePhillips — Fri, 14 Feb 2025 20:12:26 GMT

Well, I haven't really been presented with a solution yet. I believe some sort of computer asset information must be recorded in the cache some where (Like @BenLoosli mentioned above). So when the cache is moved to a new computer the information no longer matches and causes our issue.

Assuming this information is stored, I would like to know where so that I can modify our installation/launch script to detect the issue and automatically correct it (delete the old cache during start up).

I've been on other tasks so this issue has lost some priority for the time being.