Lars, I was going to suggest exactly what you seemed to have figured out the space in the path to the svn executable maybe an issue. I would try reinstalling your SVN and when prompted to name the directory instead of taking the deault path remove the space. At the very least this will remove one more possible impediment. The problems with the SVN everyone was mentioning is manifested by the fac tyou would get a malformed xml error during the log step, this is not the issue you are seeing.
On Dec 4, 10:34 pm, Lars Zeb <[EMAIL PROTECTED]> wrote: > This box is running svnserve and VisualSVN. I used <executable> to > point to the VisualSVN directory. > > If I run the following command, it errors out, however the second > version with the command surrounded with double-quotes is OK. > > C:\Program Files\VisualSVN Server\bin\svn.exe > loghttps://server:8443/svn/MyProject/ > -r "{2008-12-05T01:35:30Z}:{2008-12-05T03:03:17Z}" --verbose --xml -- > username user --password password --non-interactive --no-auth-cache > > "C:\Program Files\VisualSVN Server\bin\svn.exe" > loghttps://server:8443/svn/MyProject/ > -r "{2008-12-05T01:35:30Z}:{2008-12-05T03:03:17Z}" --verbose --xml -- > username user --password password --non-interactive --no-auth-cache > > I am running ccnet 1.4.1.3833, which I think was a nightly build from > a few days ago. I saw the warning about svn, but I can't remember > where. Perhaps its at the ThoughtWorks site, which is down. > > I am running the ccnet console, not the service. I am running as > Administrator, which has full rights. > > If I have the following in ccnet.config: > <executable>"C:\windows\Microsoft.NET\Framework\v3.5\MSBuild.exe"</ > executable> > > ccnet.log echos: > Unable to execute file [C:\Program Files\VisualSVN Server\bin\svn.exe] > whether I place double-quotes or not. Something's weird.
