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

Wednesday, March 11, 2009

Yesterday I was trying to add a large directory of files to Subversion. I tried it my usual way, via Subclipse, and got this error: can't open .svn\tmp\tempfile.tmp: access is denied Then I tried with Tortoise. Same thing. I piddled for a bit, with no luck. Off to google I goes, and then I came across this thread on the tortoise list. No need to read it... the bottom line is that the Tortoise folks are blaming McAfee Antivirus for the problem. It just so happens, we use McAfee at work. And, naturally, it's locked down so that I can't do anything about it. Fortunately, our "network guy" here in the office is the model of pragmatism. He works extremely well with us... in short, he's the antithesis of Dilbert's Mordac, the "we will authenticate you by the sound of your scream" IT security dude. So I says to my network guy, "Can you disable McAfee for me so that I can confirm this is the problem". He does so. I try committing the files, and bam, they commit. So, if you're getting that error, your antivirus software may be to blame.

9 comments:

Eric Cobb said...

Awesome find! Thanks for sharing, I'm sure this will come in handy.

davidhenry said...

I have faced the same issue with Mcafee on-access scan. Similar to your situation, an excellent help desk hero was able to grant an exception for my svn directory. This privilege comes with responsibility! Obviously, you must now be very careful what you check out into this directory. I shutter to think of the consequences of a virus getting committed to SVN and then updated to the entire development team.

Marc Esher said...

davidhenry, I don't worry about that for this reason: the .svn directories, which are the ones we added to the exclusion list, are subversion-only directories. they're its swap space, so to speak. they are a client-side artifact, and lots of the IO is temporary. None of the files in a .svn directory are stored in the repository and consequently aren't pulled when you do a checkout. We didn't add an exclusion into mcafee for the actual directories being stored in subversion. So if by some manner of sheer developer dumbassery somehow a file did get put into a svn-controlled directory, mcafee would flag it right away.

sheva said...

Thanks a lot for defining the root of problem!

PhoneixS said...

Thank you.
Disabling it, solve my problem.

Shawn said...

I had the same issue and do run McAfee. Unfortunately disabling McAfee was not an option for me. I found that by rebooting the error went away.

saheel said...

This issue was bugging me for a while now.
Thanks a lot!!

Rich said...

Rebooting has worked in the past but this morning it didn't :(

draymer said...

If you get this error when installing a program..I guarantee a way around it