Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
User has checked out a document from Windchill and opened it in Arbortext Editor 6. The user has made revisions and now wants to "save" the file. The user gets the following message:
Cannot find path specified
Error: [A11972]
She is also unable to check the file back into Windchill as the system doesn't recognize her changes.
Could this have something to do with the user's cache folders or temp folders? If not, what are the other possibilities?
Solved! Go to Solution.
There were actually several issues experienced by the user when trying to check in the file(s). Java errors and the error above. We did remove the cache folder but his didn't resolve the problems.
The solution was actually quite simple. We had to clean the user's workspace and then delete the workspace. We then re-created the workspace. Voila!! all issues resolved. The workspace must have become corrupted.
Note: we have also noticed (with other issues) that if a workspace name has an apostrophe (i.e. Joe's workspace) this can cause issues. When the apostrophe is removed from the name files can then be checked in and checked out without problems.
Hi Kathleen,
The cache is certainly one possible thing that may be the culprit here. Deleting the cache and letting Editor create a new one is always an easy check.
Aside from that, there's one article which notes this error message may have something to do with one of our advanced preferences:
Setting the saverenames option to off may resolve this issue
Maybe between these two you'll be able to resolve this. If not, let me know what the results were. Thanks!
There were actually several issues experienced by the user when trying to check in the file(s). Java errors and the error above. We did remove the cache folder but his didn't resolve the problems.
The solution was actually quite simple. We had to clean the user's workspace and then delete the workspace. We then re-created the workspace. Voila!! all issues resolved. The workspace must have become corrupted.
Note: we have also noticed (with other issues) that if a workspace name has an apostrophe (i.e. Joe's workspace) this can cause issues. When the apostrophe is removed from the name files can then be checked in and checked out without problems.