Cannot rename folders anymore

Hi Mathieu,

This looks like a stale checkout lock. When RDM goes to save a renamed folder, it checks whether anything inside is currently checked out. If a previous session left a lock open without releasing it properly (say, after a crash or an abrupt disconnect), RDM blocks the rename and attempts a new checkout on the folder itself, which then has to be cleared manually before you can try again.

As an administrator, you can release the stuck lock directly from the RDM tree: right-click the affected folder and select Check in. That option is available to admins even when the entry is checked out by someone else. You can also see everything currently locked under View > Opened Sessions > Entry states. And to prevent stale locks from piling up going forward, there's an automatic check-in timeout under Administration > System Settings > Vault.

Please give that a try and let us know if it does the trick for your colleague!

Best regards,

Hi Mathieu,

This looks like a stale checkout lock. When RDM goes to save a renamed folder, it checks whether anything inside is currently checked out. If a previous session left a lock open without releasing it properly (say, after a crash or an abrupt disconnect), RDM blocks the rename and attempts a new checkout on the folder itself, which then has to be cleared manually before you can try again.

As an administrator, you can release the stuck lock directly from the RDM tree: right-click the affected folder and select Check in. That option is available to admins even when the entry is checked out by someone else. You can also see everything currently locked under View > Opened Sessions > Entry states. And to prevent stale locks from piling up going forward, there's an automatic check-in timeout under Administration > System Settings > Vault.

Please give that a try and let us know if it does the trick for your colleague!

Best regards,

@Eduard Sepúlveda López

Good morning Eduard, this doesn't seem to be the issue. The other user himself has no problem manually clearing the locked folder again. Plus I also just logged in with the superadmin and there are currently no entries checked out or stuck in that vault. Weirdly enough, I was able to briefly reproduce this for my own user but it doesn't seem to be occuring for me anymore.

I have enabled the Automatic check-in after 60 minutes, I'll ask the affected user if he can test again in an hour to be absolutely sure.

Edit: An hour has passed since the change, issue still persists.

Hi MathieuVHM,

Thanks for testing that out and keeping us posted.

A couple of things worth trying with the affected user before we dig deeper:
Does a full restart of RDM make any difference? If the error disappears right after a restart but comes back after a while, that would point to something in the client's session state getting confused over time rather than a persistent configuration problem.

Also, before triggering the rename, is there any chance the affected user has a Properties window open for any entry inside that vault, even one that's been minimized or pushed to the background? The error itself says "entries being edited in other windows," which can sometimes refer to open edit dialogs rather than checkout locks. Worth a quick check.

If neither of those leads anywhere, the most useful next step would be a profiler trace captured right when the error occurs. To grab one, the affected user just needs to go to Help > Profiler (how to use the profiler), reproduce the rename, and hit Send trace to Support (direct message with a link to upload the results will be sent) and we'll take a look at what RDM is detecting internally when it blocks the operation.

Best regards,

Does a full restart of RDM make any difference? If the error disappears right after a restart but comes back after a while, that would point to something in the client's session state getting confused over time rather than a persistent configuration problem.

Also, before triggering the rename, is there any chance the affected user has a Properties window open for any entry inside that vault, even one that's been minimized or pushed to the background? The error itself says "entries being edited in other windows," which can sometimes refer to open edit dialogs rather than checkout locks. Worth a quick check.

No to both unfortunately, he can reproduce it by renaming a folder right after restarting RDM. Laptop was also restarted a few times so guessing not a weird Windows thing either.

If neither of those leads anywhere, the most useful next step would be a profiler trace captured right when the error occurs. To grab one, the affected user just needs to go to Help > Profiler (how to use the profiler), reproduce the rename, and hit Send trace to Support (direct message with a link to upload the results will be sent) and we'll take a look at what RDM is detecting internally when it blocks the operation.

User is currently out of office until 6 July so will ask him to provide one next week.