svnsync E175002: Could not execute PROPPATCH

Dear Team:  I am trying to sync a repo from primary server to secondary server. During svn sync, I have got the below error:  Copied properties for revision 2327.  svnsync: E175002: Could not execute PROPPATCH.  Visual SVN Server 2.7.13, installed on Windows Server 2007 SP2 operating system. Two servers are the same. The 2327 revision seems to be normal（no log）:   My command: svnsync init https://10.7.0.88:8443/svn/SW https://10.7.0.84:8443/svn/SW --non-interactive --allow-non-empty svnsync sync https://10.7.0.88:8443/svn/SW https://10.7.0.84:8443/svn/SW --non-interactive  How to resolve?  Thank you so much! 

Last updated 4 years ago

Last updated

To me it looks like Rev 2327 is ok. What does Rev 2328 look like? Anything strange?  FWIW, those are both very old versions (Windows Server 2007 and Visual SVN Server 2.7)...

To me it looks like Rev 2327 is ok. What does Rev 2328 look like? Anything strange?  FWIW, those are both very old versions (Windows Server 2007 and Visual ------------My reply here------------ Because the previous post I can not commit, I commit here.  The Rev 2328 looks like(see attachment):  It seems that this Rev is not good, I mentioned similar questions in my previous post： https://www.svnforum.org/forum/opensource-subversion-forums/apache-subversion-1-8-support/80344-using-the-pre-commit-hook-to-restrict-the-size-of-the-submitted-file-failed

Last updated

Repository corruption is a serious matter. The other thread you point to includes the same possible solution: dump up to the bad revision and then dump from 1 after it until the end of the repo. Then load the 1st then the 2nd.  But doing this again is silly until/unless you fix the underlying cause of the corruption. Certain non-server hardware being used for server-duty can be the cause - for instance non-ECC memory can enable corruption pretty trivially. Given the age of the operating and Visual-SVN I'd say it's had a lovely run but it's time is done.