FrameMaker 2022 version 17.0.0.226 locked files not deleting when closing file

[kathyP@cpg]

We just upgrade to FrameMaker 22 version 17.0.0.226. The locked files are not deleting when we close our files. They don't go away so the files don't open. We have had to restart our machines to several time and then they sometimes go away? Is anyboby having this issue and is there a fix for it?

[LinSims]

You don't have to restart your machines. The easiest workaround I've found is to go to the file folder where the .lck files are and delete them when you're done editing.

You could turn off the network locking in FrameMaker Preferences, but don't do that if there's a chance two writers might want to edit the same file.

[kathyP@cpg]

We have done that. When we go to the file folder to delete them. It doesn't delete them.

Changing the preference we would prefer to not do that.

.

[LinSims]

Do you have administrator rights? Can you get them if you don't?

[kathyP@cpg]

yes

[LinSims]

Hmmm. Are you using a CCMS? Although I don't think that should interfere with the .lck files, you're not checking those in, after all. 

I'd try to talk to your IT support people first and find out if there's anything special about your network connections, drive setups, or permissions. I've had issues in the past with FM not deleting the lock files, but I've never not been able to manually delete the lock files. Or if you are using a C/CMS, is there a setting for it to automatically check in everything in whatever your current working folder is (I've used a CCMS, but never installed/configured one).

I think your only other choice is talking to tcssup@adobe.com, unless someone else here has more clues. 

[Barb Binder]

Hi kathyP@cpg:

I second @LinSims's suggestion to reach out to via the support email. When Fm crashes, I open the project folder, sort by file type and quickly delete the .lck files. It's never an issue (though I am working locally with folder-editing permissions). It would be great if you could come back and let us know what this all about, once you have it worked out.

I haven't ported any work files up to 2022 yet, FWIW. Waiting a few weeks after a new release always seems to be the best approach for me. 

~Barb

[LinSims]

I moved because I could. 😃

When I have a moment to catch my breath, I'm going to add the Right Line Indent to all my TOC tags.

Now, if we could just get them to duplicate the functionality of Cudspan's TOCBreaker ....