[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Help - any Angels there?

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 30 Aug 2016 20:12:51 +0200

On 30.08.2016 17:05, L Dobson wrote:
> Hi there,

> The shop put all of my old programmes onto the new machine. These
> included CollabetSubversionServer1.6.3Win32 and Tortoise1.6.12, although
> I couldn't see that anything but the Tortoise was actually installed. I
> followed what I thought were the right instructions and did a clean
> CheckOut onto the new machine [for the first of my 4 repositories].
> However all seemed to work - but only after a good deal of 'CleanUp' etc
> of various folders when all finally reached a green tick.

just FYI:
those tools are way too old.
We're now at version 1.9.4 for TortoiseSVN, and the collabNet server
also is somewhere at 1.9.x.

> To confuse matters, I also reinstalled my CanonZoombrowser Utility and
> this seemed to go through and install a ZbThumnail.nfo file in many
> files. In the past, I've found that, when these are committed, some
> working copies will accept them on Update and others do not with the
> result that some of my working copies [eg Photographs] seem to
> permanently show a red exclamation mark which no amount of Clean ups and
> deleting the Thumbnails seems to sort out all of the copies all of the
> time! Some seem to need the thumbnails and others refuse them!
>
> I rather wonder whether my present problems partly arise from the same base?
>
> So, for the W10 machine's new Working Copy, all seemed ok at first - but
> various folders then gradually developed Red Exclamation Marks! I found
> that a mixture of Cleanup, UndoAdd for new files, revert and deleting
> the Thumbnails was ok - until I tried to Commit!!
>
> The error message was as follows:-*Commit failed - Can't open
> db/txn-current-lock*
> *
> *
> I read the instructions over and couldn't find* *any reference to this
> error, bar checking for Locks on either the Working copy or the
> Repository. There are none. I was too scared to delete the above file
> from the Repository!! The file txn-current-lock and txn-current had not
> been revised since 2009 and both seemed to be zero bytes!!

They're zero bytes because they only serve as locks, i.e. they only have
to be there or not (if they exist, the db is locked, if they don't then
they're not locked).

That error message comes from the server and usually means the server
permissions are not set up properly: the server process needs full
access to the repository path. On Windows, the server process is either
the user SYSTEM or NETWORK.

A very quick web search gives you plenty of hints:
https://www.bing.com/search?q=Commit+failed+-+Can%27t+open+db%2Ftxn-current-lock&pc=MOZI&form=MOZSBR

> However there seemed to be an update to Tortoise which could be
> installed over the earlier version for the 64 bit version of Windows. So
> I downloaded and installed 1.9.4.2785 but nothing seemed to change.
>
> So I checked the Tortoise website again and found the message about the
> problems with the install. As directed I did a Repair and it seemed to
> do that - but it only ran for a couple of seconds with no messages!!
>
> In desperation, I thought to try a new CheckOut but first moved the
> existing Working Copy to a different HDD in the machine [as it had some
> updated files on it], and did the new CheckOut into the space created on
> the disc. Had more problems with the Red Exclamation marks all over and
> cured most by deleting some of the Thumbnails again [how did they get
> there if Commit failed???]. Commit would not work [as there had been no
> changes]!! So I moved one new file into one of the folders and the
> result is as shown on the attachment - a different failure message.
>
> Am I confused in thinking TortoiseSVN doesn't need a separate SVN???

no, TSVN has all the svn libraries included (for a client).

> Also the Working copies have always demanded the Reposiory be on Drive F
> but it is now Drive H and nothing changed when I revised the Drive to F.

drive F or H indicates a network share. Do NOT store working copies on
network shares but only *local* harddrives:
https://tortoisesvn.net/faq.html#wconshare

>
> I'm in heart attack/stroke country now and far beyond my limited
> competence!!! Is there any chance you will advise me if and how I can
> get out of these problems as there don't seem to be many SVN-type folk
> standing around, especially in France where I am until October.

the error message in your screenshot also indicates that you store your
working copy on a network share. Again: do NOT do that!
And if your repository is stored on a network share, don't do that either:
https://tortoisesvn.net/faq.html#reponoserver

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3184282
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-08-30 20:13:03 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.