can't open .svn\tmp\tempfile.tmp: access is denied

[golan davidovits]

Hi,

We have moved from Tortoise 1.4.x to 1.5.x, and now i see this error many times when trying to commit merge:

can't open .svn\tmp\tempfile.tmp: access is denied

Can you please explain why does it happen and how to resolve?

Thanks,
gzd

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=979752

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

[Simon Large]

2008/12/4 golan davidovits <gola...@yahoo.com>:

> Hi,
>
> We have moved from Tortoise 1.4.x to 1.5.x, and now i see this error many times when trying to commit merge:
>
> can't open .svn\tmp\tempfile.tmp: access is denied
>
>
> Can you please explain why does it happen and how to resolve?

Is your working copy on a SAMBA share?

Simon

--
: ___
: 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=979821

[golan davidovits]

No, the working copy is on local drive.

Simon

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=979821

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=979853

[Stefan Kueng]

golan davidovits wrote:
> Hi,
>
> We have moved from Tortoise 1.4.x to 1.5.x, and now i see this error
> many times when trying to commit merge:
>
> can't open .svn\tmp\tempfile.tmp: access is denied
>
>
> Can you please explain why does it happen and how to resolve?

Disable your virus scanner and try again.

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=980024

[golan davidovits]

Hi,

Unfortunately I see this error too many times. What i found is that the .svn folder somehow turns to read only and adding it write resolve it.

Please let me know if you have resolution for that. Same environment worked with no issue with tortoise 1.4.x

Stefan

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=980024

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=981285

[Stefan Kueng]

golan davidovits wrote:
> Hi,
>
> Unfortunately I see this error too many times. What i found is that
> the .svn folder somehow turns to read only and adding it write
> resolve it.
>
> Please let me know if you have resolution for that. Same environment
> worked with no issue with tortoise 1.4.x

http://tortoisesvn.tigris.org/faq.html#samba

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=981549

[postm...@tigris.org]

I found this problem today; after trying several work arounds I managed to get a successful commitment by creating an exception in my virus scanner.

I cannot disable my virus scanner as part of the IT system at my office forbids it but it does allow me to create exceptions. From within McAfee I created an exception so that the On-Access scanner does not scan any files within the root working directories .svn\ folder when they are either written or read. Before this change I could commit a handful of files successfully but not any complex directory structures. After this change I have managed to commit over 5000 files in a directory structure with at least 5 levels to it.

I had seen the same problem as a few others where parts of the .svn directory structure became read only after attempting to commit. At a guess this is a result of the virus scanner interrupting Tortoise SVN before it finishes and returns the directory to read only. (I am using version 1.5.5 r14063)

Hope this helps some of you;
TafT

> golan davidovits wrote:
> > Hi,
> >
> > Unfortunately I see this error too many times. What i found is that
> > the .svn folder somehow turns to read only and adding it write
> > resolve it.
> >
> > Please let me know if you have resolution for that. Same environment
> > worked with no issue with tortoise 1.4.x
>
> http://tortoisesvn.tigris.org/faq.html#samba
>
> 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=1041322

[Divis, Jason]

I found the following discussion on svn.haxx.se and have a follow-up:

 

On Wed, 21 Jan 2009 07:31:15 -0800 (PST) TafT wrote:

> From within McAfee I created an exception so that the On-Access scanner does not scan any files within

> the root working directories .svn\ folder when they are either written or read. Before this change I could

> commit a handful of files successfully but not any complex directory structures. After this change I have

> managed to commit over 5000 files in a directory structure with at least 5 levels to it.

 

I am seeing a similar situation, but with imports, instead of commits. I too cannot disable the McAfee virus scanner in total. We've created the .svn\ exception, but since there are no .svn\ directories created on the local machine, until a checkout is performed, I don't think that is my solution. Is the work-around to add my working directory that I am importing from, to the McAfee exception list?

 

I realize this is not just an TSVN issue, and that McAfee has its fair share of blame, but it seems that this sort of question might help the TSVN community as a whole, as the McAfee support isn't as accessible as the TSVN support.

 

Thanks in advance for your help.

Divis

 

SE2 Confidentiality Notice: This e-mail and any files transmitted with it are private, confidential and solely for the use of the intended recipient. It may contain material that is legally privileged, proprietary or subject to copyright belonging to SE2 and its subsidiaries, and it may be subject to protection under federal or state law. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this e-mail and delete the material from any computer. Thank you!

[blac...@collab.net]

I faced the same problem in windows XP, the problem did not occur after I dissabled the Antivirus. Thanks a ton!

-Aashish

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1169930

[Simon Large]

2009/2/2 Divis, Jason <jason...@se2.com>:

> I found the following discussion on svn.haxx.se and have a follow-up:
>
> On Wed, 21 Jan 2009 07:31:15 -0800 (PST) TafT wrote:
>> From within McAfee I created an exception so that the On-Access scanner
>> does not scan any files within
>> the root working directories .svn\ folder when they are either written or
>> read. Before this change I could
>> commit a handful of files successfully but not any complex directory
>> structures. After this change I have
>> managed to commit over 5000 files in a directory structure with at least 5
>> levels to it.
>
> I am seeing a similar situation, but with imports, instead of commits. I too
> cannot disable the McAfee virus scanner in total. We've created the .svn\
> exception, but since there are no .svn\ directories created on the local
> machine, until a checkout is performed, I don't think that is my solution.
> Is the work-around to add my working directory that I am importing from, to
> the McAfee exception list?

Tell you what. Since you have the PC which exhibits the problem and we
don't, why don't you try it and see if it works, then report back :-)

> I realize this is not just an TSVN issue, and that McAfee has its fair share
> of blame, but it seems that this sort of question might help the TSVN
> community as a whole, as the McAfee support isn't as accessible as the TSVN
> support.

Your input will be a valuable part of that community resource.

Simon

--
: ___
: 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=1170150

[Adam]

Hi guys,

I've also been seeing this a lot recently and had already assumed it
was a virus scanner issue before finding this thread. I'm currently
trying to get my IT to stop the McAfee on-access scanner from
interfering with any TSVN processes.

In the meantime I thought I would give the command line svn ago to see
if they showed anything different in it's behaviour. The result was it
did, it successfully committed the files. Unfortunately I realised to
late that my command line installation was really out of date and was
actually 1.5.0rc4 (doh!), so it might not be of much use if the
problem is in one of the more recent svn builds.

However it's definitely interesting that the process was still
possible from another client. Maybe its worth others who use other
clients, command line, subversive, subclipse could maybe try commits
with these when they find TSVN stops working.

While I agree that McAfee is at least partly to blame (I hate the damn
thing!) if the effect is specific to TSVN rather than all SVN clients
would this not be something that could be worked around?

If I get another commit that fails I'll try what I've suggested above
with a the v1.5.5 of the command line client.

Adam

On Feb 16, 11:21 am, Simon Large <simon.tortoise...@googlemail.com>
wrote:
> 2009/2/2 Divis, Jason <jason.di...@se2.com>:

> ------------------------------------------------------http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMess...
>
> To unsubscribe from this discussion, e-mail: [users-unsubscr...@tortoisesvn.tigris.org].

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1184664

[Stefan Küng]

Adam wrote:
> Hi guys,
>
> I've also been seeing this a lot recently and had already assumed it
> was a virus scanner issue before finding this thread. I'm currently
> trying to get my IT to stop the McAfee on-access scanner from
> interfering with any TSVN processes.
>
> In the meantime I thought I would give the command line svn ago to see
> if they showed anything different in it's behaviour. The result was it
> did, it successfully committed the files. Unfortunately I realised to
> late that my command line installation was really out of date and was
> actually 1.5.0rc4 (doh!), so it might not be of much use if the
> problem is in one of the more recent svn builds.
>
> However it's definitely interesting that the process was still
> possible from another client. Maybe its worth others who use other
> clients, command line, subversive, subclipse could maybe try commits
> with these when they find TSVN stops working.
>
> While I agree that McAfee is at least partly to blame (I hate the damn
> thing!) if the effect is specific to TSVN rather than all SVN clients
> would this not be something that could be worked around?
>
> If I get another commit that fails I'll try what I've suggested above
> with a the v1.5.5 of the command line client.

The command line client is a console application. Virus scanners treat
console applications differently than windowed applications. That's why
the svn command line client is not as often affected by virus scanners
than TSVN is.

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=1187149

[Adam]

I wasn't aware of that. That would certainly explain things.

I will try to get IT to find a way of getting the damn virus scanner
to mind its own business. Back to my other issue (see coming post ;) )
about merge info.

> ------------------------------------------------------http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMess...
>
> To unsubscribe from this discussion, e-mail: [users-unsubscr...@tortoisesvn.tigris.org].
>
>  signature.asc
> < 1KViewDownload

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1192150

[Mubasher Hanif]

I got into same problem while I committed a larger chunk of files to SVN.

Does anyone found any other good solution other than adding exclusion to McAfee?

-mh

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1257660

[Kurt Pruenner]

Mubasher Hanif wrote:
> Does anyone found any other good solution other than adding exclusion to McAfee?

How about "uninstalling McAfee"?

Sorry, but if the $%&*#@! virus scanner is keeping files locked when
it's not supposed to you're not going to find "another good solution"
unless McAfee get their act together and fix their broken behaviour...

--
Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
.......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
np: Telefon Tel Aviv - You Are the Worst Thing in the World
(Immolate Yourself)

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1261406

[Mubasher Hanif]

> Mubasher Hanif wrote:
> > Does anyone found any other good solution other than adding exclusion to McAfee?
>
> How about "uninstalling McAfee"?
>
> Sorry, but if the $%&*#@! virus scanner is keeping files locked when
> it's not supposed to you're not going to find "another good solution"
> unless McAfee get their act together and fix their broken behaviour...
>
> --
> Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
> .......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
> np: Telefon Tel Aviv - You Are the Worst Thing in the World
> (Immolate Yourself)

Well, with due respect, first of all I can't ask 100 people in my office to uninstall some software and secondly according to our company policy we are not suppose to disable McAfee even for a moment.

Just to mind you it could be broken behavoiur of *Tortoise*. If you read thread and even we had same experience that everything was working perfect with previous version of *Tortoise*.

Anyhow, thanks for your suggestion.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1261982

[Bob Archer]

> Well, with due respect, first of all I can't ask 100 people in my
office
> to uninstall some software and secondly according to our company
policy we
> are not suppose to disable McAfee even for a moment.

Our office policy allows us to add exclusion to the on demand scan list
for McAfee. Also, by default the policy excludes some common dev tools
and folders like c:\projects, c:\dev and a few others.

Can you request exclusions to a directory for this purpose be added to
the corporate policy?

BOb

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1261993

[Simon Large]

2009/3/3 Mubasher Hanif <mubashe...@yahoo.com>:

>> Mubasher Hanif wrote:
>> > Does anyone found any other good solution other than adding exclusion to McAfee?
>>
>> How about "uninstalling McAfee"?
>>
>> Sorry, but if the $%&*#@! virus scanner is keeping files locked when
>> it's not supposed to you're not going to find "another good solution"
>> unless McAfee get their act together and fix their broken behaviour...
>>
>> --
>> Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
>> .......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
>> np: Telefon Tel Aviv - You Are the Worst Thing in the World
>>     (Immolate Yourself)
>
> Well, with due respect, first of all I can't ask 100 people in my office to uninstall some software and secondly according to our company policy we are not suppose to disable McAfee even for a moment.
>
> Just to mind you it could be broken behavoiur of *Tortoise*. If you read thread and even we had same experience that everything was working perfect with previous version of *Tortoise*.
>
> Anyhow, thanks for your suggestion.

All subversion operations are performed by the subversion libraries,
not by TortoiseSVN. And as has already been explained, you won't see
this with the command line client because virus scanners treat console
apps differently. If you think Subversion has broken behaviour then
you need to report it on the subversion mailing list. Be prepared to
back up your claims with solid evidence that the fault is with
subversion and not McAfee.

Simon

--
: ___
: 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=1262007

[Mubasher Hanif]

Simon:

If you read my earlier reply again, then it's clearly stated that "It could be Tortoise". I didn't claim that it is Tortoise. Honestly, I hate to play blame game without evidence.

And the only proof that I have so far that we saw broken/whatever behaviour on three different machines and like I said everything was working perfect on old version of Tortoise and with same version of McAfee.

Again, I am not blaming anyone here and we are going to ask our IT help to push that exclusion in all McAfee installations.

Thanks Bob for your suggestion.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1262508

[Simon Large]

2009/3/3 Mubasher Hanif <mubashe...@yahoo.com>:

>> 2009/3/3 Mubasher Hanif <mubashe...@yahoo.com>:
>> >> Mubasher Hanif wrote:
>> >> > Does anyone found any other good solution other than adding exclusion to McAfee?
>> >>
>> >> How about "uninstalling McAfee"?
>> >>
>> >> Sorry, but if the $%&*#@! virus scanner is keeping files locked when
>> >> it's not supposed to you're not going to find "another good solution"
>> >> unless McAfee get their act together and fix their broken behaviour...
>> >>
>> >> --
>> >> Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
>> >> .......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
>> >> np: Telefon Tel Aviv - You Are the Worst Thing in the World
>> >>     (Immolate Yourself)
>> >
>> > Well, with due respect, first of all I can't ask 100 people in my office to uninstall some software and secondly according to our company policy we are not suppose to disable McAfee even for a moment.
>> >
>> > Just to mind you it could be broken behavoiur of *Tortoise*. If you read thread and even we had same experience that everything was working perfect with previous version of *Tortoise*.
>> >
>> > Anyhow, thanks for your suggestion.
>>
>> All subversion operations are performed by the subversion libraries,
>> not by TortoiseSVN. And as has already been explained, you won't see
>> this with the command line client because virus scanners treat console
>> apps differently. If you think Subversion has broken behaviour then
>> you need to report it on the subversion mailing list. Be prepared to
>> back up your claims with solid evidence that the fault is with
>> subversion and not McAfee.
>

> If you read my earlier reply again, then it's clearly stated that "It could be Tortoise". I didn't claim that it is Tortoise. Honestly, I hate to play blame game without evidence.
>
> And the only proof that I have so far that we saw broken/whatever behaviour on three different machines and like I said everything was working perfect on old version of Tortoise and with same version of McAfee.

I am not trying to shed blame. I only said it is not (or at least very
unlikely to be) Tortoise because that part is done by the SVN library.
I did not say that it is *not* SVN, so if you have evidence to suggest
that it is you need to take it to the subversion users list. But it
would need to be more evidence than "it was working before and it
ain't working now".

> Again, I am not blaming anyone here and we are going to ask our IT help to push that exclusion in all McAfee installations.

That's the best plan for now. Subversion 1.7 will include a completely
rewritten working copy structure using an SQLite database in place of
the .svn folder structure. That may or may not help, but it is a long
way off yet as 1.6 is still in its release cycle.

Simon

--
: ___
: 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=1263540

[Mubasher Hanif]

Thanks for the kind reply and providing us updates about new SVN. I really appreciate when people do follow up with their threads.

OK, lets work together instead of suggesting each other different things and going into details of what you said and what I said.

What do you think what evidence I can provide in such situation. Please advice!

I will be happy to work with you to sort out this problem.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1263853

[Stefan Küng]

Mubasher Hanif wrote:

> Thanks for the kind reply and providing us updates about new SVN. I
> really appreciate when people do follow up with their threads.
>
> OK, lets work together instead of suggesting each other different
> things and going into details of what you said and what I said.
>
> What do you think what evidence I can provide in such situation.
> Please advice!
>
> I will be happy to work with you to sort out this problem.

There's not much you can do besides configure your McAffee scanner to
not interfere.

What has changed in the svn library is that newer versions do more with
the files inside the .svn folders (and the working copy files too). For
example, the permissions on the files are now set explicitely. I guess
that's what your virus scanner interprets as "bad" and interferes. But
that's not really bad but required.

But that's why you can configure a virus scanner to exclude certain
locations - use that feature of your scanner, because that's what it is
there for.

There is no way that Subversion would change the way it treats its *own*
files just because of a virus scanner.

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=1265425

[Mubasher Hanif]

Alright, Thanks Stefan!
--
Mubasher

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1268531

[Milton Spinner]

I had the same error, not able to commit a larger set of files. I updated my version of Tortoise to 1.6.6 and the check-ins worked perfectly. My earlier version was 1.4.3.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2418237