We are currently evaluating Agent SVN as an alternative to our current SourceControl-System used with PB Classic.
The repository is on a linux server, accessed via http, authentication enabled.
Putting all objects in the repository using PBs "Add to source control" worked fine, no problems. When trying to checkout an object it failed, the debug log shows this error:
Agent SVN Info: svn: warning: W215004 No more credentials or we tried to many times
Agent SVN Info: Authentication failed
Locking the same file with Turtoise works: it asks for authentication information and than locks the file.
Neither the Agent configuration nor the SCC-Plugin in PB ever asks for authentication infos, what could go wrong here?
Thanks
Dirk
Checkout problem with Powerbuilderm authentication error
Hi Dirk,
There is code in Agent SVN to prompt for authentication so it is strange that it you are not seeing a prompt
Could you delete the current log file, replcate the error and then e-mail me the new log file that gets create (NOTE: only user details go into the log, no passwords are logged).
I'm fairly confident that log file will reveal the answer.
FYI, the way Agent SVN handles authentication is also changing so worse comes to worse what I will do is send you the latest beta with the new authentication code.
Cheers Jussi
Neither the Agent configuration nor the SCC-Plugin in PB ever asks for authentication infos, what could go wrong here?
There is code in Agent SVN to prompt for authentication so it is strange that it you are not seeing a prompt

Could you delete the current log file, replcate the error and then e-mail me the new log file that gets create (NOTE: only user details go into the log, no passwords are logged).
I'm fairly confident that log file will reveal the answer.
Locking the same file with Tortoise works: it asks for authentication information and then locks the file.
FYI, the way Agent SVN handles authentication is also changing so worse comes to worse what I will do is send you the latest beta with the new authentication code.
Cheers Jussi
This issue should now be fixed in the latest version of the Agent SVN software found here: http://www.zeusedit.com/agent/download.html
Cheers Jussi
Cheers Jussi