We are running VisualSVN Server 1.5.2 on Windows 2003. One of my users
reports the following problem.
When he (or anyone else) tries to commit a change from his machine, it
fails due to a permission problem. From another machine, using the same
credentials, the commit succeeds. So far, it looks like there is some
issue his machine configuration. He tried checking out a pristine working
copy - committing changes using that working copy also failed.
So we tried capturing the network traffic from a failing commit and from a
successful commit from another client. The traces seem similar
<rant>(except for the fact that he is using two different versions of
Tortoise on the 2 clients even though I asked him to use the SVN command
line client - the joys of off-shoring)</rant> until the following request
which results in
HTTP/1.1 403 Forbidden.
From the other client (the one that works), the analogous request is
HTTP/1.1 201 Created.
We just started using Subversion, and I know nothing about the details of
the protocol, so I don't know if the different GUID's in the two requests
are a sign of an issue, or if that is expected, i.e., client or
Is the fact that the GUID-like portions of the URL's differ significant?
Is the fact that apparently he used different casing (MonitorWebsites vs.
monitorwebsites) potentially problematic?
What else can I try to try to diagnose this problem?
This message contains information that may be confidential and
proprietary. Unless you are the intended recipient (or authorized to
receive this message for the intended recipient), you may not use, copy,
disseminate or disclose to anyone the message or any information contained
in the message. If you have received the message in error, please advise
the sender by reply e-mail, and delete the message immediately. Thank you
Received on 2008-08-07 18:47:17 CEST