Re: Rapid SVN Locking issue

There is a difference between the looks of a file/folder and a lock on=20
the working copy. Locks on the working copy stay in place if a command=20
aborts or crashes. You should be able to resolve this with=20
"Extras->Cleanup".

Am 18.02.2014 18:49, schrieb Richard Smith:
> User Group,
>
> I have been using RapidSVN to manage VisualSVN for over a year without
> incident. About a month ago, a folder became locked during a 'commit',
> and the 'commit' never completed. After way too long, I finally closed
> RapidSVN with Task Manager, but when I reopened Rapid, the folder was
> still locked. At that time, I tried various methods of recovery, read
> all of the literature I could find, and ultimately checked out a full
> new =E2=80=98Working Copy', and that did the trick, for the moment.
>
> I have been very careful in how I handle adds, updates and commits, but
> today, the same thing happened. If the repository was not so large and
> didn=E2=80=99t take so long to download a new Working Copy, I would just =
do that
> anytime this happened, but I feel that there must be a way to get around
> this issue.
>
> When I attempt to 'unlock=E2=80=99 (even when I use 'Force') an error com=
es up
> saying that the unlock failed. The Server is Windows Server 2008 32-bit,
> and the RapidSVN is on a Laptop with Windows 7 Enterprise SP1 64-bit.I
> looked at the Server Event Viewer logs, but there are no events from
> today in the VisualSVN Server events log. I have not located the
> RapidSVN logs.
>
> The SeerverSVN is Version 2.6.5, and the RapidSVN is version 0.12.1
> Revision 8257.
>
> Regards,
> *Richard W Smith*| [email protected] <mailto:[email protected]=
m>
> Voice Experience Analyst - Customer Care  | * vht*|   mobile
>   330.328.8349   | desk  330.670.2223
> try a demo:  888.412.2214  |  read
> ourblog<http://info.virtualhold.com/blog>*/
>
> /*
>

------------------------------------------------------
http://rapidsvn.tigris.org/ds/viewMessage.do?dsForumId=3D671&dsMessageId=3D=
3073217

To unsubscribe from this discussion, e-mail: [[email protected]=
gris.org].