"SVN Move/Copy and Rename versioned item here" in Windows Explorer no longer works

[Arnoud Berendsen]

Using TortoiseSVN 1.14.5 Build 29465 64 bit on Windows 11

 

Steps to reproduce:

1. Run SVN Cleanup to make sure SVN db is not locked

2. Choose any committed file in any repository

3. Using the RIGHT mouse button, drag and drop the file to any other committed folder in the same Working Copy. A context menu should appear on dropping the file.

4. Choose either of the four options "SVN Move/Copy (and rename) versioned item here". Type a new file name in case "..and rename.." was chosen.

Actual result:

When MOVE is chosen in step 4:

TortoiseSVN shows the following error:

"Subversion reported an error:

Working copy [...] locked.

[...] is already locked.

Please execute the 'Cleanup' command.

When COPY is chosen in step 4:

After thinking about it for a few seconds, TortoiseSVN shows an error dialog reporting the following:

"Subversion reported an error:

sqlite[S5]: database is locked

Additional errors:

sqlite[S5]: database is locked

Another process is blocking the working copy database, or the underlying filesystem does not support file locking; if the working copy is on a network filesystem, make sure file locking has been enabled on the file server.

"

After this, SVN Cleanup must be run to return the WC to a usable state.

Expected result:

File is correctly copied or moved without any errors.

[Stefan]

On Monday, July 3, 2023 at 4:54:14 PM UTC+2 Arnoud Berendsen wrote:

When MOVE is chosen in step 4:

TortoiseSVN shows the following error:

"Subversion reported an error:

Working copy [...] locked.

[...] is already locked.

Please execute the 'Cleanup' command.

works fine for me. Tried on two systems (one Win10, one Win11)

 

When COPY is chosen in step 4:

After thinking about it for a few seconds, TortoiseSVN shows an error dialog reporting the following:

"Subversion reported an error:

sqlite[S5]: database is locked

Additional errors:

sqlite[S5]: database is locked

Another process is blocking the working copy database, or the underlying filesystem does not support file locking; if the working copy is on a network filesystem, make sure file locking has been enabled on the file server.

"

Works fine for me too.

So, is your working copy on an network share?

[Arnoud Berendsen]

I tried multiple working copies of different projects, all of them on a local drive, one that hasn't changed for many years, and where this feature always used to work for me before. I'm also keeping the WCs far away from OneDrive and similar tools as well.

I will investigate more.

Op maandag 3 juli 2023 om 20:27:16 UTC+2 schreef Stefan:

[Daniel Sahlberg]

måndag 3 juli 2023 kl. 21:16:33 UTC+2 skrev Arnoud Berendsen:

I tried multiple working copies of different projects, all of them on a local drive, one that hasn't changed for many years, and where this feature always used to work for me before. I'm also keeping the WCs far away from OneDrive and similar tools as well.

I will investigate more.

I'd suggest using Sysinternals' Process Monitor to check what processes are accessing the working copy. (Make sure you start process monitor as an elevated process)

Kind regards,

Daniel Sahlberg