Dear Support Team,
I have encountered below exception while
executing cleanup command of SVN.
Following are the steps:
1. Tried to execute update command, which give the missing error for
some file, which is actually available on server as well as on end M/C.
2. Then, to
Hi,
when I try to cp or mv a directory within a repository, I get (after
several seconds of waiting with no cpu/disk activity) the following
error.
rj@sol$ svn cp .test_equ_simple/ /opt/PetaMem/PMLS/active/data/lexica/c/e/s/
svn: E200033: Another process is blocking the working copy database,
o
On Fri, Jun 13, 2014 at 9:28 AM, Richard Jelinek wrote:
> Hi,
>
> when I try to cp or mv a directory within a repository, I get (after
> several seconds of waiting with no cpu/disk activity) the following
> error.
>
>
>
> rj@sol$ svn cp .test_equ_simple/ /opt/PetaMem/PMLS/active/data/lexica/c/e/s/
Hi,
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
(users@subversion.apache.org)
with as much information as possible about what
you were trying to do.
But p
On Fri, Jun 13, 2014 at 10:15 AM, wrote:
>
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> (users@subversion.apache.org)
>
I see you read this part.
> with as much informat
Hi,
On Fri, Jun 13, 2014 at 09:41:27AM -0400, Andy Levy wrote:
> Does anything in the error message pertain to your setup? IOW, do you
> have other processes running that may be locking the file (antivirus
> is notorious for this)? Is it a local filesystem, or mounted from the
> network? If local,
Are there any symlinks involved in these paths that you passed to Subversion?
Bert
Sent from Windows Mail
From: Richard Jelinek
Sent: Friday, June 13, 2014 4:45 PM
To: Andy Levy
Cc: users@subversion.apache.org
Hi,
On Fri, Jun 13, 2014 at 09:41:27AM -0400, Andy Levy wr
Thanks Johan. The solution ended up being to reset the password in the domain.
The odd thing is the user account was fine, not locked and the password was
not expired. It had been approximately 90 days since we set the password, so I
assume something is going on with the domain settings or us
