Solved! Go to Solution.
I am not sure how old it is, but I am thinking it might be several years old. I think the issue is resolved now, though.
I recently recreated this user's Windows profile and copied the old cache into the new profile. Unfortunately, the old profile folder did not completely delete, so the user had two profile folders, user.old and user.new. We did point Creo to the new profile folder, but it would still sometimes grab cache data from somewhere else. It turns out the old profile folder still had cache data in it, and it was showing that it had been recently modified. We think Creo might have been trying to pull from this user.old profile for whatever reason. Suffice to say, we completely deleted both profiles and created a new profile and we're thinking this will fix the issue.
What version of Windchill?
Are you setting your workspace before opening it to be sure you have the proper workspace.
This is version 7.0.8.0.
Yes, there is a batch script that sets the location of the workspace cache before it launches.
Misread your question, sorry! I am not sure of the version of Windchill.
On your Windchill home page in the upper right corner is a Quick Links button.
Press it, then Help-About Windchill. You will see a listing like this:
Thank you, the release version is 11.1 M020-CPS08.
When was the PTC directory originally created? Is it too old? Have you tried clearing out all your workspaces then deleting the PTC directory and having it recreated?
I am not sure how old it is, but I am thinking it might be several years old. I think the issue is resolved now, though.
I recently recreated this user's Windows profile and copied the old cache into the new profile. Unfortunately, the old profile folder did not completely delete, so the user had two profile folders, user.old and user.new. We did point Creo to the new profile folder, but it would still sometimes grab cache data from somewhere else. It turns out the old profile folder still had cache data in it, and it was showing that it had been recently modified. We think Creo might have been trying to pull from this user.old profile for whatever reason. Suffice to say, we completely deleted both profiles and created a new profile and we're thinking this will fix the issue.