You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Daniele Pedroni <pe...@zapispa.it> on 2015/09/04 17:15:11 UTC
Access denied error on checkout-commit after updating to 1.9.X
After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN as well as command line throw the following error after trying to checkout or commit a Working Directory on a network share:
Commit failed (details follow):
Can't move 'U:\1-Administration\Management\.svn\tmp\svn-ADD80C28' to
'U:\1-Administration\Management\.svn\pristine\b7\b7c3f06170d83d3aac6b4489b78c4c8509c70ed6.svn-base':
Access is denied.
(full discussion on TSVN mailing list here: https://groups.google.com/forum/#!topic/tortoisesvn/Goi-Ay3BV6U )
It seems to be a Subversion issue, not a TortoiseSVN one, since command line acts exactly the same as TSVN: everything fine with local paths, issues with network drives. Sometimes, trying more and more, the checkout/commit succeeds also on network share, but it is a random occurrence.
Any clue? As you can see in the suggested link, it seems that everyone who works on network drive has the same problem: something has been changed or broken in 1.9.X release about it? I didn't find anything about it.
Thank you in advance
Daniele P.
Zapi Spa - Societ? per Azioni con Unico Socio - Via Parma, 59, 42028 Poviglio (RE) - Tel. +39 0522 960050 - Fax +39 0522 960259 - E-mail: zapi@zapispa.it - web site: www.zapispa.it - Capitale Sociale EUR 2.582.500,00 - Iscrizione Registro Imprese di Reggio Emilia n. 00794070342 - C.F. 00794070342 - P. IVA 01184200358
AVVERTENZA: Ai sensi del Codice Privacy DLGS n.196/03 si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio Le fosse pervenuto per errore La preghiamo di eliminarlo senza copiarlo, di non inoltrarlo a terzi e di darcene tempestiva comunicazione. According to Privacy Code DLGS n.196/03 we state that the information contained in this message are contidential and for the exclusive use of the receveir. In case the message reached you by mistake, we kindly ask you to delete it without copying it, not to send it to others and to inform us about it immediately.
Rispetta l'ambiente: non stampare questa e-mail se non ti ? necessario. Please consider your environmental responsability before printing this e-mail.
Re: Access denied error on checkout-commit after updating to 1.9.X
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On 7 September 2015 at 19:45, Ivan Zhakov <iv...@visualsvn.com> wrote:
> [Moving to dev@s.a.o]
>
> On 4 September 2015 at 18:15, Daniele Pedroni
> <pe...@zapispa.it> wrote:
>> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN
>> as well as command line throw the following error after trying to checkout
>> or commit a Working Directory on a network share:
>>
>> Commit failed (details follow):
>> Can't move 'U:\1-Administration\Management\.svn\tmp\svn-ADD80C28' to
>>
>> 'U:\1-Administration\Management\.svn\pristine\b7\b7c3f06170d83d3aac6b4489b78c4c8509c70ed6.svn-base':
>> Access is denied.
>>
>> (full discussion on TSVN mailing list here:
>> https://groups.google.com/forum/#!topic/tortoisesvn/Goi-Ay3BV6U )
>>
>> It seems to be a Subversion issue, not a TortoiseSVN one, since command line
>> acts exactly the same as TSVN: everything fine with local paths, issues with
>> network drives. Sometimes, trying more and more, the checkout/commit
>> succeeds also on network share, but it is a random occurrence.
>>
>> Any clue? As you can see in the suggested link, it seems that everyone who
>> works on network drive has the same problem: something has been changed or
>> broken in 1.9.X release about it? I didn’t find anything about it.
>>
> Bert and I were able to reproduce this issue with help from Daniele
> and Marco. In short: Subversion 1.9.x doesn't work with working copies
> stored on SMBv1 network shares (i.e. hosted on Windows XP/Windows
> Server 2003 or Windows Server 2008 with SMBv2 disabled). It is not
> related to background antivirus/indexers. So the bug affects many
> users.
>
> While r1701298 fix still makes sense to workaround background
> antivirus/indexers it doesn't help to fix Access Denied errors on
> SMBv1 network shares.
>
> In nutshell problem is that SetFileInformationByHandle() API cannot be
> called more than once if first call failed for any reason for SMBv1
> shares. We retry SetFileInformationByHandle() call if destination
> directory doesn't exist or if we rename over read-only file. It works
> fine for local directories or SMBv2 shares, but doesn't work for SMBv1
> network shares. SetFileInformationByHandle() returns
> ERROR_ACCESS_DENIED without even sending request to SMB server.
>
> We developed patch that converts all ERROR_ACCESS_DENIED errors from
> SetFileInformationByHandle() to SVN_ERR_UNSUPPORTED_FEATURE and
> fallbacks to normal close + rename() (see attached file), but I'm not
> sure it's the best solution and going to investigate this problem
> tomorrow.
>
I didn't find better solution and committed this patch in r1701736.
--
Ivan Zhakov
CTO | VisualSVN | http://www.visualsvn.com
Re: Access denied error on checkout-commit after updating to 1.9.X
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On 7 September 2015 at 19:45, Ivan Zhakov <iv...@visualsvn.com> wrote:
> [Moving to dev@s.a.o]
>
> On 4 September 2015 at 18:15, Daniele Pedroni
> <pe...@zapispa.it> wrote:
>> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN
>> as well as command line throw the following error after trying to checkout
>> or commit a Working Directory on a network share:
>>
>> Commit failed (details follow):
>> Can't move 'U:\1-Administration\Management\.svn\tmp\svn-ADD80C28' to
>>
>> 'U:\1-Administration\Management\.svn\pristine\b7\b7c3f06170d83d3aac6b4489b78c4c8509c70ed6.svn-base':
>> Access is denied.
>>
>> (full discussion on TSVN mailing list here:
>> https://groups.google.com/forum/#!topic/tortoisesvn/Goi-Ay3BV6U )
>>
>> It seems to be a Subversion issue, not a TortoiseSVN one, since command line
>> acts exactly the same as TSVN: everything fine with local paths, issues with
>> network drives. Sometimes, trying more and more, the checkout/commit
>> succeeds also on network share, but it is a random occurrence.
>>
>> Any clue? As you can see in the suggested link, it seems that everyone who
>> works on network drive has the same problem: something has been changed or
>> broken in 1.9.X release about it? I didn’t find anything about it.
>>
> Bert and I were able to reproduce this issue with help from Daniele
> and Marco. In short: Subversion 1.9.x doesn't work with working copies
> stored on SMBv1 network shares (i.e. hosted on Windows XP/Windows
> Server 2003 or Windows Server 2008 with SMBv2 disabled). It is not
> related to background antivirus/indexers. So the bug affects many
> users.
>
> While r1701298 fix still makes sense to workaround background
> antivirus/indexers it doesn't help to fix Access Denied errors on
> SMBv1 network shares.
>
> In nutshell problem is that SetFileInformationByHandle() API cannot be
> called more than once if first call failed for any reason for SMBv1
> shares. We retry SetFileInformationByHandle() call if destination
> directory doesn't exist or if we rename over read-only file. It works
> fine for local directories or SMBv2 shares, but doesn't work for SMBv1
> network shares. SetFileInformationByHandle() returns
> ERROR_ACCESS_DENIED without even sending request to SMB server.
>
> We developed patch that converts all ERROR_ACCESS_DENIED errors from
> SetFileInformationByHandle() to SVN_ERR_UNSUPPORTED_FEATURE and
> fallbacks to normal close + rename() (see attached file), but I'm not
> sure it's the best solution and going to investigate this problem
> tomorrow.
>
I didn't find better solution and committed this patch in r1701736.
--
Ivan Zhakov
CTO | VisualSVN | http://www.visualsvn.com
Re: Access denied error on checkout-commit after updating to 1.9.X
Posted by Ivan Zhakov <iv...@visualsvn.com>.
[Moving to dev@s.a.o]
On 4 September 2015 at 18:15, Daniele Pedroni
<pe...@zapispa.it> wrote:
> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN
> as well as command line throw the following error after trying to checkout
> or commit a Working Directory on a network share:
>
> Commit failed (details follow):
> Can't move 'U:\1-Administration\Management\.svn\tmp\svn-ADD80C28' to
>
> 'U:\1-Administration\Management\.svn\pristine\b7\b7c3f06170d83d3aac6b4489b78c4c8509c70ed6.svn-base':
> Access is denied.
>
> (full discussion on TSVN mailing list here:
> https://groups.google.com/forum/#!topic/tortoisesvn/Goi-Ay3BV6U )
>
> It seems to be a Subversion issue, not a TortoiseSVN one, since command line
> acts exactly the same as TSVN: everything fine with local paths, issues with
> network drives. Sometimes, trying more and more, the checkout/commit
> succeeds also on network share, but it is a random occurrence.
>
> Any clue? As you can see in the suggested link, it seems that everyone who
> works on network drive has the same problem: something has been changed or
> broken in 1.9.X release about it? I didn’t find anything about it.
>
Bert and I were able to reproduce this issue with help from Daniele
and Marco. In short: Subversion 1.9.x doesn't work with working copies
stored on SMBv1 network shares (i.e. hosted on Windows XP/Windows
Server 2003 or Windows Server 2008 with SMBv2 disabled). It is not
related to background antivirus/indexers. So the bug affects many
users.
While r1701298 fix still makes sense to workaround background
antivirus/indexers it doesn't help to fix Access Denied errors on
SMBv1 network shares.
In nutshell problem is that SetFileInformationByHandle() API cannot be
called more than once if first call failed for any reason for SMBv1
shares. We retry SetFileInformationByHandle() call if destination
directory doesn't exist or if we rename over read-only file. It works
fine for local directories or SMBv2 shares, but doesn't work for SMBv1
network shares. SetFileInformationByHandle() returns
ERROR_ACCESS_DENIED without even sending request to SMB server.
We developed patch that converts all ERROR_ACCESS_DENIED errors from
SetFileInformationByHandle() to SVN_ERR_UNSUPPORTED_FEATURE and
fallbacks to normal close + rename() (see attached file), but I'm not
sure it's the best solution and going to investigate this problem
tomorrow.
--
Ivan Zhakov
Re: Access denied error on checkout-commit after updating to 1.9.X
Posted by Ivan Zhakov <iv...@visualsvn.com>.
[Moving to dev@s.a.o]
On 4 September 2015 at 18:15, Daniele Pedroni
<pe...@zapispa.it> wrote:
> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN
> as well as command line throw the following error after trying to checkout
> or commit a Working Directory on a network share:
>
> Commit failed (details follow):
> Can't move 'U:\1-Administration\Management\.svn\tmp\svn-ADD80C28' to
>
> 'U:\1-Administration\Management\.svn\pristine\b7\b7c3f06170d83d3aac6b4489b78c4c8509c70ed6.svn-base':
> Access is denied.
>
> (full discussion on TSVN mailing list here:
> https://groups.google.com/forum/#!topic/tortoisesvn/Goi-Ay3BV6U )
>
> It seems to be a Subversion issue, not a TortoiseSVN one, since command line
> acts exactly the same as TSVN: everything fine with local paths, issues with
> network drives. Sometimes, trying more and more, the checkout/commit
> succeeds also on network share, but it is a random occurrence.
>
> Any clue? As you can see in the suggested link, it seems that everyone who
> works on network drive has the same problem: something has been changed or
> broken in 1.9.X release about it? I didn’t find anything about it.
>
Bert and I were able to reproduce this issue with help from Daniele
and Marco. In short: Subversion 1.9.x doesn't work with working copies
stored on SMBv1 network shares (i.e. hosted on Windows XP/Windows
Server 2003 or Windows Server 2008 with SMBv2 disabled). It is not
related to background antivirus/indexers. So the bug affects many
users.
While r1701298 fix still makes sense to workaround background
antivirus/indexers it doesn't help to fix Access Denied errors on
SMBv1 network shares.
In nutshell problem is that SetFileInformationByHandle() API cannot be
called more than once if first call failed for any reason for SMBv1
shares. We retry SetFileInformationByHandle() call if destination
directory doesn't exist or if we rename over read-only file. It works
fine for local directories or SMBv2 shares, but doesn't work for SMBv1
network shares. SetFileInformationByHandle() returns
ERROR_ACCESS_DENIED without even sending request to SMB server.
We developed patch that converts all ERROR_ACCESS_DENIED errors from
SetFileInformationByHandle() to SVN_ERR_UNSUPPORTED_FEATURE and
fallbacks to normal close + rename() (see attached file), but I'm not
sure it's the best solution and going to investigate this problem
tomorrow.
--
Ivan Zhakov
Re: Access denied error on checkout-commit after updating to 1.9.X
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On 8 September 2015 at 13:12, Branko Čibej <br...@wandisco.com> wrote:
> On 07.09.2015 18:42, Ivan Zhakov wrote:
>> We developed patch that converts all ERROR_ACCESS_DENIED errors from
>> SetFileInformationByHandle() to SVN_ERR_UNSUPPORTED_FEATURE and
>> fallbacks to normal close + rename() (see attached file), but I'm not
>> sure it's the best solution and going to investigate this problem
>> tomorrow.
>
> Ideally, there'd be a way to check if the 'access denied' error is real,
> or just a side effect of SMBv1. But I can't think of a reasonable way to
> do this without (probably) incurring an unacceptable slowdown in the WC.
>
Agree. But I think r1701736 approach is acceptable, given that
RenameByHandle code is performance optimization and 'access denied'
error only happens when we retry rename after finding that target
directory doesn't exists. So generally we don't get these access
denied errors.
--
Ivan Zhakov
Re: Access denied error on checkout-commit after updating to 1.9.X
Posted by Branko Čibej <br...@wandisco.com>.
On 07.09.2015 18:42, Ivan Zhakov wrote:
> We developed patch that converts all ERROR_ACCESS_DENIED errors from
> SetFileInformationByHandle() to SVN_ERR_UNSUPPORTED_FEATURE and
> fallbacks to normal close + rename() (see attached file), but I'm not
> sure it's the best solution and going to investigate this problem
> tomorrow.
Ideally, there'd be a way to check if the 'access denied' error is real,
or just a side effect of SMBv1. But I can't think of a reasonable way to
do this without (probably) incurring an unacceptable slowdown in the WC.
-- Brane
Re: Access denied error on checkout-commit after updating to 1.9.X
Posted by Ivan Zhakov <iv...@visualsvn.com>.
[Moving to dev@s.a.o]
On 4 September 2015 at 18:15, Daniele Pedroni
<pe...@zapispa.it> wrote:
> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN
> as well as command line throw the following error after trying to checkout
> or commit a Working Directory on a network share:
>
> Commit failed (details follow):
> Can't move 'U:\1-Administration\Management\.svn\tmp\svn-ADD80C28' to
>
> 'U:\1-Administration\Management\.svn\pristine\b7\b7c3f06170d83d3aac6b4489b78c4c8509c70ed6.svn-base':
> Access is denied.
>
> (full discussion on TSVN mailing list here:
> https://groups.google.com/forum/#!topic/tortoisesvn/Goi-Ay3BV6U )
>
> It seems to be a Subversion issue, not a TortoiseSVN one, since command line
> acts exactly the same as TSVN: everything fine with local paths, issues with
> network drives. Sometimes, trying more and more, the checkout/commit
> succeeds also on network share, but it is a random occurrence.
>
> Any clue? As you can see in the suggested link, it seems that everyone who
> works on network drive has the same problem: something has been changed or
> broken in 1.9.X release about it? I didn’t find anything about it.
>
Bert and I were able to reproduce this issue with help from Daniele
and Marco. In short: Subversion 1.9.x doesn't work with working copies
stored on SMBv1 network shares (i.e. hosted on Windows XP/Windows
Server 2003 or Windows Server 2008 with SMBv2 disabled). It is not
related to background antivirus/indexers. So the bug affects many
users.
While r1701298 fix still makes sense to workaround background
antivirus/indexers it doesn't help to fix Access Denied errors on
SMBv1 network shares.
In nutshell problem is that SetFileInformationByHandle() API cannot be
called more than once if first call failed for any reason for SMBv1
shares. We retry SetFileInformationByHandle() call if destination
directory doesn't exist or if we rename over read-only file. It works
fine for local directories or SMBv2 shares, but doesn't work for SMBv1
network shares. SetFileInformationByHandle() returns
ERROR_ACCESS_DENIED without even sending request to SMB server.
We developed patch that converts all ERROR_ACCESS_DENIED errors from
SetFileInformationByHandle() to SVN_ERR_UNSUPPORTED_FEATURE and
fallbacks to normal close + rename() (see attached file), but I'm not
sure it's the best solution and going to investigate this problem
tomorrow.
--
Ivan Zhakov
Re: R: Access denied error on checkout-commit after updating to 1.9.X
Posted by Marco Pelagatti <mp...@gmail.com>.
Branko Čibej <brane <at> wandisco.com> writes:
>
> On 07.09.2015 10:45, Daniele Pedroni wrote:
> > Hi Ivan,
> >
> > yes, definitely, thank you a lot!
> >
> > So, if I got your point, with your updated svn.exe I'll be able to
test if command line work properly, but
> I'll have to wait for TortoiseSVN update to use it? Or the latter relies
on the same svn.exe so it should work
> as well after the update?
>
> You'll have to wait for the TortoiseSVN update; TSVN doesn't call
> svn.exe, it uses our libraries. So you'll also have to wait for the
> Subversion 1.9.2 release.
>
Hi,
I have the very same problem here. Please keep us posted on your progress.
If you want me to make some test, just let me know.
Thanks!
Marco
Re: R: Access denied error on checkout-commit after updating to 1.9.X
Posted by Branko Čibej <br...@wandisco.com>.
On 07.09.2015 10:45, Daniele Pedroni wrote:
> Hi Ivan,
>
> yes, definitely, thank you a lot!
>
> So, if I got your point, with your updated svn.exe I'll be able to test if command line work properly, but I'll have to wait for TortoiseSVN update to use it? Or the latter relies on the same svn.exe so it should work as well after the update?
You'll have to wait for the TortoiseSVN update; TSVN doesn't call
svn.exe, it uses our libraries. So you'll also have to wait for the
Subversion 1.9.2 release.
-- Brane
> -----Messaggio originale-----
> Da: Ivan Zhakov [mailto:ivan@visualsvn.com]
> Inviato: lunedì 7 settembre 2015 10:27
> A: Daniele Pedroni
> Cc: users@subversion.apache.org
> Oggetto: Re: Access denied error on checkout-commit after updating to 1.9.X
>
> On 7 September 2015 at 11:12, Daniele Pedroni <pe...@zapispa.it> wrote:
>> Hi Ivan,
>>
>> thank you very much, but honestly speaking I don't know how to test it: I installed SVN server through Redmine Bitnami package, and I update SVN on my PC using TortoiseSVN installer.
>> If you provide me some suggestions about how to test it, I'll try it!
>>
>> Looking forward to hear from you soon,
>>
> Hi Daniele,
>
> This is client-side bug, there is no need to update server-side to test it. To test I'll send you compiled svn.exe, then you just need to extract it and run svn.exe update. Does it work for you?
>
>
> --
> Ivan Zhakov
> Zapi Spa - Società per Azioni con Unico Socio - Via Parma, 59, 42028 Poviglio (RE) - Tel. +39 0522 960050 - Fax +39 0522 960259 - E-mail: zapi@zapispa.it - web site: www.zapispa.it - Capitale Sociale € 2.582.500,00 - Iscrizione Registro Imprese di Reggio Emilia n. 00794070342 - C.F. 00794070342 - P. IVA 01184200358
> AVVERTENZA: Ai sensi del Codice Privacy DLGS n.196/03 si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio Le fosse pervenuto per errore La preghiamo di eliminarlo senza copiarlo, di non inoltrarlo a terzi e di darcene tempestiva comunicazione. According to Privacy Code DLGS n.196/03 we state that the information contained in this message are contidential and for the exclusive use of the receveir. In case the message reached you by mistake, we kindly ask you to delete it without copying it, not to send it to others and to inform us about it immediately.
> Rispetta l'ambiente: non stampare questa e-mail se non ti è necessario. Please consider your environmental responsability before printing this e-mail.
R: Access denied error on checkout-commit after updating to 1.9.X
Posted by Daniele Pedroni <pe...@zapispa.it>.
Hi Ivan,
yes, definitely, thank you a lot!
So, if I got your point, with your updated svn.exe I'll be able to test if command line work properly, but I'll have to wait for TortoiseSVN update to use it? Or the latter relies on the same svn.exe so it should work as well after the update?
Daniele Pedroni
Embedded Software Engineer
ZAPI S.p.A. - Via Parma 59, 42028 Poviglio (RE) Italy
Tel +39 0522 960050 - Fax +39 0522 960259
pedroni.daniele@zapispa.it
http://www.zapispa.it/
Rispetta l'ambiente: non stampare questa e-mail se non ti è necessario.
Please consider your environmental responsibility before printing this e-mail.
-----Messaggio originale-----
Da: Ivan Zhakov [mailto:ivan@visualsvn.com]
Inviato: lunedì 7 settembre 2015 10:27
A: Daniele Pedroni
Cc: users@subversion.apache.org
Oggetto: Re: Access denied error on checkout-commit after updating to 1.9.X
On 7 September 2015 at 11:12, Daniele Pedroni <pe...@zapispa.it> wrote:
> Hi Ivan,
>
> thank you very much, but honestly speaking I don't know how to test it: I installed SVN server through Redmine Bitnami package, and I update SVN on my PC using TortoiseSVN installer.
> If you provide me some suggestions about how to test it, I'll try it!
>
> Looking forward to hear from you soon,
>
Hi Daniele,
This is client-side bug, there is no need to update server-side to test it. To test I'll send you compiled svn.exe, then you just need to extract it and run svn.exe update. Does it work for you?
--
Ivan Zhakov
Zapi Spa - Società per Azioni con Unico Socio - Via Parma, 59, 42028 Poviglio (RE) - Tel. +39 0522 960050 - Fax +39 0522 960259 - E-mail: zapi@zapispa.it - web site: www.zapispa.it - Capitale Sociale € 2.582.500,00 - Iscrizione Registro Imprese di Reggio Emilia n. 00794070342 - C.F. 00794070342 - P. IVA 01184200358
AVVERTENZA: Ai sensi del Codice Privacy DLGS n.196/03 si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio Le fosse pervenuto per errore La preghiamo di eliminarlo senza copiarlo, di non inoltrarlo a terzi e di darcene tempestiva comunicazione. According to Privacy Code DLGS n.196/03 we state that the information contained in this message are contidential and for the exclusive use of the receveir. In case the message reached you by mistake, we kindly ask you to delete it without copying it, not to send it to others and to inform us about it immediately.
Rispetta l'ambiente: non stampare questa e-mail se non ti è necessario. Please consider your environmental responsability before printing this e-mail.
Re: Access denied error on checkout-commit after updating to 1.9.X
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On 7 September 2015 at 11:12, Daniele Pedroni
<pe...@zapispa.it> wrote:
> Hi Ivan,
>
> thank you very much, but honestly speaking I don't know how to test it: I installed SVN server through Redmine Bitnami package, and I update SVN on my PC using TortoiseSVN installer.
> If you provide me some suggestions about how to test it, I'll try it!
>
> Looking forward to hear from you soon,
>
Hi Daniele,
This is client-side bug, there is no need to update server-side to
test it. To test I'll send you compiled svn.exe, then you just need to
extract it and run svn.exe update. Does it work for you?
--
Ivan Zhakov
R: Access denied error on checkout-commit after updating to 1.9.X
Posted by Daniele Pedroni <pe...@zapispa.it>.
Hi Ivan,
thank you very much, but honestly speaking I don't know how to test it: I installed SVN server through Redmine Bitnami package, and I update SVN on my PC using TortoiseSVN installer.
If you provide me some suggestions about how to test it, I'll try it!
Looking forward to hear from you soon,
Best regards.
Daniele Pedroni
Embedded Software Engineer
ZAPI S.p.A. - Via Parma 59, 42028 Poviglio (RE) Italy
Tel +39 0522 960050 - Fax +39 0522 960259
pedroni.daniele@zapispa.it
http://www.zapispa.it/
Rispetta l'ambiente: non stampare questa e-mail se non ti è necessario.
Please consider your environmental responsibility before printing this e-mail.
-----Messaggio originale-----
Da: Ivan Zhakov [mailto:ivan@visualsvn.com]
Inviato: sabato 5 settembre 2015 18:58
A: Daniele Pedroni
Cc: users@subversion.apache.org
Oggetto: Re: Access denied error on checkout-commit after updating to 1.9.X
On 4 September 2015 at 18:15, Daniele Pedroni <pe...@zapispa.it> wrote:
> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck),
> TortoiseSVN as well as command line throw the following error after
> trying to checkout or commit a Working Directory on a network share:
>
> Commit failed (details follow):
> Can't move 'U:\1-Administration\Management\.svn\tmp\svn-ADD80C28' to
>
> 'U:\1-Administration\Management\.svn\pristine\b7\b7c3f06170d83d3aac6b4489b78c4c8509c70ed6.svn-base':
> Access is denied.
>
>
> (full discussion on TSVN mailing list here:
> https://groups.google.com/forum/#!topic/tortoisesvn/Goi-Ay3BV6U )
>
>
> It seems to be a Subversion issue, not a TortoiseSVN one, since
> command line acts exactly the same as TSVN: everything fine with local
> paths, issues with network drives. Sometimes, trying more and more,
> the checkout/commit succeeds also on network share, but it is a random occurrence.
>
> Any clue? As you can see in the suggested link, it seems that everyone
> who works on network drive has the same problem: something has been
> changed or broken in 1.9.X release about it? I didn’t find anything about it.
>
I've attempted to fix this problem in r1701298 [1]. Could you test it?
I may provide development build of Subversion with this fix if needed.
[1] http://svn.apache.org/r1701298
--
Ivan Zhakov
Zapi Spa - Società per Azioni con Unico Socio - Via Parma, 59, 42028 Poviglio (RE) - Tel. +39 0522 960050 - Fax +39 0522 960259 - E-mail: zapi@zapispa.it - web site: www.zapispa.it - Capitale Sociale € 2.582.500,00 - Iscrizione Registro Imprese di Reggio Emilia n. 00794070342 - C.F. 00794070342 - P. IVA 01184200358
AVVERTENZA: Ai sensi del Codice Privacy DLGS n.196/03 si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio Le fosse pervenuto per errore La preghiamo di eliminarlo senza copiarlo, di non inoltrarlo a terzi e di darcene tempestiva comunicazione. According to Privacy Code DLGS n.196/03 we state that the information contained in this message are contidential and for the exclusive use of the receveir. In case the message reached you by mistake, we kindly ask you to delete it without copying it, not to send it to others and to inform us about it immediately.
Rispetta l'ambiente: non stampare questa e-mail se non ti è necessario. Please consider your environmental responsability before printing this e-mail.
Re: Access denied error on checkout-commit after updating to 1.9.X
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On 4 September 2015 at 18:15, Daniele Pedroni
<pe...@zapispa.it> wrote:
> After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN
> as well as command line throw the following error after trying to checkout
> or commit a Working Directory on a network share:
>
> Commit failed (details follow):
> Can't move 'U:\1-Administration\Management\.svn\tmp\svn-ADD80C28' to
>
> 'U:\1-Administration\Management\.svn\pristine\b7\b7c3f06170d83d3aac6b4489b78c4c8509c70ed6.svn-base':
> Access is denied.
>
>
> (full discussion on TSVN mailing list here:
> https://groups.google.com/forum/#!topic/tortoisesvn/Goi-Ay3BV6U )
>
>
> It seems to be a Subversion issue, not a TortoiseSVN one, since command line
> acts exactly the same as TSVN: everything fine with local paths, issues with
> network drives. Sometimes, trying more and more, the checkout/commit
> succeeds also on network share, but it is a random occurrence.
>
> Any clue? As you can see in the suggested link, it seems that everyone who
> works on network drive has the same problem: something has been changed or
> broken in 1.9.X release about it? I didn’t find anything about it.
>
I've attempted to fix this problem in r1701298 [1]. Could you test it?
I may provide development build of Subversion with this fix if needed.
[1] http://svn.apache.org/r1701298
--
Ivan Zhakov
R: Access denied error on checkout-commit after updating to 1.9.X
Posted by Daniele Pedroni <pe...@zapispa.it>.
Yes Bert, you’re right, my explanation wasn’t 100% clear: I meant that everyone who pointed out this issue was using SVN on network drives.
I’m using svnserve service on a windows 2003 server with F-Secure 11.01; my PC has Windows 7 x64 with F-Secure 12.00. I tried disabling the antivirus on my pc, without any luck, but I didn’t try on server side.
Daniele Pedroni
________________________________
[Zlogo]
Embedded Software Engineer
ZAPI S.p.A. - Via Parma 59, 42028 Poviglio (RE) Italy
Tel +39 0522 960050 - Fax +39 0522 960259
pedroni.daniele@zapispa.it<ma...@zapispa.it>
http://www.zapispa.it/
P Rispetta l'ambiente: non stampare questa e-mail se non ti è necessario.
Please consider your environmental responsibility before printing this e-mail.
Da: Bert Huijben [mailto:bert@qqmail.nl]
Inviato: sabato 5 settembre 2015 18:36
A: Daniele Pedroni; users@subversion.apache.org
Oggetto: RE: Access denied error on checkout-commit after updating to 1.9.X
I have no problem using Subversion on 1.9.x on network drives, testing to Windows servers and to Samba 4.x, so clearly not everyone using Subversion on a network drive has this problem.
Perhaps you tried to say that most users seeing this problem have it on a network drive?
Are there other common similarities?
Are you all using the same virus scanner on either the client or the server, or the same windows version on client and/or server? (Or not even using Windows at all on the server?)
Bert
From: Daniele Pedroni [mailto:pedroni.daniele@zapispa.it]
Sent: vrijdag 4 september 2015 17:15
To: users@subversion.apache.org<ma...@subversion.apache.org>
Subject: Access denied error on checkout-commit after updating to 1.9.X
After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN as well as command line throw the following error after trying to checkout or commit a Working Directory on a network share:
Commit failed (details follow):
Can't move 'U:\1-Administration\Management\.svn\tmp\svn-ADD80C28' to
'U:\1-Administration\Management\.svn\pristine\b7\b7c3f06170d83d3aac6b4489b78c4c8509c70ed6.svn-base':
Access is denied.
(full discussion on TSVN mailing list here: https://groups.google.com/forum/#!topic/tortoisesvn/Goi-Ay3BV6U )
It seems to be a Subversion issue, not a TortoiseSVN one, since command line acts exactly the same as TSVN: everything fine with local paths, issues with network drives. Sometimes, trying more and more, the checkout/commit succeeds also on network share, but it is a random occurrence.
Any clue? As you can see in the suggested link, it seems that everyone who works on network drive has the same problem: something has been changed or broken in 1.9.X release about it? I didn’t find anything about it.
Thank you in advance
Daniele P.
Zapi Spa - Società per Azioni con Unico Socio - Via Parma, 59, 42028 Poviglio (RE) - Tel. +39 0522 960050 - Fax +39 0522 960259 - E-mail: zapi@zapispa.it<ma...@zapispa.it> - web site: www.zapispa.it<http://www.zapispa.it> - Capitale Sociale € 2.582.500,00 - Iscrizione Registro Imprese di Reggio Emilia n. 00794070342 - C.F. 00794070342 - P. IVA 01184200358
AVVERTENZA: Ai sensi del Codice Privacy DLGS n.196/03 si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio Le fosse pervenuto per errore La preghiamo di eliminarlo senza copiarlo, di non inoltrarlo a terzi e di darcene tempestiva comunicazione. According to Privacy Code DLGS n.196/03 we state that the information contained in this message are contidential and for the exclusive use of the receveir. In case the message reached you by mistake, we kindly ask you to delete it without copying it, not to send it to others and to inform us about it immediately.
Rispetta l'ambiente: non stampare questa e-mail se non ti è necessario. Please consider your environmental responsability before printing this e-mail.
Zapi Spa - Società per Azioni con Unico Socio - Via Parma, 59, 42028 Poviglio (RE) - Tel. +39 0522 960050 - Fax +39 0522 960259 - E-mail: zapi@zapispa.it - web site: www.zapispa.it - Capitale Sociale € 2.582.500,00 - Iscrizione Registro Imprese di Reggio Emilia n. 00794070342 - C.F. 00794070342 - P. IVA 01184200358
AVVERTENZA: Ai sensi del Codice Privacy DLGS n.196/03 si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio Le fosse pervenuto per errore La preghiamo di eliminarlo senza copiarlo, di non inoltrarlo a terzi e di darcene tempestiva comunicazione. According to Privacy Code DLGS n.196/03 we state that the information contained in this message are contidential and for the exclusive use of the receveir. In case the message reached you by mistake, we kindly ask you to delete it without copying it, not to send it to others and to inform us about it immediately.
Rispetta l'ambiente: non stampare questa e-mail se non ti è necessario. Please consider your environmental responsability before printing this e-mail.
RE: Access denied error on checkout-commit after updating to 1.9.X
Posted by Bert Huijben <be...@qqmail.nl>.
I have no problem using Subversion on 1.9.x on network drives, testing to Windows servers and to Samba 4.x, so clearly not everyone using Subversion on a network drive has this problem.
Perhaps you tried to say that most users seeing this problem have it on a network drive?
Are there other common similarities?
Are you all using the same virus scanner on either the client or the server, or the same windows version on client and/or server? (Or not even using Windows at all on the server?)
Bert
From: Daniele Pedroni [mailto:pedroni.daniele@zapispa.it]
Sent: vrijdag 4 september 2015 17:15
To: users@subversion.apache.org
Subject: Access denied error on checkout-commit after updating to 1.9.X
After updating from 1.8.X to 1.9.X (tried also 1.9.1, no luck), TortoiseSVN as well as command line throw the following error after trying to checkout or commit a Working Directory on a network share:
Commit failed (details follow):
Can't move 'U:\1-Administration\Management\.svn\tmp\svn-ADD80C28' to
'U:\1-Administration\Management\.svn\pristine\b7\b7c3f06170d83d3aac6b4489b78c4c8509c70ed6.svn-base':
Access is denied.
(full discussion on TSVN mailing list here: https://groups.google.com/forum/#!topic/tortoisesvn/Goi-Ay3BV6U )
It seems to be a Subversion issue, not a TortoiseSVN one, since command line acts exactly the same as TSVN: everything fine with local paths, issues with network drives. Sometimes, trying more and more, the checkout/commit succeeds also on network share, but it is a random occurrence.
Any clue? As you can see in the suggested link, it seems that everyone who works on network drive has the same problem: something has been changed or broken in 1.9.X release about it? I didn’t find anything about it.
Thank you in advance
Daniele P.
Zapi Spa - Società per Azioni con Unico Socio - Via Parma, 59, 42028 Poviglio (RE) - Tel. +39 0522 960050 - Fax +39 0522 960259 - E-mail: zapi@zapispa.it <ma...@zapispa.it> - web site: www.zapispa.it <http://www.zapispa.it> - Capitale Sociale € 2.582.500,00 - Iscrizione Registro Imprese di Reggio Emilia n. 00794070342 - C.F. 00794070342 - P. IVA 01184200358
AVVERTENZA: Ai sensi del Codice Privacy DLGS n.196/03 si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio Le fosse pervenuto per errore La preghiamo di eliminarlo senza copiarlo, di non inoltrarlo a terzi e di darcene tempestiva comunicazione. According to Privacy Code DLGS n.196/03 we state that the information contained in this message are contidential and for the exclusive use of the receveir. In case the message reached you by mistake, we kindly ask you to delete it without copying it, not to send it to others and to inform us about it immediately.
Rispetta l'ambiente: non stampare questa e-mail se non ti è necessario. Please consider your environmental responsability before printing this e-mail.