Checkout Error: Lock Request failed

( SVNSCC , Codewright, 1.3.0.1, Windows 2000 )

Type: Public Status:Closed Created: 07 Apr 06 04:00 Updated: 16 Jun 06 06:00

--> Igor Pushkov (admin) at 16 Jun 06 06:00 writes

Several news for you:
1. We checked plug-in 1.3.1rc and it seems to use user name in lower case
as in Tortoise.

2. Latest mod_auth_sspi (1.0.4) has two new options wich completely
eliminate this issue on server side:
SSPIOmitDomain On/Off # removes domain name from user identity
SSPIUsernameCase lower/upper #makes user name always either lower case or
upper

--> achim (user) at 19 May 06 05:00 writes

I tested it with Visual Studio 2005 today with the same results. My
username is a lowercase username like "qwertz" but if i lock or checkout
something and check the repository with TortoiseSVN, i always see "QWERTZ"
as lock owner.

--> achim (user) at 15 May 06 05:00 writes

The problem is always there and i get many problems with it. TortoiseSVN
and the SVN plugin do not work together anymore because locks are created
with DOMAIN\USERNAME by the plugin but TortoiseSVN needs DOMAIN\username.
So i get problems if i want to checkin files with TortoiseSVN which are
locked with the SVN plugin. It is unimportant in my opinion that this
problem has something to do with a library you use. Fact is that the plugin
do not work like expected. The NEON library is available as open source, so
it is possible to fix this bug.

--> Igor Pushkov (admin) at 12 Apr 06 04:00 writes

Well, we donot do anything with this... I think all issues is arounf new
NEON library which has minor issues with new SVN. I'll put accepted status
to your ticket untill we find the solution for problem.

--> achim (user) at 10 Apr 06 04:00 writes

I definitly found the problem. We use an access file (AuthzSVNAccessFile)
for subversion users which consists of case sensitiv usernames. I don't
know who or why but the plugin converts the usernames always to uppercase.
Normally we use a compination of upper and lowercase usernames and im sure
that i configured the plugin with the right username (DOMAIN\username).
Please check if the plugin converts the username somewhere.
All works perfectly if i add both combinations of the username
(DOMAIN\username and DOMAIN\USERNAME) to the authorization file.

--> Igor Pushkov (admin) at 08 Apr 06 04:00 writes

The plug-in version 1.3.0.1 should not have any physical problems with
authorization since it uses SVN client code directly. So this must be
some kind of logical problem. Let's try to find it...
0. This situation looks like your server either allow read-only access
for anonymous users or you authenticate with wrong user name who have
read-only access, but not have write access (lock requires write
access)
1. According to rules of SCC API plug-in receives and tries to use the
user name passed by IDE. This use name can be configured in VS.NET ide
_before_ opening project or accessing any other functions of source
control. So be sure that right user name placed here.
2. If all above will not work for you try to switch off authentication
caching for plug-in. This can be done at the plug-in options window,
page SVN options. Disabling auth cache plug-in should ask each time
user name and password (not convenient but will find where we need to
search source of issue)

--> achim (user) at 07 Apr 06 04:00 writes

May be i found something. I analyzed the log files of our apache server and
found the following line:

Access denied: 'DOMAIN\\USERNAME' LOCK PROJECTNAME:/trunk/Sources/test.c

The username has only uppercase letters. The problem is now that our
usernames normally have the following layout: "DOMAIN\username". The domain
consists of uppercase letters and the username of lowercase letters.

--> achim (user) at 07 Apr 06 04:00 writes

Again the username: "DOMAIN\USERNAME"

--> achim (user) at 07 Apr 06 04:00 writes

I get always the following error if i try to checkout a file:

COM.SvnClient.Error, HRESULT=0x80020009
Lock request failed: 401 Authorisation Required (...)

The file has the attribute "needs-lock". I do not have any problems with
TortoiseSVN. I can lock and checkin the file and anything else. With the
SVNSCC Proxy i get always this error if i try to checkout. History and
compare works fine with the plugin! Can it be, that the lock function do
not understand usernames with backslashes? We use a domain authorisation
and the usernames looks like: "\".

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Checkout Error: Lock Request failed