Skip to main content
K
kregimbald1-Visitor
1-Visitor
February 4, 2014
Solved

Cannot find path specified - When saving

  • February 4, 2014
  • 2 replies
  • 1631 views

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?

    Best answer by kregimbald

    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.

    2 replies

    R
    rdiaz5-Regular Member
    5-Regular Member
    February 4, 2014

    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

    • When this option is set to on (the default), the save command saves a document by writing a temporary file, deleting the original file, and then renaming the temporary file to the original name.
    • When this option is set to off, save rewrites the original file directly.
    • The default is on to prevent data loss in the case of insufficient disk space.
    • However, the rename strategy may somtimes fail on certain kinds of network systems.
    • For those situations, setting saverenames to off may resolve the issue.

    Maybe between these two you'll be able to resolve this. If not, let me know what the results were. Thanks!

    K
    kregimbald1-VisitorAuthorAnswer
    1-Visitor
    February 4, 2014

    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.

    Terms & ConditionsAccessibility statement