oh one more thing - if you upgraded as well there is a problem with
buildArgs - write them as a single row with no space in front of first
and after last arg...

On Feb 15, 11:43 am, östen petersson <[email protected]>
wrote:
> Hi Tom
> I had similar problems (among many) when I went from xp to 2008 rc2.
> I use visualsvn so I am not sure my solution works for you though:
> As far as I could discern the ccnet log in to svn didn't work.
> To make the connection between the servers I had to do it manually
> first in cmd
> and accept some security warning. Then it worked.
>
> (it been 6 months so I don´t rememeber the exact problem, my collegue
> might have documented it though - will check)
>
> //ö
>
> On Feb 9, 12:06 am, Thomas Wheeler <[email protected]> wrote:
>
> > I am migrating our build machine from a virtual machine running
> > Windows Server 2003 32bit with IIS6 to Windows Server 2008 R2 64bit
> > with IIS7.5
>
> > Everything went great and I am able to do a svn up on my project
> > directory with no problems with this dedicated build user that we have
> > created on the domain.   However if I go into CruiseControl and force
> > a continuous build on that very same project directory I get this
> > error:
>
> > Error Message: ThoughtWorks.CruiseControl.Core.CruiseControlException:
> > Source control operation failed: svn: OPTIONS of 'http://indyscc/svn/
> > projects/myproject/trunk': authorization failed: Could not
> > authenticate to server: ignored NTLM challenge, rejected Basic
> > challenge (http://indyscc)
> > . Process command: C:\Program Files (x86)\CollabNet Subversion Server
> > \svn.exe loghttp://indyscc/svn/projects//myproject/trunk-r
> > "{2011-02-08T22:58:25Z}:{2011-02-08T22:59:26Z}" --verbose --xml --no-
> > auth-cache --non-interactive
> >    at
> > ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.Execute(ProcessInfo
> > processInfo)
> >    at
> > ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.GetModifications(IIntegrationResult
> > from, IIntegrationResult to)
> >    at
> > ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModificationsWithLogging(ISourceControl
> > sc, IIntegrationResult from, IIntegrationResult to)
> >    at
> > ThoughtWorks.CruiseControl.Core.Sourcecontrol.QuietPeriod.GetModifications(ISourceControl
> > sourceControl, IIntegrationResult lastBuild, IIntegrationResult
> > thisBuild)
> >    at
> > ThoughtWorks.CruiseControl.Core.IntegrationRunner.GetModifications(IIntegrationResult
> > from, IIntegrationResult to)
> >    at
> > ThoughtWorks.CruiseControl.Core.IntegrationRunner.Integrate(IntegrationRequest
> > request)
>
> > I'm not sure what to do.  I originally copied over my project
> > directories along with state from the old server to this server, but
> > then I cleared all of that out and cleared my tortoise svn
> > Authentication data (not sure if that matter because tortoise
> > shouldn't have anything to do with this) and then did a fresh checkout
> > from svn of the project using the correct Domain\build username that i
> > created.   I also have the CCnet Server service running under this
> > Domain\build username and this user has been set up as a local admin
> > on the build box.    Can someone please help me out?   It's been years
> > since I had to create a new build server and I feel like i'm missing a
> > critical step.   Is there a setting in CruiseControl to use a
> > specified user or is Windows 2008 r2 completely different when it
> > comes to security using NTLM now?    Thanks!
>
> > Tom
>
>

Reply via email to